IBM Tivoli Composite Application Manager for Transactions, Version 7.4.0.0

Configuring the Internet service monitoring agent on Linux or UNIX systems

To configure the Internet service monitoring agent to work with IBM Tivoli Monitoring, you must set the connection parameters that enable it to contact the Tivoli Enterprise Monitoring Server (TEMS) or to the ObjectServer if using IBM Tivoli Netcool/OMNIbus. This configuration must be done manually on Linux or UNIX systems after installing Internet Service Monitoring.

About this task

Perform the configuration as the same user that was used when IBM Tivoli Monitoring was installed. You can update your configuration at any time. A log file is generated for each configuration. Use this file to diagnose any problems.

The file is located at:

/opt/IBM/ITM/InstallITM/plugin/executionEvents/logs/install_plugin_comp_is_n

where n is a number increasing by one for each generation.

Note: Ensure that Tivoli Enterprise Portal Server is running before you configure the Internet service monitoring agent.
To configure the Internet service monitoring agent from the command line, run the following command from the computer where the agent is installed:
/opt/IBM/ITM/bin/itmcmd config -A is

Procedure

To configure the agent using Manage Tivoli Enterprise Monitoring Services:

  1. Change directory to /opt/IBM/ITM/bin.
  2. Run the command: ./itmcmd manage. The Manage Tivoli Enterprise Monitoring Services window is displayed.
  3. Select Internet Service Monitoring.
  4. Right click and select Configure. The Internet Service Monitoring Configuration window is displayed, and the Object Server Connection tab is presented.
  5. If using Netcool/OMNIbus, set Configure Object Server Connection to YES and enter the name of the ObjectServer, the host name or IP address of the Netcool/OMNIbus ObjectServer computer and its port number. Click OK.
  6. Ensure that the check box for No TEMS is cleared and type the TEMS Hostname.
  7. On the Protocol 1 tab select the protocol required to communicate with the monitoring server. You can specify two protocols, one as the standard protocol and one to be used as a backup. Four types of protocol are available: IP.TCP, IP.PIPE (uses unsecured TCP communications), IS.PIPE (uses SSL secure TCP communications), and SNA (uses SNA for mainframe components).
  8. Enter the settings or accept the defaults for the selected protocol and click Save.
    Note: The default port number for IP.PIPE is 1918, for IP.SPIPE the port number is 3660.
Parent topic: Configuring Internet Service Monitoring


Last updated: September 2014