I have just started a new series on using the new WS-Resource Transfer (WS-RT) standard. WS-RT is a simpler replacement for the original WS-Resource Framework and WS-Resource Properties solutions. In fact, IBM’s own WS-RT implementation is built around an existing WS-RP/WS-RF implementation in Apache Muse. This new looks at how you can apply the technology behind WS-RT within a grid system. Certain areas of the typical grid solution will benefit from the ease of use offered by WS-RT. The bulk of the functionality is a simple XML document that you can access through a structured interface. Over the series I’ll be looking at different ways of taking advantage of this simplified interface, but the first piece looks at the basics of WS-RT and how it integrates into the typical grid system. This piece was written by Tyler Anderson while I was busy moving house. The series intro:

In this five-part “Building a grid system using WS-Resource Transfer” series, we will look at the use of WS-Resource Transfer (WS-RT) in different areas of the grid environment – from using it as a method for storing and recovering general information about the grid to grid monitoring and management, and security. We will also examine how WS-RT can be used for the distribution and division of work. Part 1 examines the WS-RT standard and looks at how to develop a WS-RT solution using Java technology and Apache Muse.

And for this piece:

The WS-RT standard provides a new method for accessing and exchanging information on resources between components. It is designed to enhance the WS-Resource Framework (WSRF) and build on the WS-Transfer standards. The WS-RT system extends previous resource solutions for Web services and makes it easy not only to access resource information by name but also to access individual elements of a larger data set through the same mechanisms by exposing elements of an XML data set through the Web services interfaces.

Read Building a grid system using WS-Resource Transfer, Part 1: Grid services and WS-RT