Scenario QCF04: Configuring a full RTE with a static hub monitoring server

If your site does not meet the requirements for a high-availability hub monitoring server, but you want to configure a hub on z/OS®, configure a static hub. You can configure other products in the same runtime environment (RTE) as a static hub. This scenario creates a full (RTE) comprising a z/OS-based hub monitoring server, OMEGAMON® monitoring agents, and the OMEGAMON enhanced 3270 user interface. You can use an IBM-provided model to create the RTE and do minimal customization to get up and running, or create the RTE from scratch and customize to your exact requirements.

Before you begin

If you intend to enable self-describing agents, or to configure any products that require a z/OS UNIX System Services directory, and you plan to create a new file system for that purpose, ensure that the file system is created and mounted before submitting the z/OS UNIX jobs. Make sure that the file system has access to a Java™ runtime environment running under IBM®'s 31-bit or 64-bit Java SDK Version 5 (or higher) on an HFS or zFS file system.

About this task

For this scenario, you use IBM-provided RTE model profile @MDLHF.

This scenario involves completing five main steps using the configuration software:

  1. Defining the new RTE.
  2. Setting up PARMGEN work environment for the runtime environment.
  3. Customizing the configuration profiles.
  4. Creating the runtime members and jobs.
  5. Submitting batch jobs to complete the RTE setup.
After you complete these steps, complete any configuration steps required outside the configuration software and start the products.
Note: If your environment meets the requirements for a high-availability (HA) hub monitoring server, consider configuring one first, and then creating a full RTE with a remote monitoring sever on the same LPAR.