Absent Member.. Absent Member..
Absent Member..
827 views

uCMDB: orm file and root_container

Jump to solution

Hello

 

I'm working with ORM.xml (Generic DB Protocol) and receive a reconciliation error. I understand why, but I'm unable to establish how to fix the problem. The error lists the criteria, with root_container being the issue I do not know how to fix.

 

What is the root_container?

How do I establish the root_container of a CIT?

How would I address this in the orm.xml file and what values must be populated?

Is there an example I can reference?

What is, for example, the root_container for CICS List?

 

Regards

Simon

 

 

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

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: uCMDB: orm file and root_container

Jump to solution

root_container is an attribute used when child CI is related to its parent CI using composition relationship. This is 'one to many' relationship, meaning child can have only one parent linked with composition relationship. Composition relationship is defined in CIT Manager for each specific CIT. If that relationship is defined, child CI cannot be created without being related to its parent. For example – CPU CI cannot be created unless you create composition relationship to its parent - Node CI. 

 Root_container is an attribute which holds parent Cis ID. This way UCMDB makes sure there can be only one parent, and this attribute is used as key attribute which makes it mandatory. That prevents creation of Cis without the parent – for example CPU will not be created, because UCMDB will seek for a value for root_container, and unless you define Composition relationship to a parent, it won't find that value.

 

This attribute exists on all CIT, but not used on all of them. Only CIT which have composition relationship valid, and they are defined as child CIT, only those would use root_container attribute.

I think you need to go to CIT manager and take a look at valid relationships defined for you CIT. Lets make sure that root_container is in use at all.

 

If you are looking for example, take a look at the SM integration, the part that handles Interface CIT.

View solution in original post

0 Likes
1 Reply
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: uCMDB: orm file and root_container

Jump to solution

root_container is an attribute used when child CI is related to its parent CI using composition relationship. This is 'one to many' relationship, meaning child can have only one parent linked with composition relationship. Composition relationship is defined in CIT Manager for each specific CIT. If that relationship is defined, child CI cannot be created without being related to its parent. For example – CPU CI cannot be created unless you create composition relationship to its parent - Node CI. 

 Root_container is an attribute which holds parent Cis ID. This way UCMDB makes sure there can be only one parent, and this attribute is used as key attribute which makes it mandatory. That prevents creation of Cis without the parent – for example CPU will not be created, because UCMDB will seek for a value for root_container, and unless you define Composition relationship to a parent, it won't find that value.

 

This attribute exists on all CIT, but not used on all of them. Only CIT which have composition relationship valid, and they are defined as child CIT, only those would use root_container attribute.

I think you need to go to CIT manager and take a look at valid relationships defined for you CIT. Lets make sure that root_container is in use at all.

 

If you are looking for example, take a look at the SM integration, the part that handles Interface CIT.

View solution in original post

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.