The interface software is started from the Transaction Server for ClearPath MCP. After it is started, it prepares to receive a connection request from a valid Operations Sentinel server.

When a user starts Operations Sentinel Console on an Operations Sentinel workstation, it causes the Operations Sentinel services (daemons) to use an established connection or to attempt a new connection with each MCP host defined in the configuration selected by the user. After a connection is made, SP-AMS sends a usercode and password that establish the Operations Sentinel server as an authorized client to the interface software. When the interface software confirms that the connection is good, it starts sending message data from the MCP host system to the Operations Sentinel server. The message data is processed by SP-AMS according to the active database, and a response is initiated.

Configurable Login Delay to Discourage Hackers

The interface software can temporarily stop listening to the subports used for connection to Operations Sentinel, if the nature of a failed connection attempt suggests that a hacker may be attempting an intrusion. Although it stops listening for new connections, it still processes all information from established connections. The administrator can configure this delay from 0 to 3600 seconds. The default is 300. See Section 3.