Message Flow from the Sender
The graphic below shows the message flow from the sender to the Integration Server.

The message flow from the sender system to the Integration Server involves the following steps:
· A message from an external system is transferred to the JCA resource adapter (JCA RA).
· The JCA resource adapter calls either the module processor of the Adapter Framework (AF MP) directly or it calls its own conversion Enterprise JavaBeans first.
· In any event, the message must go through the module processor to ensure that the module interfaces are taken into account.
The module processor is called in the same way as the individual Adapter Framework modules, that is, it implements the Module-, ModuleContext-, ModuleData-, and ModuleException-interfaces.
· You can use adapter-specific Adapter Framework modules, either before or after message transfer to the Adapter Framework messaging service (AF MS). The Adapter Framework provides the CallSapAdapter module for this purpose. This is always the last module in the module processor. Before this module is called, the adapter or its modules must convert the message to a Java object that implements the XIMessage interface.

Use the Adapter Framework message factory to create these messages.
· Finally, the Adapter Framework messaging service (AF MS) receives the message and saves it (if it is sent asynchronously) or sends a response message (if it is transferred synchronously). Adapter-specific modules can be called on the way back to the JCA resource adapter.