Install Model Driven MES content packages in Work Tasks

Locate the files that were extracted from the installation Zip file.

For a description of the extracted folder and file contents, see Extracted installation files folder structure.

Open the Enterprise Console Repository list by entering the following URL in a web browser: https://host.fully.qualified.domain.name:portnumber/EnterpriseConsole

To log in to Enterprise Console, select the Active Directory link.

Note: When opening Enterprise Console, unless you already have an active session, you will be prompted to log in to obtain an AVEVA Identity Manager (AIM) access token.

On the Enterprise Console menu, click Package, and then click Manage Package.

In the Manage Packages action bar, click New, and then click Import.

The Import Package dialog appears.

Click Choose File, and browse to the location of the packages in the extracted installation files.

Select one of the application packages for import:

• MES_PKG_Inventory_Management_versionnumber_x64.awsPKG

• MES_PKG_Job_Management_versionnumber_x64.awsPKG

• MES_PKG_Quality_Management_versionnumber_x64.awsPKG

• MES_PKG_Wo_Po_Management_versionnumber_x64.awsPKG

  Note: You can import only one package at a time, so you have to repeat the same steps starting from step 5 for each package. Perform all the steps first for the first package, and then start from step 5 for the next package.

Click Import.

If this is the initial installation of the package, the message that the package is successfully imported appears. Go to step 12.

If you are updating an installed package with a later version of the package, you are prompted to save it as the next major version.

To continue with importing the latest version of the package, click OK.

The message that the package is successfully imported appears.

Click Close.

If this is the initial installation of the package, the package is listed on the Manage Packages page as not installed.

If you are updating a package that is already installed, it replaces the previous version of the package in the list on the Manage Packages page. Its status will still appear as installed. However, if you right-click the package and click Show All versions, the version you just imported is listed as not installed.

(Optional) If you are updating the package from a previous version, you might want to edit the package to change the artifact install options. See Model Driven MES package update considerations.

On the Manage Packages page, select the package, and then select Install.

The Runtime Initialization Values page appears.

Enter the required runtime initialization settings.

MES Web API

The base address for accessing the MES Web API using the following syntax: https://<machine name>/mesmw/

The following fields are only required if you are using the MES Connector:

[Optional] Unique Environment Name

The Unique Environment Name (UEN) for the MES Workflow repository connection. The UEN is configured using the Workflow Connector Configuration utility.

The UEN is specified on the Workflow Server and Repository Details page of the Workflow Connector Configuration utility, and also shown on the Manage Workflow Repositories page. For information about configuring the MES Connector, see the Work Tasks Extension and Connector for MES Installation Guide.

[Optional] Middleware Machine Name

The machine name of the server where the MES middleware is installed. The middleware machine name MUST be specified if existing workflows use the Wait for MES Event Activity.

Note: localhost is not a valid entry. Also, enter only the host name. Do not enter the host's fully qualified domain name.

Click Finish.

The package pre-install validation starts.

When the pre-install validation is complete, the Pre-install Validation and Configuration page appears.

Review the package validation logs (at the lower left of the page) and address any errors or warnings before proceeding.

You can ignore warnings related to folders that already exist as some folders are shared between different MES Model-Driven application content packages.

Wait for all of the artifacts to be loaded before proceeding to the next step. The Validation is in progress message at the upper right will no longer appear and the Install Package button will become available.

Click Install Package.

When the installation is complete, the message that the package was successfully installed appears.

Click Close.

The Package Installation page lists the imported contents.

Review the list of imported contents to verify that all package components were installed, and then click Close.

If this is the initial installation of the package, the package is listed on the Manage Packages page as installed.

If you are updating a package that is already installed, it is listed as updated.

Do the following to make sure that the target environment reflects all of the package installation changes:

• Reset IIS (Internet Information Service). Use the IIS Management tool or run the following command from the admin command prompt: IISRESET.

• Clear you web browser cache (refer to your individual browser documentation for specific instructions).

Check that you can open the imported forms:

• For Inventory Management: On the Enterprise Console menu select Operations, Supervisor, and then Inventory Management.

• For Job Management: On the Enterprise Console menu select Operations, Operator, and then Job Management.

• For Quality Management: On the Enterprise Console menu select Operations, Operator, and then Quality Management.

• For Work Order Management: On the Enterprise Console menu select Operations, Supervisor, and then WO/PO Management.