(Optional) Push CI Data from UCMDB to APM

Data push jobs copy or update CI or CI relationship records from the local UCMDB system to your APM system.

To run a customized data push job, complete the following steps:

  1. Log in to UCMDB as an administrator.

  2. Go to Data Flow Management > Integration Studio.

    UCMDB displays a list of existing integration points.

  3. Select the integration point you created for APM.

  4. Or, if the default data push job does not satisfy your needs, you may add a new data push job as follows:

    1. Click the New Integration Job button in the right panel.

    2. In the Name field, type a unique name for the job.

    3. Click the Add Query button to add existing TQL queries to the job.

      UCMDB creates a default data push job when creating the integration point for APM. The following table lists the Topology Query Language (TQL) queries in the default data push job. If required, you may create, update, or remove TQL queries for the push job. You may also need to update the mapping. See .

      Note: To access these OOTB TQL queries for push, navigate to Modelling > Modeling Studio > Resources, select Queries from the drop-down list for the Resource Type field and then navigate to Root > Integration > APM Push.

      TQL Query Description
      APM Location Push

      Pushes Location CIs.

      Mapping XML: pushMappingAPMLocation.xml
      APM Process Push

      Pushes BusinessProcess CIs.

      Mapping XML: pushMappingAPMProcess.xml
      APM Process Relation Clear Push

      Clears old relations between processes in APM.

      This TQL query synchronization must have been run BEFORE the 'APM Process Relation Push' TQL query synchronization.

      Mapping XML: pushMappingAPMProcessRClear.xml
      APM Process Relation Push

      Pushes relations between Processes (pushed by APM Process Push) to other business elements or to processes.

      BusinessProcess CIs must have been pushed before this TQL query synchronization in the ‘APM Process Push’ TQL query synchronization.

      Mapping XML: pushMappingAPMProcessR.xml
      APM Server Push

      Pushes Node CIs (Computers, Network Devices, etc.).

      Mapping XML: pushMappingAPMServer.xml
      APM Server Relation Clear Push

      Clears old relations between Servers in APM.

      This TQL query synchronization must have been run BEFORE the 'APM Server Relation Push' TQL query synchronization.

      Mapping XML: pushMappingAPMServerRClear.xml
      APM Server Relation Push

      Pushes relations between Servers (pushed by APM Server Push) to other servers.

      Node CIs must have been pushed before this TQL query synchronization in the ‘APM Server Push’ TQL query synchronization.

      Mapping XML: pushMappingAPMServerR.xml
      APM Application Push

      Pushes BusinessApplication CIs.

      Location, BusinessProcess, and/or Node CIs must have been pushed before this TQL query synchronization.

      Mapping XML: pushMappingAPMApplication.xml
      APM Application Relation Clear Push

      Clears old relations (except for the downstream relations) between Applications in APM.

      This TQL query synchronization must have been run BEFORE the 'APM Application Relation Push' TQL query synchronization.

      Mapping XML: pushMappingAPMApplicationRClear.xml
      APM Application Relation Push

      Pushes relations (except for the downstream relations) between Applications (pushed by APM Application Push) to other business elements or to nodes.

      BusinessApplication CIs must have been pushed before this TQL query synchronization in the ‘APM Application Push’ TQL query synchronization.

      Mapping XML: pushMappingAPMApplicationR.xml
      APM Application Relation Clear Down Push

      Clears old downstream relations between Applications in APM.

      This TQL query synchronization must have been run BEFORE the 'APM Application Relation Down Push' TQL query synchronization.

      Mapping XML: pushMappingAPMApplicationDownRClear.xml
      APM Application Relation Down Push

      Pushes downstream relations between Applications (pushed by APM Application Push) to other business elements or to nodes.

      BusinessApplication CIs must have been pushed before this TQL query synchronization in the ‘APM Application Push’ TQL query synchronization.

      Mapping XML: pushMappingAPMApplicationDownR.xml

    4. Select the Allow Deletion option for each query.

      This allows deletion of synchronized data in APM when data in UCMDB are deleted. Otherwise requests created in APM as a result of synchronization remain even when their original data in UCMDB are deleted.

      Note: For scheduling configuration, see Schedule Data Push Jobs.

    5. Click OK.
    6. Save the integration point.

  5. Run the job manually to see if the integration job works properly:

    1. To push all the relevant data for the job, click the All Data Synchronization button (or Full Synchronization ).

    2. To push only the changes in the data since the job last executed, click the Changes Synchronization button (or Delta Synchronization ).

  6. The job is in Running status. Wait for the job to complete; click the Refresh button multiple times as needed until the job is completed.

    You can also look at the Query tab as that gives a progress bar against the query it is running.

  7. When the job is completed, the job status becomes one of the following depending on the results:

    • Succeeded
    • Passed with failures
    • Failed

  8. Click the Statistics tab to view the results; if any errors occur, click the Query Status tab and Job Errors tab for more information. For more information about errors, see Troubleshooting and Limitations.