Outbound communication with XATMI partners

You need to take account of the following special characteristics if you program outbound communication with XATMI partners:

• Transaction management

  The transaction environment in the user program and the transactional property of the ConnectionFactory determines whether communication with the partner application is performed with or without Commit FU (TRAN or NOTRAN in XATMI).

• typed buffer

  Only typed buffers of type X_OCTET are supported.

• Message length and message segments

  When the OLTP message interface is used, a message segment in a message sent to an XATMI partner may be a maximum of 32,000 bytes in length. Longer message segments are rejected by means of an OltpMessageException. The same restriction to 32,000 bytes per message segment applies to all the EIS connection interface methods for which the restriction for other partners is 32,767 bytes.

  Messages to XATMI partners in request/reply mode may only consist of one message segment and this may be a maximum of 32,000 bytes in length.

  Messages to XATMI partners in conversational mode may consist of more than one message segment. Each of these message segments may be up to 32,000 bytes in length.

  Messages passed to BeanConnect via interface methods for which there is no message length restriction, e.g. sndRecord(String) are fragmented by BeanConnect into message segments of a maximum of 32,000 bytes in length during communication with XATMI partners in conversational mode. In the case of XATMI partners in request/reply mode, messages with a length of more than 32,000 bytes are rejected with an exception.

• The reception of a FAILURE_RI is indicated to an application by means of an EISConnectionException.

• For XATMI partners, the default value of the communication property endConversation is always false.