Inbound communication with UTM partners

For inbound communication with an UTM partner, BeanConnect supports the communication protocol OSI-TP (transactional or non-transactional) as well as transport-level protocols such as RFC1006 or the UTM-socket protocol, all of which are non-transactional protocols.

The configuration of the UTM partner application needs to be adapted properly in order to be able to call an OLTP message-driven bean.

You can call an OLTP message-driven bean for asynchronous communication using the OSI-TP protocol or a transport-level protocol. You can call OLTP message-driven beans for dialog communication using the OSI-TP protocol.

• Connections to BeanConnect for communication using the OSI-TP protocol can be configured with the Management Console (see Configuration of BeanConnect ).

• Connections to BeanConnect for communication using a transport-level protocol must be configured in the EIS (see Adapting the configuration in the EIS partner ). The Management Console does not support the configuration of these connections.

• An LTAC must be configured in the EIS for each OLTP message-driven bean to be called using the OSI-TP protocol. The RTAC name assigned to this LTAC must be identical to the inbound service name of the inbound message endpoint which has been assigned to this EJB at the time of deployment.

• The encoding of the user messages is determined on deployment of the OLTPmessage-driven bean (activation-config properties encodingActive and encoding, see Configuration properties in the ejb-jar.xml ) or on the configuration of the inbound service, see Configuring inbound services .

The handshake functional unit of OSI-TP must not be used in communication with OLTP message-driven beans.

The messages sent by an UTM partner application to an OLTP message-driven bean may consist of one or more message parts. Each message part can be read separately by the OLTP message-driven bean. Likewise, the OLTP message-driven bean may assemble the reply message from several message parts which are to be read by the UTM partner application with a sequence of MGET NT calls.

For details see Program framework using the interfaces AsyncOltpMessageListener and OltpMessageListener .

If you use the transport-level protocol to call an OLTP message-driven bean, the first message part sent to this bean must be prefixed with the service name that was assigned to the message endpoint corresponding to this EJB at the time of deployment.

You can find further information in the openUTM documentation.