J2C inbound processes
You can create a Java™ application that uses the Java connector tools to create applications that use inbound transactions.
Inbound processes
JCA 1.0 did not provide a mechanism for inbound communications from EISs to application servers, such as asynchronous message delivery or event notification. Inbound event processing means that the adapter polls the enterprise server at specified intervals for events. When the adapter detects an event, it converts the event data into a business object and sends it to the client application. For example, the client application might want to know about a change to the data on the enterprise server. You can generate a J2C Bean that listens for such events on the enterprise server and notifies client applications with the update. In this case, the interaction begins at the enterprise server.
Support for inbound communication was added in JCA 1.5, which provided
system-level contracts including transaction inflow and message inflow
to support bi-directional communications between Java EE applications and EISs:
- Transaction inflow contract: allows an application server to process an imported transaction propagated from a resource adapter, and ensure that the properties of the imported transaction are preserved.
- Message inflow contract: allows a resource adapter to send asynchronous messages to the message endpoints of the application server, regardless of the messaging style, semantics, or delivering infrastructure.