Customization points during invocation channel processing
Invocation channels process outbound integration messages that require a response. The invocation channel request class and the invocation channel response class include several hooks where you can insert code to provide custom logic.
The illustration shows the customization points during inbound and outbound processing of integration messages by using invocation channels.

When a user action in Maximo® Manage starts an outbound integration transaction that requires a response, an invocation channel provides integration processing of requests and responses.
- Request, outbound: User exit class that runs before the external exit class
- Request, outbound: External exit class
- Request, outbound: User exit class that runs after the external exit class
- Response, inbound: User exit class that runs before the external exit class
- Response, inbound: External exit class
- Response, inbound: User exit class that runs after the external exit class
When you configure an external exit or user exit script for the request or the response of an invocation channel, 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.