Responding to Srinivas’ comment requesting more on debugging, I thought I’d post on one common question when using the service integration bus: where has my message gone? By this I mean the case when a message has been sent but not received by the consumer.
Archive for the ‘Technology’ Category
Missing messages
Monday, October 16th, 2006WebSphere 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.
IE7 and Firefox 2.0
Wednesday, October 11th, 2006The Register reports that IE7 is due to be released later this month. The pressure is on for Firefox, with Release Candidate 2 of Version 2 released last week.
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.
WS-Notification
Wednesday, October 11th, 2006Continuing my series of posts on new functionality in WebSphere Application Version 6.1, today I’m looking Web Services Notification (WS-Notification). For those with a messaging background, WS-Notification basically provides publish/subscribe capabilities for Web services i.e. a one-to-many relationship between client and service.
Message ordering
Tuesday, October 10th, 2006One subject that keeps cropping up with customers is the subject of message order. Now I’ll say up front, having a requirement to maintain the order of messages in an application is a bad thing. If messages can’t be processed in parallel due to ordering constraints then the resulting application is unlikely to scale and high availability will be difficult to achieve. This, however, doesn’t seem to stop people wanting it, so here’s a few things you should know about message order and the service integration bus.
Tightened bus security
Monday, October 9th, 2006Another area of the service integration bus which has seen some significant changes in WebSphere Application Server Version 6.1 is that of security. For starters, the option for bus security has always been checked by default but it is only enforced when global security is enabled. To reduce the confusion, this option is now greyed out in the administration console if global security is not enabled.
RSS - Posts