Open Service Grid Initiative
English | Japanese

Operating Service Grid

Overview

A Service Grid is operated by using the Service Manager. The Service Manager is a Web-based management tool of the Service Grid Server Software developed by National Institute of Information and Communications Technology (NICT), Japan. With this tool, Users can manage their resources easily. Also, the Service Grid Operator can manage the entire Service Grid. The tool allows easy management of registered information of the Users, access by the Users, resources, and services. Each Operator has its own Service Manager for managing the Service Grid. Please find the URL of the Service Manager in the webite of each Service Grid Operator. We outline the Service Grid Operating procedures using Service Manager for dealing with the following events:
  1. Concluding agreements with Users and registering accounts
  2. Registering resources
  3. Deleting resources
  4. Registering services
  5. Suspending services
  6. Restarting services
  7. Deleting services
  8. Monitoring excessive use of services

Service Grid Operating Procedures

Here we summarize Service Grid Operating procedures for dealing with the main tasks in operating the Service Grid.

Concluding agreements with Users and registering accounts

  • Concluding Agreements
    1. An organization that wishes to join the Service Grid should check whether it fulfills the conditions listed below. If the organization meets all requirements, its official representative should send by email an application to join the Service Grid, including the following information in the email. It is also possible for the Operator to invite a User to participate in the Service Grid.
      Required Information:
      • Corporate Name of Operator
      • Corporate Address
      • Name of Operation Entity (Include the name of the organization as well as the name of your group, such as the name of the research lab or department.)
      • Operation Entity's Address
      • Operation Entity's Website
      • Operation Entity's Representative
      • Operation Entity Representative's E-mail
      • Operation Entity's Contact E-mail
      • Postal address
      The request needs to be sent by the official representative of the organization.

      Requirements for joining the Service Grid:
      • The size of a user group has to be small enough to enable the representative to have control over the usage of the Service Grid by all members.
      • The group must be able to manage the user ID and password for the Service Grid within only a few administrators in order to prevent any leakage.
      • The following information concerning the user group must be published on the groups' website: the name of the user group, the representative's name, and the postal address.
      • In principle, an individual is not qualified to conclude an agreement with the Service Grid Operator.
    2. If the Operator accepts the application to join from the User, the Operator will send the Service Grid Agreement form via email.
  • The User signs the Agreement and sends a scanned Agreement form (PDF file) to the Operator via email.
  • The Operator signs the Agreement and sends a scanned Agreement form (PDF file) to the User via email.
  • After the Agreement is thus concluded, the Operator adds the new User's registration information to the Service Grid User List on the Service Grid Operation website.
    • Registering User Accounts
      1. The Service Manager is used to create new accounts (user ID and password), and enter user profile information (organization, representative, address, email, and URL).
      2. Account information along with the Agreement is sent to the User via email.

    Registering Resources

    1. A resource provider enters required information (resource ID, resource name, type of resource, supported languages (optional), the resource itself or URL to access the resource) and registers the resource.

    Deleting Resources

    1. When a resource provider completes settings to delete a resource, the Service Manager displays a message to the Operator and Users stating "the date that the resource will be deleted" and "the date that the service using the resource will be deleted." After the deletion date, another message is displayed stating "the resource has been deleted" and "the service using the resource has been deleted."

    Registering Services

    1. A service provider enters required information (service ID, service name, type of service, supported languages (optional), WSDL, terms of service use) and registers the service.

    Suspending Services

    1. When a service provider suspends a service, a message stating "the period that the service will be suspended" will be displayed on the Service Manager to the Operator and the Users. When the suspension period expires, the message stating "the service has been suspended" will be displayed.

    Restarting Services

    1. When a provider restarts a service, the Service Manager displays a message stating "the service has been restarted".

    Deleting Services

    1. When a service provider completes settings to delete a service, the Service Manager displays a message to the Operator and Users stating "the date that the service will be deleted." After the deletion date, another message is displayed stating "the service has been deleted."

    Monitoring Excessive Use of Services

    1. If the Operator finds a message stating "excessive use of services warning" on the Service Manager, the Operator checks the recent usage of the service in question. If a user appears to be using the service much more frequently than in the past, the Operator sends an email inquiry to the user of the relevant service.
    2. If the usage reported by the user and the actual access frequency are substantially different, the Operator asks the user to change passwords.
    3. If the user does not respond, the Operator suspends the user's access to the service and sends a notification to the user that the user's access has been suspended. The length of time before a user's access is suspended is determined by the Operator according to the circumstances. In emergency situations, the Operator has the right to suspend a user's access rights immediately.
  • Last updated: April 30th, 2010.