Follow the instructions in “Create the runtime members” on page 61 to create the runtime members for the remote monitoring server, and then follow the instructions in “Configure the persistent datastore” on page 61 to configure the persistent datastore and create its runtime members.
Then press F3 (Back) until you return to the Product Component Selection panel (Figure 28 on page 64).
Step 5. Configure monitoring agents to report to the remote monitoring server
In this step, you configure monitoring agents in the same runtime environment with the remote monitoring server.
1. On the Product Component Selection panel (Figure 28 on page 64), select the monitoring agent. If two monitoring agent components are listed, select the OMEGAMON II component first.
COMPONENT TITLE
1 Tivoli Enterprise Monitoring Server 2 OMEGAMON II ...
3 IBM Tivoli OMEGAMON XE ...
2. To configure the monitoring agent, follow the configuration instructions in the product publications in the Tivoli Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/
tivihelp/v15r1/index.jsp?toc=.
Be sure to select the option Register with local TEMS. This option produces a job that enables the monitoring agent to transmit data to the remote monitoring server.
If you are configuring the monitoring agent in its own address space, be sure to leave the default value of Y at this prompt:
Connect to TEMS in this RTE ==> Y (Y, N)
Follow the steps up to Complete the configuration.
3. Press F3 until you return to the Product Selection Menu (Figure 5 on page 33).
4. On the Product Selection Menu, enter S (Select) to the left of the name of another monitoring agent.
5. On the Runtime Environments (RTEs) panel (Figure 6 on page 34), type C (Configure) in the Action field to the left of the name of the runtime environment where you configured the remote monitoring server and the first monitoring agent.
6. On the Product Component Selection panel (Figure 28 on page 64), select the monitoring agent. You do not have to reconfigure the remote monitoring server to add a monitoring agent to the runtime environment.
7. Repeat steps 2 to 6 until you have configured all desired monitoring agents in the runtime environment.
Step 6. Load the runtime libraries
Before you complete the configuration of the monitoring server and monitoring agents outside the Configuration Tool, you must load the runtime libraries from the target libraries that were installed by SMP/E. The load job requires exclusive access to the runtime libraries.
1. On the Runtime Environments (RTEs) panel Figure 6 on page 34, enter L (Load) in the Action field to the left of the name of the runtime environment.
2. Review the JCL and submit the job. Verify that the job completes successfully and that the return code is 04 or lower.
3. When you finish loading the libraries, press F3 (Back) to return to the Runtime Environments (RTEs) panel.
4. Go to Chapter 6, “Completing the configuration,” on page 119, Chapter 7, “Adding application support to a monitoring server on z/OS,” on page 129, and Part 3 of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide for instructions on completing the configuration, adding application support to the monitoring servers, and validating the configuration.
5. After you validate the configuration, perform the tasks in Chapter 8, “Configuring security on a monitoring server on z/OS,” on page 143.
6. Go to Parts 4 and 5 of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:
Common Planning and Configuration Guide for instructions on using batch mode to replicate the configured environment to other LPARs.
Chapter 4. Configuring the hub monitoring server and monitoring agents in the same runtime environment
If your environment does not have DVIPA or does not meet some other requirement of the high-availability hub, you have other configuration options. The configuration shown in Figure 34 depicts the hub
monitoring server and several monitoring agents installed in the same runtime environment 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.
PARMGEN method
Complete these steps to configure a hub monitoring server and monitoring agents in the same runtime environment.
Tip: To configure a stand-alone hub monitoring server that is not a high-availability hub, perform the monitoring server configuration as described in this section, but omit “Step 2. Set configuration parameters for the monitoring agents in the same runtime environment” on page 81.
Step 1. Create the runtime environment and set the configuration parameters for the hub
Follow the steps in the "Configuring products with the PARMGEN method" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide to create a runtime environment. In "Step 2. Set up your PARMGEN configuration profile," refer to the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference for information about the parameters in the configuration profile. The configuration profile is the
&rhilev.&rte.WCONFIG(&rte) member.
Figure 34. Hub monitoring server and monitoring agents in the same runtime environment
Tips
v The parameters shown in this section are specific to the hub monitoring server but are not the only parameters for which you must either accept or override the default values 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.
v The parameters with names beginning KDS_HUB are not parameters for the hub monitoring server; they are parameters for remote monitoring servers.
v 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.
Before:
**KDS_TEMS_EIF_FLAG Y
After:
KDS_TEMS_EIF_FLAG Y
Be sure to set the following parameter values for the hub in the configuration profile:
* Tivoli Enterprise Monitoring Server: KDS flag CONFIGURE_TEMS_KDS "Y"
** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:
RTE_TEMS_CONFIGURED_FLAG Y
RTE_TEMS_NAME_NODEID "rte_name:CMS"
** TEMS configuration values:
KDS_TEMS_TYPE HUB
The following additional requirements also apply to the hub configuration:
KDS_TEMS_COMM_PROTOCOLn parameter
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 XE on z/OS (for the EPILOG facility of the OMEGAMON II
component) and OMEGAMON XE for Messaging on z/OS (for the 3270 interface component). See the product-specific configuration guides for further information about SNA requirements.
KDS_TEMS_TCP_PIPEc_PORT_NUM
The port number that you set for each protocol used by the hub must be respecified for every component that will communicate with the hub.
Many other KDS_* parameters are needed for the hub monitoring server configuration. See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference for information about them.
Configuring the monitoring server to support encryption/decryption
To activate ICSF encryption/decryption within your newly configured hub monitoring server using the PARMGEN configuration method, locate these lines in the configuration profile for the runtime environment of the monitoring server::
** GBL_DSN_CSF_* ICSF system libraries:
GBL_DSN_CSF_SCSFMOD0 "CSF.SCSFMOD0"
** TMS KAES256 password encryption key:
**KDS_TEMS_SECURITY_KAES256_ENCKEY "IBMTivoliMonitoringEncryptionKey"
Set GBL_DSN_CSF_SCSFMOD0 to the name of your site's Integrated Cryptographic Service Facility (ICSF) library. Uncomment KDS_TEMS_SECURITY_KAES256_ENCKEY, and set it to your site's ICSF encryption key for IBM Tivoli Monitoring.
Once you have set these parameters, if you enabled ICSF password encryption for your monitoring server after creating the runtime environment, rerun the following jobs:
WCONFIG($PARSE*)
File-tailoring job to recreate:
WKANSAMU(KDSDKAES)
Stand-alone Tivoli Management Services on z/OS password encryption job, if you want a sample job that you can edit manually.
WKANSAMU(KCIJPSEC)
Composite security job's KAES256 step, if you want a file-tailored job.
WKANSAMU(CANSDSST)
Monitoring server started task to concatenate the ICSF load library in the STEPLIB DDNAME.
CANSDSST is the IBM-supplied default; set the value to whatever you specified for the KDS_TEMS_STC parameter.
WKANSAMU(KDSDKAES) or WKANSAMU(KCIJPSEC) Creates the encryption key member.
WKANPARU(KAES256) or WKANSAMU(KCISYPJB)
Run either WKANPARU(KAES256), the stand-alone started task procedure copy job, or WKANSAMU(KCIJPSYS), the composite system copy job that copies the modified monitoring server started task to the system procedure library.
Step 2. Set configuration parameters for the monitoring agents in the same runtime environment
In the same configuration profile, set parameter values for each of the products you want to include in the runtime environment of the hub monitoring server. Follow the instructions in each product's Planning and Configuration Guide, and use the information in each product's Parameter Reference.
After you finish customizing the configuration profile, go on to "Step 3. Submit batch jobs to complete the PARMGEN setup" in the "Configuring products with the PARMGEN method" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
Step 3. (Optional) Replicate the runtime environment to a remote system
If desired, you can replicate the configured runtime environment to another LPAR where the Tivoli Enterprise Monitoring Server and monitoring agents are installed, and set the monitoring server
parameters for a remote rather than a hub monitoring server configuration. Follow the instructions in the
"Using the PARMGEN method to replicate a configured environment" chapter of the IBM Tivoli
OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
In the configuration profile of the second runtime environment, set the following parameter values for the remote monitoring server:
** Tivoli Enterprise Monitoring Server (TEMS) flag and CMS_NODEID name:
RTE_TEMS_CONFIGURED_FLAG Y
RTE_TEMS_NAME_NODEID "remote_rte_name:CMS"
** TEMS configuration values:
KDS_TEMS_TYPE REMOTE
The following additional requirements also apply to the remote monitoring server configuration:
KDS_TEMS_COMM_PROTOCOLn parameter
At least one of the communication protocols must be the same as a protocol selected for the hub.
For information about the communication protocols, see "Decision 5: How to set up communications between components" in the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
KDS_TEMS_TCP_HOST parameter
This is the TCP/IP host name (in IPV4 dotted-decimal format) of the z/OS system where the remote monitoring server is installed.
KDS_HUB_TCP_HOST parameter
This is the TCP/IP host name (in IPV4 dotted-decimal format) of the z/OS system where the hub monitoring server is installed. This parameter applies only to a remote monitoring server that uses TCP/IP for communications. The value specified for this parameter must match the value set for the KDS_TEMS_TCP_HOST parameter in the runtime environment where the hub is configured.
KDS_HUB_TCP_pipe_type_PORT_NUM
The value must be the port number of the hub for each protocol selected.
Many other KDS_* parameters are needed for the remote monitoring server configuration. See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference for information about them.
Modify as needed the monitoring agent parameter values for communication with the remote monitoring server in the same runtime environment. Follow the instructions in each product's Planning and
Configuration Guide, and use the information in each product's Parameter Reference.
After you finish customizing the configuration profile, go on to "Step 3. Submit batch jobs to complete the PARMGEN setup" in the "Configuring products with the PARMGEN method" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
Now you can replicate to other z/OS systems the configured runtime environment that contains the remote monitoring server and its monitoring agents. Follow the instructions in the "Using the PARMGEN method to replicate a configured environment" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli
Management Services on z/OS: Common Planning and Configuration Guide.
Configuration Tool (ICAT) method
Be sure to complete Steps 1, 2, and 3 in the "Configuring products with the Configuration Tool" chapter of the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide before you begin the configuration steps in this section.
Important
v When you select a product on the Product Selection Menu (Figure 5 on page 33), select one of the monitoring agents, not IBM Tivoli Management Services on z/OS, if you want to configure both a monitoring server and monitoring agents in the runtime environment. If you select IBM Tivoli Management Services on z/OS, you can only configure a stand-alone monitoring server in its own runtime environment, without any monitoring agents.
v To configure a stand-alone hub monitoring server that is not a high-availability hub, you select IBM Tivoli Management Services on z/OS and perform the monitoring server configuration as described in this section, but omit “Step 2. Configure monitoring agents in the runtime environment” on page 97.