Governance Interoperability Framework - GIF Overview

GIF Overview

GIF represents a collection of APIs defined by standards organizations, data mappings and classifications and leverages UDDI and WS-Policy standards, among others, as building blocks. In order to promote commonality of approaches and understanding of the information represented, GIF also defines vocabularies for the purpose of applying metadata to service information.

Integration with the Governance Interoperability Framework is based on two primary pillars of integration: Control Integration and Service Data Integration. These themes are based on the famed Model-View-Controller (MVC) pattern:

Control integration - Consists of alerting and notification integration; launching events and actions; and integration of business service governance and lifecycle.

Data integration - Consists of leveraging the Business Service Registry as the primary service description, characteristic, and policy catalog.

GIF provides control and data integration needed to support activities such as the governance of business service provisioning and lifecycle management. Aspects of this are:

Provisioning integration - Leverage the SOA governance system as part of the provisioning and deployment process of business services. Once integrated, bi-directional exchange of service information between participants is enabled.

Deployment integration - Upon deployment of services, any party should have the ability to alert others to the existence of the service and the need to put the service and its definitions under management.

Lifecycle management - Lifecycle management of all facets of a business service is required. This means collaborating and integrating components for the purpose of managing:

• service and artifact versioning
• lifecycle information (e.g. development, test, production, deprecated)
• lifecycle status and state of the service (availability)
• deployment information including up-time, first deployed date, last deployment date
• contact and support information about the service or template (owner, responsible organization, support contact, manager, etc.)
• compliance status
• dependencies and relationships between:
  • services – those dependencies that the partner creates partner
  • proxies and the services they proxy
  • services consumed by another service

GIF has been driven by several use cases, including:

• SOA governance system acting as the authoritative source of service descriptions and metadata to other components of an SOA ecosystem.
• SOA governance system as the recipient of service descriptions, metadata and policy information, including but not limited to publishing service descriptions (typically WSDL documents and associated metadata) and lifecycle information.
• Publish service characteristics to the SOA governance system to enable the searching and reporting of services and their artifacts. This may include publishing performance data, historical trends and other facets of service information such as constraints and capabilities of the service.
• Make service characteristics, such as configuration, constraints and capabilities typically expressed as policy, discoverable.
• Publishing and making available protocol and binding information, such as the WSDLs of proxied services by security or management partners, and their associated business service (functional) WSDLs.