By Steve Chatten

You may often want to map data to/from a non MXES format. This can be achieved by constructing an xslt document to do the translation, and referencing this on the Integration Interface.

Use a mapping tool to generate the xslt document. Some gotcha’s to watch out for:

The Maximo Enterprise Adapter (MEA) will wrap the original inbound message inside a MESSAGE/ER tag structure before it is presented to the xslt document for translation, so you will need to do the same in any sample source xml files you may use in a mapping tool. 
i.e.
<MESSAGE>
<ER>
[Original Message]
</ER>
</MESSAGE>
 

Your translated IR message, will need to carry a root tag of IntegtationPointName rather than IntegrationInterfaceName.
i.e. the translated output should be:
<IntegrationPointName xmlns="http://www.mro.com/mx/integration">
  <Header>
    <SenderID>[ExternalSystemName]</SenderID>
  </Header>
  <Content>
    <IntegrationObjectName>
      <BusinessObjectName>
        <Field1Name>[value1]</Field1Name>
        <Field2Name>[value2]</Field2Name>
      </BusinessObjectName>
    </IntegrationObjectName>
  </Content>
</IntegrationPointName>

Similarily, for outbound messages, the MXES compliant message is wrapped in a MESSAGE/IR tag structure before it is presented to the xslt document for translation, and again, the source root tag will be the IntegrationPointName.
i.e. your source MXES output before translation would look like:
<MESSAGE>
<IR>
<IntegrationPointName xmlns="http://www.mro.com/mx/integration">
  <Header>
    <SenderID>[ExternalSystemName]</SenderID>
  </Header>
  <Content>
    <IntegrationObjectName>
      <BusinessObjectName>
        <Field1Name>[value1]</Field1Name>
        <Field2Name>[value2]</Field2Name>
      </BusinessObjectName>
    </IntegrationObjectName>
  </Content>
</IntegrationPointName>
</IR>
</MESSAGE>