A number of constraints apply when you use this pattern.
You can use the
Service Facade to WebSphere MQ: request-response pattern only if you
meet all of the following constraints:
-
Requests must be received as SOAP messages over HTTP.
-
Requesting applications must support a synchronous request response interaction
style.
-
Provider applications must be able to respond to requests in a time frame
appropriate for synchronous interaction.
-
Provider applications can receive requests and return responses over WebSphere MQ.
-
Provider applications must support the standard behavior of copying the message
identifier to the correlation identifier.
-
WSDLs defining the broker interface have only one port type and one binding.
-
WSDLs must contain the definitions that define properties for the SOAPInput node in the
definitions of the top level WSDL. Therefore, some complex nested WSDLs cannot automatically
be processed by the pattern.
If WSDLs that do not meet this constraint are used, the pattern does not configure the
SOAPInput node, but lists configuration of the SOAPInput node
as a task to complete after generation of the pattern instance.
-
The provider application supports WebSphere MQ XML messages in a format that can be used
as the body of a SOAP request and response, or you can customize the Request
Processing subflow to transform the format to non-XML messages.
-
If logging is required, the format used by this pattern is assumed to meet your
requirements.