BeanConnect supports both BeanConnect-specific interfaces and standard interfaces in accordance with the JCA specification. This section presents an overview of the interfaces for outbound and inbound communication.
Detailed information on the programming interfaces can be found in Interfaces and programming .
Interfaces for outbound communication
During outbound communication, an EJB deployed in the application server communicates with a partner application in the EIS system. This EJB can communicate with EIS partners via interfaces in the following packages.
net.fsc.jca.communicationThe interfaces combined in the package
net.fsc.jca.communicationdefine proprietary BeanConnect-specific communication interfaces. These support different programming modes (like send/receive and call) and provide access to the functions supported by the underlying communication protocol.net.fsc.jca.communication.cciThe Common Client Interface (CCI) is defined in the JCA specification. It describes a standard client API and primarily addresses the requirements of developing application development tools and EAI frameworks (Enterprise Application Integration). Compared with the BeanConnect-specific API, the CCI provides a restricted functional range.
Interfaces for inbound communication
With inbound communication, an EIS can send messages to a message-driven bean application in a Java EE application server.
The message-driven bean must implement a resource-adapter-specific message listener interface.
BeanConnect supports the following message listener interfaces:
net.fsc.jca.communication.AsyncOltpMessageListenerBeanConnect-specific interface for asynchronous communication
net.fsc.jca.communication.OltpMessageListenerBeanConnect-specific interface for dialog communication
javax.resource.cci.MessageListenerCommon Client Interface (CCI) for dialog communication
A message-driven bean which implements one of the first two message listener interfaces is called an OLTP message-driven bean.