Configuring

Once you have installed Tivoli Integrated Portal, you can configure it to operate in a variety of ways, for example, you can enable load balancing and employ a central user repository.

Central user registry
As a post-installation task you can configure a central user registry for user management and authentication. You can configure an LDAP server or Tivoli Netcool/OMNIbus ObjectServer registry (or both).
Single sign-on
The single sign-on (SSO) capability in Tivoli® products means that you can log on to one Tivoli application and then launch to other Tivoli Web-based or Web-enabled applications without having to re-enter your user credentials.
Load balancing
You can setup a load balancing cluster of portal nodes with identical configurations to evenly distribute user sessions. Load balancing is ideal for Tivoli Integrated Portal installations with a large user population. When a node within a cluster fails, new user sessions are directed to other active nodes.
Configuring Tivoli Access Manager in Tivoli Integrated Portal
You can configure Tivoli Integrated Portal to use Tivoli Access Manager WebSEAL Version 6.1 to manage authentication.
Protecting the vault key file
To keep the encryption key for the administrator password secure, establish strict read-only access to the vault key file.
Configuring access for HTTP and HTTPS
By default, the application server requires HTTPS (Hypertext Transfer Protocol Secure) access. If you want some users to be able to log in and use the console with no encryption of transferred data, including user ID and password, configure the environment to support both HTTP and HTTPS modes.
Enabling FIPS on the application server
Tivoli Integrated Portal encryption algorithms on the application server use Federal Information Processing Standard (FIPS) approved cryptographic providers regardless of whether FIPS is enabled for the application server. However, you can configure the application server to use Federal Information Processing Standard Java Secure Socket Extension files.
Configuring the LPTA token timeout value
You can configure the Lightweight Third Party Authentication (LTPA) token timeout value for Tivoli Integrated Portal in the WebSphere Application Server console.
Configuring CMS to use a remote database
The Context Menu Service (CMS) is a component of Tivoli Integrated Portal and it can be configured to use a remote database, which can be used by product to share information outside of the Tivoli Integrated Portal environment.
Charting
Administering charting involves assigning user IDs to roles, editing the general properties such as to specify the refresh interval, configuring another ITM Web Service, and configuring for localized charts.
Configuring SSO between Charting and Tivoli Monitoring
The instructions below describe how to configure IBM Tivoli Monitoring and Charting for single sign on (SSO) using the ITMWebService. At the bottom are also instructions for how to configure Tivoli Integrated Portal to communicate with a remote Tivoli Monitoring Web Service, which only works in an SSO environment.