BeanConnect-specific interfaces and Common Client Interface (CCI)

BeanConnect offers two different sets of interfaces:

• BeanConnect-specific interfaces

• Common Client Interface (CCI)

Recommendations: BeanConnect-specific interfaces or CCI

The Common Client Interface (CCI) is defined in the JCA specification of Oracle^TM. The CCI defines a standard API and addresses primarily the needs of application development tools and EAI Frameworks (Enterprise Application Integration). If you are familiar with the CCI in the JCA specification, it makes sense to use the CCI.

In any other case it is advisable to use the BeanConnect-specific interfaces, because the associated programming effort is considerably reduced.

Differences between the BeanConnect-specific interfaces and CCI

For outbound communication, BeanConnect-specific interfaces and the CCI offer virtually the same functionality.

For OLTP communication with UTM partners and for CICS partners, the BeanConnect-specific EISOltpConnection interface and the CCI offer the identical functionality.
The BeanConnect-specific EISUpicConnection interface merely provides additional functionality for UPIC connections to UTM partners (see "Additional functionality provided by the EISUpicConnection interface" in Connection interfaces (overview) ).

For inbound communication, the BeanConnect-specific OltpMessageListener interface and the CCI offer the same functionality for dialog communication. Additionally, BeanConnect provides the AsyncOltpMessageListener interface for asynchronous communication.

Selecting the interfaces to be used

For outbound communication, you specify the interface to be used as follows:

• In the application server-specific deployment descriptor file weblogic-ra.xml of the resource adapter, you specify the connection factory interface in the <connection-factory-interface> entry:

  • For the BeanConnect-specific interfaces:

    net.fsc.jca.communication.EISOltpConnectionFactory or
    net.fsc.jca.communication.EISUpicConnectionFactory (only if the EIS partner is an UTM application)

  • For CCI:

    net.fsc.jca.communication.cci.BCOltpConnectionFactory or
    net.fsc.jca.communication.cci.BCUpicConnectionFactory (only if the EIS partner is an UTM application)

• In the deployment descriptor file ejb-jar.xml of an EJB, you specify the connection factory interface in the <res-type> entry:

  • For the BeanConnect-specific interfaces:

    net.fsc.jca.communication.EISOltpConnectionFactory or net.fsc.jca.communication.EISUpicConnectionFactory

  • For CCI:

    net.fsc.jca.communication.cci.BCOltpConnectionFactory or
    net.fsc.jca.communication.cci.BCUpicConnectionFactory

For inbound communication, you specify your favored interface in the deployment descriptor file ejb-jar.xml of the message-driven bean.

You specify the interface in the <messaging-type> entry:

• For the BeanConnect-specific interfaces:

  net.fsc.jca.communication.AsyncOltpMessageListener or
  net.fsc.jca.communication.OltpMessageListener

• For CCI:

  javax.resource.cci.MessageListener