IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Upgrade from a previous installation > Plan your upgrade > Prerequisites for IBM Tivoli Monitoring V6.3
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Tivoli Business Service Manager and Tivoli Enterprise Portal Server integration over SSL
For releases before V.6.2.3, HTTP was only used to transfer static content such as help files from the embedded HTTP server in IBM Tivoli Monitoring, or for single sign-on using the embedded HTTP server in the WAS component. As of version 6.2.3 and higher, the Tivoli Enterprise Portal Server installation contains a required IBM HTTP Server front end for all HTTP and HTTPS traffic.
The IBM HTTP Server provides increased scalability, performance, and unifies HTTP(S) access to the Tivoli Enterprise Portal Server to a single pair of ports.
By default, the IBM HTTP Server is assigned ownership of the HTTP and HTTPS ports 15200 and 15201. These ports are currently used by the embedded HTTP server in the Tivoli Enterprise Portal Server. This ensures that existing Tivoli Enterprise Portal Server clients, configured for single sign-on, migrate to the new architecture. However, with the use of HTTPS you must now consider the SSL/TLS certificate of the server.
A trusted signing authority must sign the IBM Tivoli Monitoring Certificate. You must import the certificate of that signing authority into any web applications that are accessing IBM Tivoli Monitoring data from the Tivoli Enterprise Portal Server using HTTPS. If this certificate is missing, and the Tivoli Enterprise Portal Server clients attempt to connect to port 15201 using SSL/TLS, the error message no trusted certificate found is displayed.
The following applications are affected:
- The Tivoli Business Service Manager Charts services for IBM Tivoli Monitoring, that is provided with Tivoli Business Service Manager 4.2.2 and higher.
- IBM Tivoli Monitoring policy-based data fetcher, that is provided with Tivoli Business Service Manager 4.2 and higher.
- Tivoli Integrated Portal when it is configured to use the IBM Tivoli Monitoring charting web service.
- Ensuring web applications connecting to the embedded HTTP server in the portal server using SSL continue to work after upgrading to V6.3
Before you upgrade to V6.3, you must generate a new pair of keys and sign the IBM Tivoli Monitoring Certificate with the key of your signer if you do not want to use the default self-signed certificates installed by IBM Tivoli Monitoring. You then import the public key certificate of your signer into the truststores of your client applications, before the upgrade to V6.3.
Parent topic:
Prerequisites for IBM Tivoli Monitoring V6.3