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.

  1. 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.
  2. 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:

  3. 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.
  4. 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.
  5. 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 This link opens in a new window WebSphere MQ library web page.
  6. 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.
  7. 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:
  8. 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.
  9. 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.

Back to the Record Distribution to WebSphere MQ: one-way pattern specification