Enterprise Integration 2017 (Version 6.0)

Материал из archestra.info
Перейти к: навигация, поиск

Enterprise Integration 2017 (Version 6.0) Readme

Enterprise Integration 2017 (Version 6.0) Readme

Last revision: Friday, September 7, 2018

In This Document

About This Readme

About This Release

System Requirements

Product Compatibility

Upgrading from a Previous Version

Resolved Issues

Known Issues

Enterprise Integration Documentation

About This Readme

This document contains important information about Enterprise Integration 2017 (version 6.0). This Readme documents the system requirements, known issues, resolved issues, and changes, if any, to the Enterprise Integration user documentation.

Readme files from previous releases of Enterprise Integration are posted to the Product Hub page of the Knowledge and Support Center. Once on the Product Hub page, you can use the filter Enterprise Integration (the product name used on the GCS website) to list the Enterprise Integration documents, which include the Readme files. To access the Knowledge and Support Center, start at the Contact Page and click through the Customer Support links.

About This Release

Enterprise Integration 2017 includes the following new features and enhancements.

  • Sample (Generate)
  • Sample (Update)
  • Licensing API updated to match MES 2017 and System Platform 2017

System Requirements

This section describes the operating system and Microsoft SQL Server requirements to install the Enterprise Integration 2017 software.

Operating System Requirements

The operating systems that are supported and can be installed on computers that run Enterprise Integration 2017 are:

  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows 8.1
  • Windows 10

SQL Server Requirements

The SQL Server versions that are supported and can be installed on computers that run Enterprise Integration 2017 are:

  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014
  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2017

Product Compatibility

Enterprise Integration 2017 is compatible and can co-exist with the following products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component

Version

Compatibility

Co-existence

System Platform

2014 R2, 2017

N/A

Y

InBatch™

2014 R3

N/A

Y

QI Analyst™

8.0 SP4

N/A

Y

Intelligence

2014 R3, 2017

N/A

Y

Manufacturing Execution System (MES)

2014 R3

N

N

MES

2017

Y

Y

Skelta™ BPM

2017, 2017 R2

N/A

Y

Recipe Manager Plus

2014 R3, 2017

N/A

Y

Upgrading from a Previous Version

Enterprise Integration 2017 supports upgrading from:

  • Wonderware Enterprise Integrator 2014 R3
  • Wonderware Enterprise Integrator 2014 R2
  • Wonderware Enterprise Integrator 2014 R2 SP1
  • Wonderware Enterprise Integrator 2014 R2 SP2
  • Wonderware Enterprise Integrator 2012

Resolved Issues

This section describes the important issues that were resolved in Enterprise Integration 2017.

  • Fixed a presentation issue with the long Status Messages in the Message Log.
  • Fixed an issue with the OUT direction MESTable location types for the following MESTable Location Context Table selections:
    • Customer
    • Data Log 48
    • SO
    • SO Line
    • Utilization Reason/Entity Links
    • Utilization States
  • Fixed an issue when an inbound location had a transfer to an outbound location, and the message had been processed with the most recent processing having an error on the outbound side.
  • Fixed an issue with using custom SQL calls due to the deprecated functionality of GetDSBySQL. The API call GetDSBySQL can only be used for single SELECT statements in SQL. Correct functionality now uses GetDSBySP where needed.
    • Direct Query: Must start with SELECT and be a single select statement. For example:

      SELECT TOP 1 * FROM MesTable

    • Stored Procedure: Must start with EXEC followed by the stored procedure name and parameter values. Do not use the name value notation for the parameters. Note that all stored procedure parameters must have a corresponding value in the SQL command, even if the stored procedure treats the parameter as optional. For example:

      EXEC SomeStoredProcedure firstParamValue, secondParamValue

  • Fixed an issue with using Enterprise Integration MESTable Out due to the functionality of GetAttrId for different attribute groups. If the attr table had at least two attributes with the same attr_desc for different attr_grps, the attr_id was not properly assigned. Now, specific GetAttrId functions are created for each attribute group.
  • Fixed an issue for which Location names with special characters would break when accessing them in the web browser. Location names can only include letters, numbers, spaces, and underscores as valid characters. Upon upgrading, special characters in Location names are replaced with an underscore character.
  • Fixed an issue with MSMQ Inbound Locations being unable to map to Folder Outbound Locations.

Known Issues

There are currently no important known issues in Enterprise Integration 2017.

Enterprise Integration Documentation

The Enterprise Integration 2017 documentation set includes the following:

  • Enterprise Integration Installation Guide
  • Enterprise Integration Plug-in User Guide (available on the Global Customer Support website)
  • Enterprise Integration User Guide (included with the installation)

Copyright © 2018 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us

The Schneider Electric industrial software business and AVEVA have merged to trade as AVEVA Group plc, a UK listed company. The Schneider Electric and Life is On trademarks are owned by Schneider Electric and are being licensed to AVEVA by Schneider Electric.