IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install the Tivoli Enterprise Portal Server

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Windows: Installing the portal server

Complete the steps in this section to install the Tivoli Enterprise Portal Server and portal client on a Windows computer.


The installation procedure for a portal server on Windows includes steps for configuring the connection between the portal server and the following components:

  1. If you have not set up the Tivoli Data Warehouse, complete this procedure but click No when asked if you want to configure the connection to the data warehouse. You can reconfigure the connection after you set up the warehouse. See Step 20 for more information.

  2. The Windows userid you use when creating the portal server database must be a local ID with Administrator privileges. In other words, it cannot be a domain ID.

  1. Launch the installation wizard by double-clicking the setup.exe file in the IBM Tivoli Monitoring Base DVD or DVD image.

  2. Click Next on the Welcome window.

  3. Read and accept the software license agreement by clicking Accept.

  4. Specify the directory where you want to install the portal server software and accompanying files. The default location is C:\IBM\ITM. Click Next

    If you specify an incorrect directory name, you will receive the following error:

    The IBM Tivoli Monitoring installation directory cannot exceed 80 characters
    or contain non-ASCII, special or double-byte characters.
    The directory name can contain only these characters:
    "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ _\:0123456789()~-./".

  5. Type an encryption key to use. This key should be the same as what was used during the installation of the hub monitoring server to which this portal server will connect. Click Next and then OK to confirm the encryption key.

  6. On the Select Features window, select Tivoli Enterprise Portal Server from the list of components to install.

    When you select the Tivoli Enterprise Portal Server check box, all of the check boxes in the attached subtree are automatically selected. The support check boxes in the subtree are for installing application support files for base monitoring agents to the monitoring server. (The base monitoring agents are included with the base IBM Tivoli Monitoring installation package.) It is best to leave all of the support check boxes selected so you do not need to reconfigure application support as new agent types are added to your environment. For detailed information about application support, see Install and enable application support.

    1. If you have purchased monitoring agents that run on z/OS, but have not purchased IBM Tivoli Monitoring as a separate product, expand the Tivoli Enterprise Portal Server node. Clear all check boxes in the subtree except the check boxes labeled Tivoli Enterprise Portal Server and, optionally, TEC GUI Integration. (See Step 7.a.)

    2. If you are updating an existing installation, all check boxes on the Select Features window reflect your choices during the initial installation. If your installation media contains a newer version of a previously installed component, the component will be upgraded unless you clear the check box for that component.

    3. The Eclipse Help Server is automatically selected when you select the Tivoli Enterprise Portal Server.

  7. Optionally select the following additional components to install:

    1. To view events on the IBM Tivoli Enterprise Console event server through the Tivoli Enterprise Portal, expand Tivoli Enterprise Portal Server and ensure that TEC GUI Integration is selected.

    2. To install a portal desktop client on this computer, select Tivoli Enterprise Portal Desktop Client.

      When you select the Tivoli Enterprise Portal Desktop Client check box, all of the check boxes in the attached subtree are automatically selected. These check boxes are for installing application support files for base monitoring agents to the portal desktop client. Leave these check boxes selected as you did for the portal server in Step 6.

      If you have purchased monitoring agents that run on z/OS, but have not purchased IBM Tivoli Monitoring as a separate product, expand the Tivoli Enterprise Portal Desktop Client node. Clear all check boxes in the subtree except the check boxes labeled Tivoli Enterprise Portal Desktop Client and, optionally, TEC GUI Integration.

  8. Click Next.

  9. If a monitoring server is not installed on this computer, go to Step 10.

    If you are installing the portal server on a computer that already has a monitoring server installed, the Agent Deployment window is displayed.

    The Agent Deployment window lists monitoring agents on this installation image that you can add to the agent depot. The agent depot contains agents that you can deploy to remote computers. For information about how to deploy agents in the agent depot to remote computers, see Deploy monitoring agents across your environment.

    By default, the agent depot is located in directory...

      itm_installdir/CMS/depot

    ...on Windows. To use a different directory, create the directory (if it does not exist) and specify the directory using the DEPOTHOME key in the KBBENV file.

    Select the agents, if any, that you want to add to the agent depot. (You can add agents to the agent depot at a later time by updating your installation.) Click Next.

  10. If no IBM Tivoli Monitoring component has been previously installed on this computer, a window is displayed for you to select a program folder for the Windows Start menu. Select a program folder and click Next. The default program folder name is IBM Tivoli Monitoring.

  11. If you are installing the Tivoli Enterprise Monitoring Server at the same time as the Tivoli Enterprise Portal Server, you are asked to set a sign on password for the Tivoli Enterprise Portal desktop and browser clients.

  12. Review the installation summary details. The summary identifies what you are installing and where you chose to install it. Click Next to start the installation.

    After installation is complete, a configuration window (called the Setup Type window) is displayed.

  13. Clear the check boxes for any components that are already installed and configured (at the current release level) on this computer, unless you want to modify the configuration. (For example, clear the check box for the Tivoli Enterprise Monitoring Server if it has already been installed and configured on this computer.) Click Next to start configuring all selected components.

  14. You are asked to choose the database management system you want to use for your portal server database, Derby, DB2 Database for Linux, UNIX, and Windows, or Microsoft SQL Server, as shown in Figure 1. Note that if a particular Database Type is uninstalled on this computer or if it installed but not at the necessary release level, the radio button is grayed out.

    Figure 1. The Select Database for Tivoli Enterprise Portal window

  15. Configure communications for the Tivoli Enterprise Portal Server:

    1. Select the communications protocol for the connection between the portal server and the hub monitoring server. You can choose from the following protocol options:

      • IP.PIPE

      • IP.SPIPE

      • SNA

      • IP.UDP

      • IP6.PIPE

      • IP6.SPIPE

      • IP6.UDP

      You can select up to six protocols and specify if the connection between the portal server and the hub monitoring server passes through a firewall.

    2. Type the host name of the computer where you are installing the portal server. (The host name of this computer is displayed by default.) Click OK.

    Figure 2. Tivoli Enterprise Portal Server Configuration

  16. Configure communications for the Tivoli Enterprise Portal Server:

    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.

    2. 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.

    3. 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.)

    4. 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.

    5. 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 Using 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.

    6. Click OK.

    Figure 3. Tivoli Enterprise Portal Server Configuration

  17. If you selected Validate User with LDAP in step 16.a, 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 4. LDAP configuration

  18. If you selected Enable Single Sign On in step 16.c 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.

  19. If you selected Enable authorization policies in step 16.f, the Authorization Policy Server Configuration window is displayed. To avoid time-consuming authorization checks across the network, the Tivoli Enterprise Portal Server retrieves its own local copy of the Authorization Policy Server's data store. For the data store retrieval to succeed, the Tivoli Enterprise Portal Server requires several pieces of information about the Authorization Policy Server.

    Figure 5. Authorization Policy Server Configuration

    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 Using 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.

  20. A message is displayed asking if you want to reconfigure the warehouse connection for the portal server.

    Figure 6. Reconfigure warehouse connection information for the portal server

    Do one of the following:

    • Click No if you have not set up a Tivoli Data Warehouse.

      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.

      If you select No, go to Step 27.

    • Click Yes if you have completed the tasks for setting up a Tivoli Data Warehouse and want to configure the connection between the portal server and the Tivoli Data Warehouse database at this time. (You can choose to configure the connection later.) The prerequisite tasks and the information configure the connection for each database type are described in the following steps.

    For additional information about warehouse configuration, press the Help button.

  21. Specify the database type to be used for the Warehouse Proxy data source.

    Figure 7. Warehouse Proxy Database Selection

    If you select Oracle without having installed an Oracle ODBC driver an error message is displayed saying Oracle ODBC driver not installed on this machine and you cannot continue with the configuration. You can obtain Oracle ODBC drivers from the following Web site: http://www.oracle.com/technology/software/tech/windows/odbc/htdocs/utilsoft.html

  22. A window is displayed for you to configure the connection between the portal server and the portal server database (TEPS database). There is check box on the configuration window: The database and the Warehouse Data Source do not exist and should be created by the Installer. If you select this check box the installation program uses the information on this window to automatically perform the following tasks:

    • Create the portal server database.

    • Create a database user for the portal server to use to access the database.

    • Configure the ODBC connection between the portal server and the database.

    Figure 8. Configuration window for the portal server database using DB2 for Linux, UNIX, and Windows
    Figure 8 shows the configuration window for a portal server database using DB2 for Linux, UNIX, and Windows. The configuration window for a Microsoft SQL Server database is similar. The fields on the configuration window are described in the following table:


    Configuration information for the portal server database

    Field DB2 for Linux, UNIX, and Windows default MS SQL default Description
    Data Source Name ITM Warehouse ITM Warehouse Name of the data source.
    Database User ID ITMUser ITMUser Name of the Windows OS user that the portal server will use to access the Tivoli Data Warehouse database.
    Database Password itmpswd1 itmpswd1 Password for the Windows user. If your environment requires complex passwords (passwords that require both alpha and numeric characters), specify a password that complies with these requirements.
    Reenter Password itmpswd1 itmpswd1 Confirm the password by entering it again.

  23. To configure a connection between the portal server and a DB2 for Linux, UNIX, and Windows data warehouse, complete the following steps:

    1. Verify that you have 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.

      • Activated the UNIX listeners on the computer where the warehouse database is located if the warehouse database is installed on UNIX systems.

      • Installed a DB2 for Linux, UNIX, and Windows client on the portal server if the data warehouse is remote and the portal server database does not use DB2 for Linux, UNIX, and Windows.

      • Cataloged the warehouse database on the computer where you are installing the portal server if the warehouse database is remote from the portal server.

      These tasks are described in Tivoli Data Warehouse solution using DB2 for Linux, UNIX, and Windows.

    2. Gather the following information: data source name, database name, database administrator ID and password, warehouse user ID and password. The warehouse user ID is the one declared in the configuration panel of the Warehouse Proxy Agent. This user ID serves as the first part of the name of all the tables created in the Warehouse database. If you do not declare the same user ID when configuring the Tivoli Enterprise Portal server you will not be able to see the Warehouse tables with the portal client even if they exist in the database.

    3. Complete the Configure a Windows portal server (ODBC connection) procedure, starting from Step 4.

    For additional information about these parameters, press the Help button.

  24. To configure a connection between the portal server and a Microsoft SQL Server data warehouse, complete the following steps:

    1. Verify that you have completed the following tasks:

      • Created a warehouse database using Microsoft SQL Server.

      • 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.

      • Installed a Microsoft SQL Server client on the portal server if the data warehouse is remote and the portal server database does not use Microsoft SQL Server.

      • Configured a remote client connection on the computer where you are installing the portal server if the warehouse database is remote from the portal server.

      These tasks are described in Tivoli Data Warehouse solution using Microsoft SQL Server.

    2. Gather the following information: data source name, database name, database administrator ID and password, warehouse user ID and password. The warehouse user ID is the one declared in the configuration panel of the Warehouse Proxy Agent. This user ID serves as the first part of the name of all the tables created in the Warehouse database. If you do not declare the same user ID when configuring the Tivoli Enterprise Portal server you will not be able to see the Warehouse tables with the portal client even if they exist in the database.

    3. Complete the procedure Configure the portal server (ODBC connection), starting from Step 4.

    For additional information about these parameters, press the Help button.

  25. To configure a connection between the portal server and an Oracle data warehouse, complete the following steps:

    1. Verify that you have 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 client on the portal server

      • Created a TNS Service Name on the computer where you are installing the portal server if the warehouse database is remote from the portal server.

      These tasks are described in Tivoli Data Warehouse solution using Oracle.

    2. Gather the following information: the data source name, database name, database administrator ID and password, and the warehouse user ID and password. The warehouse user ID is the one declared in the configuration panel of the Warehouse Proxy Agent. This user ID serves as the first part of the name of all the tables created in the Warehouse database. If you do not declare the same user ID when configuring the Tivoli Enterprise Portal server you will not be able to see the Warehouse tables with the portal client even if they exist in the database.

    3. Complete the procedure Configure a Windows portal server (ODBC connection), starting from Step 4.

    For additional information about these parameters, press the Help button.

  26. Configure the default connector for the Common Event Console.

    Figure 9. Common Event Console Configuration window

    The default 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.

    Click OK to accept the default values or specify values for the following fields, then click OK:

    Enable this connector

    Select Yes to enable the connector to collect and display situation events in the Common Event Console, or No to configure the connector without enabling it. The connector is enabled by default.

    Connector name

    The name that is to be displayed in the Common Event Console for this connector. The default name is ITM1.

    Maximum number of events for this connector

    The maximum number of events that are to be available in the Common Event Console for this connector. The default value is 100 events.

    View closed events

    Select No to display only active events in the Common Event Console for this connector. Select Yes to view both active and closed events. By default, only active events are displayed.

  27. Configure the default communication between any monitoring agents installed on this computer and the hub Tivoli Enterprise Monitoring Server:

    1. Click OK to accept the default communications protocol.

    2. Ensure that the host name and port number of the Tivoli Enterprise Monitoring Server are correct. Click OK.

    For additional information about these parameters, press the Help button.

  28. Click Finish to complete the installation.


Parent topic:

Install the Tivoli Enterprise Portal Server

+

Search Tips   |   Advanced Search