Customizing the configuration profiles

The configuration profiles have been tailored with the values you provided when 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. You must also enable and configure any features you want to exploit (such as event forwarding or support for self-describing agents).

1. From the Workflow - Primary Option Menu, select Customize PARMGEN configuration profiles,

   The Customize PARMGEN Configuration Profile Members panel (KCIP@PG6) is displayed.

2. Type DLAJOB in the Command line and press Enter to review the composite KCIJPDLA job that auto-discovers the values to some parameters in the configuration profiles. Submit the job after you review the job settings.
   For more information about the KCIJPDLn jobs, see Preparing the configuration profiles by running the KCIJPDLn jobs, and PARMGEN z/OS DLA utility jobs and commands.
3. Edit the RTE configuration profile.
   1. Select option 1 to edit the RTE profile.
   2. Customize the profile as follows.
      • Change all instances of _TCP_HOST host values to the reserved DVIPA name. For example:

        ISREDDE2 TSTEST.&userid.DEMO.WCONFIG(DEMO) 
        Command ===> C &hostname OMEGHAHUB ALL                            Scroll ===> CSR  
        ****** ***************************** Top of Data ******************************
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   307 Line(s) not Displayed 
        000308 **       000029 RTE_TCP_HOST                      "OMEGHAHUB"                
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   197 Line(s) not Displayed 
        000506 RTE_TCP_HOST                      "OMEGHAHUB"                                
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -   186 Line(s) not Displayed 
        000693 ** Note: If this is a High-Availability Hub TEMS, KDS_TEMS_TCP_HOST     
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  1 Line(s) not Displayed 
        000695 KDS_TEMS_TCP_HOST                 "OMEGHAHUB"                                
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 90 Line(s) not Displayed 
        000786 ** Note: If this is a High-Availability Hub TEMS, KDS_PH01_TEMS_TCP_HOST
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  9 Line(s) not Displayed 
        000796 KDS_PH01_TEMS_TCP_HOST            "OMEGHAHUB"                                
        - - -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  -  - 32 Line(s) not Displayed 
        ****** **************************** Bottom of Data ****************************

      • If you are configuring the RTE from scratch, instead of using the model profile, customize the monitoring server protocols to support only IP: At least one of the values must be IPPIPE, IP6PIPE, IPSPIPE, or IP6SPIPE. Nullify the KDS_TEMS_COMM_PROTOCOL2 parameter by setting it to "" (instead of the SNA value set initially).

        ISREDDE2 TSTEST.&userid.DEMO.WCONFIG(DEMO) 
        Command ===>                                                  Scroll ===> CSR  
        000658 ** TEMS communication protocols:                                        
        000659 ** Specify the communication protocols to be used by the local TEMS.    
        000660 ** Valid values are IPPIPE, IP, SNA, IP6PIPE, IP6, IPSPIPE, and         
        000661 ** IP6SPIPE. When communication with another ITM component (TEPS, Hub   
        000662 ** TEMS or Remote TEMS, Agents) is initiated, the TEMS tries Protocol 1 
        000663 ** first and goes to Protocol 2 and so on, in case of failure.          
        000664 ** Note: Update the corresponding KDS_TEMS_TCP_*_PORT_NUM port number   
        000665 **       parameter for each KDS_TEMS_COMM_PROTOCOLx parameter enabled.  
        000666 **       For example, if KDS_TEMS_COMM_PROTOCOL1="IPPIPE", set the      
        000667 **       corresponding KDS_TEMS_TCP_PIPE_PORT_NUM parameter.            
        000668 **       If KDS_TEMS_COMM_PROTOCOL2="IP" (for IP.UDP), set the          
        000669 **       corresponding KDS_TEMS_TCP_UDP_PORT_NUM parameter.             
        000670 **       If this is a Remote TEMS, update the KDS_HUB_* parameters      
        000671 **       by uncommenting out the corresponding KDS_HUB_TCP_*_PORT_NUM   
        000672 **       parameters and specify the Remote's Hub TEMS port numbers.     
        000673 KDS_TEMS_COMM_PROTOCOL1           IPPIPE                                
        000674 KDS_TEMS_COMM_PROTOCOL2           ""                                    
        

      • Change the value of the KDS_TEMS_TCP_KDEB_INTERFACELIST parameter from the null default ("") to !dvipa_hostname, where dvipa_hostname is the private DVIPA name set for the KDS_TEMS_TCP_HOST parameter (in this example, !OMEGAHUB). This setting ensures that the high-availability hub is restricted to its private DVIPA address and cannot interfere with the remote monitoring server configured on the same LPAR.

        ISREDDE2 TSTEST.&userid.DEMO.WCONFIG(DEMO) 
        Command ===>                                                  Scroll ===> CSR  
        000698 ** If the TEMS requires network interface list support:                 
        000699 ** Note: If this is a High-Availability Hub TEMS, uncomment the         
        000700 **       KDS_TEMS_TCP_KDEB_INTERFACELIST and set its value to           
        000701 **       "!<dvipa_address>"                                             
        000702 KDS_TEMS_TCP_KDEB_INTERFACELIST   "!OMEGHAHUB"                         

      • If the Integrated Cryptographic Service Facility (ICSF) is installed on the z/OS system, you can configure the monitoring server to enable encryption and decryption of communication among products and framework components. Enable IBM Tivoli Monitoring encryption by uncommenting the RTE_SECURITY_KAES256_KEY parameter. If you are using a KAES256 encryption key other than the IBM-supplied PARMGEN default key, specify the value. This value must match across your site. If you enable encryption, you must also edit the $GBL$USR profile to set the GBL_DSN_CSF_SCSFMOD0 parameter to the name of your site's ICSF library.

        ISREDDE2 TSTEST.&userid.DEMO.WCONFIG(DEMO) 
        Command ===>                                                  Scroll ===> CSR  
        000462 ** ----------------------------------------------------------------- -
        000463 ** (Required) KAES256 encryption key:                                 
        000464 ** The "RTE_SECURITY_KAES256_KEY" value is encrypted and              
        000465 ** xKANPARU(KAES256) member is created as part of the                 
        000466 ** xKANSAMU(KCIJPSEC) composite security or standalone KDSDKAES job.  
        000467 ** The TEMS and Agents started tasks are also updated to concatenate  
        000468 ** the ICSF load library (GBL_DSN_CSF_SCSFMOD0 parameter value) in the
        000469 ** RKANMODL DD.                                                       
        000470 ** Notes:                                                             
        000471 ** 1. Any customizations to the key must now be made through the      
        000472 **    global RTE RTE_SECURITY_KAES256_KEY parameter as this           
        000473 **    key is applicable to all components, including the Agents.      
        000474 ** 2. Starting in ITM6.3.0, specification of the ICSF load library and
        000475 **    enabling the KAES256 key is required.                           
        000476 ** 3. For an existing RTE, ensure that you rerun the                  
        000477 **    xKANSAMU(KCIJPSYS) job to refresh the TMS:Engine started tasks  
        000478 **    in the system procedure library (GBL_DSN_SYS1_PROCLIB value).   
        000479 ** 4. Related PARMGEN CONFIG profile parameters:                      
        000480 **    - GBL_DSN_CSF_SCSFMOD0 (DSN value is concatenated in the        
        000481 **      TEMS and Agent STCs' RKANMODL DD)                             
        000482 **    - KDS_KMS_SECURITY_COMPATMD (applicable to ITM6.3.0+ only)      
        000483 ** ----------------------------------------------------------------- -
        000484 RTE_SECURITY_KAES256_KEY     "IBMTivoliMonitoringEncryptionKey"         

      • If you intend to enable support for self-describing agents, or configure any products that require a z/OS® UNIX System Services directory, set RTE_USS_RTEDIR to the directory created for that purpose.

        Command ===>                                                  Scroll ===> CSR  
        000488 ** (Optional) If any products to be configured in this RTE require      
        000489 ** Unix System Services (USS) directories created, specify the main RTE 
        000490 ** HFS/zFS USS directory (#rtedir):                                     
        000491 ** Note: This is also required if you are enabling the Self-describing  
        000492 ** Agent (SDA) functionality in the z/OS TEMS and Agents:               
        000493 ** Related PARMGEN CONFIG profile parameters (for SDA):                 
        000494 **       - GBL_HFS_JAVA_DIRn                                            
        000495 **       - GBL_DSN_SYS1_SBPXEXEC                                        
        000496 **       - RTE_USS_RTEDIR                                               
        000497 **       - KDS_KMS_SDA                                                  
        000498 **       - KDS_TEMA_SDA                                                 
        000499 **			  - KDS_KMS_SDA_NO_GRANULAR                                      
        000500 **       - Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)              
        000501 RTE_USS_RTEDIR                    "/tstest"                       
        

      • To enable the SDA feature, set KDS_KMS_SDA to Y.
   3. Save your changes and return to the Customize PARMGEN Configuration Profile Members panel.
4. Edit the $GBL$USR profile as follows:
   1. From the Customize PARMGEN Configuration Profile Members panel, select option 2.

      The profile is displayed.

   2. Set the GBL_DSN_CSF_SCSFMOD0 parameter to the name of your site's ICSF load library.
   3. If any of the components you are configuring within this RTE require Java support or if you enabled the self-describing agent (SDA) feature now or intend to at a later time, customize the GBL_HFS_JAVA_DIR1 parameter and point to a valid path to a Java installation on HFS or zFS. Note that /bin is automatically appended to this value by the PARMGEN KCIJPUS* z/OS UNIX jobs.