Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

TABLE OF CONTENTS

Upgrade the MES Client API script libraries

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedAug 26, 2024
  • 2 minute read

The MES Client API Wrapper is delivered in the following files.

  • aaFactMES.aaSLIB

    This file contains the Stateful API Wrapper.

  • aaMES.aaSLIB

    This file contains the Stateless API Wrapper.

You can import these files into Application Server so that the Client API Wrappers can be used in Application Server scripting. Wrapper files from any previous version can be upgraded.

The Application Server does not fully support upgrading the MES Client API (aaFactMES) script library. To upgrade from a previous version, you must manually upgrade the library on the Application Server. You must also ensure that all the deployed objects that are using these scripts are properly upgraded.

To upgrade the MES Client API script library on the Application Server

  1. In the System Platform IDE, undeploy the AppEngine that contains objects that are using an earlier version of the aaFactMES or aaMES script libraries.

    For detailed information on managing objects in the System Platform IDE, refer to the System Platform IDE help.

  2. To import the script library file, do the following:

    1. Click the Galaxy menu, point to Import, and then click Script Function Library.

      The Import Script Function Library dialog box appears.

    2. In the MES application folder, browse to the Controls folder.

      If the MES .NET Controls component was not installed on this node, you can copy the wrapper files from another node on which it was installed to the local MES\Controls folder.

    3. In the File Type list to the right of the File name box, select Script Library Files (*aaSLIB).

    4. Click the aaFactMES.aaSLIB file, and then click Open.

      The script library is imported and a success message appears.

      You must import aaMES.aaSLIB file using the same procedure.

    5. Click OK.

  3. Right-click the corresponding template or object, and then click Validate.

    You must validate all the objects that are using the script library. The derived templates that use the script library must be validated first.

  4. Redeploy the AppEngine and associated objects.

TitleResults for “How to create a CRG?”Also Available in