Inbound communication with other EIS partners (openUTM)

For inbound communication, BeanConnect supports the following EIS partners other than TM or CICS:

• UPIC partners

• Transport-system partners such as RFC1006 partners or UTM-socket partners

The following rules apply for communication using the UPIC protocol or transport-level protocols (RFC1006 or the UTM-socket protocol), all of which are non-transactional protocols:

• UPIC partners can only be used to call OLTP message-driven beans for dialog communication. UPIC message parts are mapped onto OltpMessagePart objects and vice versa.

• 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 inbound service name that was assigned to the message endpoint corresponding to this EJB at the time of deployment.

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