Tasks to complete after generating the Record Distribution to WebSphere MQ: one-way pattern
Tasks that you must complete after you have generated the pattern.
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.
If you have used a message set to define how records are parsed, you must add the message set to the BAR file.
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 Record Distribution to WebSphere MQ: one-way pattern instance,
but you might want to review some of the default options and configure changes for your environment.
In the Manage page of the Broker Archive
editor:
Optional: Use the
LoggingOn user-defined property to
select whether logging is on or off for the message flow.
Optional: Use the ErrorLoggingOn
user-defined property to select whether
error messages are generated.
Optional: You can also change any of the configurable properties
in the broker archive, for example, properties for security or creating
additional instances. You must ensure that any values that you
change do not impact the behavior of the pattern instance.
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 the 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 the message settings that are required by the pattern are
set explicitly on the messages and are not dependent on queue settings.
Create the 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.
If you use the Lookup routes value in the
Routing parameter,
you can define routes dynamically in the database
but the routes are not listed in the summary file.
If you have added routes to the database,
you must create the corresponding queues and queue managers.
Set up a routing database if required.
If the Lookup routes value is selected in the
Routing parameter, the data source
must be set up with a ROUTING_TABLE table. This table must include the following columns:
ROUTING_CONTEXT
Use a value that identifies the routing entries for this flow.
VARIABLE1
The value that the KEY1 property
from the message element must match.
VARIABLE2
The value that the KEY2 property
from the message element must match.
QUEUE_MANAGER
The queue manager of the destination.
QUEUE_NAME
The destination queue.
If you have chosen to use FTP to obtain input files,
you must create an FtpServer configurable service
on the target broker matching the name specified in your pattern.
This action is required by the FileInput node to connect to the remote FTP server.
Deploy the BAR file. If a message set is used to define records, this message set
must be deployed by using the same, or another, BAR file.