How to Discover Full DB2 Topology

This task discovers IBM DB2 Server databases and their components on the network, and includes the following steps.

1. Prerequisite - Set up protocol credentials

   • For SQL-based Discovery: The IBM DB2 SQL-based Discovery uses the Generic DB Protocol (SQL).

     When setting up protocol credentials:

     • In the Database Type box, choose db2.

     • Verify the user name, password, and port used by IBM DB2 Server.

       For more information on configuring the Generic DB Protocol (SQL), see Supported Protocols.

   • For Shell-based Discovery:

     • Configure the appropriate shell protocol. For more information, see Supported Protocols.
     • All possible ports used by IBM DB2 Databases must be added to portNumberToPortName.xml file. Make sure that portName="db2".
2. Prerequisites - Miscellaneous

   • To perform an IBM DB2 discovery, copy the following files from the directory <db2_home_directory>\IBM\SQLLIB\java (for windows) or /opt/ibm/db2/<version>/java (for UNIX-like systems) to the Data Flow Probe machine:

     • db2java.zip

     • db2jcc.jar

     • db2jcc_license_cisuz.jar

     • db2jcc_license.jar

     On the Data Flow Probe machine, place the files in the following folder: <hp>\UCMDB\DataFlowProbe\runtime\probeManager\
     discoveryResources\db\db2 and restart the Data Flow Probe.

3. Run the discovery

   The jobs that you need to execute to perform this discovery are determined by whether shell access is provided to DB2 destinations. If shell access is provided, then perform discovery according to the instructions in the section below DB2 Discovery with Shell Access Provided to DB2 Destinations. If shell access is not provided to DB2 destinations, perform discovery according to the instructions in the section below DB2 Discovery without Shell Access Provided to DB2 Destinations.

   The two possible approaches to discovering full DB2 Topology are depicted in the following diagram:

   

   DB2 Discovery with Shell Access Provided to DB2 Destinations

   Note When shell access is provided to DB2 destinations, DB2 Discovery can be performed in either shallow mode or deep mode. To perform a shallow discovery where the basic topology is discovered (Db2Instance, Db2Database, and Db2Alias CITs), carry out steps a-c below. To perform a deep discovery, carry out all the steps below.

   To perform the DB2 Discovery:

   1. In the Universal Discovery window, execute the Range IPs by ICMP job. This job discovers all reachable IPs.

   2. Execute the job Host Connection by Shell. Discovers host's connectivity by shell protocol to the DB2 servers.

   3. Execute the job Host Applications by Shell. Discovers DB2 instances, their databases and aliases.

   4. To perform a deeper discovery, execute the following jobs in the order listed:

      1. DB2 Universal Database Connection by SQL. This job discovers the credentials_id attribute of Db2Databases and Db2Aliases. The discovered credentials_ids are used in the DB2 Topology By SQL job (for the list of discovered CITs see Discovered CITs).

         Note This job is triggered when one of the following conditions is true:

         • A Node has Db2Instance and Db2Aliases that are not linked with a realization link to any Db2Databases (discovered by the Host Applications by Shell job.

         • A Db2Databasehas DB2 IpServiceEndpoint (discovered by the Host Applications by Shell job).

         • A Node is linked to DB2 IpServiceEndpoint (discovered by the Host Applications by Shell job).

           DB2 IpServiceEndpoint is an endpoint with db2 in the service_names attribute or with the ip_service_name attribute equal to db2.

      2. DB2 Topology By SQL. This job discovers the full DB2 topology, including the CITs listed in Discovered CITs.

         Note This job is triggered when one of the following conditions is true:

         • A Db2Alias with the credentials_id attribute is reported.

         • A Db2Database with the credentials_id attribute is reported.

   DB2 Discovery without Shell Access Provided to DB2 Destinations

   To perform the DB2 Discovery:

   1. In the Universal Discovery window, execute the Range IPs by ICMP job. This job discovers all reachable IPs.

   2. Execute the job Databases TCP Ports. This job discovers the DB2 IpServiceEndpoint, which is a trigger for the DB2 Universal Database Connection by SQL job.

   3. Execute the following jobs in the order listed:

      • DB2 Universal Database Connection by SQL. This job discovers credentials_ids for both Db2Databases and Db2Aliases. The discovered credentials_ids are used in the DB2 Topology By SQL job (for the list of discovered CITs see Discovered CITs).

        Note This job is triggered when a Node is linked to DB2 IpServiceEndpoint (discovered by the Databases TCP Ports job). DB2 IpServiceEndpoint is an endpoint with db2 in the service_names attribute or with the ip_service_name attribute equal to db2.

      • DB2 Topology by SQL. This job discovers the full DB2 topology, including the CITs listed in Discovered CITs.

        Note This job is triggered when one of the following conditions is true:

        • A Db2Alias with the credentials_id attribute is reported.

        • A Db2Database with the credentials_id attribute is reported.

   For details on running jobs, refer to "Module/Job-Based Discovery" in the HPE Universal CMDB Data Flow Management Guide.