Tasks to complete after generating the Message Splitter for WebSphere MQ: one-way (for XML) pattern

Tasks that you must complete after you have generated the pattern.

  1. Create the broker archive (BAR) file. The message flow must be added to a broker archive file. Any message sets that are referenced by the flow are automatically added.
    1. Click File > New > BAR File.
    2. Enter the name of your server project or select one from the displayed list. The list is filtered to show only projects in the active working set.
    3. Enter a name for the BAR file that you are creating.
    4. Click Finish. A file with a .bar extension is created and is displayed in the Broker Administration Navigator view, under the Broker Archives folder. The Content editor for the BAR file opens.
    5. On the Prepare tab, select the generated message flow file to add it to your BAR file.
    6. Select Compile and in-line resources and then click Build and Save to create your 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 Message Splitter for WebSphere MQ: one-way (for XML) pattern instance, but you might want to review some of the default options and configure changes for the your environment.

    In the Manage page of the Broker Archive editor:

    1. Optional: Use the Logging required property to select whether logging is on or off for the message splitter message flow.
    2. Optional: Use the Error message required property to select whether error messages are generated for the message splitter message flow.
    3. 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 you change do not impact the behavior of the pattern instance.
  3. Create queues. When you apply the pattern, a list of WebSphere MQ queues is generated, with queue names and queue manager names, which 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.
    1. 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.
    2. 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 This link opens in a new window WebSphere MQ library web page.
    3. If you use the Lookup routes value in the Routing parameter, routes can be defined dynamically and are not listed in the summary file. When routes are added to the database, the corresponding queues must be created.
  4. 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:
Back to the Message Splitter for WebSphere MQ: one-way (for XML) pattern specification