Hi Vijay Reddy,
"If you want to modify the message payload using an Adapter Engine module, but there is
no standard module that meets your requirements." then you configure customer-specific modules.
A message from the Integration Server arrives in the Adapter Framework and is processed by the messaging service. Based on the receiver information, the corresponding module chain is selected for further processing.
The Adapter Framework contains two default module chains: one for the sender/inbound direction and one for the receiver/outbound direction. You can use these default module chains for the adapter if the entire message processing is executed within the adapter.
You can enhance the default module chains with customer-specific modules.
The module processor controls the steps in the module chain by calling generic and, if defined, adapter-specific modules. The last module in the module chain forwards the message to the adapter. The adapter transfers the message to the connected system.
Message processing in the sender/inbound direction proceeds in a similar way. In this case, the adapter calls the module processor in the form of an EJB 2.0 local session bean and transfers the message object either as an XI message or in its own format. In the case of the latter, the conversion to an XI message must then take place in an adapter-specific module.
Reward Points If helpful
Regards,
Varun Reddy.K
Edited by: Varun Reddy K on Dec 24, 2007 10:28 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.