Integration Framework - Using XSLT to transform inbound transactions

Answer

There are two ways to achieve this:

1 - Writing a custom UserExit: A UserExit is a JAVA class written to apply extra logic on MIF.

2 - Using XSLT: ( EXtensible Stylesheet Language Transformation) can be used to transform the inbound message when it arrives MIF. This does not require any code customization.

As Maximo has its own schema, we need to have the external schema reference to create a XSL file to convert it.

For this example, the standard MXASSETInterface will be used to update an existing ASSET description.

IMPORTANT: The XSL creation will not be covered in this Technote as it is beyond the scope of Maximo support. Its creation requires either XSL skill or a third party tool to automatically convert the schema.

Sample XSL ( for demonstration only )


sample1.xsl

Enterprise Service Settings:

In order to use the XSL to transform the inbound message, it needs to be associated with the Enterprise Service:

1 - Copy the XSL file to [MEA_GLOBAL_DIR]\schema\external folder.

If the external folder does not exist, it needs to be created.

2.1 - Check the "Use External Schema?" option so both "XSL Map" and "Split Tag" fields will turn editable.

2.2 - In the "Split Tag" field, set its value as "MPCDocument" which is the main element from the external schema.

2.3 - In the "XSL Map" field, set the path to the XSL file as specified in Step 1.

Sample XML to be Imported ( A new ASSET record will be created as MPC1 )

ASSET.xml