IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with Tivoli Monitoring components in a Microsoft Cluster Server environment > Set up the portal server in a Microsoft Cluster Server > Install and set up the portal server in the cluster

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Install and set up the portal server in clusternode1


Before installing or configuring any components in a Microsoft Cluster environment, all other components which are already added to resource groups on this cluster should be offline. This precautionary measure prevents conflicts between the cluster management tool and the Tivoli Monitoring MTEMS tool. Also, you should shut down clusternode2 to prevent the Microsoft Cluster Server moving the resource to clusternode2 during installation. Ensure that basic cluster resources are online while installing components.

Before installing the portal server, complete the following prerequisite steps:

Install the portal server by completing the following steps:

  1. Start the installation using the setup.exe command.

  2. On the feature tree, choose only TEPS and TEPD (Eclipse Help Server will be chosen automatically).

    Figure 1. Selecting the features that setup will install

  3. Click Next and enter the host name of the machine where the TEP Server resides.

    Figure 2. Selecting the features that setup will install

  4. See Set up basic cluster resources for specifying the installation drive and location.

  5. Start the setup and make sure that the installation directory is on the shared disk R.

  6. Select the required Application Support.

  7. Configure the virtual host name as the host name of the portal server.

  8. Assuming the hub monitoring server is clustered, specify the virtual host name of the hub monitoring server as the monitoring server host name.

  9. For the portal server database access, specify the DSN (TEPS2) and the user (ITMUser) just created.

  10. The installation now uses the existing database and user ID to continue.

  11. Finish the installation as usual.

Configure the portal server to use the virtual host name .

  1. Make sure Tivoli Enterprise Portal Server and Tivoli Enterprise Portal Server Extensions are stopped.

  2. Back up your configuration data %CANDLE_HOME%\CNPSJ\profiles directory.

  3. Run the cmd shell.

  4. Change the current directory to %CANDLE_HOME%\CNPSJ\scripts

  5. Run updateTEPSEHostname.bat <old_hostname> <new_hostname>.

    Under <old_hostname> substitute the current host name, do not include domain name.

    Under <new_hostname> substitute the valid virtual host name for the Tivoli Enterprise Portal Server cluster.

  6. If the operation is successful, 'BUILD SUCCESSFUL' is displayed.

  7. Configure the portal server interface and URL such that the portal clients can connect to the portal server on its the virtual host name . On the Manage Tivoli Enterprise Monitoring Services GUI, select portal server and then:

    • Advanced->Configure TEPS Interfaces

    • Click Edit on CNPS and type in the portal server virtual host name. in this case IVTCS020.

    Figure 3. Editing the portal server virtual host name

  8. The second configuration is for the communication between the portal server and the rest of the Tivoli Monitoring infrastructure, including the monitoring server.

    • Right-click the portal server, select Advanced, and then Set Network Interface. Set the network interface also to the virtual host name, (IVTCS020).

    • This setting creates an environment variable for the portal server, so it does not take effect until the computer is restarted. Also, this setting affects every IBM Tivoli Monitoring component that is installed on the same computer (node).

  9. Start the portal server.

  10. Configure a Tivoli Enterprise Portal Console to connect to this portal server virtual host name.

  11. Start the Console and make sure the Console to portal server communication is working.

  12. As a last step of the portal server configuration on the cluster, set the portal server service to manual startup.

In some cases, the portal server environment entries might not be displayed correctly in the registry, especially the entries for the authorization key and the DSN.

When the portal server entries are not displayed correctly, the startup of the portal server fails. If you encounter this problem, complete the following steps, based on Microsoft Windows-specific behavior.

  1. Check this key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KFW\CNPS\KFWSRV\
    Environ ment\KFW_AUTHORIZATION_KEY
    It might reflect: @Authorizationkey@
    But it should be: AABA-AAAA-ACDI-AFgA

    The registry replication entries might not be identical to the ones in this document.

  2. Also check this key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Candle\KFW\CNPS\KFWSRV\
    Environ ment\KFW_DSN
    It might be: @ODBCDSN@
    But it should be: TEPS2

    The registry replication entries might not be identical to the ones in this document.

  3. Correct the keys, start the tool Manage Tivoli Enterprise Services, right-click the TEPS, and select:

    Advanced-> Utilities-> Build TEPS Database

    Then select DB2 and follow the few steps to configure the parameters again as you did during the installation.

  4. Start the portal server.

  5. Open a command prompt and change the directory to R:\IBM\ITM\CNPS on the shared disk.

    1. Run the Buildpresentation.bat command.

  6. Restart the portal server.


Parent topic:

Install and set up the portal server in the cluster

+

Search Tips   |   Advanced Search