Network Deployment (Distributed operating systems), v8.0 > Applications > Web services
Web Services Distributed Management
Web Services Distributed Management (WSDM) is an OASIS approved standard that supports managing resources through a standardized web service interface. Your environment, such as WAS host or an operating system host that has an exposed resource as a web service within a single interface is used to manage and control resources. WSDM is a distributed management model, but it does not replace any existing WAS administration models. WSDM provides a new way to expose the internal product administration functions for a web service interface.
The existing administration interfaces, such as managed bean (MBean), wsadmin, and Java API, are more language and platform specific. WSDM provides a common, flexible infrastructure to manage the product resources by leveraging the web services protocols.
WSDM defines two specifications: Management Using Web Services (MUWS) and Management of Web Services (MOWS). MUWS defines how resources interact with the resources managed through a set of accessible web services interfaces. MOWS extends the MUWS concepts to define how a web service resource, itself, is managed. See Specifications and API documentation for MOWS and MUWS specifications. In addition to the manageability capabilities defined in the MUWS specifications, WAS WSDM also defines manageability capabilities unique to the product environment.
There is a general pattern that managed resources use to expose their manageability services through WSDM compliant web services interfaces. First, create a model of the managed resource. Typically the model of the resource is created using a modeling tool such as the Test and Performance Tools Platform (TPTP), an eclipse plug-in tool; however, a simple text document is sufficient. Use the modeling tool to develop the model of WAS managed resources. The following graphic illustrates the process.
Figure 1. Generic WSDM Concept
Code artifacts are generated from the resource model. Generated artifacts for each resource model include:
- A WSDL document that describes the web service interface for the management functions for that resource
- An implementation stub for the service implementation classes for that web service
- A client proxy for the service used in a program that needs to invoke the management functions of that resource
- A unit test code for invoking test cases that exercises the functions of that service
- Additional XML documents and schema that describe the properties, operations, and notifications associated with the managed resource
The code generated from the resource model is essentially an empty shell of the management web service for the modeled resource. The next step in the process is to enter code that acts as an adapter between the implementation stub for the service and the real resource management functions. In the case of the WSDM support implementation, this adapter code contain calls to theWAS AdminService APIs that expose normal product management functions. We must install the completed service implementation in a hosting web service environment. To install your WSDM application, see Deploying and administering enterprise applications and follow the steps for installing enterprise application files on an application server.
WSDM is a system application and it is disabled by default when the product is installed. We must first enable WSDM before you can use it to manage the product resources. Use scripting to enable WSDM.
Deploy and administering enterprise applications
Enable WSDM using wsadmin.sh
Install enterprise application files
Make deployed web services applications available to clients
Configure application and system policy sets for web services using wsadmin.sh
Related
Specifications and API documentation
Web Services Distributed Management manageability capabilities for WAS resource types
Web Services Distributed Management support in the application server
Concept topic