Archive for the ‘WebSphere Service Registry and Repository’ Category

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.

Tooling for classifications

Monday, April 2nd, 2007

A common question from users of WebSphere Service Registry and Repository is ‘what tooling should I use to generate the OWL and SACL files that represent classifications and lifecycles?’. SACL files can be generated with WebSphere Integration Developer but not everyone has this installed. In answer to this question, Ian Shore from the development team has written a developerWorks article providing a couple of utilities for generating OWL and SACL files from simple text files.

Service Registry Eclipse Plugin

Friday, March 9th, 2007

There 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.


64-bit Service Registry

Friday, March 9th, 2007

As I don’t believe this is currently documented, I thought I should mention that although WebSphere Service Registry and Repository will run on 64-bit AIX, it cannot be used with 64-bit DB2. If you’re running on a 64-bit platform then make sure that you create a 32-bit DB2 instance otherwise you will get failures during the installation process (he says having learnt this the hard way!).

WebSphere Service Registry and Repository Handbook

Friday, March 9th, 2007

The WebSphere Service Registry and Repository Handbook has now made it out of draft. Having submitted a whole raft of feedback on an early draft I did appear in the acknowledgements but mysteriously my name hasn’t made the final cut! Notwithstanding this, the book provides excellent coverage from the basic concepts, through installation, to advanced customization, governance and integration with WebSphere ESB, ITCAM for SOA, WebSphere Message Broker and CICS. (Note that, as of the recent firmware version, DataPower can also be used to perform lookups in the registry.)

One topic that the WebSphere ESB chapter covers is how to connect the endpoint lookup mediation primitive to WebSphere Service Registry and Repository via SSL. This doesn’t currently work out of the box. You will need to apply APAR IC51354 to WebSphere ESB and then follow the instructions in the book or corresponding technote.


Friday, March 2nd, 2007

IBM Tivoli Composite Application Manager for SOA (or ITCAM for SOA as it is usually referred to) is, as the name suggests, an important part of IBM’s monitoring solution for the SOA, tracking web service requests not only through IBM products such as WebSphere Application Server, DataPower and WebSphere ESB but also into other environments like SAP NetWeaver and JBoss. WebSphere Service Registry and Repository has a number of integration points with ITCAM for SOA, one of which is an Event Handler. This enables situations detected by ITCAM for SOA (such as an excessive response time or message size) to result in the creation, update, or removal, of properties on a WSDL port or SCA export in the registry. You can read a developerWorks article that describes how to configure ITCAM for SOA to monitor a web service running in WebSphere Application Server and update the metadata for the service entry in the registry.

One possible usage is to modify the behaviour of clients depending on the current system status. For example, by using a query to select endpoints which are not currently experiencing response time issues. This isn’t currently possible in WebSphere ESB when using the endpoint lookup primitive due to the internal caching that is performed. Unlike WebSphere Message Broker, the primitive does not currently have any mechanism to invalidate the cache when service definitions are modified.

WebSphere User Group meeting

Tuesday, February 27th, 2007

I headed down to Bedfont early this morning for the WebSphere User Group meeting. Such is the traffic on the M3 that I missed the start but arrived in time for Jim Caldwell’s keynote presentation. Jim is the IBM Director of WebSphere Application Infrastructure and had some interesting things to say about many parts of the portfolio from WAS CE to WebSphere XD. Two products were mentioned that I’ve never really paid much attention to in the past. WebSphere Real Time is a Java environment for real-time applications, providing for sub-second response times free from the usual vagaries of garbage collection. Meanwhile, WebSphere Remote Server is targetted at the retail market, providing a J2EE runtime for the store with remote management capabilities.


More from developerWorks

Friday, February 2nd, 2007

I’ve been catching up on some of the developerWorks articles published in the past week and here are a selection of the best. First up is an up-date to the top Java EE best practices. As the article states, it’s amazing how many customers still aren’t following these simple steps. On the WebSphere ESB front we have the third part in Rachel and Andre’s series on Building an Enterprise Service Bus using WebSphere ESB. This looks at using SOAP/HTTP bindings, property promotion and administrative modification of endpoint addresses. Greg Flurry goes one step further in his article, covering the new dynamic endpoint capability in WebSphere ESB V6.0.2 including the use of the endpoint lookup primitive in combination with WebSphere Service Registry and Repository. This leads me on nicely to a new series which looks at the use of generic objects in Service Registry to group related documents.