Configuring secure connections

You can configure secure connections for IBM® Sterling Control Center Monitor. These connections can be configured in either a high availability environment or a non-high availability environment.

The following graphic shows the secure connections that can be configured for interacting with IBM Sterling Control Center Monitor and the connections that cannot be secured:

The following secure connections can be configured for use with IBM Sterling Control Center Monitor in either a high availability or non-high availability environment:

  • A secure connection between the IBM Sterling Control Center Monitor engine and an IBM Sterling Control Center Monitor console. This secure connection uses Secure Sockets Layer (SSL) or Transport Layer Security (TLS).
  • A secure connection between the browser and the IBM Sterling Control Center Monitor web server that is used to display the launch page and the web console. This secure connection uses SSL or TLS.
  • A secure connection between the IBM Sterling Control Center Monitor engine and the database server. This secure connection uses SSL or TLS.
  • A secure connection between the IBM Sterling Control Center Monitor engine and a managed Sterling Connect:Direct® server or Sterling B2B Integrator SOA SSL Server Adapter. This secure connection uses SSL or TLS.
Tip: Use the information that is recorded on the HTTPS worksheet to complete the configuration procedures.

The IBM Sterling Control Center Monitor engine uses the same keystore and truststore files for all of these secure connections.

In a high availability environment, every event processor's keystore certificate must be trusted by your other event processors in the cluster. In every event processor's truststore, you must include the certificate. You can use the same keystore and truststore files for every event processor in your high availability environment. You might receive a browser security warning when you access the web console on an event processor where the common name does not match the host name that you are connecting to.