Before you start

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

About this tutorial

This tutorial teaches you about an often-overlooked tool in the Apache Muse project, one that can help you align with the best practices discussed in a previous article, "Designing manageable resources with Apache Muse." The tool, WSDLMerge, allows you to design your manageability capabilities using separate WSDL and XML schema files and then generate a single WSDL that can be consumed by Muse's code-generation tool, WSDL2Java. Read this article to learn how to design and develop a system with multiple manageable resources without a great deal of cut-and-paste hacks.

Back to top

Objectives

In this tutorial, two sample resource types that are commonly seen in today's IT systems are defined; these resources share some traits but also have their own unique features. Learn how to break up the features of these resources so that you can design Web service interfaces for them that share as many definitions as possible. The Web service interfaces are made up of multiple capabilities, each with its own separate WSDL document. The WSDLMerge tool is used to manage these WSDLs, allowing you to develop each capability separately and then generate a single WSDL for application deployment. This tutorial shows you how to define complex resource types with Apache Muse without resorting to WSDL files that have thousands of lines of code and lots of duplicate XML.

Back to top

Prerequisites

You should have experience with Apache Muse and the standards that it implements: WS-ResourceFramework (WSRF), WS-Notification (WSN), and WS-DistributedManagement (WSDM). You do not have to be an expert, but you should understand the basic concepts behind the Muse programming model and be able to complete the Muse tutorial on your own. Also, it is recommended that you read the precursor article to this tutorial.

Back to top

System requirements

To run the examples in this tutorial, you need Apache Muse 2.1.0 or higher, as well as Apache Ant 1.6.0 or higher.

1 of 14 | Next

Comments

Back to top

Table of contents

• Before you start
• A sample project: Build WSDM interfaces for multiple resources
• Design a WSDM interface for Java application servers
• Design a WSDM interface for database servers
• Create common WSDL documents, 1: WS-* definitions
• Create common WSDL documents, 2: Custom definitions
• Create WSDL documents for resource-specific behavior
• Use WSDLMerge to create a complete WSDL
• Use WSDL2Java to generate the resource implementations
• The WSDLMerge/WSDL2Java development cycle
• In conclusion
• Download
• Resources
• About the author

---

1 of 14 | Next

Next steps from IBM

• Try: WebSphere Application Server
• Briefing: Building SOA solutions and managing the service lifecycle
• Buy: WebSphere Application Server

Dig deeper into Tivoli on developerWorks

Try IBM PureSystems. No charge.

Experience today!

---

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