The next part in the series on using WS-RT in your grid applications is available to read. In this second part of the series we get into the meat of the implementation and look at how to integrate the information that you create within WS-RT with a backend database solution. From the intro:

In this five-part “Building a grid system using WS-Resource Transfer” series, we 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 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. In any grid, there is a huge amount of metadata about the grid that needs to be stored and distributed. Using WS-RT makes sharing the information, especially the precise information required by different systems in the grid, significantly easier. Here in Part 2, examine how this information can be shared, how to integrate a WS-RT interface with a database solution, and how to employ WS-RT to support key operations of the grid, such as in node registration.In this tutorial
In any grid, there is a huge amount of metadata about the grid that needs to be stored and distributed. Using WS-RT makes sharing the information, especially the precise information required by different systems in the grid, significantly easier. In this tutorial, Part 2 of the series, we look at how to store the grid information and how that relates to the structures we’ll need for WS-RT. We also look at the mechanics of the Apache Muse solution and at the WSDL we need to write to support a WS-RT application. And finally, we use the basic methods of WS-RT for registration of nodes into the grid.

Read: Building a grid system using WS-Resource Transfer, Part 2: Share information and integrate with a database solutionRead: Building a grid system using WS-Resource Transfer Series