Show TOC

Outbound CommunicationLocate this document in the navigation structure

Use

The outbound communication contract in the JCA 1.5 standard enables the resource adapter to provide a connection to a client that needs to access an EIS (Enterprise Information System).

Features

The general logic of the outbound communication is almost unchanged since the 1.0 version of the connector architecture. However, the changes in the functions implemented in a resource adapter, as well as the JavaBeans-oriented approach to the adapter development in the 1.5 specification impose some modifications in the implementation of the outbound communication:

  • The javax.resource.spi.ManagedConnectionFactory interface is implemented as a JavaBean - that is, its properties are defined using getter and setter methods.

    The implementation of a ManagedConnectionFactory as a JavaBean improves the ability of tools (for tools that are based on the JavaBeans framework) to manage the configuration of ManagedConnectionFactory instances.

  • The ManagedConnectionFactory JavaBean should be associated to a single resource adapter JavaBean, which is done by the setResourceAdapter() method of the ResourceAdapterAssociation . This association should remain unchanged during the whole lifecycle of the ManagedConnectionFactory JavaBean.

Activities

The development of the resource adapter outbound communication involves implementing interfaces from two packages:

  • javax.resource.cci - this part of the API enables the client-side connectivity to the EIS.

  • javax.resource.spi - this part of the API enables the application server to create the physical connection to the EIS and to access the system-level contracts that provide transaction and security management.