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.
The following functionality is available with Outbound:
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).
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 model | Transaction management method | Transaction attribute | Transaction support level | ||
---|---|---|---|---|---|
NoTransaction | LocalTransaction | XATransaction# | |||
Outbound | CMT | Required RequiresNew Supports NotSupported Mandatory Never | Y | Y | Y |
BMT | -- | Y | Y | Y |
#: If the resource adapter is included in a J2EE application, XATransaction is not available.
Table 3-44 Transaction attributes that can be specified when a resource adapter is used with Inbound
Used communication model | Transaction management method | Transaction attribute |
---|---|---|
Inbound | CMT | Required# |
NotSupported | ||
BMT | -- |
#: You cannot specify this attribute for the CJMSP resource adapter or FTP inbound adapter.