IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Securing communications
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure TLS/SSL communication between Dashboard Application Services Hub and an HTTP server used for load balancing multiple portal servers
To use HTTPS in a dashboard environment that is using a HTTP server to load balance multiple Tivoli Enterprise Portal Servers, you must configure TLS/SSL communication from the Dashboard Application Services Hub to the HTTP server.
Roadmap
In order to use HTTPS and its security encryption features, complete the following tasks in the roadmap.
Roadmap to configure TLS/SSL communication between Dashboard Application Services Hub and a HTTP server used for load balancing multiple Tivoli Enterprise Portal Server
Step Description Where to find information 1 Determine if you want to use the self-signed certificate that came with the HTTP server or request a certificate that is signed by a certificate authority. If you do not want to use a self-signed certificate, see your HTTP server documentation to determine how to request a certificate.
If you are using the IBM HTTP Server, see "Securing IBM HTTP Server" in the WebSphere Application Server Information Center.
If you create a new key database to contain a certificate from a certificate authority, you must add the portal server signer certificates into the new database. See steps 2 and 3 of the roadmap in Configure TLS/SSL communication between the load balancing HTTP Server and each portal server's local HTTP server.
2 Export the HTTP server’s public signer certificate. See your HTTP server documentation to determine how to perform this step. If you are using the IBM HTTP Server, see Export the IBM HTTP Server signer certificate.
3 Add the HTTP public signer certificate to Dashboard Application Services Hub. Add the HTTP Server certificate to the Dashboard Application Services Hub trust store
- Export the IBM HTTP Server signer certificate
On the computer system where the load balancing IBM HTTP Server is installed, export the public signer certificate from the key database using the iKeyman graphical interface.
- Add the HTTP Server certificate to the Dashboard Application Services Hub trust store
Add the public signer certificate used by the HTTP Server that is load balancing multiple portal servers to the Dashboard Application Services Hub WebSphere trust store to configure TLS/SSL communication.
Parent topic:
Securing communications