Integrate > Micro Focus UCMDB > Using the ServiceManagerAdapter9.41 Adapter > Standards and Best Practices > Frequently Asked Questions > What is the Purpose of the <container> Element in a Population XSLT File

What is the Purpose of the <container> Element in a Population XSLT File

Out-of-the-box, in the runningsoftware_population.xslt file, there is a container element:

<link direction="incomming" linkType="composition">
     <ci class="node">
         <container tql="SM Computer Population" keyFields="CIIdentifier">
             <linkTql>SM Computer To Software With Composition</linkTql>
             <linkRetrieveCondition>downstreamci.logical.name=&quot;<xsl:value-of select="CIIdentifier"/>
&quot;</linkRetrieveCondition>
              <linkValueFields>upstreamci.logical.name</linkValueFields>
          </container>
      </ci>
</link>
  • In UCMDB, RunningSoftware CIs must exist together with a Root Container (Node), however Service Manager allows RunningSoftware CIs without a Node.
  • The current integration adapter synchronizes CIs and Relationships separately; when populating a RunningSoftware CI, the integration has no chance to check if a relationship exists between the CI and a Node.

With the <container> element, the integration populates RunningSoftware CIs together with a container.