Tasks to complete after generating the
Service Facade to WebSphere MQ: one-way with acknowledgment pattern
Tasks that you must complete after you have generated the pattern.
-
Review the CCSID. This pattern assumes that the CCSID used for SOAP requests is
1208. If the provider application requires messages with a different CCSID, this
parameter must be configured in the RequestProcessing subflow by using the Message Flow
editor. This property cannot be modified with the Broker Archive editor.
-
Review the configuration of the SOAP node. In the case of complex WSDLs, it might be necessary for you to
select the WSDL from within the Message Flow editor,
this requirement is shown in the summary file.
-
Create the broker archive (BAR) file.
Add the generated message flow to your BAR file. In the Broker Archive editor, you must select the
Compile and in-line resources option before you build the BAR file.
Message sets that are referenced by the flow must also be added.
-
Configure the broker archive file. Further configuration of the message flow in the broker archive
file is not required before you deploy the message flows for your
Service Facade to WebSphere MQ: one-way with acknowledgment
pattern instance, but you might want to review some of the default options and
configure changes for your environment. For instance, you might want to review the following properties:
- LoggingOn.
If logging is included, at deployment time this switch determines whether logging of
requests is required for the current environment.
- ErrorLoggingOn.
If error messages are included, at deployment time this switch determines whether
logging of errors is required for the current environment.
You can change any of the pattern parameters that are listed in the
parameter tables as configurable, but you must be
careful because the pattern might be assuming specific behavior. However, you can
change properties that are determined by operational
characteristics and do not affect flow logic, for example,
security configuration or additional instances.
-
Create queues. When you apply the pattern a list of WebSphere MQ queues is
generated, with queue names and queue manager names, these WebSphere MQ queues must be created if
they do not already exist. All of the message settings that are required by the
pattern are set explicitly on the messages and are not dependent on queue
settings.
- In the summary file, view the list of queues that you must create. The summary file
is located in the Pattern Configuration folder of the
InstanceName pattern instance project.
- Create WebSphere MQ
resources. You can create WebSphere MQ
resources either on the command line by using programs and
utilities such as runmqsc, or by using the
WebSphere MQ Explorer graphical interface. For more information about creating
WebSphere MQ resources, see WebSphere MQ Intercommunication,
available on the
WebSphere
MQ library web page.
- Deploy the BAR file. The message set containing the deployable WSDL must be
deployed, by using the same or another BAR file, to every broker where the flows
are deployed.
Back to the Service Facade to WebSphere MQ: one-way with acknowledgment pattern specification