1

A flow or Java service, typically invoked by an Integration Server client, initiates the Get service on Integration Server.

You configure the Get service, and the wrapping flow or Java service, using Designer.

2

The Get service retrieves a connection from the service's associated connection pool.

You configure and enable the adapter connection using Integration Server Administrator. For more information about connection pooling, including the runtime behavior of connection pools, see Connection Pools.

3

The Get service uses the values from the input signature fields as filter criteria.

You define the Get service's input signature when you configure the service. The fields that you select on the MQMD Header tab in the adapter service become the service's input signature.

The following diagram illustrates the Get service's input signature properties where selectionCriteria fields are copied into the MQMD Header:

4

The Get service retrieves the message from the WebSphere MQ queue. The document, or the properties from the Get service's output signature, contain the retrieved MQMD properties, JMS properties, and the payload.

5

The Get service returns a message to Integration Server that contains output signature properties. You define the Get service's output signature when you configure the service. The fields that you select on the MQMD Header tab and the JMS Properties tab become the service's output signature.

The reasonCode, conditionCode, and errorMsg properties are also returned in the output signature's document.

The following diagram illustrates the Get service's output signature. The MQMessage's payload is mapped to the Get service's msgBody and the MQMD Header fields are copied back to the msgHeader properties: