UCMDB Support Tip: UCMDB and SM Integration Duplication rules
UCMDB may create two completely separate yet legit CI records that happen to have the same “name”. The UCMDB name field is mapped to the logical.name field (which must be unique) in Service Manager. Pushing the two CI records to Service Manager would cause a duplicate logical name problem. You have several ways to avoid this problem.
- Change the names directly in UCMDB or change the UCMDB reconciliation rule to make sure the names are not the same. This is highly recommended.
- In the integration adapter mapping configuration (xslt) file, avoid mapping the UCMDB name field to the SM logical name field directly in either of these ways:
- Map another UCMDB unique attribute to the SM logical.name field, and map the UCMDB name field to another SM field;
- Add a prefix to the name. The following are examples.
- UCMDB switches or routers are simply named as “Router” or “Switch” and identified by their underlying MACs. You can configure their “SM logical name” to be “<MAC> + <name>”.
- UCMDB databases often have the same name (due to the implementation of clusters and Oracle RACs). You can configure their “SM logic name” to be “<full DNS name> + <name>”.
In Service Manager
- Use the duplication rule options in DEM Rules in Service Manager.
Service Manager offers the following duplication rule options on the Duplication Rule tab in each DEM rule with a Table Name other than “cirelationship”:
• Action if logical name is duplicated (CI with different uCMDB ID): This is the action you want Service Manager to perform if the logical name is already used by another CI record when a CI record is added or updated.
— Rename to <name>_[RENAMED]_1/2/3: (Default) Service Manager changes the
logical name by adding a suffix.
— Return Error: Service Manager returns a duplicate key error to UCMDB.
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."
Click the KUDOS star on the left to say 'Thanks'