Integrate > Integration Studio > How to Work with Population Jobs

How to Work with Population Jobs

This task explains how to schedule population jobs and select the queries that are used to populate the CMDB with data.

  1. Create an integration point.

    Set up the integration to populate the data. For details, see How to Set Up an Integration Point.

  2. Set Reconciliation priority.

    In the Integration Point pane, right-click the integration, and select Reconciliation Priority Manager from the shortcut menu. For more details, see Reconciliation Priority Window.

  3. Run the population job.

    Population jobs are set to run according to a default schedule setting. However, you can manually run the integration at any time from the Integration Jobs pane. For user interface details, see Integration Jobs Pane.

    Select the job.

    • To synchronize all data for the first time, click the Full Synchronization button.

    • To synchronize only the data changes since the job last ran, click the Delta Synchronization button.

    • If CIs in a population job fail, the query is displayed in the Query Status tab as Completed with a warning symbol . You can drill down to see the errors that occurred and the CIs affected. This error data is saved in the system. When the job runs again to synchronize changes, UCMDB remembers the failed CIs and repopulates these as well.
    • If, since the last synchronization, you have changed a TQL query (other than changes to conditions on existing nodes), click the Clear Probe Results Cache button to ensure that the next run of the job is a full synchronization.

    • High Availability environment: If a population job is running, and the UCMDB Server responsible for write requests becomes unavailable or is changed, the job fails. You can wait for the next invocation of the job schedule, or alternatively rerun the population job manually.

    • For ResultTreeNodes (RTNs) coming from external sources, their isDeleted attribute setting will not be overridden by the mapping process. For example, if one RTN, which has isDeleted attribute set true, comes from SM, using a population job, it will be deleted even if the mapping processing changes isDeleted to false.
  4. Build a view of the population results.

    For details about viewing the populated data, see Working with Views in IT Universe Manager.

  5. View instances in IT Universe Manager.

    For details about viewing the CI instances, see Working with Views in IT Universe Manager.

  6. View reports.

    You can view reports about the integration in the Modeling Studio. For details see Reports.

Related Topics Link IconRelated Information