Another useful fact I picked up at WSTC was around retry behaviour for JMS exports. Pamela Fong and Jeff Brent have put together a very detailed developerWorks article covering all aspects of exception handling in WebSphere Process Server and WebSphere ESB. Definitely worth trying to get your head round this stuff.
Archive for the ‘WebSphere Process Server’ Category
Process Server and ESB exception handling
Monday, May 21st, 2007WSTC Day 3
Wednesday, April 25th, 2007A 7 o’clock business breakfast meant that much of the rest of today was spent wandering around in a daze. My first presentation of the day was by Marc-Thomas Schmidt who is the architect responsible for ESB (in all its guises) and Service Registry and Repository. This was followed by an excellent session given by Mike Capern and Ryan Zombo. This covered a selection of use cases from WebSphere Service Registry and Repository Proof of Concepts. It demonstrated that, although still a young product, its numerous customizable aspects means that it can meet most requirements.
(more…)
WSTC Day 2
Tuesday, April 24th, 2007So, I’m going to use the title whether Andy likes it or not! My day started with a focus on the JMS and MQ bindings in WebSphere Process Server and ESB. Corville Allen from development gave an excellent session on some of the intricacies. I picked up a few facts. For example, the ability to set the SCA_JMS_SEND_DB_ERROR system property so that a ServiceRuntimeException is sent back if parsing fails in the data binding for a response. Also, I was aware that the SCA system bus is now optimized out of a flow using a JMS export and import but apparently if the request message is rolled back then, on retry, the system bus is used so that the failed event manager can kick in.
(more…)
WSTC Day 1
Tuesday, April 24th, 2007My creative juices aren’t flowing today hence the unimaginative title for this posting (and if I couldn’t come up with a good title today, there was no chance I would be able to be inventive by day 5). Sadly, as an internal conference with significant IBM confidential content I can’t cover everything here but I’ll cover what I can. As Andy has already blogged, someone had the good sense to realise that we are a technical audience and the keynote speech was given by Jerry Cuomo, CTO for WebSphere. I particularly liked his demo around Real Time Java which showed garbage collection leading to breaks in a piece of music played with with a Sun JVM compared to the flawless playback when using Metronome GC in an IBM J9 JVM.
(more…)
Service Registry Eclipse Plugin
Friday, March 9th, 2007There are a couple of options for accessing artifacts in WebSphere Service Registry and Repository at development time. (NB I used to call them artefacts but this seemed to confuse the Americans!) If you are using WebSphere Integration Developer (Version 6.0.2) then you can use the Enterprise Service Discovery wizard to query a registry and retrieve artifacts. This support is the subject of a new developerWorks article.
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.
All the twos
Thursday, December 28th, 2006Santa arrived early with the latest release of IBM’s business integration products. WebSphere Process Server 6.0.2 and WebSphere ESB 6.0.2 were both released just before Christmas. There is a developerWorks article providing an overview of the new features. WebSphere Integration Developer 6.0.2 is also available as an update via the Rational Product Updater (as is the first ifix). Note that this will also bring the Process Server installation that forms part of the Integration Test Environment up to the 6.0.2 level. For the runtimes, make sure you also get the critical fixes.
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.
RSS - Posts