Enterprise services provide asynchronous and synchronous processing of inbound integration messages. You can insert code to provide custom logic to the Java™ request processing class for inbound processing and to the Java response processing class for outbound processing.
The illustration shows the customization points during the inbound and outbound processing of integration messages by using enterprise services.
For asynchronous messages that do not require a response, an external service opens a connection to send an enterprise service request. When the request is validated, the message is dropped into a JMS queue for enterprise services processing. For synchronous messages that require a response, the external service maintains a continuous connection during the transaction until the response is received.
- Insertion points for inbound asynchronous processing:
- Request, inbound: User exit class that runs before the external exit class
- Request, inbound: External exit class
- Request, inbound: User exit class that runs after the external class
- Insertion points for inbound synchronous processing, where a response
is required:
- Request, inbound: User exit class that runs before the external exit class
- Request, inbound: External exit class
- Request, inbound: User exit class that runs after the external class
- Response, outbound: User exit class that runs before the external exit class
- Response, outbound: External exit class
- Response, outbound: User exit class that runs after the external class
When you configure an external exit or user exit script for the request or the response of an external service, a predefined Java class is inserted that runs the script. The predefined classes are the com.ibm.tivoli.maximo.script.ScriptExternalExit class and the com.ibm.tivoli.maximo.script.ScriptUserExit class. You cannot implement a script and a Java class at the same processing point. If you attempt to create a script on a processing point where a Java class is configured, you cannot save the script.