Figure 2.1-1
shows a composition of the web services architecture with the artifacts
and
roles of the web services distributed management architecture.
In the above
figure, added to the web services architecture are the following web
services
distribute management artifacts and roles: [ED: add each bullet
id to figure.]
(a)
An execution environment within which the service is run.
This environment exists
as part of the service provider.
(b)
A manageability interface for the service and execution
environment [ED:
??]. The service provider advertises the
manageability interface as appropriate.
(c)
A functional interface for the service.
The service provider advertises the functional interface as
appropriate.
(d)
A discovery agency for manageability interfaces and a
discovery agency for
functional interfaces. These components
are conceptually separate but may overlap in an implementation.
(e)
A consumer of management services and a consumer of
functional
services. These roles are conceptually
separate but may overlap in an implementation.
In the above scenario,
the service provider advertises a manageable service in an appropriate
management discovery
agency.
First, the management
consumer uses a management discovery agency to find an
advertised management service and the interface
of its manageable web service. Next, the management consumer interacts
with this
manageability interface and accesses the management information and
operations provided
by the manageable web service.
The above
scenario is consistent for a management consumer interacting with
manageability
interfaces for discovery agencies and for execution environments. A
management consumer
can discover the managability portType for a discovery agency,
execution
environment, or functional service and interact with any of these
components
just as the businsess consumer can discover the portType for, and
interact
with, the functional service.
If a web service can
expose the functionality of an exposed resource though a web services
functional interface,
then, a web service can expose the manageability of an exposed resource.
[ED: figure 2.1-2
goes here]
Figure 2.1-2
illustrates
two possibile methods a manageable web service may use to fulfill
management requests
on an exposed resource.
With the first
method, a manageability service interacts directly with an exposed
resource
through a supported management interface.
For example, the manageability service may interact with an
exposed
resource supporting Java’s JMX facility, or, interact with an exposed
resource
supporting a proprietary C API.
With the second method,
the manageability service interacts indirectly with an exposed resource
through
a management agent acting as an intermediary.
This management agent interacts either directly or indirectly
with the exposed
resource.
This second
method enables existing management instrumentation of a resource to be
exported through web services to a management consumer.
Whether the
manageability
service uses the direct method or the indirect method, the management
consumer is
provided a consistent view of the management instrumentation of the
exposed
resource. The WSDM management consumer
remains unaware of any legacy management agent, facillity or API
utilized by
the manageability service.
Using web
services to describe and provide access to a manageability interface
for an
exposed resource creates a consistent, cross platform, cross vendor,
and
potentially cross enterprise interaction model for consumers and
producers of
management information.
Creating a web
services to access manageability information of an exposed resource
does not preclude
alternate means to access this information.
For example, a management consumer is able to use any and all
of WSDM, SNMP
or CIM/WBEM to access manageability information for an exposed resource
supporting these facilities.