Configuring a static hub monitoring server

A hub monitoring server that is not configured for high availability is sometimes referred to as a static hub. A static hub can be configured in the same runtime environment as some or all of the agents that report to it.

About this task

The configuration shown in Figure 1 depicts the hub monitoring server and several monitoring agents installed in the same RTE on a single z/OS® image, with the monitoring agents reporting directly to the hub. This configuration is a basic one that you can expand to accommodate more systems.
Figure 1. Hub monitoring server and monitoring agents in the same runtime environment
Configuration graphic: Hub and monitoring agents in the same runtime environment
Tips:
  • The parameters shown in this section are not the only parameters you might need to set in the configuration profile for the runtime environment. After you set the parameters shown here, be sure to go through the entire configuration profile to make sure the parameter values are correct for the configuration you want.
  • The parameters with names beginning KDS_HUB are not parameters for the hub monitoring server; they are parameters for remote monitoring servers.
  • For information on the XF (“EXCLUDE FIND") macro, see XF edit macro.
The following instructions assume that the KDS_TEMS_TYPE parameter was set to HUB during the set up of the environment. If this is not the case, set those parameters in the RTE configuration profile before completing the following procedure.

Procedure

  1. Set the KDS_TEMS_COMM_PROTOCOLn parameters.

    At least one of the values must be IPPIPE, IP, IP6PIPE, IP6, IPSPIPE, or IP6SPIPE. If this monitoring server will communicate with any monitoring agents that require SNA, SNA must be one of the protocols chosen, but it does not have to be Protocol 1. Examples of such monitoring agents include OMEGAMON® for z/OS (for the EPILOG facility of the OMEGAMON II component) and OMEGAMON for Messaging on z/OS (for the 3270 interface component). See the product-specific configuration guides for further information about SNA requirements.

  2. Set the KDS_TEMS_TCP_PIPEc_PORT_NUM parameter for each protocol.

    The port number that you set for each protocol used by the hub must be re-specified for every component that will communicate with the hub.

What to do next

There are many other KDS_* parameters that are required for hub monitoring server configuration. You must either accept the defaults for these parameters or customize them for your site. See Tivoli Enterprise Monitoring Server (KDS) parameters for more information on these parameters. You may also want to enable the following optional features: Be sure to uncomment any parameters that are needed for your configuration but are commented out by default. For example, if you want to enable event forwarding, uncomment the KDS_TEMS_EIF_FLAG parameter and make sure its value is Y. To uncomment a parameter in the configuration profile, delete the two asterisks (**) from the beginning of the line.

See Scenario PGN01: Creating a full runtime environment with a hub monitoring server and OMEGAMON agents (Standard configuration) or Scenario QCF02: Configuring a full RTE with a static hub and variables enabled (Quick configuration) for step-by-step instructions for configuring an RTE with a static hub and several monitoring agents and many of these features enabled.