Use the following steps to install a distributed monitoring agent on a Windows computer.
Use either the IBM® Tivoli® Monitoring Agent DVD or a distributed agent product CD for Windows. Do not use a Data Files for z/OS® CD.
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()~-./".
Click Next and then click OK to confirm the encryption key.
The Agent Compatibility Package in version ver_num is required but unavailable.
If you are installing monitoring agents on a computer that already has a monitoring server installed, the Agent Deployment window is displayed.
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. For information about how to deploy agents in the agent depot to remote computers, see Deploying monitoring agents across your environment.
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.) IBM strongly recommends you also add the agent compatibility (AC) package at this time. 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.
After installation is complete, a configuration window (called the Setup Type window) is displayed.
You have four choices: IP.UDP, IP.PIPE, IP.SPIPE, or SNA. You can specify up to three methods for communication. If the method you have identified as Protocol 1 fails, Protocol 2 is used. If Protocol 2 fails, Protocol 3 is used. When you configure the protocol for the Warehouse Proxy Agent, configure the same protocols used by the application agents and by the hub monitoring. If the proxy agent does not have the same protocol as the hub monitoring server, it cannot register with the hub. If the proxy does not have the same protocol as the application agents, then the application agents cannot communicate with the proxy when they to create a route to it.
Field | Description |
---|---|
IP.UDP Settings | |
Hostname 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 number is 1918. |
IP.PIPE Settings | |
Hostname 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 number is 1918. |
IP.SPIPE Settings | |
Hostname or IP Address | The host name or IP address for the hub monitoring server. |
Port number | The listening port for the hub monitoring server. The default value is 3660. |
SNA Settings | |
Network Name | The SNA network identifier for your location. |
LU Name | The LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software. |
LU 6.2 LOGMODE | The name of the LU6.2 LOGMODE. The default value is "CANCTDCS." |
TP Name | The transaction program name for the monitoring server. |
Local LU Alias | The LU alias. |
For additional information about these parameters, press the Help button.