WebSphere Message Broker Fix Pack 22.214.171.124 has been released.
The issues reported on the withdrawn Fix Pack 126.96.36.199 has been addressed.
August 13, 2007 • 11:33 0
July 12, 2007 • 08:33 5
An WebSphere MQ resource adapter support statement can be found here.
The MA0Y support pack includes two downloads:
Get going with the samles download
Get going with a clean Geronimo and curl
June 27, 2007 • 11:10 0
Today a new release of the IH03: WebSphere Message Broker V6-Message display, test & performance utilities support pack was released (more commonly known as RFHUTIL).
The most interesting and important feature for me in my day to day work was the introcuced SSL capabilities. RFHUTIL now works as you would expect from a native WebSPhere MQ client application, reading the MQSSLKEYR environment variable to locate the keystore.
I used a script like this to connect to a remote queue manager using a server connection channel with a NULL_SHA SSL configuration:
The keystore is named key.kdb and is stored together with stash and the other related files in the c:\ih03\ssl\ folder.
I used these settings in the “Set Connection User Id” dialog (click the Set Conn Id button to open):
Be sure to select the correct settings from the Queue Manager Name drop-down list.
This will enable the usage of IH03 in in environments with SSL security requirements, a really good thing!
June 25, 2007 • 16:15 0
A couple of fixpacks ago I tested to connect to a remote queue manager sing a SSL configured server connection channel. Then things didn’t work out that well, but now a couple of refresh/fixpacks later everything wors much better.
To start with I must say that I don’t really fancy the way SSL is enabled from the WMQ Explorer point of view. The keystore parts of the configuration is ok but to connect to a queue manager using SSL you need to provide the WMQ Explorer with client channel definition table (CCDT).
For those of you not familiar with CCDT: it’s basically a binary format where an MQ server can store it’s client connections. Client connections in turn is data needed to connect to a queue manager in a client mode (includes parameters as connection, ssl etc). The CCDT file can be distributed to clients who can use it as the basis for their connection. As the CCDT file is binary there is no easy way to create it by hand. Running runmqsc on a WebSphere MQ server box will make it possible to create the CCDT but that is a bit heavy-weight in my opinion. The best aproach I’ve found so far is to use the MO72: MQSC Client for WebSphere MQ support pack by Paul Clarke.
MO72 has the follwing features (among others):
To create a CCDT from scratch using MO72 run the following command:
mqsc -n -t c:\AMQCLCHL.TAB
to add a client connection channel issue a define script:
DEFINE CHANNEL('CLIENTS.ADMIN') CHLTYPE(CLNTCONN) CONNAME('188.8.131.52(1414)') MAXMSGL(104857600) QMNAME('QM1') SSLCIPH('NULL_SHA') TRPTYPE(TCP) REPLACE
This CCDT assumes that there are a server connection channel named CLIENTS.ADMIN defined in the queue manager listening on port 1414 and host 184.108.40.206 with the rest of the properties in the client connection channel also defined in the server connection channel.
To gain access to the remote queue manager using SSL:
Mission accomplished, SSL now works as a charm.
But why was this implemented using CCDT’s? I can’t see any reason really. I would like to see something like a custom SSLSocketFactory implemented in WebSphere MQ Explorer making it possible to use multiple key and trust stores and easier configuration on top of that. An example of an custom SSLSocketFactory was published by Peter Broadhurst on the a Hursley view on WebSphere MQ blog a couple of months ago.
Perhaps I’ll send in a proposal/requirement to get this configuration more simple and understandable.
June 18, 2007 • 20:28 0
For those of you who don’t know that much about IS02 here’s the short-short summary:
Back in may I wrote a post on the IS02 support pack. The background story was a customer of mine who currently set up multiple message brokers (WebSphere Message Broker) in an active-active cluster utilizing WebSphere MQ workload balancing features.
From a management/tool view-point the message broker has been all but complete. I was very excited to try out the IS02 support pack as it’s a lean alternative to the all-but-lean Message Broker Toolkit.
The previous post covered the functionality of version two, the version three of IS02: WebSphere Message Broker Explorer Plug-in was released a couple of days ago and today I gave it a shot.
The conclusion is (based on a setup where the configuration manager is installed on a separate box from the eclipse platform):
So, a bit better but more need to come before this becomes really useful.
May 24, 2007 • 19:40 1
In my current assignment I’m architecting “a version two” of my customers corporate ESB.
These core components that make up the actual ESB runtime:
As a part of the architectural work I needed to look into the management possibilities of the components. I’ve been working with both WMQ 5.3 and WBIMB 5.0 before but newer the 6.0’s.
What I wanted to do, if possible, was to use the IS02 support pack in favor the WebSphere Message Broker Toolkit to administer the broker domains. The Toolkit is based on Eclipse and includes both administration and development capabilities (a huge overhead for pure operational tasks).
The runtime setup as follows (BK=Broker, CM=Configuration Manager, QM=Queue Manager):
Objectives: Use IS02 to connect to CM (through QM2) and administer BK1 and BK2 from Workstation1.
IS02 (v2 – the current one) doesn’t work in a clustered environment (one without XMIT queues and sender/receiver (non-cluster) channels. The senders (QM2 to QM1 and QM2 to QM3) channel is needed on QM2 for the tooling to display the brokers. The receiver corresponding receiver channels are needed to administer the brokers (sending messages basically)
Well, I set up the XMIT’s and channel’s and tried again. The brokers and configuration manager is nicely shown in the IS02 eclipse plugin. You can do the things you can expect like deploying (to multiple execution groups “concurrently”) , starting, stopping and removing flows etc.
Still some things doesn’t work as expected:
Based on what I’ve heard at IBM the problems should hopefully be fixed in the upcoming release.
May 19, 2007 • 09:54 2
I just read about new release of MQMON or MO71: WebSphere MQ for Windows – GUI Administrator that IBM wish calling it.
The support pack can be downloaded from here.
I havn’t had the time to play around with it yet but i definitely will very soon. By looking at the new features one can find:
I’ll get back with another post on the subject as soon as I’ve had a chance to test it.
May 14, 2007 • 22:21 0
For all you WebSphere InterChange Server users out there wanting to get to WebSphere MQ 6 here’s the thing: support for WMQ 6
May 8, 2007 • 22:16 0
Hi and welcome!
Yesterday night I installed Kubuntu 7.04 on an old IBM laptop of mine (from the time IBM laptops were actually from IBM) . Canonical has really done a good work in making the installation process work like a charm. The main reason for setting Kubuntu up was to use the laptop as a HTPC playing audio, recording TV and so forth.
The first thing I tried to get working was mounting a windows share and playing a couple of mp3’s from my library. After adding the required restricted format from the repository I thought I was home safe but Amarok didn’t start no more…
I turned to Google and after a while I found this bug report: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/8971
To kill all that has to do with Amarok did it!