IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install and enable application support > Configure application support for nonbase monitoring agents > Install application support on monitoring servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Windows: Installing application support on a monitoring server
To install application support for monitoring agents on Windows monitoring servers.
- The monitoring server is stopped during this process.
- If you are running in a Hot Standby environment, shut down your Hot Standby monitoring server before completing this procedure. Restart the Hot Standby monitoring server only after you have seeded the acting hub server.
- In the \WINDOWS subdirectory on the agent product CD (for distributed products) or data files CD (for z/OS products), double-click the setup.exe file to launch the installation.
- Click Next on the Welcome window.
If a monitoring agent is already installed on this computer, select Modify on the Welcome window to indicate that you are updating an existing installation. Click OK on the message telling you about preselected items. Then skip to Step 6.
- On the Install Prerequisites window, read the information about the required levels of IBM Global Security Toolkit (GSKit), and IBM Java.
The check box for each prerequisite is cleared if the correct level of the software is already installed. Otherwise, the check box is selected to indicated that the software is to be installed. If you are installing support from the data files CD for z/OS agent products, you might be prompted to install Oracle Java Runtime Environment (JRE) 1.4.2, even if you have already installed IBM JRE 1.5 with the distributed components of Tivoli Management Services. The two versions can coexist, and installation of application support for some monitoring agents requires Oracle Java 1.4.2. You might also see a message indicating that you can decline the installation of JRE 1.4.2 and that accepting installation of JRE 1.4.2 results in uninstallation of other Java versions. Ignore this message, because you cannot proceed without accepting the installation of Oracle Java 1.4.2, and accepting the installation does not uninstall IBM Java 1.5.
- Click Next. The prerequisite software is installed if necessary.
If the installation program installs IBM GSKit or IBM JRE, you might be prompted to restart the computer when the installation is complete. If so, you receive an abort message with a Severe error heading. This is normal and does not indicate a problem.
If you are prompted to reboot, do the following:
- Click OK on the window prompting you to reboot.
- Click No on the window asking whether you want to view the abort log.
- Restart the computer.
- Restart the installation program.
- Click Accept to accept the license agreement.
- If you see a message regarding installed versions being newer than the agent installation, click OK to ignore this message.
- Select the application support packages that you want to install:
- On the Select Features window, select Tivoli Enterprise Monitoring Server.
- Expand the Tivoli Enterprise Monitoring Server node to display a list of application support packages that you can install on the monitoring server. Initially, all application support packages are selected.
- Clear the check boxes for application support packages that you do not want to install.
If you are updating an existing installation (you selected Modify on the Welcome window), all check boxes on the Select Features window reflect your choices during the initial installation. Clear a check box has the effect of uninstalling the component (for example, the Tivoli Enterprise Monitoring Server) or product package. Clear a check box for an application support package only if you want to remove the application support.
- If you have other components installed on the same computer, such as the desktop client, also select those components to install the component-specific application support.
- Click Next.
- (Distributed agents only) To add the agent to the deployment depot, select the agent and click Next.
This step does not occur for z/OS agents. z/OS agents cannot be added to the deployment depot.
- On the Start Copying Files window, read the list of actions to be performed and click Next to start the installation.
The application support packages that you selected are installed.
- On the Setup Type window, do the following:
- Select Install application support for a local/remote Tivoli Enterprise Monitoring Server.
- Optionally, select the check box for launching the Manage Tivoli Enterprise Monitoring Services window. (If selected, this window is displayed when the installation procedure is finished.)
- Clear the check boxes for any components that you have already installed on this computer, such as the monitoring server.
- Click Next.
- On the two Tivoli Enterprise Monitoring Server configuration windows that are displayed, make sure the information is correct and click either Next or OK.
- Enable application support on the monitoring server:
In Step 7, you selected the application support packages that you wanted to install on the monitoring server. In this step, you activate the application support through a process known as seeding the monitoring server.
- Specify the location of the monitoring server to which to add application support. You have two choices:
- On this computer
- On a different computer
Click OK.
For additional information about these parameters, press the Help button.
- If you are updating a hub Tivoli Enterprise Monitoring Server, you are asked to choose whether you want to add the default managed system list when you process the application-support files:
- All
- Add the default managed system groups to all applicable situations.
- New
- Add the default managed system groups to all applicable situations from the product support packages being seeded for the first time. Modifications are not made to managed system groups in previously upgraded product support packages.
- None
- The default managed system group is not added to any situation.
Not all situations support the default managed group setting. For some, you might need to manually define the distribution using the Tivoli Enterprise Portal due to the specific content of the agent support package.
Figure 1. The Select the Application Support to Add to the TEMS window
For each product-specific support package the installer checks if the Tivoli Enterprise Monitoring Server database was previously seeded with product-specific support in the self-describing mode. If so, the selected support file is excluded from the Tivoli Enterprise Monitoring Server seeding process. To overwrite the support that was seeded in self-describing mode, you can select the option to...
Skip self-describing mode seeding status check
- Click OK on the Select the Application Support to Add to the TEMS window.
This window lists the application support packages that you selected in Step 7. Click OK to begin seeding the monitoring server (using the SQL files listed on this window). This process can take up to 20 minutes.
- Click Next on the message that provides results for the process of adding application support (see Figure 2).
Figure 2. Application Support Addition Complete window
A return code of 0 (rc=0) indicates that the process succeeded.
If the Application Support Addition Complete window is not displayed after 20 minutes, look in the IBM\ITM\CNPS\Logs\seedkpp.log files (where pp is the two-character code for each monitoring agent) for diagnostic messages that help you determine the cause of the problem.
- Click Finish to close the installation wizard.
- If you installed application support on the Hub monitoring server and the Tivoli Enterprise Monitoring Automation Server is also installed, restart the automation server.
Parent topic:
Install application support on monitoring servers