IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Use the z/OS Tivoli Management Services Discovery Library Adapter
The z/OS Tivoli Management Services Discovery Library Adapter (zTMS DLA), available as of V6.2.2 Fix Pack 7 or later and IBM Tivoli Monitoring V6.2.3 Fix Pack 1 or later, scans the IBM Tivoli Monitoring environment and discovers resources monitored by the OMEGAMON agents. The zTMS DLA identifies resources only on z/OS operating systems. To discover resources on distributed systems, you must also run the Tivoli Monitoring Services Discovery Library Adapter.
The data in the IDML book generated by the zTMS DLA can be used to supplement data gathered by the z/OS DLA, enabling context sensitive launching into the Tivoli Enterprise Portal from z/OS objects or events in Tivoli Business Service Manager (TBSM) or Tivoli Application Dependency Discovery Manager (TADDM).
The zTMS DLA creates the following Common Data Model (CDM) objects:
- sys.zOS.Sysplex
- sys.zOS.SysplexGroup
- sys.zOS.ZSeriesComputerSystem
- sys.zOS.ZOS
- sys.zOS.CICSRegion
- sys.zOS.DB2Subsystem
- sys.zOS.IMSSubsystem
- sys.zOS.MQSubsystem
- sys.zOS.AddressSpace
To reconcile with the zTMS DLA book, the version of the z/OS DLA required is V3.1, with PTF UA61720. The IDML book generated by the zTMS DLA does not contain all required attributes for the various z/OS CDM objects. Before importing the zTMS DLA book into a consuming application, first run the z/OS DLA on all the systems monitored by the IBM Tivoli Monitoring OMEGAMON agents and import the resulting z/OS DLA books into the consuming application. Then you can import the zTMS DLA book, and all objects will be reconciled with existing objects found in the z/OS DLA books. If the zTMS DLA book is imported without having imported the z/OS DLA books first, objects might be displayed in the TBSM UI as NO_LABEL_SUPPLIED.
User scenarios
- On z/OS LPARS, execute the z/OS DLA on all z/OS LPARs of interest.
- On the Tivoli Enterprise Portal Server, execute the zTMS DLA on portal servers with z/OS agents.
- If you are using TBSM, complete the following steps:
- On the TBSM data server, import z/OS DLA books into TBSM using the TBSM discovery library toolkit.
- On the TBSM data server, import the zTMS DLA book into TBSM using the TBSM discovery library toolkit.
- On the TBSM server graphical user interface, right-click on the TBSM object to display the IBM Tivoli Monitoring launch-in-context menu items.
- If you are using TADDM, complete the following steps:
- On the TADDM server, import the z/OS DLA books into TADDM using the bulk load utility.
- On the TADDM server, import the zTMS DLA books into TADDM using the bulk load utility.
Run the following DLA script from the command line on the computer where the Tivoli Enterprise Portal Server is installed:
Procedure
- To make an IDML book, enter the following command:
install_dir\CNPS\ztmsdla.exeThe output file is written to the install_dir\CNPS\tmsdla directory.
To make an IDML book, enter the following command: install_dir/bin/itmcmd execute cq "ztmsdla"The output file is written to the install_dir/arch/cq/bin/tmsdla directory.
Results
The DLA generates the XML output file in the directory identified above. The name of this file begins with the string ZTMSDISC100-B and follows the standard Discovery Library file name format, for example: ZTMSDISC100-B.<hostname>.<timestamp>.refresh.xml.To import this book into TADDM or TBSM, you must transfer the XML file to the Discovery Library File Store and then use the Discovery Library Bulk Loader.
Usage
Use the following usage notes for your reference:
ztmsdla [/?] [/b] [/d] [/o orgname] [/s] [/p port] [/x outputfile]where:
- /?
- Displays the syntax help information.
- /b
- Opens a browser to view the output file of the Discovery Library Adapter (on Windows only).
- /d
- Creates a diagnostic file during the discovery process. You can use this file for debugging. The file is located in the same directory as the DLA IDML book. The file name is the same as the DLA IDML book, with an extension of .log at the end of the file name, for example: ZTMSDISC100-B.<hostname>.<timestamp>.refresh.log.
- /o orgname
- Sets the Organization GlobalName value. If this argument is not specified, the GlobalName defaults to <defaultOrg>.
- /s
- When specified, the URL created for the sourceContactInfo attribute of the ManagementSoftwareSystem class is created using the HTTPS protocol. This URL is used by TBSM and TADDM when performing a launch in-context to the Tivoli Enterprise Portal.
- /p port
- Set the port used for the URL created for the sourceContactInfo attribute. The default port is 1920 for HTTP. If the /s option is specified, the default port is 3661 for HTTPS. Use this option if the IBM Tivoli Monitoring Administrator has changed the default ports of the web server used to contact the portal server.
- /x outputfile
- Indicates the name of the XML output file.
Known limitations
Limitations exist when using SNA instead of IP.PIPE communication between a z/OS Tivoli Enterprise Monitoring Server and OMEGAMON agents. Two CICS objects representing the same CICS Region are displayed in TBSM, but only one can be right-clicked to launch one of the TBSM CICS objects to the OMEGAMON CICS Tivoli Enterprise Portal workspace.