Service Images for JMS Transport Protocol

This topic describes specific characteristics of service images that are created using the JMS transport protocol.

The following items apply to the request side:

By default, the operation name for the transaction is set to the request channel name defined in the request step in the virtual service model.
The metadata properties that are not grouped with a prefix contain the queue and connection information for the proxy request queue.
The metadata properties that start with liveRequest contain the queue and connection properties for the live request queue.
The channel.name metadata property must match the request channel name defined in the request and live invocation steps in the virtual service model. This property is the only required metadata property on the request side. You can change the virtual service model's request queues as needed, as long as the request channel name remains the same.

The following items apply to the response side:

The metadata properties that are not grouped with a prefix contain the queue and connection information for the proxy response queue.
The metadata properties that start with msg are used to reconstruct the JMS response message and its properties. The only required property is msg.type, which indicates the type of message to send.
The channel.name metadata property must match a response channel name defined in the respond and live invocation steps in the virtual service model. The value specifies the response channel name to be used to send the response to the client. If there is more than one response, the responses can specify different channel names.
The metadata properties that start with liveResponse contain the queue and connection properties for the live response queue.