Federated Service Management (FSM) requires more information than where the service is and how to invoke it. The GridScope Repository stores all then critical information the Gateway needs for defining and provisioning services-protocols, policies, SLAs, etc. The set of non-functional characteristics defined in the service metadata can be referred to as a service configuration. Configurations can be derived from an extended service definition, when available. Or, a business can define and store its own consumption-based policies and exceptions as a configuration, regardless of the service endpoint.

The repository is persisted in a high performance data store and can be viewed and managed using the Console. The stored configurations in the Repository can be accessed as a web service.

The Repository also enables caching to help manage performance latencies across multiple domains. Caching service configurations and metadata as services are invoked eliminates many latencies and significantly improves the processing time.

  Centralized Data Store for Service Assets: Stores all service data and metadata, not just registry information, in a centralized fashion.
  Configurable Auto-updating of Services: Proactively seeks out new and updated services and automatically registers them so they are available to the entire enterprise. Automatic discovery can be configured to occur at any interval the user desires.
  Batch Registration of Services: Electronically registers batches of services from any other UDDI-compliant registry, either public or private. Can be configured to automatically update from the same registries to capture new or updated services.
  Caching of Service Assets: Provides auto-update of high-performance cache with service configurations and other service assets, as appropriate.