Customizing the configuration profiles
The configuration profiles have been tailored with the values you provided as you set up the work environment. They also contain default values for all required parameters and some optional parameters. The amount of additional customization that is required depends upon how much your environment differs from the model or product-provided defaults. At a minimum, you must supply certain site-specific values, including variable resolution values. You must also enable and configure any features you want to exploit (such as support for self-describing agents).
About this task
- RTE configuration profile
- The RTE profile inherits the symbolics specified on the KCIP@PG3
panel. However, you must replace all instances of the actual RTE name
in the RTE profile with a symbolic (for example, &SYSNAME.), except
for the RTE_NAMESV parameter instance. You can
assign symbolics to additional parameters, but see Parameters ineligible to use variables for
parameters that must be excluded from use of symbolics. In addition,
you must also customize the product-specific parameters listed in Configure OMEGAMON monitoring agents and other components, as applicable. Optionally, you
can configure any monitoring server features that you want to enable
(Configure a Tivoli Enterprise Monitoring Server).
If you want to use the self-describing agent (SDA) feature, set the resolution value for KDS_KMS_SDA to Y, and provide site-specific values for RTE_USS_RTEDIR.
- Global configuration profile
- You can assign symbolics to any of the parameters in the global profile. At a minimum, if you
enabled SDA, you must assign a symbolic value to the GBL_HFS_JAVA_DIR1
parameter (for example, &GBL_HFS_JAVA_DIR1.), or change the literal
default to a site-appropriate one. You must also edit the value for load library parameter
GBL_DSN_CSF_SCSFMOD0 and any of the product-specific parameters listed in Customizing the global configuration profile, as appropriate.
At a minimum, provide site-appropriate resolution values for the following parameters, which apply to the hub to which the remote monitoring server connects:
- KDS_HUB_TEMS_NAME_NODEID
- KDS_HUB_VTAM_APPL_GLB_BROKER (if the hub uses SNA)
- KDS_HUB_VTAM_NETID (if the hub uses SNA)
- KDS_HUB_TCP_HOST
- KDS_HUB_TCP_PIPE_PORT_NUM