The asynchronous nature of message-driven beans means that the JMS provider must be permanently connected to the messaging system in order to know when a message is available for delivery. I received a question last week as to what WebSphere Application Server’s behaviour is when that connection is broken.
Archive for the ‘WebSphere Application Server’ Category
MDB reconnection
Sunday, January 7th, 2007WebSphere Application Server V6.1 security
Monday, December 11th, 2006Two words you don’t often see in the same sentence: simplicity and security. Peter Birk and Keys Botzum have written an in-depth article covering the enhancements to the SSL, certificate, and key management, capabilities for WebSphere Application Server in Version 6.1.
WebSphere Process Server made easy
Saturday, December 9th, 2006The first in a series of three introductory tutorials on WebSphere Process Server is available on developerWorks. Interestingly, the tutorials are aimed at administrators, not developers, and are designed for those coming from a WebSphere Application Server background.
Exploring Web services
Tuesday, December 5th, 2006Rational Application Developer and WebSphere Integration Developer both come with a piece of functionality known as the Web Services Explorer. Part of the unit test client, this provides a user interface for invoking WSDL defined Web services. Until now, I’ve always used the Explorer by right-clicking on a piece of WSDL and selecting Web Services > Test with Web Services Explorer. This is all very well if the WSDL happens to be in your workspace. What I hadn’t realised until this week is that you can also use the Explorer with any arbitrary URL addressable WSDL.
JMS Application Server Facilities
Thursday, November 23rd, 2006On the basis of a thread of notes I was involved in this week, I was considering a post on the WebSphere Application Server support for JMS providers that don’t implement the Application Server Facilities (ASF) part of the JMS specification. As the name suggests, these facilities cover aspects of integration between a JMS provider and a J2EE application server such as transactionality and message-driven bean support. Paul Titheridge (who works in the service team covering the WebSphere MQ and WebSphere Application Server JMS providers) has done the hard work for me and written a developerWorks article on the subject.
Feature Pack for Web services podcast
Thursday, November 23rd, 2006In a previous posting I covered the Feature Pack for Web services. This week’s developerWorks Making SOA real with WebSphere podcast includes an interesting interview with Nathan Goike on this subject. Points of particular interest to me was the inclusion of Apache Axis2 and the use of policy sets to ease Web service configuration.
Security presentations
Thursday, November 23rd, 2006Keys Botzum has provided updates to his security hardening and programming presentations, written in combination with my UK colleagues Cameron Martin and Peter Kovari, to cover Version 6.0 and 6.1 of WebSphere Application Server.
WS-Notification
Tuesday, November 21st, 2006Ben Bakowski, Chris Whyley and Matt Roberts have written a nice developerWorks article introducing WS-Notification in WebSphere Application Server Version 6.1. For once I’ve actually sat down myself and worked my way through it so I know it’s good! It illustrates the use of a publisher, asynchronous consumer and pull point for lightweight consumers, along with mixing WS-Notification and JMS. One thing to watch out for though: the authors have chosen to use scripting for the setup and pre-written applications which, although providing useful examples, means it’s easy to get to the end of the article without knowing what you’ve done if you don’t take the time to look at the content of the scripts and code.
RSS - Posts