IBM BJ0NJML Integration Guide - Page 250

Predefined Service and Channel Modifications All request and response processing classes and user exits have access to the invocation channel request and response objects by using the IntegrationContext.getCurrentContext() API. Endpoint The endpoint definition identifies how an invocation channel routes outbound data to a specific location. Invocation channel endpoints can be modified by using the IntegrationContext.getCurrentContext().getProperty(MetaDataPropert ies.ENDPOINTPROPS) API. You can use this class when no endpoint is specified on the invocation channel. The endpoint name can be passed when the invocation channel invokes the API. The endpoint name can also be set in the class by using the integration context. You must set the context API to IntegrationContext.getCurrentContext().setProperty(MetaDataPropert ies.ENDPOINT,). Predefined Service and Channel Modifications Rather than create a service or channel, you can duplicate predefined services and channels, and then modify the duplicate record. You can work with the service configurations to redefine the following characteristics: T Classes T Event filtering T XSL files T Processing rules You can work with the channel configurations to redefine the following characteristics: T Classes T Extensible Stylesheet Language (XSL) files T Processing rules Your modified definitions determine the data source and how the service and channel handle customized data processing, filtering, and mapping. Creating an External System You can create an external system and associate the applicable services and channels with it. 236 Integration Guide