Archive for the ‘WebSphere Application Server’ Category

Web Service Transactions

Monday, June 4th, 2007

As I’ve mentioned previously, shortly after I first joined IBM I was a member of the development team for the transactions component, initially of Component Broker and then WebSphere Application Server. My team leader back then was one Ian Robinson. Ian has since risen to the heady heights of Senior Technical Staff Member and I’m glad to say that he now acts as my mentor. Ian is co-chair of the OASIS WS-Tx committee and, as announced on his blog (of which I had no idea of the existence), Version 1.1 of the standard has just been announced. Ian has also added his name to the list of contributors on the WebSphere Community Blog (note the new location) having authored a lengthy article on the support for Web Service Transactions in WebSphere Application Server.

Virtualized WebSphere Application Server

Monday, May 21st, 2007

I mentioned that Ruth Willenborg gave a presentation at WSTC on virtualization and WebSphere Application Server. She now has an article on developerWorks that covers one technique she was talking about: creating and then deploying customized WebSphere Application Server images. Now where this gets really interesting is when you apply it to something like WebSphere Process Server…

WSTC Day 3

Wednesday, April 25th, 2007

A 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, 2007

So, 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, 2007

My 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…)

Transactional simplicity

Tuesday, April 10th, 2007

It’s good to read articles like this once in a while to remind oneself how much simpler J2EE made transactions.

WebSphere Application Server trace

Tuesday, April 10th, 2007

Daniel Julin is also co-author of another developerWorks article looking at WebSphere Application Server trace. The article describes what trace is, how to turn it on (including the appropriate wsadmin incantations) and how to interpret it. Note that, as the article demonstrates, trace can be very useful in diagnosing some issues, it is really intended for use by IBM service personnel who also have access to the corresponding source code, so don’t expect the trace messages always to be self explanatory. The article also has a plug for Trace Analyzer for WebSphere Application Server, a great tool for viewing and analyzing trace logs (and large ones at that) written by two of my one-time colleagues in the transactions team.

Co-locating applications

Tuesday, April 10th, 2007

There was a time when customers would only ever have a single application running on any given application server instance. In the drive to cut costs, this level of application isolation isn’t one that many customers can still afford. Daniel Julin and Stacy Joines have written a developerWorks article that covers some best practices and techniques for troubleshooting co-located applications.