Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
344 views

Integration with HP uCMDB

Jump to solution

Hi everybody,

I have a question for the experts regarding the integration with uCMDB. The DEM reconciliation rules, exactly how do they work?

I have successfully integrated with uCMDB, it updates the items we need (servers, databases, and so on) using the ucmdb.id, but the mechanism is a bit opaque. I tried to create a DEM rule so if it can't find a record by ucmdb.id it the tries to update based on logical.name but this doesn't work at all; if for some reason uCMDB detects an old item as if it was new and assigns it a new ucmdb.id it will no longer update the old item in SM and will try to create a new one with the same logical.name, which of course fails.

Thanks

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Integration with HP uCMDB

Jump to solution

Hi,

Here is some information from the SM 9.41 Codeless Help Server that should help answer your query:

Create a DEM reconciliation rule

Create a DEM reconciliation rule

Applies to User Roles:

System Administrator

It is possible that your Service Manager system already contains CI records that match CIs in your UCMDB system. Rather than add duplicate CI records to your Service Manager system, you can configure Service Manager to reconcile CI records between the two systems based on specified Discovery Event Manager (DEM) reconciliation rules.

A DEM reconciliation rule record allows you to specify what Service Manager queries you want to use to determine whether an existing CI record matches a CI in an UCMDB system. An administrator typically specifies reconciliation rules prior to starting the integration to the HP Universal CMDB system so that Service Manager will not create duplicate CI records.

When performing CI reconciliation between Service Manager and UCMDB, Service Manager uses the ucmdb.id field to query the device table or a join table to determine whether an Update or Create operation is needed. The reconciliation process is as follows:

  1. The UCMDB system sends a web service message containing the latest CI attribute data to Service Manager.
  2. Service Manager scans the web service message for the CI ucmdb.id value.

    Note: The ucmdb.id field is displayed in the Actual State Section of the CI form, with a label of Ucmdb ID.

  3. Service Manager searches for an existing CI record that has the same ucmdb.id value.
  4. If Service Manager finds a CI that has the ucmdb.id value, no reconciliation is needed. Service Manager compares the UCMDB CI attributes to the Service Manager managed fields and runs the appropriate Discovery Event Manager (DEM) rules as needed to update the CI record in Service Manager.
  5. If Service Manager cannot find a CI that has the ucmdb.id value, it searches for a DEM reconciliation rule record that is defined for the CI type.
  6. If no DEM reconciliation rule record is found, Service Manager creates the CI record according to the appropriate DEM rules.
  7. If a DEM reconciliation rule record is found, Service Manager evaluates the rules and appends (ucmdb.id=NULL or ucmdb.id~=NULL and istatus=”XXXXXX”) to the reconciliation rules in the backend, where the istatus value is retrieved from the DEM rule for deletion (for example, Retired/Consumed). If no istatus value is found in the DEM rule, Service Manager only appends ucmdb.id=NULL to the reconciliation rules in the backend.

  8. If no matching CI record is found by the reconciliation rules, Service Manager creates the CI record according to the appropriate DEM rules.
  9. If a matching CI record is found by the reconciliation rules, Service Manager updates the CI record according to the appropriate DEM rules

Using join tables for reconciliation

When setting reconciliation rules, if the CI type you are reconciling has a joindef definition (as defined in the devtype table), use the join table name instead of the device table. For example, if you want to reconcile computer CIs, use the joinnode table instead of the device table.

Sequence of reconciliation

By default, Service Manager executes the reconciliation rules in their listed order. To change the order in which Service Manager reconciles CIs, you can add a numeric value to the Sequence field.

Multi-company mode

By default, Service Manager uses only the ucmdb.id field for CI reconciliation, and the company.id field is not used. You can manually add DEM reconciliation rules.

Steps to create a DEM reconciliation record

To create a DEM reconciliation rule record, follow these steps:

  1. Click Tailoring > Web Services > DEM Reconciliation Rules.

    Service Manager displays the DEM Reconcile Record form.

  2. In the Table field, select a Service Manager table against which you want to run reconciliation queries.

    Note: Only tables that are specified in CI type records are displayed in the drop-down list. You can create only one DEM reconciliation record for one table.

  3. Click New.
  4. Enter expressions in the Expression column, and enter a sequence number for each expression in the Sequence column.  For example, you can add the following expressions for the device table. In this example, Service Manager looks for a matching record first based on the logical.name field, and then based on the sm.device.display.name field.

    Expression Sequence

    logical.name=logical.name in $L.file

    1
    sm.device.display.name=sm.device.display.name in $L.file2
  5. Click Add.

    Service Manager creates the reconciliation rule record.

