WSRR support for the deployment phase

WSRR provides the system of record for metadata describing service interaction endpoints. It is populated with metadata as part of SOA solution deployment or through the discovery of existing endpoints.

WSRR is used by SOA runtimes as well as deployer and administrator roles when detailed information about service endpoints is required to drive operations of the deployed composite applications.

After the development team has finished its work and testing is complete, deployers further augment the service metadata, providing binding information for service endpoints used in composite applications and managing deployment of the metadata from the development environment to the staging or production instance of WSRR as part of the service deployment process. Governance over the service metadata takes place, as metadata is promoted from test to staging to production environments that might have separate WSRR installations. In the production WSRR, service metadata is made available to a broader audience and shared. It is available to the runtime systems and those user roles that are responsible for the management of the IT systems.

Also, service metadata can be discovered in other service registries and repositories, published in WSRR, and can be used as input for the application configuration and binding tasks performed by the deployers and solution administrators. Discovered service metadata is usually incomplete and not yet suitable for broader visibility and consumption. Deployers work with asset managers to ensure the metadata is augmented with necessary semantics, permissions, and scoping constraints.

Automation of service metadata publication during service application deployment integrates the management of service metadata with the overall SOA management and governance processes in a highly product way.

Execution time interactions with WSRR can be implemented in a service endpoint by a component developer, or by a mediating intermediary that acts on behalf of the service requester or the provider and is configured by an integration developer. Dynamic endpoint selection is a key use case that involves querying WSRR for the service provider or a set of candidate service providers, and binding to the endpoint that is the best choice. Endpoint selection rules can be encoded in ESB-managed mediations.

Another use case is dynamic retrieval and enforcement of the policies that are in effect for a service interaction in the areas of logging, filtering, data transformation, or routing. WSRR can store the policy definitions; service interaction endpoints can reference applicable policies; policy enforcement points, such as mediations, can be configured using that information and can be updated when the metadata managed by WSRR changes.