Before you start

Learn what to expect from this tutorial, and how to get the most out of it.

About this tutorial

This tutorial goes beyond simple examples and illustrates how to build a WS-DistributedManagement (WSDM) interface for a software product that is very common in today's IT systems. It uses the tools and framework from the Apache Muse project to design, implement, and deploy a WSDM interface for the Apache HTTP Server, commonly-referred to as "httpd." If you have not used Muse before you are not expected to fully understand this tutorial until you have completed the introductory tutorial (see Resources) that is part of the project's documentation.

Back to top

Objectives

In this tutorial, you learn some of the finer points of designing a Web services interface for an existing manageable resource; along the way, you create a Service Definition Language (WSDL) document that defines a Web services interface for httpd. You'll then use the tools that ship with Muse to generate code and artifacts that adhere to the interface and which can be deployed as a Java™ Platform, Enterprise Edition (Java EE) Web application. Finishing the application so that it allows WSDM-compatible management clients to manipulate httpd will teach you how to map the concepts in WSDM to a product's existing management API.

Back to top

Prerequisites

This tutorial is written for Java programmers whose skills and experience are at an intermediate level. You should also have a solid understanding of the concepts and XML schemas that are defined in the WS-ResourceFramework (WSRF) and WSDM standards. Finally, it is expected that you have tried the introductory tutorial (see Resources for a link) that is included with the Muse 2.0 distribution and have successfully run the sample applications.

Back to top

System requirements

To run the application that you build in this tutorial, you need to have Apache Tomcat installed on your system. Keep in mind that Tomcat 5.5 requires Java Platform, Standard Edition (Java SE) 1.5, so if you are using Java SE 1.4, you'll want Tomcat 4.1 or 5.0. The work is shown using a Microsoft Windows console, but the tutorial can be completed by UNIX® and Linux® users as well.

1 of 15 | Next

Comments

Back to top

Table of contents

• Before you start
• Installing and understanding the Apache HTTP Server
• Designing a WSDL, Part 1: The resource properties
• Designing a WSDL, Part 2: The resource operations
• Designing a WSDL, Part 3: Creating the XML
• Designing a WSDL, Part 4: Adding the HTTP definitions
• Code generation with WSDL2Java
• Implementing the HTTP Server operations
• Implementing the HTTP Server operations
• Making the implementation more configurable
• Building and deploying the WSDM endpoint
• Testing the WSDM endpoint
• Conclusion
• Resources
• About the author

---

1 of 15 | Next

Next steps from IBM

Rational Application Developer features provide the comprehensive Integrated Development Environment (IDE) used to develop J2EE applications requiring Servlets and JavaServer Pages (JSPs).

---

• Try: Try the free Rational Application Developer, which helps developers quickly design, develop, test, analyze, and deploy high-quality Java, Javaserver pages, and J2EE applications.
• Article: Learn how you can deliver accurate, higher-quality J2EE apps with Rational Application Developer, open source JUnit and JUnitEE test frameworks.
• Tutorial: Build a Facebook application using PHP, the Spring framework, and J2EE.
• Demo: This demo shows how to use the new Java EE 5 Java Persistence API (JPA) framework.
• Buy: Rational Application Developer

Dig deeper into Tivoli on developerWorks

Try IBM PureSystems. No charge.

Experience today!

---

Get started with the cloud-based trial and pattern development kit.