Message Inflow Contract implementation

In the inbound communication model, the EIS initiates all communication to an application. The application can be composed of EJBs (session, entity and message-driven beans) and it can reside in an EJB container.

The figure below shows the process of the inbound communication.

Diagram showing the process of inbound communication.

The inbound communication is supported by Message Inflow contract of JCA1.5.

The table below lists the implementation classes used by SNA JCA LU0 Connector to fulfil the Message Inflow Contract:

Table 1. Message Inflow Contract Implementation of JCA LU0 Connector
Interface Implementation class
javax.resource.spi.ResourceAdapter com.ibm.connector.lu0.Lu0ResourceAdapterImp
javax.resource.spi.work.Work com.ibm.connector.lu0.Lu0Work
javax.resource.spi.ActivationSpec com.ibm.connector.lu0.LU0ActivationSpec
com.ibm.connector.lu0.Lu0MessageListener MDB implementation of application
com.ibm.connector.lu0. LU0XAResource javax.transaction.xa.XAResource