There 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.
Archive for the ‘WebSphere’ Category
WebSphere ESB and Messaging
Friday, March 2nd, 2007WS-Addressing endpoint references
Friday, March 2nd, 2007Ben Bakowski has written a very thorough developerWorks article covering the use of WS-Addressing endpoint references with WebSphere Application Server Version 6.1 to act as references to stateful session beans. Ben uses his sample online shop application to show the possibilities including how to achieve high availability in a cluster.
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.
More from developerWorks
Friday, February 2nd, 2007I’ve been catching up on some of the developerWorks articles published in the past week and here are a selection of the best. First up is an up-date to the top Java EE best practices. As the article states, it’s amazing how many customers still aren’t following these simple steps. On the WebSphere ESB front we have the third part in Rachel and Andre’s series on Building an Enterprise Service Bus using WebSphere ESB. This looks at using SOAP/HTTP bindings, property promotion and administrative modification of endpoint addresses. Greg Flurry goes one step further in his article, covering the new dynamic endpoint capability in WebSphere ESB V6.0.2 including the use of the endpoint lookup primitive in combination with WebSphere Service Registry and Repository. This leads me on nicely to a new series which looks at the use of generic objects in Service Registry to group related documents.
Service Integration Bus Performance
Monday, January 29th, 2007Another great tool for those working with the Service Integration Bus is now available on alphaWorks. The Service Integration Bus Performance tool (written by David Granshaw who leads the Service Integration Bus Performance team in Hursley) provides an SWT front-end to all of the WebSphere Application Server PMI statistics that are relevant to messaging performance. When you start the tool and point it at a server and messaging engine, it selects a useful set of default statistics. You can then use the configuration menu to select additional statistics with an indication given of the level of performance impact of doing so. Best of all (at least for someone as forgetful as me) is that when you close the tool it turns off the PMI stats before shutting down.
My first WebSphere ESB cluster
Saturday, January 27th, 2007The second instalment of the WebSphere Process Server and WebSphere ESB deployment patterns series is now available. This describes in considerable detail the steps required to configure a simple Process Server cluster. By removing the parts that are plainly not applicable, you are left with a set of good instructions for creating a simple WebSphere ESB cluster. You should, however, refer back to the first article to review when using this simple topology is valid. In particular, you should note that co-locating the SCA modules and messaging engines is generally only possible when you are not using asynchronous SCA i.e. the module imports are not using JMS. If you do use asynchronous SCA then the partitioning of destinations on the SCA.SYSTEM bus that occurs as a result of clustering the messaging engines can become a problem, with responses no longer guaranteed to get back to a partition that is accessible by the instance of the module waiting for it.
Direct JNDI lookup warnings
Saturday, January 27th, 2007I was browsing through the fix list for Version 6.1 of the Application Server and was interested to note that APAR PK32169 is removing the J2CA0294W warning messaging (unless you have debug trace turned on) in Fix Pack 5. This is the warning that you see when performing a direct JNDI lookup of a connection factory i.e. you go straight to the global namespace rather than using a resource-reference and the application’s local namespace (java:comp/env). This message has always been rather contentious as it asserted that direct JNDI lookups were being deprecated yet various parts of the product still continued to use them. There was even a technote describing how to suppress the warnings as, in some cases, they were causing significant performance degradation.
More WebSphere ESB content on developerWorks
Saturday, January 20th, 2007I’m catching up on my developerWorks reading and there are a couple more articles on WebSphere ESB that are worth mentioning. The first is What’s new in WebSphere Enterprise Service V6. Note that the title actually refers to V6 not V6.0.2 so in fact this article provides a good overview of all of the product’s capabilities (although those new in V6.0.2 are highlighted). There are a couple of factual inaccuracies in the article which I’ve alerted the author to so hopefully those will get corrected.
One of the new features in 6.0.2 is the WebSphere MQ binding support which certainly seems to be getting a lot interest from my colleagues. Phil Norton from the WebSphere ESB development team has provided a tutorial that covers invoking a mediation module from an MQ Java client. In particular, it shows how to use a custom data binding to map from the MQ message to a data object. In the tutorial the service being invoked is represented as a Java component in the mediation module. This is by way of example and should not be considered best practice.
RSS - Posts