Highlighted
Absent Member.
Absent Member.
109 views

UCMDB 8 to SM7 Integration

While I have a deep understanding of the HP Service Manager environment, I admit I am a noob when it comes to UCMDB.  We recently had the following issue in our environment and I'm hoping someone can provide some insight into *why* it occurred:

Existing routers/switches in our environment, which previously had their host key field populated by short name, started populating by Fully Qualified Domain Name.  This led to the undesired result of passing over "new" CIs to the Service Manager environment that already existed in our CMDB.  These duplicate CI names are getting a "_1" appended to their CI name. 

While our UCMDB support guy is attempting to understand why the host key values were discovered by FQDN, I am trying to understand why the UCMDB pushes over the 'display label' field as the field to be populated as the primary key (logical.name) within the SM7 CMDB?  Wouldn't we want the UCMDB unique field of 'Host Key' to be synched up with the SM7 unique key of 'logical.name'?  We did have a lot of consultants working on this integration over the years, is it possible they modified the way the data is being pushed over to SM7?

 

Any insight into this would be greatly appreciated.

0 Likes
1 Reply
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: UCMDB 8 to SM7 Integration

Hello Dpetrich , 

 

I hope you are doing well . 

 

I reviewed and it probably appear if change the code dealing with how SM create relationships. 

 

Please review if before this issue  your environment  suffered an  customization . 

 

 

Best Regards , 

 

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
0 Likes
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.