Updating Existing Converters
Usually this type of customization is useful when the OOTB converter does not take care of mapping all the attributes associated with an object or there are some custom-specific mapping updates. Since it is an object-specific converter change; you have to identify the object-specific converter file (.inn file). Once the converter is identified, various converters need to be updated based on basic user scenarios such as ADD or UPDATE or DELETE of attribute mapping.
Following section defines the steps to be taken in each of these use cases
• ADD : Adding mapping for an unmapped attribute.
◦ Ensure that attribute is not yet mapped. (check resulting exported step file)
◦ Add new EXPRESS X Mapping in converter file
• UPDATE : Updating mapping of an already mapped attribute.
◦ Identify the attribute-specific mapping section.
◦ Add desired mapping updates in the converter file.
• DELETE : Removing mapping of an already mapped attribute.
◦ Identify the attribute-specific mapping section.
◦ Remove the attribute-specific inn file and save it.
Once the converter files have been updated, you must overwrite the existing converter-specific schemas from the EDM database. For information on updating the specific conversion schema, see
Load Schema and
Load Conversion (EXPRESS-X) Schema.
Since update of the converters usually takes place in master replica of EDM™ Database. One has to follow the Configuration steps again to copy the working replicas for same. For details on configuration, please see
EDM Installation and Configuration.
For details on OOTB AP214 Object mapping, please refer
AP214 AIM Mapping.