Xsl Mapping; Handler Exits - IBM BJ0NJML - Service And Asset Management Integration Manual

Outbound Customization

XSL Mapping

Handler Exits

218
The following method can perform the noted processes:
Validate data
Change data by changing the ER record to be sent to the external
system
Map additional data from the IR to the ER
Stop the transaction from being saved in database by throwing a
system exception
Stop the message from being sent to the external system by throwing a
SKIP_TRANSACTION exception
Log the transaction
You identify the publish channel user exit class on the Publish Channel tab in the
Publish Channels application.
The framework provides a placeholder to implement an XSL file. You can use the
XSL file to manipulate the data that is sent to the external system after the Java
exit processing completes.
The XSL file is always called with the ER XML message. You identify the publish
channel XSL mapping on the Publish Channel tab in the Publish Channels
application.
The XSL file can be part of the EAR file and must reside in the businessobjects/
classes/. . . folder structure. You also can define the XSL file on a publish channel
by using a directory file path that is not part of the EAR file.
Register the XSL file mapping in the following manner when the XSL file
mapping.xsl resides in the businessobejcts/classes/psd/iface/xsl folder.
psdi.iface.xsl.mapping
The .xsl extension is omitted when the mapping.xls 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.
Multiple predefined methods (handlers) are provided so that you can send data
to an external system, including HTTP, Enterprise JavaBean (EJB) call, and
interface tables. Some of these methods have user exit placeholders available for
customization.
Integration Guide