Unless otherwise specified, the following limitations apply to
both SOAP and Non-SOAP message types:
- If you use two different execution groups, one for the HTTP request
flow and one for the HTTP response flow, the correlation between message
flow instances cannot be maintained. In this case, only the request
message flow instance is monitored.
- The ability to monitor services by the remote host name or IP
address form of Requester Identity is supported only for WebSphere® Message Broker version 6.1.0.2
or later. In WebSphere Message
Broker version 6.0.0.5, no requester identity or remote host name
and IP address is available in the WebSphere Message
Broker HTTP transport protocol.
- For a server-side message flow, if the correlation information
between the request and response expires, the response flow fails
to find the context for the request flow. In this case, the response
message is ignored, and the message metric and content information
for the response is not written to the log files.