TCP/IP Collection Example
This section introduces a workflow example using a TCP/IP collection agent in MediationZone. A workflow containing a TCP/IP collection agent can be set up to send responses back to the source from which the incoming data was received, with an APL agent (Analysis or Aggregation) included in the workflow.
The section is divided into two parts: one explains how to set up a single TCP/IP connection, and the other describes the configuration for multiple TCP/IP connections.
Agent | Description/purpose |
|---|---|
TCP_IP_1 (Collection) | Collects incoming data from external TCP/IP sources and inserts it into the workflow. Supports both single and multiple TCP/IP connections, and enables response routing back to the source as configured. |
Analysis | Validates incoming records, determines the appropriate response (such as returning anum or a sequence number), and routes valid UDRs for further processing. Handles response logic for both single and multiple connection scenarios. |
Encoder | Converts processed UDRs into the required output format for downstream systems or external delivery, using the defined Ultra format mappings. |
Inter_Workflow | Facilitates routing of UDRs between different workflows, enabling integration and data exchange across multiple workflow streams within MediationZone. |
To illustrate how such a workflow is defined, an example is provided where an incoming UDR is validated, resulting in either the field ‘anum’ or a sequence number being sent back as a reply message to the source. Depending on whether one or several TCP/IP connections are allowed, the format of the reply message sent from the Analysis agent differs:
Number of Connections Allowed | Description |
|---|---|
Single Connection | The reply is sent as a bytearray. |
Multiple Connections | The reply is sent as a UDR extended with the built-in TCP/IPUDR format, with the reply message (bytearray) inserted into the response field. |
Note!
To keep the examples as simple as possible, the valid records are not processed. Usually, no reply is sent back until the UDRs are fully validated and processed. These examples focus only on the response handling.