IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Create clusters with monitoring components in a System Automation for Multiplatforms environment > Install the portal server on the Tivoli System Automation for Multiplatforms cluster

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Install and set up the portal server on clusternode1


To install and set up the portal server on clusternode1, complete the following procedure:


Procedure

  1. Check which cluster node is active (online):

    lsrg –m

  2. If you installed other Tivoli Monitoring components to the shared file system, use the same installation path for the portal server.

  3. Change the cluster's mode to Manual:

    samctrl –M T

  4. On the active node, install the portal server, according to IBM Tivoli Monitoring: Installation and Setup Guide.

    If you are installing the portal server on Linux on zSeries in 64- bit mode, you need to run the install script from a 31-bit session. To open a 31-bit session, run:

    s390 sh

  5. Configure the portal server interface and URL such that the portal clients can connect to portal server on its virtual host name. Add the following line to the <CANDLEHOME>/config/cq.ini file: 

      KFW_INTERFACE_cnps_HOST=<virtualhostname>

    where <virtualhostname> is the virtual host name of the portal server.

  6. Use one of the following 2 methods to configure the portal server:

    • To invoke a GUI application, use <CANDLEHOME>/bin/itmcmd manage, which requires a connection to an X Server.

    • To invoke a text application, use <CANDLEHOME>/bin/itmcmd config –A cq, which prompts you for the configuration values.

    If you are configuring the portal server on Linux on zSeries in 64-bit mode, you need to run the command from a 31-bit session. To open a 31-bit session, run:

    s390 sh

  7. Configure the monitoring server host name so that it is the same as the virtual host name of the monitoring server (assuming the hub monitoring server is clustered).

    The monitoring server host name is the TEMS Hostname field on the GUI TEMS Connection tab, and the CMS Host Name field in the text application.

  8. 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 located in the $CANDLEHOME/<architecture>/iw/profiles directory.

    3. Run UNIX terminal.

    4. Change the current directory to $CANDLEHOME/<architecture>/iw/scripts

    5. Run sh updateTEPSEHostname.sh <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.

      If you repeat the updateTEPSEHostname script execution, make sure to use correct old_hostname. For example, the following sequence it correct:

      • updateTEPSEHostname.bat h1 crocodile, the ewas host name was changed to "crocodile".

      • updateTEPSEHostname.bat crocodile hippi, as old host name, use "crocodile" or the script will have no effect.

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

    7. Set the Primary Network Name to the virtual host name of the portal server. This configuration is necessary for the communication between the portal server and the rest of the Tivoli Monitoring infrastructure, including the monitoring server.

      The Primary Network Name in the Network Name field, which is available after selecting Specify Optional Primary Network on the GUI TEMS Connection tab, and the Optional Primary Network Name field in the text application.

  9. Configure the portal server to have access to the database which you created before (see Create the Database for Portal server/Tivoli Data Warehouse on node1).

  10. Change the cluster's mode to Automatic:

    samctrl –M F

  11. Disable the automatic startup of the portal server:

    1. Edit the /shareddisk/ITM/config/kcirunas.cfg file.

    2. Add the following section after the <agent> line by including the following syntax:

      <productCode>cq</productCode>
      <default>
      <autoStart>no</autoStart>
      </default>

    3. Save the file.

    4. As user root, run...

        /shareddisk/ITM/bin/UpdateAutoRun.sh

    The path to the kcirunas.cfg file and the UpdateAutoRun.sh command (/shareddisk/ITM) might be different on your system.


Parent topic:

Install the portal server on the Tivoli System Automation for Multiplatforms cluster

+

Search Tips   |   Advanced Search