Technical background

Gateway technical context

South Side

Various South Side communication patterns are available for connecting stations (machines and devices) to the Nexeed Gateway module (Communication types and protocols).

North Side

The message type for North Side communication is OpConXml if communication takes place via Nexeed DirectDataLink.

The communication protocol for the Nexeed Gateway and Nexeed DirectDataLink modules is a TCP socket.

Gateway configurator

After starting, the Gateway service attempts to retrieve the last active configuration of the connector based on the saved metadata.

If the metadata does not exist or information about the last active configuration is missing, the connectors are not initialized. If the connectors are not initialized, the configuration must be saved and activated via the REST endpoints of the configuration controller via the Nexeed Gateway Controller (NGC).

For details on setting up the connector configurations, see the documentation for the Nexeed Gateway Controller .

The configuration controller provides a number of endpoints for managing configurations for different clients.

Overview of the communication process

Sequence

Description

1

The station sends a request message to the Nexeed Gateway module.

2

The Nexeed Gateway module translates the request message into the OpConXml message format.

3

The request message is sent to the Nexeed DirectDataLink module via TCP socket.

4

The Nexeed DirectDataLink module forwards the request message to the Nexeed IAS service.

5

The Nexeed DirectDataLink module receives a response message from the Nexeed IAS service and forwards it to the Nexeed Gateway module.

6

The Nexeed Gateway module translates the response message from the OpConXml message format into the message format required by the station.

7

The Nexeed Gateway module forwards the translated response message to the station.

User Manual | Nexeed Global Production Overview