GSCD_TE

Grid Middleware Successfully Deployed in BEinGRID for Finance and Tourism

Use nested workflows (sub workflows)

Monitor execution

Manage jobs and results

2.3.1.4. Saving a workflow

his window shows you the progress of the workflow and also the results on completion

The standard GRIA client does not know about the sample service or the resources it creates

The Java interfaces which define the interaction between the service and the client go in a single jar which is used by each of them.

A data stager is a container for a single file (or zip file)

although GRIA does not require them to be located on the same machine

Managed Services The SLA service is of no use if it does not manage any functional services. There are five conditions that must be met in order for a functional service to be managed: At the functional service: The SLA service must be in the functional service's list of "Trusted Management Services". The SLA service's CA certificate must be a trusted CA in the functional service's key-store. The SLA service must be in the "management-services" group of the functional service. At the SLA service: The functional service's CA certificate must be a trusted CA in the SLA service's key-store. The functional service must be in the "sla-managed-services" group of the SLA service. If the functional services that require managing are hosted on the same machine as the SLA service (and therefore share the same certificate) then steps 2-5 are not necessary, otherwise see below for more detail.

none has a higher preference/authority than any other

3.2.4. Nested workflowsWithin the Interactive Diagram nested workflows are not represented in their expanded state, but instead as a single processor coloured pink. A view of the expanded state is, however, still avialable through the static Graphical view.To edit a nested workflow, right-click on the nested workflow element and select the menu item "Edit Nested Workflow". This will open up the nested workflow in a new view allowing it to be manipulated just like any other workflow. The original parent workflow can be reselected via through the Taverna "Workflows" menu.

The GRIA Workflow Application v0.2 software includes tools for deploying and running XScufl workflows as GRIA applications. XScufl workflows may be created using Taverna or g-Eclipse. A command line deployment tool generates GRIA application wrapper scripts and other requisite files from an XScufl workflow. Running the deployment tool generates a new application that can be deployed to the GRIA Job service in the usual way using the Job Service Administration web pages.

Management View The management view displays resources under the resource which they are managed by. This relationship is a parent-child relationship and this can be seen in the resources endpoint reference, right click a resource and select View EPR there is a managingresource element which tells us the endpoint of the managing resource. If a resource is unmanaged then it appears under the Management Resources node otherwise it appears under its managing resource.

Management View The management view displays resources under the resource which they are managed by. This relationship is a parent-child relationship and this can be seen in the resources endpoint reference, right click a resource and select View EPR there is a managingresource element which tells us the endpoint of the managing resource. If a resource is unmanaged then it appears under the Management Resources node otherwise it appears under its managing resource.

Vine is a modular, extensible Java library created by the authors of GridSphere's GridPortlets Project. Vine inherits and improves upon the Resources Model of GridPortlets and generalizes it for use in many application environments. Vine can be easily packaged and deployed for use in desktop, Java Web Start, Java Servlet 2.3 and Java Portlet 1.0 applications. Using the Vine Toolkit, one composes applications as collections of resources and services for utilizing those resources. The Vine Toolkit makes it possible to organize resources into a heirarchy of domains to represent one or more virtual organizations (VOs). Vine offers security mechanisms for authenticating end-users and authorizing their use of resources within a given domain. Other core features include an extensible model for executing tasks and transparent support for persisting information about resources and tasks with in-memory or external relational databases.

For Linux, the first line of the script (eg. #!/usr/bin/python) is used to determine which interpreter to use. The filename extension can be anything (eg. startJob.py, startJob.sh).

The application wrapper scripts are deployed along with the applications - either on a shared file system or individually on each compute node. Their function is to provide a uniform interface to the Job Service for starting, monitoring and stopping applications.

The GRIA API is used to create and manage the GRIA resources representing databases, roles and subscriptions

This allows you to access managed Basic Application Services on griademo2. You can now use the client to store data and run jobs, much as you did before, but managed by the SLA that you proposed and billing to the trade account that you have just opened: