Part 5 of the Building a grid with Web services series is now available on the IBM developerWorks site. In this part we cover the management and flow of information and work through the grid. This is the part where movies submitted to the grid are routed through to a suitable storage node according to their size and available storage capacity. Here’s the official blurb:

Storing movies across a grid is more than just a case of handling the security and effective transfer of the information between system components. For the system to be an effective grid, you need to be able to manage the individual components and processes that make up the grid solution.For example, when submitting a movie into the grid, there is more to the process than just transferring the movie. The grid manager must make a decision about which grid node stores the movie, then record the information so the movie can be located again when it is requested. You may also want to control individual nodes — for example, when upgrading the node or storage, you may want to disable it while you update the available storage locations. All of these items will be tackled in this tutorial.

And you may want to take a look at the previous parts before leaping into part 5:

• Building a grid with web services, Part 1
• Building a grid with web services, Part 2
• Building a grid with web services, Part 3
• Building a grid with web services, Part 4

You can then feel free to read Building a grid with web services, Part 5.