Java Exits; User Exit Preprocessing - IBM BJ0NJML - Service And Asset Management Integration Manual

Outbound Customization

Java Exits

User Exit Preprocessing

216
The following figure illustrates the hierarchy of standard Java exit classes for
outbound processing. These Java classes are available to both the publish channel
and the invocation channel.
The hierarchy illustration does not apply to processing rules, XSL, and handler
exits.
Integration processing for publish channel messages can be based on system
events or initiated events by using the Data Export feature. Publish channels
subscribe to these events and receive an event notification when a system
transaction is saved using the business objects.
Publish channels subscribe to these exit events and receive an event notification
when a transaction is saved based on the business objects. An integration XML
message is created based on the publish channel object structure when the Java
exits run. Both the XML message and the business objects can be referenced. The
data in the business object is saved, but not committed, so the Java exit cannot
update the values of the business object.
You can access a business object that is not part of the publish channel object
structure by using any relationship from an object available in the exit. You can
also instantiate a new object from the database as needed. You can use either
option to retrieve additional data from the system. You then can map the data to
the outbound XML message so that it is available to the external systems.
The user exit class has two methods: one exit runs before and one exit runs after
the execution of the channel processing class. In the first user exit, the input is the
XML, as generated by the object structure. If you have an ERP adapter processing
class, use either the preprocessing method or postprocessing method to run your
custom logic depending upon your requirement.
If necessary, you can change data in the message to alter the processing logic in
the publish channel processing class.
Outbound message customization can be done in the first user exit by using the
following method:
public StructureData setUserValueOut(StructureData irData)
This method can perform the following processing:
Validate data
Integration Guide