Tasks to complete after generating the
Service Access from WebSphere MQ: one-way pattern
Tasks that you must complete after you have generated the pattern.
Review the configuration of the SOAPRequest node.
In the case of complex WSDLs,
you might have 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.
You must also add any message sets that are referenced by the flow.
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 Access from WebSphere MQ: one-way
pattern instance, but you might want to review some of the default options and
configure changes for your environment.
For example, you might want to review the following properties:
Request logging required and
Response logging required.
Use these properties to switch logging on and off.
When you turn logging on, you must check that the logging queue is
correctly defined for your 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 and queue managers.
When you apply the pattern, a list of WebSphere MQ queues is
generated with queue names and queue manager names.
These WebSphere MQ queues and queue managers must be created if
they do not already exist.
For each queue manager that is created, the connection to the broker queue manager
must also be created. 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 site.
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.