When configuring WebSphere Message Broke to call services loaded into WSRR the following two node can be used:
1. Registry Lookup
2. Endpoint Lookup
When using any of the two nodes the following configuration needs to be done:
Make sure Broker has been started when running the config: mqsistart.exe / mqsistart.sh
1. WSRR unsecure (No security enabled on WAS and URL start with http://)
mqsichangeproperties -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v https://localhost:9443/WSRR6_3/services/WSRRCoreSDOPort
2. WSRR secure (Security enabled on WAS and URL start with https://)
Step 1: mqsichangeproperties -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v https://localhost:9443/WSRR6_3/services/WSRRCoreSDOPort
Step 2: mqsireportproperties -o BrokerRegistry -r
Step 3: mqsichangeproperties -o BrokerRegistry -n brokerKeystoreFile -v C:\WSRR\SSL\DummyClientKeyFile.jks
Step 4: mqsichangeproperties -o BrokerRegistry -n brokerTruststoreFile -v C:\WSRR\SSL\DummyClientTrustFile.jks
Step 5: Stop the Broker: mqsistop.exe/mqsistop.sh
Step 6: mqsisetdbparms -n DefaultWSRR::WSRR -u wasadmin -p wasadmin
Step 7: mqsisetdbparms -n brokerKeystore::password -u dummy -p WebAS
Step 8: mqsisetdbparms MB7BROKER -n brokerTruststore::password -u dummy -p WebAS
Step 9: Start the Broker: mqsistart.sh/mqsistart.exe
Transactional Objects (those who have the Input/Output prefix):
- Body – Root
Non transactional :
Below is a basic Websphere Message Broker JMS flow using Websphere MQ JMS.
Setup of Websphere MQ for JMS flow:
Step 1: Create JMS Initial Context
Step 2: Create Connection Factory
Specify the WMB Queue Manager as the JMS Queue Manager
Easy way to JMS Queues it to create a Lcoal Queue and right clicking on it and selecting ‘Create JMS Queue’
Step 3: Specify a JMS Destination
Step 4: Deploy and Test the flow
JMS flow is great for integrating with Websphere Application Server where an application executes code and put the result on a JMS queue, the JMS picks the information up and processes by doing validation, transformation and mediation.
Important to note is that Websphere Message Broker only supports Websphere JMS and no other JMS provider.
Project architects need to consider the importance of how to include WebSphere® Business Integration Message Broker in a highly available configuration. This article describes how to achieve high availability through a combination of application design and use of software-based clustering of queue managers using MQ clustering and machine clustering provided at the hardware level.
How to catch Websphere Transformation Extender Error in Websphere Message Broker:
I have created a flow that will validate a message (WTX Validate) and also catch any error:
The Transformation Errors can be put on a Queue to be consumed by an Monitoring tool, Exported to a file for debugging.
If you have created a WTX transformation map and would like to call it as part of your message flow you will have to install Webphere Transformation Extender for Integration Server.
It provides installation and integration support when combining WebSphere Transformation Extender with additional IBM products. It includesWebSphere Transformation Extender components that are ready to deploy in message and mediation flows. WebSphere Transformation Extender complements the native capabilities of these products, and can process large documents and messages with more complex formats that are not based on XML.