Before you start
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.
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).
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.
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.
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.