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

Java Exits

User Exit Preprocessing

Integration Framework Customization with Java and XSL
Log the transaction
You identify this class in the Cron Task Setup application in the Configuration
module.
The following figure illustrates the hierarchy of standard Java exit classes for
inbound processing. These Java classes are available to the enterprise service.
The hierarchy illustration does not apply to processing rules, XSL, or interface
table exits.
When the preprocessing, processing, and postprocessing Java exits are run, the
business objects for the enterprise service message have not been created. The
business object user exit only can take a processing action against the business
objects that are created for the incoming message. However, in all exits you can
instantiate a new object from the database to perform lookups or gather
additional system information as part of your custom logic.
The user exit class consists of two methods: one exit runs before and one exit runs
after the enterprise service processing class. If you have an ERP adapter that
provides a processing class, your user exit logic can be implemented to run before
or after the ERP adapter logic.
In the first user exit, the input is the XML message that is delivered from the
external system. If necessary, you can change data in the message that affects the
processing logic in the processing class.
Inbound transaction customization can be done in the first exit using the
following method:
public StructureData setUserValueIn(StructureData erData)
This method can perform the following processing:
Validate data
Change external data by changing the ER record before it is mapped to
the IR record and saved in the system
Inbound Customization
225