Table B-1 shows the configuration requirements for the Operations Sentinel server and the interface software.
Table B.1. Configuration Requirements
| Configuration Data for Operations Sentinel Server | Operations Sentinel Server Configuration Requirements | MCP System Configuration Requirements | Configuration Data for Operations Sentinel Interface |
|---|---|---|---|
| Hosts file entry: network-address host-name host-name must match name in Operations Sentinel configuration. | Update hosts file to include MCP system network address | ||
| Services file entry: service-name port-number/spo_msg Default service-name is spo_mcp. Default port-number is 10301. | Update services file to include assigned MCP TCP port (socket) and service name. Only necessary if values are used. | Define socket name for MCP TCP port interface connection. | DEFAULT_SOCKET statement in configuration file. Default socket is 10301 for production instance of MCP Interface, and 10302 for test instance. |
| Key attributes of an MCP system defined in Operations Sentinel configuration: host-name network-name service-name host-name and network-name match hosts file. service-name must match services file. | Define MCP system using Operations Sentinel Console. | ||
| SP-AMS database messages: ”SINGLE POINT AMS AUTOMATION STARTED USING DATABASE db-name FOR SYSTEM host-id.” and “TIMEOUT WAITING FOR SP-AMS USERCODE/PASSWORD.” Action: PASSWORD %usercode/password | Define SP-AMS pattern for AUTOMATION START message and appropriate usercode/password response message to enable port logon. Do the same for TIMEOUT WAITING message. | Establish port logon usercode in MCP USERDATAFILE. - - - - - - - - - - - Usercode must be privileged and system user (unless overridden by option in configuration file). | See configuration file statement “USE_PRIVILEGED_SYSTEM_ USERCODE_ON_SP_AMS_ PORT {TRUE|FALSE}” Default is TRUE. |