Message Broker Knowledge Collection

HTTP transport nodes in WebSphere Message Broker V6 :
http://www.ibm.com/developerworks/websphere/library/techarticles/0608_braithwaite/0608_braithwaite.html

Message Broker Explorer plug-in :
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24012457&loc=en_US&cs=utf-8&lang=en
  
    
RFHUtil :
http://www-01.ibm.com/support/docview.wss?rs=203&uid=swg24000637
  
WebSphere Message Broker deployment scripting using Ant :
http://www.ibm.com/developerworks/websphere/library/techarticles/0706_spriet/0706_spriet.html
  
Transformation Options for WebSphere Message Broker V6 :
http://www.ibm.com/developerworks/websphere/library/techarticles/0608_piper/0608_piper.html
  
New and enhanced nodes in WebSphere Message Broker V6.1 :
http://www.ibm.com/developerworks/websphere/library/techarticles/0805_lee/0805_lee.html
  
Dynamically update a Web service interface using WebSphere Message Broker Version 6 :
http://www.ibm.com/developerworks/websphere/library/techarticles/0602_thompson/0602_thompson.html
  
Timeout notification example :
http://www.ibm.com/developerworks/websphere/library/techarticles/0603_schutz/0603_schutz.html
  
Message Broker Code Deploy Best Practices :
http://andypiper.files.wordpress.com/2007/06/messagebrokercodedeploy.pdf
 
Error Handling in Message Broker :
http://linderalex.blogspot.com/2009/03/error-handling-in-websphere-message.html
 
Testing and troubleshooting message flows with WebSphere Message Broker Test Client :
http://www.ibm.com/developerworks/websphere/library/techarticles/0702_spriet/0702_spriet.html
 
Using Java in WebSphere Message Broker V6 :
http://www.ibm.com/developerworks/websphere/library/techarticles/0605_crocker/0605_crocker.html
 
Message Parsing MB :
http://www.ibm.com/developerworks/websphere/library/techarticles/0810_hanson/0810_hanson.html
 
XML Transformation in Message Broker :
http://www.ibm.com/developerworks/websphere/library/techarticles/0612_zhang/0612_zhang.html?ca=drs-&ca=dkw-xml
 
SOAP Nodes tutorial :
http://www.ibm.com/developerworks/websphere/library/techarticles/0902_henley/0902_henley.html
 
Collection Nodes tutorial :
http://www.ibm.com/developerworks/websphere/library/techarticles/0805_coleman/0805_coleman.html
 
Testing and troubleshooting message flows with WebSphere Message Broker Test Client  
http://www.ibm.com/developerworks/websphere/library/techarticles/0702_spriet/0702_spriet.html

Configuration Manager Proxy API and WMB v7

Wave goodbye to the Configuration Manager. Starting with WebSphere Message Broker v7, there is no longer a separate Configuration Manager. That likely won’t be of great interest to the majority of users as they will likely not even notice the difference.


The removal of the Config Manager caught my attention and raised the question – what happens to my utilities that talk to it via the Configuration Manager Proxy API? After some investigation, here is what I found.


If your environment is running v6.1 or lower and has custom code that leverages the Configuration Manager Proxy API, an upgrade to v7 will require additional review. The following qoute comes from the WMB helpfiles:

“Some applications that conform to the CMP API for Version 6.0 or Version 6.1 might need to be migrated to conform to the CMP API for Version 7.0, although most can run without change against the new API, and the API itself handles the differences.”

The concept of the Configuration Manager Proxy API is still supported, but it has a new nickname: Administration API for WebSphere Message Broker. I’m using the term nickname because IBM, in some cases, is still using CMP API. Here is the statement from the help files that discusses the use of both names.

“The full name of the API has changed to Administration API for WebSphere Message Broker. However, the terms CMP application and CMP API have been retained, and are used in this information center to refer to the Administration API, for continuity and consistency with the JAR file ConfigManagerProxy.jar that supplies all the classes.”

The help files also mention the removal of certain classes and methods.

So what does it all mean?

I suspect IBM is saying they think everyone is covered with the Administration API. However, because it is impossible to tell what some developers cooked up in the middle of the night, they can’t guarantee a seamless transition. The only way to tell will be to run your CMP API programs against the Admin API in v7 and check for continued success.