In some circumstances, it may be useful to have both SINGLEPOINT and SINGLEPOINTTEST connected to the same Operations Sentinel server. This would permit a certain amount of automation and alarm testing to be done without having an additional Operations Sentinel server. This is illustrated in Figure 1–4.
For this testing setup, the MCP host is configured as two different hosts in the Operations Sentinel configurations. For example, the connection through SINGLEPOINT might be called ROSE1 and the connection through SINGLEPOINTTEST might be called ROSE1TEST. Both ROSE1 and ROSE1TEST could appear in the same Operations Sentinel configuration, or they might only appear in separate configurations. Each would have its own log files, and the automation rules in the SP-AMS database would distinguish between them by their configured host names.
An Operations Sentinel configuration that includes both connections should define the MCP host service name to be spo_mcp for the connection to SINGLEPOINT and spo_mcp2 for the connection to SINGLEPOINTTEST, as shown in Figure 1–5.
