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, Part 1: Apache Derby and OpenOffice.org Calc

Use Derby as a data store for OpenOffice.org Calc

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: Apache Derby signals a sea change in both desktop and Web-based applications. For the first time, that elusive target for developers -- complete data portability -- is easily attainable. This tutorial, the first in a series, shows how you can use Derby as a data store to overcome row-length limitations in OpenOffice.org's Calc and use that program's interface for data analysis while leaving the storage to Derby.

View more content in this series

Date: 26 Sep 2006
Level: Intermediate
PDF: A4 and Letter (1145 KB | 38 pages)Get Adobe® Reader®

Activity: 10305 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 shows you how to set up a Derby database that you can use as a data store for analysis. The data consumer is immaterial, but you'll use one of the more flexible, powerful tools available: OpenOffice.org Calc. The strengths of this approach are data portability, separation of concerns, and the leveraging of standards and best practices. Most approaches to interfacing with data rely on the use of object-relational mapping tools. However, the goal of this tutorial is actually the opposite: no mapping and direct client access to the underlying data.

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.

System requirements

To run the examples in this tutorial, you need:

JVM 1.4.x or later (version 1.5 or later is recommended).
Approximately 100 to 200MB of free space, depending on your choice of toolset.
At least 64MB of RAM for your virtual machine (VM).

You should also have the following tools to ensure portability -- both between toolsets and operating systems. I've chosen the Eclipse platform and the Derby plug-ins, but you may want to add the Callisto Data Tools plug-ins as well (although you won't use them during this tutorial). You also need the OpenOffice.org suite of tools, chief among them Base and Calc.

Download and install the following programs: