Configure the DBM Data Service

The Database Management Data Service (DBM Data Service) hosts a RESTful API that enables access to Db2 for z/OS data, such as the metrics that are provided by the following products:
dm20
The Database Management Data Service (DBM Data Service) hosts a RESTful API that enables access to Db2 for z/OS data provided by the following product RESTful APIs:
  • CA Detector® for DB2 for z/OS
    (CA Detector)
  • CA SYSVIEW® Performance Management Option for DB2
    (CA SYSVIEW for DB2)
  • Object Framework Services Agent (OFA)
The DBM Data Service retrieves the data by connecting to the
CA Database Management Solutions for DB2 for z/OS
through Xnet and Xmanager services. Mainframe and non-mainframe applications can access the collected data by using the APIs that are hosted by the DBM Data Service.
When the DBM Data Service configuration is complete, it can be used by the
Mainframe Team Center - Database Management for Db2 for z/OS
(MTC-DBM) user interface and to integrate with the API Mediation Layer.
To configure the DBM Data Service for use with the MTC-DBM user interface, see Configure the Mainframe Team Center User Interface. To configure the DBM Data Service to integrate with the Zowe API Mediation Layer, use the following procedure.
Follow these steps:
  1. Address prerequisites:
    1. Install the CA Common Services for z/OS ESM Microservice (CCS ESM Microservice) as described in the CA Common Services for z/OS (CCS) documentation. See CCS ESM Microservice Requirements for a high-level summary of these tasks that prepare the ESMPROC started task.
    2. Install product (CA Detector, CA SYSVIEW for DB2) and component (Xmanager, Xnet, DBM Data Service) maintenance.
    3. Perform the following post-install customization:
    4. Gather configuration values for the DBM Data Service.
  2. Configure Xnet for each Xmanager where CA Detector, CA SYSVIEW for DB2, and/or the DBM OFS Agent are running:
    • Address PassTicket security requirements.
    • Edit the PXNPARM member of CDBAPARM to remove the comment indicator from the PASSNAME parameter and the set of XES-related statements, specify the application name (APPLID) to use for PassTicket generation in the PASSNAME parameter, and tune the OPSEVENT health check controls as needed. Save your changes.
    • Set the XNETAGT system parameter to YES in CA SYSVIEW for DB2 to activate the data transfer through Xnet. This step is not required for CA Detector.
  3. Customize Using the DBM for Db2 Configuration Utility:
    1. Define configuration settings.
    2. Select products (DBM Data Service).
    3. Select product options:
      • (Recommended) Enable secure connections (HTTPS).
      • Enable Zowe API Mediation Layer.
      • Set diagnostic options.
    4. Define values for the following parameter groups:
      • General settings
      • ESM Microservice settings
      • Client key ring/keystore security settings
      • Xnet connection settings (global and Xnet server connections)
      • (Optional) Server key ring/keystore security settings
      • (Optional) Zowe API Mediation Layer integration settings
        This option lets you integrate with the API Mediation Layer to access the product-specific REST API services.
      • (Optional) Diagnostic settings
    5. Execute the following tasks:
      • Create configuration files
      • Copy configuration files to USS
      • Edit the DBMDS STC PROC and copy to PROCLIB
When the DBM Data Service configuration is complete, you can Integrate with the API Mediation Layer to access the product-specific REST API services.