IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 48 / 330

Synchronous Inbound Integration Processing
34
Integration Guide
The integration framework inbound integration can process numbers in either
standard or scientific notation.
T
IP To see the processing sequence of multiple object structures associated
with an enterprise service, go to the Add/Modify Additional Object
Structures dialog box in the Enterprise Services application. Look for
the processing order field on the Object Structure Sub-Records table
window.
The Enterprise Service primary object structure is always processed after all
the additional object structures.
If the integration framework creates copies of the enterprise service, the
remaining inbound processing actions apply to each copy of the enterprise
service.
Output
The output of this activity is one copy of the enterprise service per object
structure.
User Exit Preprocessing
Summary
The integration framework applies the custom processing logic in the user exit
class to the enterprise service.
You can use a preprocessing method to manipulate the enterprise service before
any predefined processing takes place.
The predefined services do not provide any user exit classes.
T
IP To see if preprocessing customization exists, go to the Enterprise Service tab in the
Enterprise Services application. If the Enterprise Service Configuration and
Enterprise Service Response Configuration table windows show user exit classes,
check each class file for a preprocessing method value.
The same processing class contains the user exit preprocessing, user exit
postprocessing, and user exit object processing methods.
Output
The following table shows the possible user exit preprocessing outcomes.
Condition Output
No user exit class exists. The existing enterprise service,
unchanged.
The user exit class skips the record
(due to non-applicable data). None; processing ends.
If there are multiple records in one
XML file, the class skips the current
record and processes the next record.
The user exit class stops the record
(due to an error). None; processing ends and an error is
sent to the caller.
The user exit class completes
successfully. The existing enterprise service,
updated.