Highlighted
Absent Member.. Absent Member..
Absent Member..
1240 views

Duplicate CI Handling: HP uCMDB and Service Manager

 

Hello

 

We're looking for a way to solve two duplicate problems in terms of SM:

1) Duplicates across CIT.

2) Duplicate CIT as a result of the uCMDB allocating a global ID per instance. An example being a process which can run on several servers. When pushed to SM the 1st would be created and the rest would be created with the same name and suffixed with "_#", with # being a sequential number.

 

Please advise whether you have any suggestions.

 

Thanks

Simon

 

P.S. This thread has been moved from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. -HP Forum Moderator

 

 

 

0 Likes
3 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Duplicate CI Handling: HP uCMDB and Service Manager

I think if you are getting this problem only for process CIT, it is very specific CIT , and it usually depends upon the it's container CI. It can be read in individual CI specific, it should be read with it's container.

 

 

Do you see this only with process kind of CIT ?

 

 

But my first question is, why do we want to push process CI to the Service Manager ?

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Duplicate CI Handling: HP uCMDB and Service Manager

This problem would exist for any CIT where it's instances appear on more than 1 server i.e. same process can on over multiple server, same with services.

 

Process (We can use it as a signature) is probably not the best option to have used. Executables would make more sense, although the concept remain the same.

 

We use executables as signatures to identify applications.

 

Example:

Tst.exe resided on Serv1, Serv2 and Serv3. The change builder only wants to change Tst.exe on Serv1 only. We can not send Tst.exe * 3 (Unique instances in uCMDB) to SM, because of the logical name key constraint.

 

 

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Duplicate CI Handling: HP uCMDB and Service Manager

I think we need to do this with below steps.

 1. Needs to find are there duplicate CIs in ucmdb and why those are created .

 2. If CI is deleted in the ucmdb and the same CI getting deleted in the SM or not, this would also cause the duplicate CI in SM.

 

 

AFIK, usually the CIs are getting created in the ucmdb with different names but the logical name which is mapped to the SM attribtues are having the same value and hence we get this problem.

 

We need to fix the issue in ucmbd to see why such seneario is generated .

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.