OLTP message-driven beans are the types of JCA-like message endpoint applications supported by BeanConnect. An EIS application can call OLTP message-driven beans deployed in an application server via BeanConnect.
In order to communicate with an OLTP message-driven bean, an EIS application sends a message to a service known to BeanConnect. BeanConnect then passes the message to an OLTP message-driven bean configured for the message endpoint name that is associated with this service name. The connection between the service name and the message endpoint name is established by the Management Console (see "Inbound Message Endpoints" in Managed objects ).
BeanConnect supports two types of OLTP message-driven beans:
OLTP message-driven beans for dialog communication
An OLTP message-driven bean for dialog communication receives messages from an EISapplication and returns messages. The related BeanConnect-specific interface is net.fsc.jca.communication.OltpMessageListener. The CCI interface javax.resource.cci.MessageListener also matches the requirements for dialog communication.
These interfaces enable an OLTP message-driven bean to receive a message from and send a reply message to the EIS application. The messages may contain one or more message parts.
OLTP message-driven beans for asynchronous communication
An OLTP message-driven bean for asynchronous communication can receive a message from an EIS application, but is not allowed to send a reply message. The associated BeanConnect-specific interface is net.fsc.jca.communication.AsyncOltpMessageListener. The message from the EIS application may contain one or more message segments.