Group items tagged

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.

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.

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:

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

GRIA    Computational Fluid Dynamics and Computer Aid Design (BE1)Collaborative Environment in the Supply Chain Management for Pharmaceutics (BE10)Anti-money Laundering in Grid (AMONG) (BE19)TravelCRM (BE21)WOW2GREEN (BE23)

Gridsphere    Computational Fluid Dynamics and Computer Aid Design (BE1)Visualisation and Virtual Reality (BE3)Integration of Engineering and Business Processes in Metal Forming (BE8)Collaborative Environment in the Supply Chain Management for Pharmaceutics (BE10)New Product & Process Development (BE14)

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

Use nested workflows (sub workflows)

Monitor execution

Manage jobs and results