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.
Archive for the ‘WebSphere’ Category
Tooling for classifications
Monday, April 2nd, 2007Integrating DataPower with WebSphere MQ
Monday, March 26th, 2007Nepotism rules so here is a plug for an article by two of my close colleagues Peter Crocker and Ben Thompson on Integrating WebSphere DataPower SOA Appliances with WebSphere MQ.
5 plus 3 support
Monday, March 26th, 2007Having mentioned the impending end of service for WebSphere Application Server Version 5.1, it is probably only fair to note that, as of Version 6.0, there is a support policy change which will see support extended to five years from general availability (previously three years) with an option to purchase a further three years support (previously two years). Support for Version 6.1 will consequently run until at least June 2011.
Software support discontinuance
Tuesday, March 20th, 2007End of service (as I prefer to call it) has just been announced for WebSphere Application Server Version 5.1 as September 2008. If you’re currently using this version it’s time to start drawing up a plan for moving, preferably to Version 6.1.
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.
64-bit Service Registry
Friday, March 9th, 2007As 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, 2007The 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 3.6.0.8 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.
ITCAM for SOA and WSRR
Friday, March 2nd, 2007IBM 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.
RSS - Posts