Importing the edited CICS SLA definitions from the XML file into the hub Tivoli Enterprise Monitoring Server

The final part for this scenario is to take the updated CICS SLA definitions in your XML file and import the definitions again to the hub Tivoli Enterprise Monitoring Server.

Use these steps to import your updated CICS SLA definitions into your hub Tivoli Enterprise Monitoring Server:
  1. Navigate to the folder where you installed the kcp_slabatch utility. This location is in the Tivoli Enterprise Portal desktop client folder. For Windows, C:\IBM\ITM\CNP\
  2. Issue a command similar to the following to import the updated CICS SLA definitions:
    C:\IBM\ITM\CNP> kcp_slabatch import –s localhost –u sysadmin –i 
    C:\temp\MyNewSLADefintions.xml -FailOnFirstError
    Once you issue the command, the following output is displayed on the console:
    IBM OMEGAMON forCICS on z/OS - SLA Command Line Utility
    (C) Copyright IBM Corporation 2012. All rights reserved.
    07/09/10 14:24:56.500 KCPSB1002I: Starting import of SLA defintions.
    IMPORT INPUT PARAMETERS
    Hostname: localhost
    Port: 1920
    Input file:  C:\temp\MyNewSLADefintions.xml
    Fail on first error: true
    Verbose: false
    No console output: false
    
    07/09/10 14:24:56.515 KCPSB1003I: Attempting to make connection to TEPS.
    07/09/10 14:24:56.531 KCPSB1050I: Attempting to establish connection to TEPS at 
    hostname: localhost, port: 1,920.
    07/09/10 14:24:59.578 KCPSB1051I: Connection to TEPS successful.
    07/09/10 14:25:00.515 KCPSB1068I: User has permission to view or modify SLA definitions.
    07/09/10 14:25:00.515 KCPSB1004I: Using input file:  C:\temp\MyNewSLADefintions.xml
    07/09/10 14:25:00.578 KCPSB1025I: Update of WORKLOAD definitions starting.
    07/09/10 14:25:00.578 KCPSB1082I: Request [1] - Request is to create a new Workload.
    07/09/10 14:25:00.640 KCPSB1072I: Request [1] - Request completed successfully.
    07/09/10 14:25:00.640 KCPSB1026I: Update of WORKLOAD definitions completed.
    07/09/10 14:25:00.640 KCPSB1025I: Update of SERVICE CLASS definitions starting.
    07/09/10 14:25:00.640 KCPSB1093I: Request [2] - Request is to edit an existing Service Class.
    07/09/10 14:25:00.687 KCPSB1071I: Request [2] - Calling EDIT on SERVICE CLASS (Name: ATRANS).
    07/09/10 14:25:00.718 KCPSB1072I: Request [2] - Request completed successfully.
    07/09/10 14:25:00.718 KCPSB1026I: Update of SERVICE CLASS definitions completed.
    07/09/10 14:25:00.718 KCPSB1025I: Update of SERVICE POLICY definitions starting.
    07/09/10 14:25:00.718 KCPSB2008I: Request [3] - Request is to edit an existing Service Policy.
    07/09/10 14:25:00.750 KCPSB2020I: Request [3] - Request is to create a new Override Goal.
    07/09/10	 14:25:00.750 KCPSB1072I: Request [3] - Request completed successfully.
    07/09/10 14:25:00.750 KCPSB1026I: Update of SERVICE POLICY definitions completed.
    07/09/10 14:25:00.750 KCPSB1025I: Update of CONTROL INTERVAL definitions starting.
    07/09/10 14:25:00.765 KCPSB1072I: Request [4] - Request completed successfully.
    07/09/10 14:25:00.765 KCPSB1026I: Update of CONTROL INTERVAL definitions completed.
    07/09/10 14:25:00.765 KCPSB1025I: Update of ACTIVE POLICY definitions starting.
    07/09/10 14:25:00.828 KCPSB1072I: Request [5] - Request completed successfully.
    07/09/10 14:25:00.828 KCPSB1026I: Update of ACTIVE POLICY definitions completed.
    SUMMARY OF UPDATES
    ==================
    Total number of CREATE requests: 1
    Total number of EDIT requests: 3
    Total number of DELETE requests: 0
    Total number of requests with NO ACTION specified: 0
    ----------
    Total number of SUCCESSFUL requests : 5
    Total number of FAILED requests: 0
    ----------
    TOTAL REQUESTS PROCESSED: 5
    07/09/10 14:25:00.828 KCPSB1007I: Disconnecting from TEPS.
    07/09/10 14:25:00.828 KCPSB1016I: Log file written to: 
                                      C:\IBM\ITM\logs\kcp_slabatch_200907091424.log
    07/09/10 14:25:00.828 KCPSB1008I: SLA Batch Utility has completed. Return code: 0.
  3. If the command has run correctly there should be a return code of 0. If a problem occurred, check the log file at your location.

    The log file provides detailed information as to when the problem occurred. Once you have corrected the issue, run the command again. Notice towards the end of the log file, there is a summary of updates that have been made as a result of running these requests. Verify that all CICS SLA definitions have been updated as expected.

  4. Sign on to the Tivoli Enterprise Portal desktop client.

    You should now see all the modified CICS SLA definitions.