IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install the Tivoli Enterprise Portal Server > Linux or AIX: Installing the portal server
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure the portal server on Linux or AIX: GUI procedure
To configure the Tivoli Enterprise Portal Server from the Tivoli Enterprise Monitoring Services window on Linux or AIX.
Configure the portal server using either the GUI procedure in this section or the command-line procedure in Configure the portal server on Linux or AIX: command-line procedure.
Either of these configuration procedures accomplishes the following tasks:
- Automatically enables application support on the portal server for the base monitoring agents.
- Includes steps for configuring the connection between the portal server and the following components:
- The hub monitoring server
- The portal server database
- The Tivoli Data Warehouse database
- Tivoli Authorization Policy Server
If you have not set up the Tivoli Data Warehouse, complete this procedure but accept the default values at the prompts for configuring the connection to the data warehouse. You can reconfigure the connection after you set up the warehouse. See Step 9 for more information.
- Log on to the computer where the Tivoli Enterprise Portal Server is installed.
- Start the Manage Tivoli Enterprise Monitoring Services utility:
- Run...
cd install_dir/bin
./itmcmd manage [-h ITMinstall_dir]
...where:
-h (optional) An option used to specify the installation directory. ITMinstall_dir The directory where the portal server is installed. The default installation directory is /opt/IBM/ITM.
The Manage Tivoli Enterprise Monitoring Services window is displayed.
- Right-click Tivoli Enterprise Portal Server and click Configure.
The Common Event Console Configuration window is displayed.
Figure 1. Common Event Console Configuration window
- Click OK to accept the default values for the ITM Connector, or specify your preferred values and then click OK.
The ITM Connector retrieves situation events reported to Tivoli Enterprise Monitoring Servers for display in the Common Event Console. You can configure connectors for other event management systems after you have completed the product installation. For configuration instructions, see the IBM Tivoli Monitoring Administrator's Guide.
The Configure Tivoli Enterprise Portal Server window is displayed.
Figure 2. Registering the portal server with the Tivoli Enterprise Monitoring Server
- On the TEMS Connection page, enter information about the Tivoli Enterprise Monitoring Server to which the Tivoli Enterprise Portal Server connects:
- Enter the host name of the monitoring server in the TEMS Hostname field. (If the field is not active, clear the No TEMS check box.)
- Select the communications protocol that the monitoring server uses from the Protocol drop-down list.
- If you select SNA, enter information in the Net Name, LU Name, and LOG Mode fields.
- If you select ip, ip.pipe, ip.spipe, ip6, ip6.pipe, or ip6.spipe enter the port number of the monitoring server in the Port Number field.
For information about these fields, see Table 1.
- Select Validate user with LDAP if you want the portal server to use an LDAP registry to authenticate users and, optionally, to enable single signon. A best practice is to install and configure the portal server with LDAP validation disabled. After a basic installation of IBM Tivoli Monitoring has been completed and tested, you can reconfigure the portal server and enable LDAP user validation using the instructions in the Enabling user authentication chapter of the IBM Tivoli Monitoring Administrator's Guide.
If you enable LDAP user validation, the LDAP server must be started so that Tivoli Monitoring can verify a connection to the LDAP server. If a connection cannot be established, LDAP user validation will be disabled when the portal server installation completes.
- Select Enable Single Sign On if you enabled LDAP user validation and you want the portal server to use single signon with other applications such as IBM Dashboard Application Services Hub or with other applications that launch the portal client. A best practice is to install and configure the portal server with single signon disabled. After a basic installation of IBM Tivoli Monitoring has been completed and tested, you can reconfigure the portal server and enable single signon using the instructions in the Enabling user authentication chapter of the IBM Tivoli Monitoring Administrator's Guide.
- Click the Agent Parameters tab.
Figure 3. Configuring database connections for the portal server
- Configure the connection between the portal server and the portal server database by entering information in the fields described in the following table:
Configuration information for the Tivoli Enterprise Portal Server database
Field Default value Description DB2 instance name db2inst1 The DB2 for Linux, UNIX, and Windows instance name. Not required if the embedded Derby database is used for the portal server and Oracle is selected for the warehouse database.
DB2 admin ID db2inst1 The DB2 for Linux, UNIX, and Windows administrator ID. The DB2 for Linux, UNIX, and Windows administrator account was created during DB2 for Linux, UNIX, and Windows installation. Not required if the embedded Derby database is used for the portal server and Oracle is selected for the warehouse database.
DB2 admin password (no default) Password for the DB2 for Linux, UNIX, and Windows administrator ID. Not required if the embedded Derby database is used for the portal server and Oracle is selected for the warehouse database.
Re-type DB2 admin password (no default) Password for the DB2 for Linux, UNIX, and Windows administrator ID. Not required if the embedded Derby database is used for the portal server and Oracle is selected for the warehouse database.
TEPS DB2 database name TEPS The Tivoli Enterprise Portal Server database name. Disabled if the embedded Derby database is chosen for the portal server database.
TEPS DB user ID itmuser The login name of the warehouse user that the portal server will use to access the database. Disabled if the embedded Derby database is chosen for the portal server database.
TEPS DB user password (no default) Password for the warehouse user ID. Disabled if the embedded Derby database is chosen for the portal server database.
Re-type TEPS DB user password (no default) Password for the warehouse user ID. Disabled if the embedded Derby database is chosen for the portal server database.
Create TEPS DB user ID if not found? yes This check box is selected by default. If the database login account (user ID and password) that you specified in the preceding fields does not exist, it is created. Disabled if the embedded Derby database is chosen for the portal server database.
- Optionally configure the connection between the portal server and the Tivoli Data Warehouse database.
If you have not set up a Tivoli Data Warehouse, accept the default values for these fields. Follow the instructions later in this book for implementing a Tivoli Data Warehouse solution, beginning with Tivoli Data Warehouse solutions. These instructions will direct you to reconfigure the connection between the portal server and the warehouse database after you have completed all preliminary setup tasks.
The bottom section of the Agent Parameters tab contains fields for configuring the connection between the portal server and a Tivoli Data Warehouse database using DB2 for Linux, UNIX, and Windows or Oracle. (See Figure 4.)
Figure 4. Configuration information for the Tivoli Data Warehouse using an Oracle database
Do one of the following:
- If you have not set up the Tivoli Data Warehouse and do not want to enable the dashboard data provider, click Save to save your settings and close the window.
–OR–
- Configure a connection between the portal server and a DB2 for Linux, UNIX, and Windows warehouse database.
Before you configure the connection, verify that you have already completed the following tasks:
- Created a warehouse database using DB2 for Linux, UNIX, and Windows
- Created a warehouse user on the computer where you created the warehouse database.
The warehouse user is the user account (user ID and password) used by the portal server and other warehousing components to access the warehouse database.
- Cataloged the warehouse database on the computer where you are installing the portal server if the warehouse database is remote from the portal server.
- Activated the UNIX listeners on the computer where the warehouse database is located if the warehouse database is installed on UNIX.
These tasks are described in Tivoli Data Warehouse solution using DB2 for Linux, UNIX, and Windows.
To configure the connection between the portal server and the DB2 for Linux, UNIX, and Windows data warehouse, you will need the name of the warehouse database and the user ID and password of the warehouse user.
To perform the configuration, complete the procedure Configure a Linux or AIX portal server (DB2 for Linux, UNIX and Windows CLI connection), starting from Step 4.
–OR–
- Configure a connection between the portal server and an Oracle warehouse database.
Before you configure the connection, verify that you have already completed the following tasks:
- Created a warehouse database using Oracle
- Created a warehouse user on the computer where you created the warehouse database.
The warehouse user is the user account (user ID and password) used by the portal server and other warehousing components to access the warehouse database.
- Activated the Oracle listener on the computer where the warehouse database is located
- Installed an Oracle JDBC Type 4 driver on the portal server.
These tasks are described in Tivoli Data Warehouse solution using Oracle.
To configure the connection between the portal server and the Oracle data warehouse, you will need:
- The name of the warehouse database and the user ID and password of the warehouse user
- The location, name, and URL of the JDBC driver
To perform the configuration, complete the procedure Configure a Linux or AIX portal server (JDBC connection), starting from Step 4.
- Select the Enable the dashboard data provider check box if Dashboard Application Services Hub will be used with monitoring dashboard applications such as IBM Infrastructure Management Dashboards for Servers, IBM Infrastructure Management Dashboards for VMware, IBM Infrastructure Management Capacity Planner for VMware, IBM Infrastructure Management Capacity Planner for PowerVM, or will be used to create or enable custom dashboard pages for monitoring agents. (See the Preparing your dashboard environment topic in the IBM Tivoli Monitoring Administrator's Guide for details on additional configuration tasks to perform after installation.)
- The domain override value is optional and is only valid when the dashboard data provider is enabled. It changes the default dashboard data provider ID and domain name for authorization policies from itm.<Hub monitoring server name> to itm.<domain override value>. The value may not exceed 124 characters. You should configure a domain override value for these scenarios:
- The Hot Standby high availability feature is being used for the Hub monitoring server. By configuring a domain override value, the dashboard data provider ID and domain name will not change when the portal server is configured to connect to the new acting Hub monitoring server. If you do not configure a domain override value in this scenario, you must reconfigure the connection between the IBM Dashboard Application Services Hub and the dashboard data provider and update any domain specific authorization policies when the portal server is configured to connect to the new acting Hub monitoring server.
- You have multiple Hub monitoring servers that are using a common set of authorization policies for controlling dashboard access and you want to create some domain specific authorization policies. You should specify a domain override value for this scenario if you want to use a more user friendly domain name in your authorization policies than the default value of itm.<Hub monitoring server name>.
- If you modify the domain override after you have configured a connection in your Dashboard Application Services Hub Server to the dashboard data provider then you must delete the connection and re-add it. See the IBM Tivoli Monitoring Administrator's Guide for details on how to configure a dashboard data provider connection. Also if you have created any domain specific authorization policies using the default domain name then you must delete the permissions that use the previous domain name and create new permissions that use the new domain name when you change the domain override value. See the Command Reference for details on the tivcmd CLI commands used to create and work with authorization policies.
Figure 5. Configure Dashboard data provider
- Select the Enable authorization policies check box if you want to use authorization policies to control which managed systems and managed system groups a user can access in monitoring dashboards of the IBM Dashboard Application Services Hub. Once authorization policies are enabled, only authorized users will see data in monitoring dashboards. You should only enable authorization policies if your administrators have already created the initial set of policies for dashboard user access using the Tivoli Authorization Policy Server and tivmd Command Line Interface for Authorization Policy. See the Enabling role-based authorization policies topic in the IBM Tivoli Monitoring Administrator's Guide for details on how to create and work with authorization policies.
If authorization policies have not been created yet, leave this box unchecked. After the authorization policies are ready reconfigure the portal server and enable authorization policies. The fields on the configuration window are described in the following table:
Configuration information for the Authorization Policy Server
Field Description Hostname or IP Address IP Address or fully qualified hostname of the IBM Dashboard Application Services Hub with the Authorization Policy Server. This parameter is required.
Protocol Choose the protocol used to connect to the IBM Dashboard Application Services Hub with the Authorization Policy Server. The default value is HTTPS. This parameter is not required. Port Choose the port used to connect to the IBM Dashboard Application Services Hub with the Authorization Policy Server. The default value is 16311 for the HTTPS protocol and 16310 for the HTTP protocol. The valid port values are from 1 to 65535 inclusive. This parameter is not required.
Polling Interval How often the local data store is updated from the Authorization Policy Server by the policy client running on the portal server. The default is 30 minutes. Valid values are from 5 to 1440 minutes inclusive. This parameter is not required.
Policy Store Expiration Interval If the policy store cannot be updated from the Authorization Policy Server, this interval is the amount of time the local policy store will continue to be utilized from the last update. If the Authorization Policy Server cannot be accessed for the time interval specified by this parameter, all subsequent requests for dashboard data will fail with an authorization error until the Authorization Policy Server is available again. The default is 7 days and 0 hours. The value specified for hours must be in the range of 0-23 hours. If the expiration interval is set to 0 days and 0 hours, the policy store will never expire. This parameter is not required.
User ID Name of the user that the portal server will use to access the IBM Dashboard Application Services Hub with Authorization Policy Server. This user must be added to the PolicyDistributor authorization policy core role or to a custom role that has been granted permission to perform the distribute operation for the role object type. See the Enabling role-based authorization policies chapter in the IBM Tivoli Monitoring Administrator's Guide and the Command Reference for more details on creating authorization policy roles and assigning users to them. This parameter is required.
Password Password for the user. This parameter is required.
Confirm Password Confirm the password by entering it again. This parameter is required. Enter the required information for the Authorization Policy Server in the fields provided and click OK. For more information about the Tivoli Authorization Policy Server and Tivoli Authorization Policy Command-Line Interface, see Install the Tivoli Authorization Policy Server and tivcmd Command-Line Interface for Authorization Policy.
- When you are done configuring the portal server, click Save to save your settings and close the window.
- If you selected Validate User with LDAP in step 5.c, enter the LDAP configuration details in the fields provided and click OK. For more information about these parameters, see Prerequisites for configuring LDAP authentication on the portal server in the IBM Tivoli Monitoring Administrator's Guide.
Figure 6. LDAP Configuration
- If you selected Enable Single Sign On in step 5.d the Single Sign On window is displayed. Enter values for the following fields and click OK:
- Domain name
- Realm name
You can also export or import LTPA keys from other participating single sign-on applications. For more information about configuring these fields and setting up SSO, see Prerequisites for configuring LDAP authentication on the portal server and About single sign-on in the IBM Tivoli Monitoring Administrator's Guide.
Parent topic:
Linux or AIX: Installing the portal server