PAS-X Configuration

The PAS-X MES must be configured to integrate with system:inmation successfully. This tutorial is designed to assist with this configuration.

Preparation

The following sections should be read and followed according to the needs of your system:

System ID and System Name

Look up the System ID and System Name defined in the prerequisites section.

Profile/User Definition

For a simple test setup and a standard installation, the system owner profile can be used for authentication. However, this is not recommended for a production or qualification system. If a dedicated Profile will be used for this connection, configure the Web API accordingly first.

This Profile must be granted access to the system using the Web API (by selecting "External API" in General Authorization). It must also be granted write access to the Message Processor object created below the Message Broker object; otherwise the communication will be unsuccessful.

Token Authentication is used for the Web API but the token itself is not configurable within the PAS-X system. The PAS-X system only requires the correct username and password. The token is used by the Authentication Endpoint (see below).

Endpoint Configuration

For successful communication, PAS-X requires the URLs of four endpoints:

  1. Endpoint to Shopfloor: this endpoint can be taken directly from the Message Broker Endpoint to Shopfloor property

  2. Endpoint to MES: this endpoint can be taken directly from the Message Broker Endpoint to MES property

  3. Authentication Endpoint: this endpoint is used to request the authentication ticket, prior to the communication

  4. Delete Endpoint: this endpoint removes messages from the outgoing message queue; the delete endpoint shall be called as acknowledgement of message reception from PAS-X

The URL of the Delete Endpoint can be derived from the Endpoint to MES (see above) with "sf_to_mes" replaced by "sf_to_mes_delete".

The URL of the Authentication Endpoint is determined by the hostname/IP address and the port of the Web API:

The Username and Password must be configured according to the defined Profile/User (see above section on Profile/User definition).

Depending on the configuration of the Web API encryption, define the endpoints as either unencrypted http:<….> or encrypted https:<…>.

Adaptor Setup

After carrying out the steps above, the PASX2MSI adaptor can be configured. To do this, please follow the manufacturer instructions provided by Körber/Werum in the "PASX2MSI Adaptor MSI – System Manual" regarding the setup of a Web Service adaptor.

During this process the MsiSystem Tab should be configured as follows:

MsiSystem Configuration
Figure 1. MsiSystem Configuration

In the Connection Tab, the endpoint information from the earlier configuration is used:

  • AuthenticateUrl: enter the system’s "Authentication Endpoint" here

  • GetMessageUrl: enter the system’s "to MES" endpoint here

  • SendAcknowledgeForGet: this must be set to true

  • AcknowledgeForGetRequestUrl: enter the system’s “Delete Endpoint" here

  • PostMessageUrl: enter the system’s "to Shopfloor" endpoint here

  • Username and Password: as previously defined

Connection Configuration
Figure 2. Connection Configuration

Get Message without Acknowledgement

It is possible to use the GetMessageUrl without using Acknowledgement if required.

In this case, 'SendAcknowledgeForGet' should be set to False in the Adaptor Setup and the GetMessageUrl needs to be extended by the query parameter '&autoack=true'. This will automatically acknowledge each message during the GET call to the GetMessageUrl.