Skip to main content


developerWorks  >  Open source | Information Management | SOA and Web services  >

Apache Derby resources from the Web services perspective, Part 2: Producing and consuming WS-Notifications with Derby

developerWorks

Level: Intermediate

David Medinets (david.medinets@gmail.com), Freelance Writer, Eclectic Consulting

17 Oct 2006

Register now or sign in using your IBM ID and password.

Continue on your mission to make your resources service-oriented architecture (SOA)-friendly. Part 1 of this three-part tutorial series showed you how to use WS-Resources to refer to Apache Derby data and structures from within the inherently stateless environment of Web services. Exposing a database entity through a Web service resource helps you easily provide state and database information through the standardized Web Services Resource Framework (WSRF). But how do you monitor the resource to check for changes? WS-Notification standard Web services. This installment, Part 2, walks you through producing and consuming Web services notifications with Apache Derby and teaches you about WS-Notification, which provides another standardized interface for the monitoring and examination of a Web service.

Objectives

  • Learn how to produce and consume Web services notifications with Apache Derby.

  • Use WS-Notification as a standardized interface to monitor and examine a Web service.

Prerequisites

None.


System requirements

The examples in this tutorial use Java code (version 1.5 or higher preferred) in combination with the following tools:

  • Apache Tomcat: This server is used to contain the Web services that provide access to the Web resources.
  • Apache Derby: This database is used to hold information about a person. The Web service looks up information about any given Web resource in the database.
  • Apache WSRF: This framework greatly simplifies development of your Web resource.
  • Apache Pubscribe: This framework supports the WS-Notification standard and provides stub messages and methods.
  • Apache Ant: Ant is a build environment that takes a standard build file and runs the commands necessary to produce the final application.

The examples and guides in this tutorial are based on the above installation within a Microsoft® Windows® environment, although the principles can also be applied within a UNIX®/Linux® environment.



Duration

Under 2 hours


Formats

html, pdf


Share this....

digg Digg this story del.icio.us del.icio.us Slashdot Slashdot it!


Back to top


Document options

Document options requiring JavaScript are not displayed


My developerWorks needs you!

Connect to your technical community


More in this series:
Apache Derby resources from the Web services perspective