Using the CA Repository Universal XML Exchange Control File Builder › How the CA Repository Universal XML Exchange Control File Builder Edits an Existing Control File

How the CA Repository Universal XML Exchange Control File Builder Edits an Existing Control File

The following procedure explains how the CA Repository Universal XML Exchange Control File Builder edits an existing control file and uses different objects to store different XML elements.

1. An existing control file is parsed using a Xerces implementation. The Xerces module loads all the information of the existing control file into the primary memory for modifying (adding, editing or deleting) the elements.
2. After specifying an input control file, the CA Repository Universal XML Exchange Control File Builder parses the XML file and retrieves data using tag names that are stored in the objects. It validates the control file with the DTD. If there are any errors in the control file, the CA Repository Universal XML Exchange Control File Builder displays the errors in a dialog.
3. The CA Repository Universal XML Exchange Control File Builder uses different objects to store different XML elements:
   • IdRule value is stored in IdRuleObject.
   • LinkRules are stored in LinkRuleObject, which in turn holds a list of LinkRule.
   • ObjectMaps are stored in ObjectMapsObject, which holds the list of Object Maps.
   • Relationships are stored in RelationShipsObject, which holds the list of relationships.
   • Mappings are stored in MappingsObject, which holds the list of Mappings.

     Note: The CA Repository Universal XML Exchange Control File Builder sets all the objects and their respective values specified in the input XML control file. If no values are specified in the input XML control file, objects are loaded with their default values.