 |
Page History
| Scrollbar |
|---|
| Children Display |
|---|
| Page info | ||||
|---|---|---|---|---|
|
Administer Services defines profiles for management of service metadata and service classification schems.
The use of well defined service metadata promotes better discovery and reuse of services during design and run time. Service metadata includes information about service interactions and dependencies. It also includes a classification scheme for organizing services based on business objectives, domain, and usage. It also links services to all the supporting artifacts in the specification and provides a placeholder for conformance statements. This enables better reuse across the enterprise and eliminates redundancy.
A service description defines or references the information needed to use, deploy, manage and otherwise control a service. Capabilities to support service metadata include:
- Versioning, configuration management, and migration tools to enable service description change over time and to reflect changing needs and context
- Semantic metadata, which may be used for categorization or providing other property and value information for service descriptions
- Bindings to policies defining conditions of use and contracts representing agreement on policies and other conditions
- Bindings to metric models to describe the operational characteristics of the subjects being described
- Interaction history to enable auditing and repeatability, thereby establishing a context for results and support for understanding observed change in performance or results
- Service assembly/composition from components
- Up-to-date information on what a resource is, the conditions for interacting with the resource, and the results of such interactions. As such, the service description is the source of vital information in establishing willingness to interact with a resource, reachability to make interaction possible, and compliance with relevant conditions of use.
One of the key requirements for participants interacting with each other in the context of a SOA is achieving visibility: before services can interoperate, the participants have to be visible to each other using whatever means are appropriate. Visibility is expressed in terms of awareness, willingness, and reachability.
The Semantic Infrastructure depends upon the underlying Platform Infrastructure to provide visibility capabilities. Visibility in a SOA ecosystem has the following architectural implications on Platform Infrastructure mechanisms providing support for awareness, willingness, and reachability:
Platform mechanisms providing support for awareness will likely have the following minimum capabilities:
...
