Web Services Distributed Management is an important open standard that enables abstracted, holistic, standardized remote management of IT resources. The following tech previews, used in conjunction with TPTP, allows developers to build WSDM based resource endpoints for managing resources:

• Tooling for Web Services Distributed Management: This set of plugins provides editors that enable the modeling of the manageability characteristics of a resource, generate the manageability endpoint, add the domain specific implementation code and deploy the built endpoint.
• WSDM Extension to the Managed Agent Explorer: This set of plugins adds a WSDM managed agent type to the Managed Agent Explorer allowing users to introspect and interact with WSDM resources including WSDM constructs like Service Groups and Relationships.
• WS-Notification support in the workbench This set of plugins add a WSDM extension to the Notification Broker in TPTP enabling the workbench to receive WS-Notifications from WSDM resources including Advertisements, Property change notifications and WEF (WSDM Event Format) events. Any plugin within the workbench can register for such notifications and the WSDM extension for the Managed Agent Explorer uses these notifications to provide dynamic updates in the Managed Agent Explorer.

The Apache Muse runtime provides an open source implementation of WSDM and related specifications. The above plugins use the runtime to build new endpoints, to add the required runtime JARs to the built endpoints, and to connect with WSDM endpoints both custom built and existing. The WSDM tech preview for TPTP 4.4 now includes the Apache Muse 2.2 runtime, the latest release of Apache Muse at this time, which implements the WSDM 1.1 specifications. More details of Apache Muse can be found here.

1. Make sure you have Java 5 / JDK 1.5 installed on your machine. The Web Tools Project which is used by the WSDM tooling has this dependency.
2. Install TPTP, its prerequisites and WSDM tech preview plugins downloaded from the release build at TPTP 4.4 download page. Download the following and extract them into a folder say c:/tptp.Do not use the all-in-one download as it contains EMF 2.2 and we need EMF 2.3 to generate WSDM endpoints that run on a J2EE container.
   • Eclipse SDK 3.3: eclipse-SDK-3.3-win32.zip (Different file name for different platforms)
   • TPTP Runtime: tptp.runtime-TPTP-4.4.0.zip
   • WSDM Plugins: btm.wsdm-TPTP-4.4.0.zip
3. Then install the latest stable build of the Eclipse WTP (Web Tools Platform) and its dependencies found on the WTP download page. Download and extract the following files to the install folder (c:\tptp). Choose to overwrite any existing files and folders when you extract the following.
   • Eclipse Modeling Framework (EMF, XSD InfoSet, SDO): emf-sdo-xsd-SDK-2.3.0.zip
   • Graphical Editing Framework (GEF): GEF-SDK-3.3.zip
   • Data Tools Platform (DTP): dtp-sdk_1.5.zip
   • WTP non-SDK package: wtp-R-2.0-200706260303.zip
4. Download and extract the Eclipse Equinox framework: eclipse-equinox-3.3.zip in the same folder (c:\tptp)
5. Start eclipse with the -clean option and the -vm option if needed. See this help section on starting Eclipse. Typically if you have installed your JDK 1.5 at c:\jdk1.5 you'd use the eclipse -clean -vm C:\jdk1.5\jre\bin\java.exe

The WSDM tooling download above includes Apache Axis2 1.1. Hence Apache Axis2 based endpoints you build using the tooling will already have all the Apache Muse and Apache Axis2 JARs as part of the deployable Web Archive (WAR). However if you wish to use a different version of Apache Axis2 then you must separately download and extract it. The endpoints generated with the tooling have currently been tested with Apache Axis2 1.1 and 1.1.1. You can download Apache Axis2 from here. Download the standard binary distribution and extract it to a folder on your machine.

Once you start the tooling you have tell it the location of Apache Axis2. You can do this by opening the Preferences dialog (Window > Preferences) and choosing Axis2 Server Location under Web services distributed management in the tree on the left. Browse to the Axis2 location. In the dialog page, uncheck the option to use the default built-in Apache Axis2 (version 1.1) and provide the location of your Apache Axis2 install. The tooling will check if the location contains a valid Apache Axis2 install before accepting your choice. You can also change the Apache Axis2 location whenever you do code generation in the tooling.