The Generic Grid Broker component acts as a meta-scheduler sitting on top of existing Grid middleware (such as Globus Toolkit, gLite, or UNICORE). Its role is to intelligently schedule the execution of jobs on the Grid with efficient and optimized management of resources. For example, as the Globus Toolkit cannot select by itself a remote resource on which to submit the job, it has to implement a meta-scheduler for handling some high-level decisions.
The GRIA Command Line Client interface has several advantages over the standard graphical interface. It provides the ability to automate various common actions through easy to write and use batch or shell scripts. Actions can be performed automatically without the need for interaction with the user, and chained together to form pipelines. In addition, the command line client uses less resources than the graphical interface.
GridSphere Plug-in for GRIA is a GridSphere (http://www.gridsphere.org/) plug-in for the GRIA 5.1 middleware (http://www.gria.org/). The plug-in is suitable to be used not only with GridSphere, but also with any other Java application which can use a GRIA 5.1 plug-in. This way, a GridSphere user can, for example, submit new jobs in a GRIA 5.1 Server through a user-friendly portal as well as monitor submitted jobs, having a keystore signed by the GRIA server administrator.
The OGSA-DAI Trigger component provides a mechanism to notify an OGSA-DAI server when a table in an SQL database has had its rows modified. It then executes a stored OGSA-DAI workflow to perform an action based on the notification. The trigger also provides the old and new values for the modified row which allows specific actions to be taken based on the exact database changes. These actions can use the full range of access, transformation, and delivery functionality available in OGSA-DAI.