IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Securing communications > Configure TLS/SSL communication between Dashboard Application Services Hub and an HTTP server used for load balancing multiple portal servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
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.
Copy the public signer certificate that was exported from the load balancing HTTP server to the computer system where Dashboard Application Services Hub is installed.
Procedure
- Log into the Dashboard Application Services Hub WebSphere Administrative Console.
- Enter the following URL in your Internet Explorer or Firefox browser: https://hostname:16311/ibm/console.
If your environment was configured with a port number other than the default, enter that number instead. The default path to the server is /ibm/console. However, this path is configurable, and might differ from the default in your environment.
- Enter the Dashboard Application Services Hub administrative user ID and password then click Go.
The user ID must be assigned the administrator and iscadmins roles.
- In the Console Settings area click on WebSphere Administrative Console and then click the Launch WebSphere administrative console button.
- Select Security → SSL certificate and key management.
- In the Related Items area, click the Key stores and certificates link and in the table click the NodeDefaultTrustStore link.
- In the Additional Properties area, click the Signer certificates link and in the page that is displayed, click Add.
- Enter a unique alias name. For example, TEPS_LOAD_BALANCE_SERVER.
- Enter the file location of the HTTP server public signer certificate.
- Ensure the Data type selection matches the format of the certificate that you exported from the HTTP server.
- Click OK, then Save.
Results
The certificates are now setup for communication between the Dashboard Application Services Hub server and HTTP server used to load balance multiple portal servers.
Parent topic:
Configure TLS/SSL communication between Dashboard Application Services Hub and an HTTP server used for load balancing multiple portal servers