Nepotism rules so here is a plug for an article by two of my close colleagues Peter Crocker and Ben Thompson on Integrating WebSphere DataPower SOA Appliances with WebSphere MQ.
Archive for the ‘WebSphere MQ’ Category
Integrating DataPower with WebSphere MQ
Monday, March 26th, 2007WebSphere ESB and Messaging
Friday, March 2nd, 2007There are two new articles on developerWorks covering connectivity between WebSphere ESB and messaging. The first, is Part 4 of Rachel and Andre’s series which takes a look at the new Websphere MQ binding in Version 6.0.2. The second article shows how to use the JMS bindings with JMS providers other than the default messaging provider or WebSphere MQ i.e. what WebSphere Application Server refers to as generic JMS providers.
WebSphere User Group meeting
Tuesday, February 27th, 2007I headed down to Bedfont early this morning for the WebSphere User Group meeting. Such is the traffic on the M3 that I missed the start but arrived in time for Jim Caldwell’s keynote presentation. Jim is the IBM Director of WebSphere Application Infrastructure and had some interesting things to say about many parts of the portfolio from WAS CE to WebSphere XD. Two products were mentioned that I’ve never really paid much attention to in the past. WebSphere Real Time is a Java environment for real-time applications, providing for sub-second response times free from the usual vagaries of garbage collection. Meanwhile, WebSphere Remote Server is targetted at the retail market, providing a J2EE runtime for the store with remote management capabilities.
Presentation and dinner
Tuesday, November 14th, 2006Many of the presentations at the conference are repeats from our internal services conference earlier this year which means I have some spare time to catch up on other work. One session I did go to today was Eric Herness (Chief Architect for WebSphere Business Integration) presenting the new content in Version 6.0.2 of WebSphere Process Service and ESB. I think it’s safe to say this is a refresh pack with more than a few functional enhancements!
WebSphere MQ JMS message selection
Thursday, November 9th, 2006Of my various publications, the one which seems to bring in the most questions at the moment is that relating to message groups in WebSphere MQ and how these are exposed through the JMS API. I should therefore confess that there are a couple of issues with the approach that the article describes.
developerWorks roundup
Thursday, November 2nd, 2006This is my usual weekly roundup of what’s new and interesting on developerWorks. This week we start with something for the WebSphere Application Server developer. When abstracting configuration properties out of code they often end up in a simple properties file. This is fine if the values are static but, if they need updating, you either need to redeploy the application containing the file or else put the file somewhere separate from the application. (If taking the latter approach then the config directory is a good place for the file as then you call leave the application server to replicate it across the nodes.) Perhaps a better approach is to configure a resource environment provider as described in this article, enabling properties to be defined administratively.
High availability of WebSphere MQ link
Tuesday, October 31st, 2006Today sees the release of WebSphere MQ SupportPac MR01. This provides the source for a WebSphere MQ channel exit which can be configured with a list of host names and port numbers to which the channel will attempt to connect. The intention is that this exit can be used when using a WebSphere MQ link to connect a clustered Service Integration Bus messaging engine to a queue manager. The messaging engine can now failover to another cluster member and the queue manager will still be able to connect.
WebSphere MQ Servers
Thursday, October 12th, 2006The final major piece of functionality that I shall cover in this series of posts looking at deliverables made by Hursley in to WebSphere Application Version 6.1 is WebSphere MQ Servers. In Version 6.0 of the Application Server, WebSphere MQ could either be accessed directly from an application using the WebSphere MQ JMS provider or via the service integration bus by using a foreign bus and WebSphere MQ link. In Version 6.1, it is possible to add a WebSphere MQ queue manager, running on z/OS and at Version 6 (CSD 1 or greater), directly as a member of the bus.
RSS - Posts