During outbound communication, an EJB deployed in the application server communicates with a partner application on the EIS side of the connection.
During inbound communication, an EIS sends messages to a message-driven bean in a Java EE application server.
With UTM partners BeanConnect supports the following communication variants:
bidirectional (outbound and inbound) and transactional or non-transactional communication to OLTP applications (On-Line Transaction Processing) via the OSI-TP protocol.
unidirectional (outbound only) and non-transactional access to UTM applications via the UPIC protocol. This access is performed without the involvement of proxies.
Non-transactional, asynchronous inbound communication via UTM-Socket and the RFC1006 protocol (see Inbound communication ).
With CICS partners BeanConnect supports the following communication variant:
bidirectional (outbound and inbound) and transactional or non-transactional access to/from OLTP (On-Line Transaction Processing) applications via the LU6.2 protocol. LU6.2 is a Systems Network Architecture (SNA) protocol that supports both system-to-system communication and system-to-device communication.
In addition, BeanConnect supports non-transactional inbound communication via the proxy with any application which supports one of the protocols: UPIC, UTM-Socket or RFC1006 (see Inbound communication ).