Business goals for WSRR

Industries are moving to service-oriented architectures (SOA) to give them increased business agility. Central to this move is the need for a service registry to help manage and govern the services and their business processes.

WSRR addresses this need and the following business goals through service metadata management:

Business process vitality

Your company needs to change quickly to address market needs. WSRR provides the following features to support this goal:

• Dynamic selection of different business services. These are published in the registry, enabling applications to be routed to them.
• Policy changes to modify behavior. Policies are published in the registry together with policy references provided by and required by individual services.

Business governance

This ensures that the business processes are legal, auditable, and mapped correctly to the IT services. WSRR provides the following features to support this goal:

• Policy enforcement and change auditing. This provides basic lifecycle state representations of business services and metadata in the registry, where any changes can be validated against policies and notified to interested parties.
• Security, to control who can change business service metadata and policies. This provides role-based access control for service metadata changes or lifecycle transitions.

IT solution - Time to value

You must bring business changes to the market quickly and at a known or lower development cost. WSRR provides the following features to support this goal:

• Development of new services. The registry ensures reuse of interfaces and existing approved services promoting interoperability and faster integration.
• Reconfiguration and assembly of existing services. WSRR builds on existing interfaces, protocols, policies, and frameworks. This promotes the reuse and adoption of standard policies.

IT governance

This ensures that the changed systems perform as intended and no other systems are impacted. WSRR provides the following feature to support this goal:

• Service lifecycle management. The registry stores information about lifecycle status and other metadata that is used to filter visibility of endpoints according to usage and context. This metadata includes information about the development, assembly, testing, deployment, operation, and version number.

Value based quality of service

This ensures that you pay for the quality of service you need, and not what you have installed.

• Policy based service selection. The registry manages runtime mediations using policies and metadata.

Business management

This helps you to monitor what is needed to effectively manage your business and IT solutions.

• Policy-based logging. The registry stores metadata that defines and controls logging and process monitoring.

Migration

This allows the successful movement from traditional architecture to SOA.

• Discovery and management tools work alongside the registry to help populate it with standards-based mappings from traditional applications.