A number of constraints apply when you use this pattern.
You can use the
Service Facade to WebSphere MQ: one-way with acknowledgment
pattern only if you meet all of the following constraints:
-
Requests are received as SOAP messages over HTTP that uses document literal style.
-
SOAP requests and responses use CCSID 1208.
-
Requesting applications can support the
Service Facade to WebSphere MQ: one-way with acknowledgment pattern.
-
Provider applications assume responsibility for acting on an update when a
message is delivered to its input queue.
-
WSDLs that define the broker interface have only one port type and one binding.
-
WSDLs must contain the definitions that define the 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, or you can
customize the Request Processing subflow to transform the format to non-XML messages.
-
The pattern defines its own format for the logging and error messages; it is
assumed that these messages are sufficient to meet the requirements in your own
environment.
Some of the preceding constraints, particularly the CCSID, can be overcome by the
configuration after the pattern has been applied.