3.13.2 Functionality available for other resource connections

This subsection describes the functionality that can be used with Application Server from among the functionality provided in Connector 1.5. The available functionality varies for Outbound and for Inbound. For details on the Application Server functionality available with the resource adapters conforming to the Connector 1.5 specifications, see 3.3.4 Resource adapter functionality.

Organization of this subsection
(1) Functionality available with Outbound
(2) Functionality available with Inbound
(3) Mapping the usage and transaction levels of the resource adapters

(1) Functionality available with Outbound

The following functionality is available with Outbound:

(2) Functionality available with Inbound

With Inbound, you can use Non-Transacted Delivery (message delivery in which the EIS does not participate in the transaction) and Transacted Delivery (message delivery in which the EIS participates in the global transaction of Application Server).

Reference note
Transaction inflow (message delivery in which the invocation of the Message-driven Bean participates in the EIS transaction) is only supported by the TP1 inbound integrated function.

(3) Mapping the usage and transaction levels of the resource adapters

The following table describes the transaction levels that can be specified when a resource adapter is used with Outbound.

Table 3-43 Transaction levels that can be specified when a resource adapter is used with Outbound

Used communication modelTransaction management methodTransaction attributeTransaction support level
NoTransactionLocalTransactionXATransaction#
OutboundCMTRequired
RequiresNew
Supports
NotSupported
Mandatory
Never
YYY
BMT--YYY
Legend:
Y: Available
--: Not applicable

#: If the resource adapter is included in a J2EE application, XATransaction is not available.


Hint
The following table describes the transaction attributes that can be specified when a resource adapter is used with Inbound.

Table 3-44 Transaction attributes that can be specified when a resource adapter is used with Inbound

Used communication modelTransaction management methodTransaction attribute
InboundCMTRequired#
NotSupported
BMT--
Legend:
--: Not applicable

#: You cannot specify this attribute for the CJMSP resource adapter or FTP inbound adapter.