This blog has been horribly stagnant for a number of months now. There are lots of reasons why that might be: Twitter, work pressures, general lack of enthusiasm for blogging. Probably all of those and more.
Previously I’ve kept work-related posts to a minimum and tried to focus on more personal stuff. That’s going to change in an attempt to revitalize my blogging. As an IBM software developer there are often things that I need to be careful about mentioning in public and that will certainly remain the case. However there are a lot of IBMers publicly talking about their work and where it takes them and I don’t see why I can’t too.
So from now on you can expect to see much more about Lotus Connections and my work interests in general. One thought I’ve had is to do some periodic posts on aspects of WebSphere Application Server that Connections administrators may find useful. I’ve been a user of WAS for ten years and have both consulted on it as well as develop parts of it in the past so hopefully I can provide some hints and tips of value to those not so familiar with the application server.
However it won’t all be about Connections and WebSphere. I’ve a great interest in agile development and in particular Rational Team Concert so there will likely be the odd post about that, as well as other software engineering and social computing topics that take my fancy.
Of course, it won’t all be work and no play – there will still be occasional posts about a new toy, hobby, pursuit or other activity. I’ll make sure to use categories well so you can skip past the stuff you don’t want to read.
If you still have me in your feed reader then thanks for sticking around and let me know what you think.
I’ll be out and about over the next month and a bit doing a few talks on Lotus Connections:
First up I’ll be at the IBM Lotus Premium Support Seminar in Boston, MA on Wednesday 27th August where I’ll be presenting with Heidi Votaw, Program Director for Social Software. We will be talking about “Leveraging Social Software to Boost Innovation and Productivity Today” with an obvious focus on Lotus Connections 2.0. Unfortunately this is an invite only event.
Next, I’ll be at the IBM Lotus TechJam event being held at IBM in Staines, UK on Wednesday 2nd September where I’ll be doing a dive on Connections 2.0 with a definite technical slant. I’m not entirely sure how people can sign up for this event, but you can try contacting Dave Hay via the blog link above.
Finally (for now I guess) myself and my colleague Karim Heredia will be at the UK WebSphere User Group meeting in Edinburgh on Wednesday (why are they all on Wednesday?) 17th September. This talk will be titled “Lotus Connections – the WebSphere perspective” and will focus on deployment and administration considerations as well as how you can extend the social computing power of Connections out into other applications. You can join the WUG and sign up for the meeting on their web site.
Sandy Carter, the VP of SOA and WebSphere Strategy at IBM has a new book available entitled The New Language of Business: SOA and Web 2.0. Details are available via the IBM Press site, along with a 35% discount code. The book covers the IBM roadmap for SOA and Web 2.0, illustrated with over 40 customer case studies and interviews with analysts and industry leaders. My copy is on its way, so I’ll blog more when I’ve read it, but for now you can access a sample chapter.
Additionally, IBM have just launched a new online SOA newsletter, which will be produced on a regular basis, containing articles and case studies. You can subscribe to receive it via email. The current issue contains a link to the Impact 2007 conference, being held in Olando, Florida on May 20-25th. Impact is the conglomeration of the annual WebSphere Technical Exchange and Transaction & Messaging conferences, and also a conference for our Inner Circle customers. Impact will also be held in Europe later in the year.
I’ve been playing with Yahoo Pipes again, this time for something a bit more useful.
There are a number of blogs from IBMers here in the UK which cover WebSphere related topics at varying degrees of frequency. Some are solely WebSphere related whilst others talk about all sorts of subjects including WebSphere.
The WebSphere related posts from UK IBMer blogs pipe takes the feeds from a number of these blogs and uses the content analysis module to filter only the WebSphere related posts into one convenient feed. It currently takes input from the following blogs:
This is not an exhaustive list of the possible bloggers, but is a start. If you think a blog should be added, let me know. This pipe could easily be cloned to add feeds for other IBM software brands as well.
What would be really nice (if the folks at Yahoo Labs are listening) is if the fetch module could take a URL input that pointed to an OPML file such as the one maintained by Elias Torres. Then you could imagine a configurable pipe with a text input that fed into the filter meaning you could filter on all sorts of topics such as Second Life for example.
WebSphere ESB 6.0.2 (along with WebSphere Process Server 6.0.2 and WebSphere Integration Developer 6.0.2) is now generally available. Existing customers can learn how to download the product from Passport Advantage here (just click on the link for the platform you require.) I’ve discussed some of the new functionality on this blog before, but you can now also access the Infocenter documentation, including a section on what’s new.
… about the software engineer who spent his birthday analysing a 1GB Java heap dump for a memory leak?
Nope, didn’t find it that funny myself 🙁
On a more positive note, if you find yourself in a similar position then I can recommend that you try out a useful tool called the Memory Dump Diagnostic for Java (MDD4J) available as part of the IBM Support Assistant. Here’s a DeveloperWorks article explaining all.
In WebSphere ESB 6.0.1, the amount of post-deployment administration you could carry out was limited to the ability to view module import and export details, and the capability to modify the target of an import with an SCA binding. Within WebSphere ESB 6.0.2 we have greatly improved the influence the administrator can have on a deployed mediation flow in two ways.
The first of these is to extend the ability to re-target endpoints to include Web Services endpoints. Thus, an administrator can override the endpoint URL for SOAP/HTTP and SOAP/JMS endpoints. This administrative capability is in addition to the new dynamic endpoint selection functionality I’ve already talked about and is more static in nature. You might ask which one takes precedence and the answer is any endpoint dynamically selected by the mediation flow.
More significantly, we’ve introduced the concept of module properties. An Integration Developer can now opt to promote certain properties of primitives within the mediation flow up to the module, where they will be exposed for viewing and modification by the administrator post-deployment. This leads to a number of interesting possibilities, from being able to make small changes to the behaviour of the flow such as whether or not a Message Logger logs within a global or local transaction, to more creative uses which can have an effect on the outcome of the flow. The combination of administrative properties, the Message Element Setter and a Message Filter primitive is a prime example of a possible application of the latter.
Apologies for the delay in producing the next in this series of posts outlining the new functionality coming up in WebSphere ESB 6.0.2. However, I’ve got a few cycles to spare so I’m going to try and get the rest of them done in short order.
One of the big questions we get on WebSphere ESB is how can you dynamically select the endpoint to invoke from within a mediation flow? In 601 you are limited to defining imports for all the endpoints you may wish to invoke and then using the Message Filter primitive to route to one of them. Whilst this works, it isn’t very dynamic. If you want to add an endpoint then you need to go back to tooling and then redeploy.
Re-tooling and deployment may be acceptable if the interface of an endpoint has changed as you may well need to update the contents of the flow accordingly (for example by changing a transformation) but is overkill in the simpler case whereby the interface remains the same but you just want to change the endpoint the message is sent to. Just such a scenario was the basis for a Developerworks article by Greg Flurry.
The dynamic endpoint selection capability in WebSphere ESB 6.0.2 will solve this issue by allowing you to augment the Service Message Object during mediation with information on the endpoint that you want to invoke. So the next question is then how do you determine the endpoint?
Well, you could use the existing Database Lookup primitive or a custom mediation, but more interestingly you can also use a new primitive available in 6.0.2, funnily enough titled Endpoint Lookup. The interesting thing about the Endpoint Lookup primitive is that it interfaces with the WebSphere Service Registry and Repository. As such, you can configure the primitive to look up endpoints based on port types, versions and even perform more complex queries based on the ontology you’ve defined within your registry. The registry may return zero, one or more results which you can then select from using a variety of methods, for instance a combination of Message Filter and Message Element Setter.
All this works for endpoints using the SCA native bindings or SOAP/HTTP and SOAP/JMS.
The Common Event Infrastructure is a core part of the runtime that WebSphere ESB and WebSphere Process Server are based on. The CEI runtime allows you to generate business or IT level events and persistently store then for consumption by monitoring tools such as WebSphere Business Monitor. The event format is defined by the Common Base Event model.
Currently in WebSphere ESB 6.0.1 you can generate CEI events when exports and imports are invoked. With the Event Emitter primitive in 6.0.2 you will be able to generate your own events from within a mediation flow, which can embed any information from within the Service Message Object.
A typical use of the Event Emitter primitive would be in conjunction with the Message Filter primitive to generate a business event when an exceptional situation is discovered based on the content of the message being mediated.
In the first of a series of posts on the new functionality coming up in WebSphere Enterprise Service Bus 6.0.2, I’d like to introduce one of our new mediation primitives: the Message Element Setter.
The job of this primitive is to provide you with an easy way to set a particular part of the message with a value. Previously, the only way to do this would be to utilise the XSLT primitive with a very simple XSLT function, or to use a custom mediation primitive. Both of these are pretty heavyweight for such a simple job, and so the Message Element Setter was born.
Very simply, you can configure the primitive to set any part of the Service Message Object, specified via an XPath, with a value of a particular type. In addition, there are two special types of setter: the copy and delete. Copy allows you to copy part of the SMO from one place to another, and delete obviously allows you to delete the value of the part of the SMO you specify.