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

Edit online

The final step is to take the CICS SLA definitions you have previously exported from the original hub Tivoli Enterprise Monitoring Server and import them into the new Tivoli Enterprise Monitoring Server using the XML file as the source.

To import your CICS SLA definitions into your new Tivoli Enterprise Monitoring Server, follow these steps:
  1. Open your generated XML file from the C:\temp\myCicsSlaDefinitions.xml folder location.
    You can see that underneath the preamble, the file is structured into groups of CICS SLA definitions for Workload, Service Class and Service Policy elements. Each element has an optional action attribute; this describes what operation you want the SLA Batch utility to perform. The available actions are create, edit, or delete to match the operations available in the CICS SLA view in the Tivoli Enterprise Portal desktop client. If you do not specify an action, then no action is performed and the element is ignored. The following entry is for a Workload element: 
    <Workload action="create">
      <Name>DFLTWORK</Name>
      <Description>DEFAULT WORKLOAD</Description>
</Workload>

    This example, creates a new Workload element with the name, DFLTWORK and the description, DEFAULT WORKLOAD. Depending on the element and action attribute you assign, certain elements are required and some are optional. All elements in the example file have action=”create” attribute because the export command was issued with the --listAsCreate flag.

  2. After you review the XML file, close the file.
  3. 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\
  4. Issue a command similar to the following to import the CICS SLA definitions from the XML file: 
    C:\IBM\ITM\CNP> kcp_slabatch import –s myserver.ibm.com –u sysadmin –i 
C:\temp\myCicsSlaDefintions.xml --failOnFirstError

    The first argument (import) indicates the operation you want to perform while the following arguments define additional connection values. This argument connects to a Tivoli Enterprise Portal running at myserver.ibm.com using the user ID (-u), sysadmin. The input XML file that was generated earlier is used (C:\temp\myCicsSlaDefinitions.xml) and the --failOnFirstError flag, which means that the kcp_slabatch utility stops processing at the occurrence of the first error while still importing the file.

    Once you issue this 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/08/09 16:59:32.125 KCPSB1002I: Starting import of SLA definitions.
IMPORT INPUT PARAMETERS
Hostname: myserver.ibm.com
Port: 1920
Input file:  C:\temp\myCicsSlaDefintions.xml
Fail on first error: true
Verbose: false
No console output: false

07/08/09 16:59:32.140 KCPSB1003I: Attempting to make connection to TEPS.
07/08/09 16:59:32.156 KCPSB1050I: Attempting to establish connection to TEPS at
 hostname: myserver.ibm.com, port: 1,920.
07/08/09 16:59:35.593 KCPSB1051I: Connection to TEPS successful.
07/08/09 16:59:36.656 KCPSB1068I: User has permission to view or modify SLA definitions.
07/08/09 16:59:36.656 KCPSB1004I: Using input file:  C:\temp\myCicsSlaDefintions.xml
07/08/09 16:59:36.734 KCPSB1025I: Update of WORKLOAD definitions starting.
07/08/09 16:59:36.734 KCPSB1082I: Request [1] - Request is to create a new Workload.
...
07/08/09 16:59:37.468 KCPSB1026I: Update of SERVICE POLICY definitions completed.
07/08/09 16:59:37.468 KCPSB1025I: Update of CONTROL INTERVAL definitions starting.
07/08/09 16:59:37.484 KCPSB1072I: Request [32] - Request completed successfully.
07/08/09 16:59:37.484 KCPSB1026I: Update of CONTROL INTERVAL definitions completed.
07/08/09 16:59:37.484 KCPSB1025I: Update of ACTIVE POLICY definitions starting.
07/08/09 16:59:37.562 KCPSB1072I: Request [33] - Request completed successfully.
07/08/09 16:59:37.562 KCPSB1026I: Update of ACTIVE POLICY definitions completed.
SUMMARY OF UPDATES
==================
Total number of CREATE requests: 33
Total number of EDIT requests: 0
Total number of DELETE requests: 0
Total number of requests with NO ACTION specified: 0
----------
Total number of SUCCESSFUL requests : 33
Total number of FAILED requests: 0
----------
TOTAL REQUESTS PROCESSED: 33
07/08/09 16:59:37.562 KCPSB1007I: Disconnecting from TEPS.
07/08/09 16:59:37.562 KCPSB1016I: Log file written to: 
                                  C:\IBM\ITM\logs\kcp_slabatch_200907081659.log
07/08/09 16:59:37.562 KCPSB1008I: SLA Batch Utility has completed. Return code: 0.

    Note that this example output has been edited.

  5. 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.

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

    You should now see all the imported CICS SLA definitions displayed that match the definitions defined on the original hub Tivoli Enterprise Monitoring Server.