Converting a hub monitoring server to a remote monitoring server

Initially, you might configure a new runtime environment to be stand-alone, with its own hub monitoring server. Later, you can integrate that runtime environment with the rest of your monitoring topology by converting its hub monitoring server to a remote monitoring server that communicates with a central hub.

Before you begin

The following procedure assumes that you have already created the following two runtime environments:

  • A runtime environment with a hub monitoring server that you want to convert to a remote monitoring server.
  • A runtime environment with the central hub monitoring server that you want the new remote monitoring server to communicate with. We'll call this the central hub runtime environment.

About this task

Converting a hub monitoring server to a remote monitoring server involves changing the KDS_TEMS_TYPE parameter value from HUB to REMOTE, and setting some other KDS_* parameters to refer to the central hub.

The following diagram shows a stand-alone runtime environment with a hub:

Figure 1. Before: A stand-alone runtime environment with a hub monitoring server
Diagram of an RTE with a hub monitoring server.

The following diagram shows the runtime environment after you have converted its hub to a remote monitoring server that communicates with a central hub:

Figure 2. After: A runtime environment with a remote monitoring server
Diagram of two RTEs: one with a hub monitoring server, the other with a remote monitoring server.

Procedure

  1. Edit the RTEDEF(KDS$PARM) or RTEDEF(KDS$lpar) member for the runtime environment with the hub that you want to convert to a remote monitoring server.

    Set the following parameters:

    KDS_TEMS_TYPE
    Change from HUB to REMOTE.
    KDS_HUB_TEMS_NAME_NODEID
    Set to the value of RTE_TEMS_NAME_NODEID in the central hub runtime environment.
    KDS_HUB_TCP_PIPE_PORT_NUM
    Set to the value of RTE_TCP_PORT_NUM in the central hub runtime environment.
    KDS_HUB_TCP_HOST
    Set to the host name of the LPAR for the central hub runtime environment.
  2. Submit a job that performs the GENERATE action for the runtime environment whose parameters you have just edited.