Importing Output Maps Metadata

You can import the metadata for output map in two ways:

  • Along with the metadata import of the repository.
  • Independent of the metadata import of the repository.

Prerequisites

  • For importing metadata for a custom output map, ensure that the synchronization format and the repository referred to in the response XML exist on the target company.
  • For importing metadata from a predefined output map, ensure that the synchronization format referred in the response XML exists on the target company.

Procedure

  1. Importing Metadata Independent of the Repository
    1. User the Response file generated from the metadata export of a output map to import metadata.

      To alter the metadata of exported entities to avoid duplication or loss of metadata in the target company, you can perform the following. However, this is not recommended.

    2. Extract the response XML from the metadata response JAR file, and edit this file.
    3. You can add new attributes to predefined as well as custom output map definitions. To do so, update the response XML extracted from the JAR file generated by the copy metadata export operation for the output map.
    4. You can also add new attributes to existing output map definitions by adding XML elements to the response XML.
    5. You can also change attribute definitions. For example, change the following attribute value in any attribute definition:

         <Attribute name="dataType" type="string">DATE</Attribute> 
   <!—changed from VARCHAR2 to DATE-->

      However the new attribute added in the XML must also be available in the referred synchronization format.

    6. If you want to add new Output maps (custom/predefined), change name of that map as follows in the XML element ExternalKeys of the output map and in EntityData > Attribute (name): 
         <ExternalKeys>
       <Key name="name" type="string">GS1</Key>
   </ExternalKeys>
   <EntityData>
   <Attribute name="name" type="string">GS1</Attribute>
    7. You can also manually create response XML; ensure it is valid per the DataService Schema.
    8. After making all required changes to the response XML, JAR it back to the source JAR file.
    9. You can also use the response XML without un-jarring it.
  2. Importing Output Maps Metadata with Cross-repository Relationships
    1. When a OutputMap is exported as a part of a MasterCatalog Entity or as an Independent Entity, related OutputMaps are also exported in the Response XML.
    2. For the Given OutputMap Entity within a Command Object, the Response XML would have multiple Entities within the same Command if the OutputMap Entity being exported has related OutputMaps.