

External Socket Agent API › Socket Agent › How the Socket Agent Works
More information:
External Agent Socket API Messages
How the Socket Agent Works
The Socket Agent:
- Socket Agent processes messages asynchronously.
- 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.
- The Application passes the request to, and receives responses from the Socket Agent in the External Agent API Message format.
- 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.
- External Agent Socket API requests are passed to, and responses received from, the External Agent API, when the entire message has been received.
- Socket Agent communications can be configured using Registry Settings.
- 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.
Copyright © 2014 CA.
All rights reserved.
 
|
|