IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Monitoring Startup Center > Deployment procedure

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Distributed installation

A distributed installation is recommended for medium and large environments that are monitoring more than 500 systems. A distributed installation offers you the most expansion possibilities as your environment grows. The distributed installation is the ideal configuration if you are looking to set up a robust foundation of IBM Tivoli Monitoring.


With a distributed installation, a predefined set of components are installed on a set of distributed machines. You can install the following components with a distributed installation:

The TEPS and WAREHOUS databases are created automatically by the Startup Center tool. The itmuser account should have a profile that sets up the DB2 environment correctly before running the Startup Center tool.

To perform a distributed installation using the Tivoli Monitoring Startup Center:

  1. Launch the Startup Center.

  2. Click Next on the Welcome screen.

  3. Click Accept to accept the license agreement.

  4. Select the Distributed radio button and click Next.

    Figure 1. Tivoli Monitoring Startup Center Installation Type window

  5. Your environment can now be scanned to discover machines within the IP range that you specify. You can also click Add System to specify a system host name or IP address. If you specify a machine using the Add System option you must ensure that the machine is online. Click Next to continue.

    Figure 2. Tivoli Monitoring Startup Center Discover Machines window

    For some systems, the Startup Center might not identify the type of operating system. These systems are listed under the Unknown Operating System category. See the Troubleshooting Guide.

  6. The Startup Center has discovered the machines in your environment. The components to be installed are represented in a graph. Now specify the components to install on a target machine. Select a machine from the list and drag it to the component that you want to install on that machine. You can also press the Enter key and select the component from the pop-up dialog box. The Tivoli Enterprise Portal Server and the Warehouse Proxy Agent are assigned to the same machine. To change a machine assignment, select a different machine from the list and drag it to a component. A green check mark indicates a completed machine assignment for the component. Repeat this action for each component in the diagram. You can use the same target machine for more than one component. The Tivoli Enterprise Portal Server, hub Tivoli Enterprise Monitoring Server, and Warehouse Proxy Agent must have a machine assignment before you can proceed. The Tivoli Enterprise Portal Desktop and remote Tivoli Enterprise Monitoring Server are optional components. Click Next to continue.

    Figure 3. Tivoli Monitoring Startup Center Assign Server Machines window

    1. If you assign a component to an unknown operating system, you are prompted to specify your operating system.

    2. By default, when you assign a machine to the Tivoli Enterprise Portal Server, the Startup Center assigns the Warehouse Proxy Agent to the same machine. Likewise, when you assign a machine to the Warehouse Proxy Agent, the Startup Center also assigns the Tivoli Enterprise Portal Server.

    3. You cannot assign a hub monitoring server and remote monitoring server on the same system.

    4. You can change a machine assignment but you cannot remove an assignment. To change any of the machine assignments, select another machine from the list and drag it to the component.

  7. The Deploy OS Agents screen is displayed. Select the check box of each machine that you want to install an OS Agent on. Enter a path for the target installation directory or accept the default. You must select at least one machine before continuing.

    The installation of OS Agents is not supported on Windows Itanium systems. Click Next to continue.

  8. Now you must provide the machine login credentials that are required to remotely access target systems. Select each machine in the list and enter the System user ID and System password in the fields provided. For information on non-root user credentials, see Non-root user support. You can select multiple machines if they share the same login credentials and enter the information once. All credentials must be validated before you can click Next.

    1. If you encounter a problem at this step, it is probably RXA related. For information about RXA, see Remote Execution and Access.

    2. The Temporary Directory must have sufficient space to accommodate the transferred installation image.

    3. In the Turkish locale, a user ID containing a lowercase "i" causes machine login credentials to fail. You can change to a locale other than Turkish, or else use only capital 'I' letters in user IDs, for example AdmInIstrator instead of Administrator.

  9. The Input Server Options screen is displayed. The following components must be configured:

    • Tivoli Enterprise Monitoring Server: Enter the installation path for the monitoring server and click Next.

    • Remote Tivoli Enterprise Monitoring Server: Enter the installation path for the remote monitoring server and click Next.

    • Tivoli Enterprise Portal Server:

      1. Enter the installation path, password, and database type for the Tivoli Enterprise Portal Server. The database types that are currently supported are embedded Derby and DB2. If you select DB2 as your database type, you must enter the corresponding database information in the fields provided.

      2. Click Next. The database connection is automatically validated.

    • Tivoli Enterprise Portal Server Desktop: Enter the installation path for the Tivoli Enterprise Portal Server Desktop and click Next.

    • Warehouse Proxy Agent: Enter a valid installation path along with the corresponding database information and click Next.

      At this point, an error might be displayed regarding your connection settings. The RXA tool is used to establish a connection with a remote computer. You must ensure that your target system meets the requirements to establish remote execution and access. For more information see Remote Execution and Access.

      If the Startup Center fails to create a warehouse database or database user, see the for more information.

  10. You can place all of your installation images on one directory and click Select Image Repository to browse to the directory. You can also click the ellipsis button at the end of the Path field to browse to each installation image individually. The directory path containing installation images cannot contain commas or spaces. Click Next to continue.

    The installation images must be extracted before you set the image location.

  11. The Pre-Installation Summary screen is displayed. Any installation errors are displayed here. Review the summary information on this screen and click Back to take corrective action, or click Next to continue.

    1. An error message is displayed on the Pre-Installation Summary screen if there is not enough space in the installation directory or the temp directory. Make sure that the directories you specified have enough free space.

    2. If the Preinstallation Summary shows that a connection could not be established to the specified system, it might be because of a slow connection. Click Back to go to the previous page and click Next to try again. If the connection problem continues to exist, try installing at a time when there is less traffic on your network.

  12. The Deployment screen displays the deployment status of each component and a progress indicator. When the deployment of each component has completed, click Next to display the Post Installation Summary page.

    Figure 4. Tivoli Monitoring Startup Center Post Installation Summary window


Parent topic:

Deployment procedure

+

Search Tips   |   Advanced Search