This blog entry is part 2 of a 2 part series on WebSphere Message Broker 8 Patterns.

Create the required resources

  • Open the summary file generated in the Pattern instance project using a web browser i.e. the file named AmcExpiryRptSplitter_summary.html

The first part lists the message flows that are part of the pattern instance.

  • Scroll down to the Tasks to complete section

Note down the instructions that are to be completed. For this Pattern instance, we need to do the following

  1. Create the required MQ Queues
    1. custinfo.amcexpiry.in
    2. notification.amcexpiry.out
    3. BAD
    4. notification.amcexpiry.error
  2. Add the pattern instance to a broker archive file and then select the option “Compile and in-line resources” before building the BAR file.
  • Using MQ Explorer, create the following MQ Queues

custinfo.amcexpiry.in

notification.amcexpiry.out

BAD

notification.amcexpiry.error

Deploy and test the generated application

The BAR can be generated next and deployed in message broker.

  • Click File menu | Select New menu-item | Select BAR file menu-item

  • Select BARfiles from Container drop-down
  • Give a name to the BAR file, say “AmcExpiryRptSplitter”
  • Click the Finish button

A BAR file is generated with the name AmcExpiryRptSplitter.bar. The BAR file editor opens automatically as shown below.

  • Select the message flow application, in our case “AmcExpiryRptSplitter”

  • Check “Compile and in-line resources” option under Build Options in BAR content editor

  • Click Build and Save button

Toolkit confirms the successful completion of the build.

  • Click OK button

  • Now deploy the .bar file by right clicking on it and selecting the Deploy menu-item from the pop-up menu
  • Right click amcExpiryMessageSplitter.msgflow and select “Test Message Flow” menu-item in the pop-up menu
  • Click the Configuration tab of test client
  • Select the option “I will deploy the specified Broker Archive manually
  • Click the Browse button and select the BAR file


  • Go back to “Events” tab in test client
  • Use the “Enqueue” option and place the XML file amcExpiryReport.xml in the MQ Queue “custinfo.amcexpiry.in”
  • Click “Send Message” button


  • Use the Dequeue button in the test client and get the message from the MQ Queue “notification.amcexpiry.out”

  • Get the next message from the same queue

Since we had two customer elements in the input XML, we have two messages in the output MQ queue.

We have successfully split the AMC expiry report from Customer Information component and placed the messages in the output MQ Queue using the pattern instance generated from the Message Splitter pattern.

Appendix A: List of patterns provided by WMB 8.0

Area

Functionality

Pattern

1

Application Integration

SAP

MQ one-way (IDoc)

2

File Processing

Record Distribution

MQ one-way

3

Message-based Integration

Message Correlator

MQ request-response with persistence

4

MQ request-response without persistence

5

Message Splitter

MQ one-way (XML)

6

Mobile

Worklight

Microsoft .NET request-response

7

Mobile service

8

Push notification from MQ

9

Resource handler

10

Service Enablement

Service Access

MQ one-way

11

Service Façade

MQ one-way with acknowledgment

12

MQ request-response

13

Microsoft .NET request-response

14

Service Virtualization

Service Proxy

Static endpoint

15

Static endpoint (web based)

Well I hope you enjoyed that little foray into IBM WebSphere Message Broker 8 patterns.

Regards,

Steve Robinson – WebSphere Consultant & Middleware Mentor

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Leave a Reply