Before you build the MDM JavaBeans library, you export the interconnected JavaBeans components from Master Data Management to a flat XML file with the XMLEncoder function in Java 6 or later. Make sure to include all of the elements that you want to transform with the library.

You use the Developer tool to create the project that contains the transformed files, Mappers, and schemas.

After you build the library, you can use the transformed files in an external tool or import them back to Master Data Management as model schemas. You can also transform the hierarchical XML files back to flat JavaBeans files with the XMLDecoder function in Java 6 or later.

The following table describes the files that are generated after the library processes the files:

File Name	DeScription
MDMJavaBeans.xml	Source XML file from Master Data Management.
<project_name>_MDMJavaBeans.xsd	Source XSD schema from Master Data Management.
input.xml	Output XML file to use as the input XML file for mappings.
<project_name>_<schema_root_name>.xsd	Output XSD schema.
<project_name>_From_MDMJavaBeans_To_XML.tgp	Script that transforms the source MDM JavaBeans file to the output XML file.
<project_name>_To_MDMJavaBeans.tgp	Script that transforms the output XML file to an MDM JavaBeans file.
<project_name>_From_MDMJavaBeans_UserDefined_Mapper.tgp	Script template for mapping the input.xml file to other message types.
<project_name>_To_MDMJavaBeans_UserDefined_Mapper.tgp	Script template for mapping other message type to the input.xml file.

After you transform the MDM JavaBeans file, you can use the MDM Mappers library to translate between the output XML file and an ACORD LNA file. You use the Developer tool to import and run the MDM Mappers. For more information about the MDM Mappers library, see MDM Mappers Library.