Configuration roadmap

The configuration roadmap guides you through the steps to configure the OMEGAMON® for IMS on z/OS® monitoring agent. As product installer, you might find the roadmap helpful before you configure the OMEGAMON for IMS on z/OS product.

In general, to complete the configuration tasks for the product, you go through the following configuration phases:
  • Completing PARMGEN prerequisite configuration tasks
  • Completing the configuration tasks
  • Completing the post-configuration tasks
Each configuration phase contains several configuration tasks that you might need to finish based on your actual business needs. The following diagram provides an at-a-glance view of the configuration tasks. In addition, the descriptions of configuration tasks in different configuration phases are documented in the following tables.
The image shows the diagram that provides an at-a-glance view of the configuration tasks.
The following table lists the PARMGEN prerequisite configuration tasks and the task description:
Table 1. PARMGEN prerequisite configuration tasks
Tasks Task description
Complete PARMGEN prerequisite configuration tasks Review the first step in the topic to complete the following relevant tasks:
  • Set up PARMGEN work libraries for your runtime environment
  • Set up the PARMGEN configuration profile for your runtime environment
Identify where your hub Tivoli Enterprise Monitoring Server is Review the second step in the topic.
Determine which Tivoli Enterprise Monitoring Server that your OMEGAMON for IMS on z/OS monitoring agent is to report to Review the third step in the topic. For more information about Tivoli Enterprise Monitoring Server planning and configuration, see OMEGAMON shared documentation, Version 6.3.0 Fix Pack 2 and above.
Determine where your IMS regions are running Review the fourth step in the topic.
Important: Ensure that the OMEGAMON for IMS on z/OS monitoring agent runs on the same LPAR as the IMS subsystem to be monitored.
Determine whether to use the default settings to configure the runtime environment

Review the fifth step in the topic. The first time you create a runtime environment for the OMEGAMON for IMS on z/OS product, use runtime environment and product or configuration default values wherever possible to complete the configuration. For more information, see OMEGAMON for IMS on z/OS parameter default values.

For information about runtime environment and global configuration parameters, see Common parameters in the Reference section of OMEGAMON shared documentation, Version 6.3.0 Fix Pack 2 and above.
Understand the PARMGEN configuration profiles required for user customization Review the sixth step in the topic. For more information, see the PARMGEN topics in OMEGAMON shared documentation, Version 6.3.0 Fix Pack 2 and above.
The following table lists the configuration tasks inside and outside of PARMGEN for the OMEGAMON for IMS on z/OS monitoring agent:
Table 2. Monitoring Agent configuration tasks
Tasks Task description
Enable historical data collection

Information to help you understand the persistent data store and help you decide whether you want to collect historical data is provided in Decision 8: Whether to collect historical data and how to manage it in the Planning section of OMEGAMON shared documentation, Version 6.3.0 Fix Pack 2 and above.

After you decide to collect historical data, enable historical data collection in the Tivoli Enterprise Portal or the e3270UI.

If the settings for the persistent data store (PDS) are not sufficient for your environment, you can change them by using PARMGEN. For more information, see Determining PDS sizes for near-term history collection.
Modify VTAM node and application definitions Learn about optional VTAM® configuration that the OMEGAMON for IMS on z/OS agent (IBMI5) provides.
Update agent and Tivoli Enterprise Monitoring Server protocols Learn about the situations in which you must update the agent parameters and the Tivoli Enterprise Monitoring Server protocols and the steps to update the parameters and protocols.
Configure an agent address space In addition to configuring an agent address space, you might also need to specify agent SNA communication values or agent IP.* and IP6.* communication values.
Register your product with a local Tivoli Enterprise Monitoring Server For information about the self-describing agent feature, see Enablement of self-describing agents and application support.
Note: This task is not required if you enable the self-describing agent feature.
Register the agent with a local monitoring server on z/OS For more information about application support, see Application support configuration for a hub monitoring server with no self-description capability.
Note: This task is not required if you enable the self-describing agent feature. Otherwise, you must manually install application support.
Enable aggregation and pruning Enable aggregation and pruning manually if the hub Tivoli Enterprise Monitoring Server on z/OS is not on the same machine as the Tivoli Enterprise Portal Server, or if the OMEGAMON for IMS on z/OS monitoring agent is not configured in the same Consolidated Software Inventory (CSI) as the hub Tivoli Enterprise Monitoring Server.
Note: This task is not required if you enable the self-describing agent feature.
After you run the PARMGEN steps to finish the setup of your runtime environment, you complete the post-configuration tasks outside of PARMGEN to complete the configuration. The following table lists the post-configuration tasks for the OMEGAMON for IMS on z/OS monitoring agent:
Table 3. Monitoring agent post-configuration tasks
Tasks Task description
Configure IMS Connect Extensions In addition to configuring collection parameters in the IMS™ Connect regions, configure the IMS Connect monitoring feature outside of PARMGEN.
Verify self-describing agent support Check the console messages that are displayed to verify whether self-description updates are successful or unsuccessful.
Enable security
Install language support

To have application data, online help, and expert advice displayed in a language other than English, install language support. The task is required even if the self-describing feature is enabled.

Restriction: The language support applies only to the Tivoli® Enterprise Portal Server and Tivoli Enterprise Portal client browser, web start, or desktop.