Xsl Mapping - IBM BJ0NJML - Service And Asset Management Integration Manual

XSL Mapping

Integration Framework Customization with Java and XSL
The following method can perform the noted processes:
Validate data
Change external data by changing IR record to be saved in the system
Map additional data from the ER to the IR
Stop further processing of the transaction throwing an exception
In this case, the transaction remains in the queue to be retried.
Stop the message from being sent to the external system by throwing a
skip_transaction exception
In this case, the message is not saved in the system; the message is
removed from the queue.
Log the transaction
You identify the enterprise service user exit class on the Enterprise Service tab in
the Enterprise Services application.
The Java user exits also provide an exit point that runs just before the object is
saved in the system.
The enterprise service has a placeholder to implement an XSL file and to
manipulate the data to be set to the object structure after the Java exit processing
is completed.
The XSL file is always called with the XML message that is output from the Java
exit processing. You identify the XSL file on the Enterprise Service tab in the
Enterprise Services application.
The XSL file can be a part of the EAR and must be under the businessobjects/
classes/. . . folder structure. The XSL file can also be referenced using a directory
file path which is not part of the application EAR file.
For example, use the following reference to register the XLS when the file
mapping.xsl is under the businessobejcts/classes/psd/iface/xsl folder:
psdi.iface.xsl.mapping
The .xsl extension is omitted when the mapping.xsl is registered.
Register the XSL file mapping in the following manner when the XSL file
mapping.xsl is located in a file directory that is accessible by the application
server. The format is specific to the operating system.
c:/psdi/iface/xsl/mapping.xsl
The .xsl extension is not omitted when the mapping.xls is registered.
Inbound Customization
227