The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Apache Derby resources from the Web services perspective, Part 3: Manage Apache Derby using Web Services Distributed Management

David Medinets (david.medinets@gmail.com), Software Consultant, Eclectic Consulting

David Medinets has been programming since 1980, when he started with a TRS-80 Model 1. He still fondly remembers the days when he could cross-wire the keyboard to create funny-looking characters on the display. Since those days, he has spent time debugging the Emacs text editor on UNIX® machines, working on VAXen, and building cutting-edge Web applications (think Toys"R"Us and 7,000 simultaneous users in 1999). David is married to Kathryn and lives in Fairfax, Virginia. He runs Eclectic Consulting and has authored books on Perl, PHP, and BASH. He also runs the CodeBits.com site.

Summary: So far in this three-part tutorial series about the concept of WS-resources and the Web Services Resource Framework (WSRF), you've created a Person resource and learned how to use WS-Notifications with it. This final installment shows you how to look at WS-Resources from a different perspective -- that of a tangible item rather than a set of information. You'll create a Web service to control the Apache Derby database you've been using throughout this project as well as the client that treats Derby as a WS-Resource.

View more content in this series

Date: 23 Mar 2007
Level: Intermediate
PDF: A4 and Letter (80 KB | 26 pages)Get Adobe® Reader®

Activity: 9455 views
Comments:

Summary

In this series, you've seen how to create WS-Resources out of bundles of information. In Part 1, you created the Person WS-Resource, and in Part 2, you added the ability to send and receive notifications to that resource.

In this final installment, you created a WS-Resource not from an object that you created, but out of the Derby database itself. In doing that, you created a Web service that enabled you to start and stop Derby remotely using a Web services client. This process demonstrated the use of the Apache Muse application, which makes this kind of thing much more straightforward than it would be if you were doing it on your own. More importantly, it demonstrated the fact that you can control applications -- or even devices -- using Web services.

At this point, you've seen WS-Resources from two sides: from the standpoint of creating them though information from the Derby database and from the standpoint of creating one out of the Apache Derby server itself. To do that, you used the Apache Muse application, which is designed as an implementation of the WSRF. You can also use this same technique to control other applications through the use of Web services, or you can build your own application from scratch.

Comments