Communication with other applications

Any other applications used in conjunction with the adapter must adhere to the message layout rules.

The WebSphere MQ messages created and accepted by the bridge component of the adapter consist of a WebSphere MQ MQMD header followed by the message body. No additional headers or message elements are allowed.

Event notification messages

The following event notification message fields of the MQMD header are set by the bridge component of the adapter for event notification messages.

Table 32. Event notification messages

Field Description Values
Format Message format There are three values:
  • INSERT, if the event indicates the creation of a new FRONT ARENA object.
  • UPDATE, if the event indicates the modification of an existing FRONT ARENA object.
  • DELETE, if the event indicates the deletion of an existing FRONT ARENA object.
Persistence Message persistence MQPER_AS_Q_DEF
UserId User ID of message creator If a user ID was supplied in the bridge configuration, this value is inserted. Otherwise, the ID that the program is running under is inserted.
Note:
As seen in Table 32, the FORMAT field is not filled with a predefined WebSphere MQ value, but with the type of operation that caused the originating FRONT ARENA notification to be issued. This piece of information is needed by the Adapter for RONT ARENA which can be used in conjunction with the bridge. As a result, code page and encoding conversion is not supported. The message body contains the FRONT ARENA message read from the AMB - without any modifications.

Request messages

The message body must contain a FRONT ARENA AMB message with all the pieces of information available that the FRONT ARENA application needs to perform the request.

The following header fields of the MQMD header must be set for request messages sent to the bridge component of the adapter.

Table 33. Header field description and value

Field Description Value
MessageId Message identifier A unique identifier generated by WebSphere MQ when the message is created.

Reply messages

The following fields of the MQMD header are set by the bridge component of the adapter in a reply message.

Table 34. Header field descriptions and values

Field Description Values
CorrelationId Message correlation ID Filled with the message ID of the corresponding request message.
MessageType Message type MQMT_DIAGRAM
Feedback Feedback code See the table below, Table 35.

All other header field values are copied from the corresponding request message, except for the message ID, which is newly generated.

Table 35. Adapter feedback codes and descriptions

Adapter feedback code Description
MQFB_PAN The INSERT or SELECT request processing was successful.
MQFB_APPL_FIRST + 2 The UPDATE or DELETE processing was successful.
MQFB_APPL_FIRST + 4 SELECT request: No hit.
MQFB_APPL_FIRST + 6 SELECT request: Multiple hits.
MQFB_NAN Request processing failed.
Note:
The feedback codes seen in Table 35are expected by the adapter.

The the message body contains the following parts:

Copyright IBM Corp. 1997, 2004