IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Install IBM Tivoli Monitoring > Install the remote monitoring servers
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Windows: Installing a remote monitoring server
IBM Tivoli Monitoring does not support multiple remote monitoring servers on the same Windows computer.
- Launch the installation wizard by double-clicking the setup.exe file in the IBM Tivoli Monitoring Base DVD or DVD image.
If you are running Windows 2003 or Windows XP and have security set to check the software publisher of applications, you might receive an error stating that the setup.exe file is from an unknown publisher. Click Run to disregard this error message.
- Click Next on the Welcome window.
If you have another IBM Tivoli Monitoring component 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.
- Click Accept to accept the license agreement.
- Choose the directory where you want to install the product. The default directory 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()~-./".
- Type a 32-character encryption key. You can use the default key.
- Do not use any of the following characters in your key:
& ampersand | pipe ' single quote = equal sign $ dollar sign In addition, do not specify double-byte (DBCS) characters.
- Document the value you use for the key. Use this key during the installation of any components that communicate with this monitoring server.
Click Next and then click OK to confirm the encryption key.
- On the Select Features window, select the check box for Tivoli Enterprise Monitoring Server.
When you select the Tivoli Enterprise Monitoring Server 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 and other to the monitoring server. (The base monitoring agents are included with the base IBM Tivoli Monitoring installation package.) If you leave all of the application support check boxes selected, you do not need to reconfigure application support as new agent types are added to your environment. However, installing support for many agents at a time can increase the installation time and you may still have to add support for an agent later if it has been updated.
For detailed information about application support, see Install and enable application support.
- 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 Monitoring Server node. Clear all check boxes in the subtree except the check boxes labeled...
- Tivoli Enterprise Monitoring Server
- Summarization and Pruning Agent
- 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. Clear a check box only if you want to remove a component.
- To install any agents on this remote monitoring server, expand Tivoli Enterprise Monitoring Agents and select the agents you want to install.
- Click Next to display the Agent Deployment window.
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.
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.
- 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.
- If the TEPS Desktop and Browser Signon ID and Password window is displayed, enter and confirm the password to be used for logging on to the Tivoli Enterprise Portal. The default logon user ID, sysadmin, cannot be changed on this window. The logon password must match the password that you specified for sysadmin when you configured the hub monitoring server.
This window is not displayed if the sysadmin user ID has already been defined in the operating system.
- Review the installation summary details. The summary identifies the components you are installing. Click Next to begin the installation.
After the components are installed, a configuration window (called the Setup Type window) is displayed.
- 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. Click Next to start configuring all selected components.
- Configure the Tivoli Enterprise Monitoring Server:
- Select the type of monitoring server you are configuring: Hub or Remote. For this procedure, select Remote.
- Verify that the name of this monitoring server is correct in the TEMS Name field. If it is not, change it.
The default name is REMOTE_host_name, for example, REMOTE_itmserv16. This name must be unique in the enterprise.
- Identify the communications protocol for the monitoring server.
You have seven choices: IP.UDP, IP6.UDP, IP.PIPE, IP6.PIPE, IP.SPIPE, IP6.SPIPE, or SNA. You can specify up to six methods for communication. If the method you identify as Protocol 1 fails, Protocol 2 is used as a backup. If Protocol 2 fails, Protocol 3 is used as a backup, and so on.
- Leaving TEMS Security Compatibility Mode enabled performs the following functions:
- It allows for backwards compatibility with previous versions of IBM Tivoli Monitoring components shipped before V6.3 when securing command execution (Situation Take Action, Execute Command, Take Action, Workflow Policy Take Action). Accept the default if you have a previous version of a hub monitoring server or OMEGAMON product connecting to this remote Tivoli Enterprise Monitoring Server or if the system clocks are not synchronized across the systems with monitoring servers, the portal server, and monitoring agents.
- It permits commands to still execute even if cryptographic facilities are not available. This gives you time to ensure that, for example, your z/OS Tivoli Enterprise Monitoring Server has the Integrated Cryptographic Services Facility (ICSF) available.
If you disable this option and you have a mixture of pre-V6.3 and V6.3 server components, if clocks are not synchronized, or if you don't have cryptographic services available, then command executions might fail.
- Click OK.
- Complete the following fields for the communications protocol for the monitoring server.
Remote monitoring server communications protocol settings
Field Description IP.UDP and IP6.UDP Settings: Primary Hub TEMS Host name or IP Address The host name or IP address for the hub monitoring server. Port # or Port Pools The listening port for the hub monitoring server. The default port is 1918. IP.PIPE and IP6.PIPE Settings: Primary Hub TEMS Host name or IP Address The host name or IP address for the hub monitoring server. Port Number The listening port for the monitoring server. The default value is 1918. IP.SPIPE and IP6.SPIPE Settings: Primary Hub TEMS Host name or IP Address The host name or IP address for the hub monitoring server. Port Number The listening port for the monitoring server. The default value is 3660. SNA Settings: Remote TEMS Local LU Alias LU alias. TP Name The transaction program name for this monitoring server. SNA Settings: Primary Hub TEMS Network Name SNA network identifier for your location. LU Name LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software. LU 6.2 LOGMODE Name of the LU6.2 LOGMODE. The default value is "CANCTDCS." TP Name The transaction program name for the monitoring server.
- If you are certain that you have typed the values for all of these fields with exactly the correct casing (upper and lower cases), you can select Use case as typed. However, because IBM Tivoli Monitoring is case-sensitive, consider selecting Convert to upper case to reduce the chance of user error.
- Click OK to continue.
- Enable application support on the monitoring server.
In Step 6, you selected the base monitoring agents for which you wanted to install application support files 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.
- Click OK on the Select the application support to add to the TEMS window.
This window lists the monitoring agents that you selected in Step 6. Click OK to begin seeding the monitoring server (using the SQL files listed on this window).
This process can take up to 20 minutes. As the seeding process completes, a progress bar is displayed, showing the progress of seeding, in turn, the application support for the agents you selected. Once seeding completes, if support could not be added, a window is displayed showing all seeding results.
- Click Next on the message that provides results for the process of adding application support (see Figure 2). 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\seedkpc.log files (where pc is the two-character product code for each monitoring agent) for diagnostic messages that help you determine the cause of the problem. For a list of product codes, see IBM Tivoli product, platform, and component codes.
- Configure the communication between any IBM Tivoli Monitoring component and the monitoring server:
- Specify the default values for IBM Tivoli Monitoring components to use when they communicate with the monitoring server.
- If agents must cross a firewall to access the monitoring server, select Connection must pass through firewall.
- Identify the type of protocol that the agents use to communicate with the hub monitoring server.
You have seven choices: IP.UDP, IP6.UDP, IP.PIPE, IP6.PIPE, IP.SPIPE, IP6.SPIPE, or SNA. You can specify up to six methods for communication. If the method you identify as Protocol 1 fails, Protocol 2 is used as a backup. If Protocol 2 fails, Protocol 3 is used as a backup, and so on.
Click OK.
- Complete the communication protocol fields for the monitoring server. See Table 1 for definitions of these fields. Click OK.
For additional information about these parameters, press the Help button.
- Click Finish to complete the installation.
- Click Finish on the Maintenance Complete window if you are updating an existing installation.
Parent topic:
Install the remote monitoring servers