A number of configuration steps must be carried out on the PAS-X MES system side to integrate with system:inmation successfully.
The following preparation sections should be read and followed according to the needs of your system:
Look up the System ID and System Name defined in the prerequisites section.
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 the General Authorization) and it must be granted write access to the Message Processor object that is created below the Message Broker object, otherwise the communication will not work.
|Token Authentication is used for the Web API but the token itself is not configurable within the PAS-X system. The PAS-X system just needs the correct username and password. Then the token will be used by the Authentication Endpoint (see below).|
For the correct communication PAS-X has to know the URLs of four endpoints:
Endpoint to Shopfloor: this endpoint can be taken directly from the
Message BrokerEndpoint to Shopfloor property
Endpoint to MES: this endpoint can be taken directly from the
Message BrokerEndpoint to MES property
Authentication Endpoint: this endpoint is used to request authentication ticket, prior to the communication
The Delete Endpoint: this endpoint removes messages from the outgoing message queue; the delete 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 the "sf_to_mes" part replaced with "sf_to_mes_delete".
The Authentication Endpoint has always the same relative URL, the only thing that changes is the hostname/IP address and the port of the Web API:
Username and Password must be configured according to the Profile/User defined (see above section on Profile/User definition).
|Depending on the configuration of the Web-API regarding encryption, define the endpoints as either unencrypted http:<….> or encrypted https:<…> endpoints.|
Once the preparation steps described above have been carried out, the PASX2MSI adaptor can be configured. To do this, please follow the manufacturer instructions provided by Körber/Werum in the "PASX2MSI Adapter MSI – System Manual" regarding the setup of a Web Service adapter.
During this process the MsiSystem section should be configured as follows: - MsiSystemName as described in the prerequisites section - MsiSystemId as described in the prerequisites section - The ExternalIdentifier is given the value "MsiSystemId"
In the Connection Tab, the other endpoint information which you collected earlier is set:
AuthenticationURL: enter the system’s Authentication Endpoint here
GetMessageURL: enter the system’s "to MES" endpoint here
SendAcknowledgeForGet: this must be true
AcknowledgeForGetRequestUrl: enter the system’s “Delete“ endpoint here
PostMessageUrl: enter the system’s "to Shopfloor" endpoint here
Username and Password: as defined earlier
If it is required for some -yet unknwon- reason, to use the GetMessageURL without using Acknowledgement, then this is also possible. In this case 'SendAcknowledgeForGet' must be set to false in the Adaptor Setup and the GetMessageURL must be extended by the query parameter '&autoack=true'. This will automatically acknowledge each message during the a GET call to the GetMEssageURL.