J2EE Resource Access
Use
The Java Connector Architecture 1.5 provides the following functions:
· Message inflow
· Transaction management and inflow
· Work management (multi-threading)
· Lifecycle management
Since the adapters in the Adapter Framework are based on JCA 1.0, these functions are not available. However, all the functions listed above are required in the Adapter Framework because it must provide communication in the sender and receiver direction.
Features
Interface Overview
Characteristic |
Value |
Name |
AF resource service |
Purpose |
Access to J2EE transaction and thread manager |
Type |
Java library |
Technical name |
Com.sap.aii.af.service.resource |
Certification |
Optional |
Syntax |
See under path: JavaDoc (.\index.html) package com.sap.aii.af.service.rsource |
· Message inflow
Message inflow is described in Message Exchange. Instead of using message-driven beans and coupling using the MessageEndpoint and ActivationSpec mechanisms, the Adapter Framework defines the module processor session Enterprise JavaBean (EJB), which implements the Module interface as the standard end point.
· Transaction management and inflow
The Adapter Framework does not use local or global (XAResource) transaction management. JCA 1.0 does not specify the transactional procedure for the message inflow. Neither does it provide a transaction concept for extending LUWs from a J2EE service to a JCA adapter by using an EJB. However, you must use a transaction concept to implement ExactlyOnce(InOrder).
Therefore, an adapter must access the transaction manager of the J2EE server (javax.transaction.TransactionManager) and control the transactions directly. The procedure is described in Transactions in the Asynchronous Sender/Inbound Message Flow and in Transactions in the Asynchronous Receiver/Outbound Message Flow. See also: Accessing the J2EE Transaction Manager
· Work management
For the message inbound channel in particular, a multi-threading mechanism is required to make it possible to wait for incoming messages in multiple threads. In JCA 1.5 this mechanism is called work management. It is not available in JCA 1.0.
The Adapter Framework allows access to the J2EE thread manager to enable adapters to generate their own threads. See also: Accessing the J2EE Thread Manager
· Lifecycle management
Lifecycle management is particularly important for starting and stopping the inbound processing of adapters. See also: Managing the Lifecycle of a JCA Adapter