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:

Real-world Apache Derby: Who needs Ajax, anyway?

Take a database-centric approach to development

Dave Warner (david.warner@ngc.com), Senior Database Administrator, Northrop Grumman IT Solutions

Dave Warner has been working with databases since the early 1980s, focusing on business productivity and analysis. A Sun Certified Java Programmer, he's also certified in Microsoft SQL Server and works with Sybase tools extensively. He was formerly a chief technology officer at a small medical software company and presently works at Northrop Grumman IT Solutions as a senior database administrator.

Summary: Asynchronous Java™Script + XML (Ajax) is a dynamite technique for greatly enhancing the user experience on the Web. But it pays to remember that it's only necessary because of the distance between the information source and the browser. Shorten that distance, and much of the need for Ajax goes away. This tutorial -- the second in this series on Apache Derby database use -- offers an alternate technique, one that allows reuse across several different environments.

View more content in this series

Date: 19 Dec 2006
Level: Intermediate
PDF: A4 and Letter (435 KB | 27 pages)Get Adobe® Reader®

Activity: 8141 views
Comments:

Before you start

About this series

Apache Derby is no longer waiting in the wings -- it has taken center stage as a mature, robust database that can be used almost anywhere. This series of tutorials is for developers or expert users who want to explore the future of data storage. On this journey, expect to combine Derby with other standard tools (both user and developer) to create solutions that solve problems you face every day: ad hoc analysis, document storage, and that newest bugbear, compliance.

About this tutorial

This tutorial takes a database-centric approach to development. It starts by explaining the benefits and drawbacks of this approach, and then applies concepts and best practices to a small applet that gathers questions about Sarbanes-Oxley Act (SOX) compliance. You'll learn about Apache Derby's stored procedures and triggers as well as where and when they're used to your best advantage. You'll also learn how to install, configure, and use data tools included in the Callisto Web Tools Platform (WTP).

Objectives

Discover how to structure a simple, database-centric solution that provides a mechanism for collecting responses to questions about SOX compliance. Also, learn aspects of database-centric design and best practices.

Prerequisites

You should be reasonably comfortable with standard Java tools and have a smattering of Structured Query Language (SQL) experience. The ability to install and configure a Java Virtual Machine (JVM), Apache Ant or Eclipse, and Derby is required, and you must know how to run an applet from within Eclipse.

System requirements

To run the examples in this tutorial, you need the following:

JVM 1.4 or later (version 1.5 or later is recommended)
Approximately 100MB to 200MB of free hard drive space, depending on your choice of tool set
At least 64MB of RAM for your virtual machine (VM)
Eclipse Workbench 3.x
Apache Derby plug-ins for Eclipse

Instructions for installing the Eclipse Callisto Web Tools Platform are included in the tutorial.

Comments