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 […]
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 […]
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. http://www.ibm.com/developerworks/websphere/library/techarticles/0403_humphreys/0403_humphreys.html
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. http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r3m0/index.jsp 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 […]