With inbound communication, an EIS sends 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 Service Endpoint Message Listener interface which forms part of the CCI (Common Client Interface) defined in the JCA specification and, additionally, its own message listener interface for dialog and asynchronous communication (see Interfaces ).
BeanConnect supports the following communication types for inbound communication:
EIS is an UTM application
transactional and non-transactional communication via the OSI-TP protocol (dialog and asynchronous)
non-transactional communication via the UTM socket protocol or RFC1006 protocol (only asynchronous)
EIS is a CICS application
transactional and non-transactional communication via the LU6.2 protocol (asynchronous and dialog communication)
EIS is another application
UPIC application: non-transactional communication via the UPIC protocol (dialog)
- UTM socket client or RFC1006 application: non-transactional communication via the UTM socket protocol or RFC1006 protocol (dialog and asynchronous)
Figure 9: Inbound communication for UTM partners
Figure 10: Inbound communication for CICS partners