Thanks

View solution in original post

2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Integration with HP uCMDB

Jump to solution

Hi,

Here is some information from the SM 9.41 Codeless Help Server that should help answer your query:

Create a DEM reconciliation rule

Create a DEM reconciliation rule

Applies to User Roles:

System Administrator

It is possible that your Service Manager system already contains CI records that match CIs in your UCMDB system. Rather than add duplicate CI records to your Service Manager system, you can configure Service Manager to reconcile CI records between the two systems based on specified Discovery Event Manager (DEM) reconciliation rules.

A DEM reconciliation rule record allows you to specify what Service Manager queries you want to use to determine whether an existing CI record matches a CI in an UCMDB system. An administrator typically specifies reconciliation rules prior to starting the integration to the HP Universal CMDB system so that Service Manager will not create duplicate CI records.

When performing CI reconciliation between Service Manager and UCMDB, Service Manager uses the ucmdb.id field to query the device table or a join table to determine whether an Update or Create operation is needed. The reconciliation process is as follows:

  1. The UCMDB system sends a web service message containing the latest CI attribute data to Service Manager.
  2. Service Manager scans the web service message for the CI ucmdb.id value.

    Note: The ucmdb.id field is displayed in the Actual State Section of the CI form, with a label of Ucmdb ID.

  3. Service Manager searches for an existing CI record that has the same ucmdb.id value.
  4. If Service Manager finds a CI that has the ucmdb.id value, no reconciliation is needed. Service Manager compares the UCMDB CI attributes to the Service Manager managed fields and runs the appropriate Discovery Event Manager (DEM) rules as needed to update the CI record in Service Manager.
  5. If Service Manager cannot find a CI that has the ucmdb.id value, it searches for a DEM reconciliation rule record that is defined for the CI type.
  6. If no DEM reconciliation rule record is found, Service Manager creates the CI record according to the appropriate DEM rules.
  7. If a DEM reconciliation rule record is found, Service Manager evaluates the rules and appends (ucmdb.id=NULL or ucmdb.id~=NULL and istatus=”XXXXXX”) to the reconciliation rules in the backend, where the istatus value is retrieved from the DEM rule for deletion (for example, Retired/Consumed). If no istatus value is found in the DEM rule, Service Manager only appends ucmdb.id=NULL to the reconciliation rules in the backend.

  8. If no matching CI record is found by the reconciliation rules, Service Manager creates the CI record according to the appropriate DEM rules.
  9. If a matching CI record is found by the reconciliation rules, Service Manager updates the CI record according to the appropriate DEM rules

Using join tables for reconciliation

When setting reconciliation rules, if the CI type you are reconciling has a joindef definition (as defined in the devtype table), use the join table name instead of the device table. For example, if you want to reconcile computer CIs, use the joinnode table instead of the device table.

Sequence of reconciliation

By default, Service Manager executes the reconciliation rules in their listed order. To change the order in which Service Manager reconciles CIs, you can add a numeric value to the Sequence field.

Multi-company mode

By default, Service Manager uses only the ucmdb.id field for CI reconciliation, and the company.id field is not used. You can manually add DEM reconciliation rules.

Steps to create a DEM reconciliation record

To create a DEM reconciliation rule record, follow these steps:

  1. Click Tailoring > Web Services > DEM Reconciliation Rules.

    Service Manager displays the DEM Reconcile Record form.

  2. In the Table field, select a Service Manager table against which you want to run reconciliation queries.

    Note: Only tables that are specified in CI type records are displayed in the drop-down list. You can create only one DEM reconciliation record for one table.

  3. Click New.
  4. Enter expressions in the Expression column, and enter a sequence number for each expression in the Sequence column.  For example, you can add the following expressions for the device table. In this example, Service Manager looks for a matching record first based on the logical.name field, and then based on the sm.device.display.name field.

    Expression Sequence

    logical.name=logical.name in $L.file

    1
    sm.device.display.name=sm.device.display.name in $L.file2
  5. Click Add.

    Service Manager creates the reconciliation rule record.

Thanks

View solution in original post

Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Integration with HP uCMDB

Jump to solution

Thanks, I already had the documentation but the one you quote is more recent and does a better job at explaining the process. I'll mark it as a solution as it seems to cover the areas where the old document was a bit "fuzzy" and I think this will actually work.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.