IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Additional Tivoli Enterprise Portal configurations
This chapter discusses how to perform advanced configuration of Tivoli Enterprise Portal components.
It also includes illustrations of firewall scenarios that can help in defining the Tivoli Enterprise Portal Server interface.
- Connecting the Tivoli Enterprise Portal Server on Windows to a different monitoring server
When reconfiguring the portal server on Windows for a different Tivoli Enterprise Monitoring Server, a pop-up window is displayed asking if a snapshot of the current Tivoli Enterprise Portal Server data should first be taken.
- Use SSL between the portal server and the client
You can choose to encrypt all communication between the portal server and portal client.
- Reverting from the IBM HTTP Server to the internal web server
The IBM HTTP Server is the default web server used for communication between the portal client and server. This provides increased scalability, performance, and reliability for portal clients. The switch to IBM HTTP Server occurs automatically with no action required on your part.
- Configure HTTP communication between the portal client and server
HTTP communication can be used between the portal client and server without the need for the CORBA communication protocol. HTTP communication requires the use of the IBM HTTP Server that is installed automatically with the portal server.