User Bridge Development
If the user (or professional services) desires, a customer-specific bridge can be developed and used the same as is describe in “Importing XML Through the GUIs” on page 256.
To accomplish this, the user will need to develop an XSLT file to translate their XML into MetaXML schema, the same as the CWM_MetaXML.xslt does. Also, an MDS metamodel must be identified as the target of the import. This metamodel may be one already pre-defined by MDS (for example, the DatabaseModel or the ClientLoadModel). However, if the XML will be “bridged” into a metamodel not already pre-defined by MDS, this metamodel will need to be developed by the user, and made available in XML format. (One easy way to do this is to create the metamodel through MetaBrowse, and then use MetaXML to export it out of the repository.)
The XSLT file and the metamodel XML file (if necessary), must be placed in the MDS installation tools folder the with the other bridge files.
Finally, the user must modify the metatools_cfg.xml and add a <Bridge> element as a child of the <Import><XML> element, the same as the CWM/XMI <Bridge> element. The proper values for the “rootnode” attribute and all the <Bridge> child elements must be included also. (Note that even if the metamodel is already installed in the repository, so an XML file is not needed for it, you must still include an empty AIMXMLFile element or the parse of the metatools_cfg.xml file will fail.)
After this is completed, the user will be able to “point” their MDS GUI “XML…Import” request at their XML file, and have it translated and imported, just the same as for a CWM/XML XML file.