Working with CA Catalyst Reconciliation › How to Perform CA Catalyst Reconciliation › Configure Existence Policy

Configure Existence Policy

Existence policy controls the domain managers that the Reconciler uses as a source of truth to detect whether to delete a CI from the Persistent Store that has been deleted from a source domain manager. By default, CA Catalyst never deletes a reconciled CI from the Persistent Store. You can edit existence policy in the sourceoftruthmdr.xml file to specify a primary and secondary source of truth and a non-source of truth to use for this calculation.

For example, consider a CI that is managed in CA NSM, CA Spectrum, and CA CMDB. If CA CMDB is set as the primary source of truth in existence policy and the CI is deleted from CA CMDB, the Reconciler deletes the CI from the Persistent Store, despite its continued existence in CA NSM and CA Spectrum.

Follow these steps:

1. Access the CA Catalyst Registry.
2. Navigate to the following location: /topology/physical/node0/sor/sourceoftruthmdr.xml.
3. Click Edit as text.
4. Enter entries for the following sections as necessary and click Save Content:

   <tns:PrimaryST>

   Defines the primary source of truth for CI existence. If a CI managed by this connector is deleted in the source domain manager, CA Catalyst deletes it from the Persistent Store.

   <tns:SecondaryST>

   Defines the secondary source of truth for CI existence. If a CI managed by this connector is deleted in the source domain manager, CA Catalyst deletes it from the Persistent Store unless it still exists in any primary source of truth.

   <tns:NonST>

   Defines the non-source of truth for CI existence. If a CI managed by this connector is deleted in the source domain manager, CA Catalyst deletes it from the Persistent Store only if it does not exist in any domain managers listed as primary or secondary sources of truth.

   You can define multiple sources of truth in each section, as long as specific instances appear in only one of the sections. When sections contain multiple sources of truth, a connector needs to match only one source of truth to trigger the appropriate action.

   Use the following format to define a source of truth:

   <tns:MdrProduct>MdrProduct</tns:MdrProduct>
   <tns:MdrProductInstance>MdrProductInstance</tns:MdrProductInstance>
   

   MdrProduct

   Defines the MdrProduct USM property value for the connector whose domain manager to use as a source of truth. All connectors have a registered MdrProduct value that is a five-digit number with a prefix of 'CA:'. The Connector Guide contains a table of all registered MdrProduct values.

   MdrProductInstance

   Defines the MdrProductInstance USM property value for the domain manager system to use as a source of truth. This value is typically the server name associated with a specific instance of the domain manager defined in the MdrProduct property.

   Important! The input string for this property is case sensitive.

5. Restart the CA SAM Application Server service.

Example: Multi-domain existence policy

The following example illustrates an existence policy with multiple domains and instances defined in each section:

<tns:SourceOfTruthMdr xmlns:tns="http://ns.ca.com/catalyst/2010/02/sourceoftruthmdr"
xmlns:usm-core="http://ns.ca.com/2009/07/usm-core">
       <tns:PrimaryST>
              <tns:MdrID>
                     <tns:MdrProduct>CA:00020</tns:MdrProduct>
                     <tns:MdrProdInstance>cmdbserver</tns:MdrProdInstance>
              </tns:MdrID>
              <tns:MdrID>
                     <tns:MdrProduct>CA:00020</tns:MdrProduct>
                     <tns:MdrProdInstance>cmdbserver2</tns:MdrProdInstance>
              </tns:MdrID>
       </tns:PrimaryST>
       <tns:SecondaryST>
              <tns:MdrID>
                     <tns:MdrProduct>CA:00003</tns:MdrProduct>
                     <tns:MdrProdInstance>nsmserver</tns:MdrProdInstance>
              </tns:MdrID>
              <tns:MdrID>
                     <tns:MdrProduct>CA:00004</tns:MdrProduct>
                     <tns:MdrProdInstance>specserver</tns:MdrProdInstance>
              </tns:MdrID>
       </tns:SecondaryST>
       <tns:NonST>
              <tns:MdrID>
                     <tns:MdrProduct>CA:00031</tns:MdrProduct>
                     <tns:MdrProdInstance>scomserver</tns:MdrProdInstance>
              </tns:MdrID>
              <tns:MdrID>
                     <tns:MdrProduct>CA:00002</tns:MdrProduct>
                     <tns:MdrProdInstance>5ehserver/tns:MdrProdInstance>
              </tns:MdrID>
       </tns:NonST>	
</tns:SourceOfTruthMdr>

Based on this example, the Reconciler determines reconciled CI existence in the Persistence Store as follows:

• Deletes the reconciled CI when the projection CI is deleted in the CA CMDB servers cmdbserver and cmdbserver2.
• Deletes the reconciled CI when the projection CI is deleted in the nsmserver CA NSM instance or the specserver CA Spectrum instance if the CI is not reported from either of the CA CMDB servers listed in the primary source of truth section.
• Deletes the reconciled CI when the projection CI is deleted from the scomserver Microsoft SCOM instance or ehserver CA eHealth instance if the CI is not reported from any of the instances listed as primary and secondary sources of truth.