Previous Topic: Socket AgentNext Topic: Policy Engine Hub


More information:

External Agent Socket API Messages

How the Socket Agent Works

The Socket Agent:

  1. Socket Agent processes messages asynchronously.
  2. The Socket Agent runs under the Policy Engine Hub. The agent is, however self-contained, enabling it to run also, if necessary, under the Policy Engine.
  3. The Application passes the request to, and receives responses from the Socket Agent in the External Agent API Message format.
  4. Applications send messages to the Socket Agent using TCP/IP. The Socket Agent acts as a TCPIP Server. The application may be running on a different Operating System, such as UNIX. The Socket Agent uses the Wgn common receiver classes. The Socket Agent always sends the response back on the same TCP/IP port that it was received on.
  5. External Agent Socket API requests are passed to, and responses received from, the External Agent API, when the entire message has been received.
  6. Socket Agent communications can be configured using Registry Settings.
  7. An External Agent Requestor is required to assist the user in formatting the External Agent messages. The External Agent Requestor is not covered by this document.