Configuring the Sterling Secure Proxy Configuration Manager
To monitor the status and activity of the Sterling Secure Proxy server, first you need to configure the Sterling Secure Proxy Configuration Manager (CM).
To configure the Sterling Secure Proxy CM:
- Log on to the Sterling Secure Proxy dashboard.
- Click .
- Click New to create a new Java™ message service (JMS) configuration file.
Define the following JMS configuration properties with information that is provided by the WebSphere® MQ administrator:
- User ID
- Topic - The topic needs to be unique for this Sterling Secure Proxy CM.
- Provider Type - The only provider type that is supported for monitoring by IBM® Control Center Monitor is WebSphere MQ.
- Queue Manager
- Channel Name - The default channel that is used is SYSTEM.DEF.SVRCONN
- Click OK.
On the Global tab, update the following settings in the JMS
Queue Management section:
- Select the Enable JMS Queuing for CM check box.
Set JMS queue heartbeat interval.
Important: Note the heartbeat interval because you need this value when you configure IBM Control Center Monitor.
- From the Select JMS connection info drop-down list, select the JMS connection that you have configured.
- On the Global tab, you can also define a Sterling Secure Proxy CM in the SSP CM name field. The CM name identifies the CM when you view events in IBM Control Center Monitor. The CM name appears as Node Name in IBM Control Center Monitor.
- Click Save.
Restart the Sterling Secure Proxy CM to put
the changes into effect.
Important: Do not enable Java message service (JMS) queuing for Sterling Secure Proxy engines. These messages are not supported by IBM Control Center Monitor and are ignored. However, the messages can still impact IBM Control Center Monitor performance.