Java 5 in WebSphere Message Broker
December 28, 2006 6 Comments
I’ve been very quiet on this blog so far, due to other commitments. I hope to make more of a contribution from now on. Let’s make a start with a small Broker tip.
A little-known addition that went into fix pack 3 for WebSphere Message Broker (220.127.116.11) is that you can now select a Java 1.5 runtime in which to execute your JavaCompute and Java plugin nodes. You’ll find this mentioned in the Infocenter, under the topic on New function added in V6 fix packs. You don’t have to use the 1.5 JRE – by default, a 1.4.2 JRE is still supplied, but you can switch to the 1.5 JRE if you need to do so.
The way this works is very straightforward. In version 6 of WMB, the environment for the broker components is initialised by script called mqsiprofile – as in previous releases – but this is now extensible. You can add additional scripts to the <workpath>\common\profiles directory – by default, this is C:\Documents and Settings\All Users\Application Data\IBM\MQSI\common\profiles on Windows (watch out, this might be hidden in Windows Explorer), and /var/mqsi/common/profiles on Linux and UNIX systems. These additional scripts will be executed automatically when the mqsiprofile script is run.
The instructions for enabling support for Java 1.5 differ very slightly depending on the platform:
- On Windows, copy mqsijava15.cmd from the broker <install_dir>\bin directory to the <workpath>\common\profiles directory.
- On Linux and UNIX, copy mqsijava15.sh from the <install_dir>\bin to <workpath>\common\profiles.
Once you’ve copied the script across, you can restart your broker components (having already re-run the mqsiprofile script, if appropriate), and the change should be picked up.
If you do choose to move to the 1.5 JRE, then it would be a good idea to re-test any Java components that you have already developed, to ensure that there are no compatibility issues.