Configuration worksheet if the hub monitoring server is on a distributed system

Edit online

Use this worksheet to record key details—such as host name, port number, server name, and encryption key—when setting up the hub monitoring server on a distributed system.

Table 1. Configuration worksheet if the hub monitoring server is on a distributed system
Value Description Value for your configuration
Monitoring server host name Host name of the system where the hub monitoring server is installed. You need both the short host name (without the domain name) and the fully qualified host name of the monitoring server workstation (with the domain name).
Monitoring server port number
Port number of the system where the hub monitoring server is installed. The default is 1918.
Note: The same TCP/IP port number must be used for every monitoring server in the enterprise. Also, make sure that the monitoring server well-known port is not on the TCP/IP reserved port list.
Monitoring server name (TEMS name, or node ID)

Name (TEMS name, or node ID) of the monitoring server. The default name for the hub monitoring server is HUB_ hostname. For example, for host ITMSERV61, the default hub name is HUB_ITMSERV61.

The TEMS name is generally not the same as the host name. It is an arbitrary name assigned during monitoring server configuration.
  • On Windows systems, you can find the TEMS name in Manage Tivoli Monitoring Services.

    Right-click Tivoli Enterprise Monitoring Server and select Browse Settings, and look for the value of CMS_NODEID.

  • On Linux and UNIX systems, you can find the value of CMS_NODEID in the KBBENV file located in the $itmhome/tables/cms_name subdirectory.
Encryption key You are prompted for a 32-bit encryption key when you begin configuration of components on a distributed system. You can use the default key. Be sure to document the value you use for the key, because you must use the same key in configuring any monitoring server and the portal servers that communicate with that monitoring server.

Use default key:

Define your own key:
Do you want to forward Take Action commands to NetView® for z/OS? You can enable forwarding of z/OS console commands issued from the Tivoli Enterprise Portal to NetView for user authorization and command execution. SeeSetting up NetView authentication of Take Action commands for instructions.