Today 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.
Archive for the ‘WebSphere ESB’ Category
High availability of WebSphere MQ link
Tuesday, October 31st, 2006WebSphere ESB vs SIBus
Thursday, October 26th, 2006Rachel Reinitz and Andre Tost have kicked off a new developerWorks series on WebSphere ESB with an article describing the relationship between the product and the Service Integration Bus. In my mind, it’s a shame the article doesn’t talk more about about the SIBus Web services support. The following phrase sums up the key difference: “WebSphere ESB is built with the strategic SCA/SDO programming model”.
Advanced XSLT for WebSphere ESB
Thursday, October 19th, 2006There is an interesting developerWorks article which looks at some advanced aspects of using XSLT with WebSphere ESB, particularly focusing on mapping element arrays in business objects.
developerWorks deluge
Wednesday, October 18th, 2006I’ve only just got round to reading last week’s developerWorks newsletter and it contains a positive plethora of interesting articles following the SOA launch.
WebSphere ESB 6.0.2
Wednesday, October 11th, 2006As Adrian notes, WebSphere Enterprise Service Bus Version 6.0.2 has now been announced for release around the end of the year. As I hinted in an earlier entry , this will include a new mediation primitive to provide integration with WebSphere Service Registry and Repository to enable the dynamic selection of endpoints at runtime. There should also be less need to use WebSphere Integration Developer to make pre-deployment modifications with the ability to alter endpoints and mediation primitive properties administratively.
One particularly welcome piece of functionality is the extension of the JMS bindings to support WebSphere MQ in addition to the default messaging provider. This, along with the WebSphere MQ bindings, means it is possible to connect directly to WebSphere MQ without first going through the service integration bus. This is important given the current complexity of configuring a highly available WebSphere MQ link on the bus. It also fits with a message that I have been trying to give to WebSphere Applications Server customers: only go through the service integration bus to reach WebSphere MQ if it adds value to your solution.
Introducing WebSphere Service Registry and Repository
Wednesday, October 4th, 2006I have spent the past few weeks educating myself on WebSphere Service Registry and Repository which became generally available last Friday. This is one of the new products forming part of the today’s SOA launch. The launch has focused on how the product can be used to enforce the governance of services (through the use of a state machine to define the service lifecycle) but, given my focus on all things ESB, my main interest is in the use of the WebSphere Service Registry and Repository to support dynamic allocation of service endpoints.
IBM Client Application Tool for JMS
Wednesday, October 4th, 2006For a while now, Martin Smithson’s JMS client application has been an essential part of my WebSphere ESB and service integration bus toolbox. I’m therefore glad to see that it’s now available to all on alphaWorks. It runs inside a J2EE client container and provides a Swing or SWT interface to browse JNDI, locate JMS resources, and then send, receive or browse messages. Simple but effective. Best of all, in the past Martin has been very responsive to making enhancements.
Supported J2SE JMS client
Thursday, August 31st, 2006I’ve previously mentioned the “Client for JMS on J2SE with IBM WebSphere Application Server” on alphaWorks which enables Java clients running in a non-J2EE environment to access destinations on a service integration bus defined in a WebSphere Application Server (or Process Server, ESB or XD) cell. This client has now graduated to a fully supported version. There is now a small install process to take you through the license agreement but you still end up with a JAR file that weighs in at only 2MB. If you also need to suport retrieval of JMS resources from JNDI then that adds around another 0.5MB.
RSS - Posts