WebSphere Application Server has introduced a new strategy for releasing additional functionality on top of existing versions, to be known as feature packs. There is now a beta of the WebSphere Application Server Version 6.1 Feature Pack for Web Services available. This feature pack will eventually deliver support for a raft of new Web service standards (WS-Reliable Messaging, WS-Addressing, MTOM and WS-Secure Conversations) along with updating the supported levels of existing standards (JAX-WS 2.0, JAXB 2.0, SAAJ 1.3 and StAX 1.0). The new Web services standards introduced form the basis of the RAMP Profile (Reliable Asynchronous Messaging Profile).
Archive for the ‘WebSphere Application Server’ Category
Feature Pack for Web Services Beta
Thursday, October 19th, 2006developerWorks 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.
Missing messages
Monday, October 16th, 2006Responding 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.
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.
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.