Configuring IBM Control Center Monitor to monitor Sterling Secure Proxy

There are two ways to monitor Sterling Secure Proxy servers, via MQ and OSA.
To monitor status and activity of the Sterling Secure Proxy server via OSA, refer Enabling OSA support via Secure Proxy .
To monitor the status and activity of the Sterling Secure Proxy server via MQ, you need to add the server to IBM® Control Center Monitor.

About this task

To set up and configure Sterling Secure Proxy in IBM Control Center Monitor via MQ:

Procedure

  1. Log on to the IBM Control Center Monitorweb console.
  2. To add the Sterling Secure Proxy server to the IBM Control Center Monitor server list, click Servers > Add Server.
  3. Follow the steps in Adding a server to configure the Sterling Secure Proxy server. Define the following JMS configuration properties with information that is provided by the WebSphere® MQ administrator:
    • User ID
    • Password
    • Host
    • Port
    • Topic - The topic Sterling Secure Proxy CM is publishing to.
    • Subscriber - This must be unique for this IBM Control Center Monitor instance.
    • Queue Manager
    • Channel Name - The default channel that is used is SYSTEM.DEF.SVRCONN
    Important:
    • The Heartbeat Interval value must be equal to or greater than the heartbeat value that is set for Sterling Secure Proxy as described in Configuring the Sterling Secure Proxy Configuration Manager. This defines how long IBM Control Center Monitor waits for a heartbeat event before it assumes the Sterling Secure Proxy Configuration Manager (CM) is down.
    • The Monitor Rest Time defines how frequently IBM Control Center Monitor checks WebSphere MQ for messages.
    • To avoid inaccurate events that indicate a monitored Sterling Secure Proxy server is down:
      • The Monitor Rest Time needs to be smaller than the Heartbeat Interval
      • The value for the Heartbeat Interval needs to double the heartbeat value for the Sterling Secure Proxy server