About Cloudscape v10.1.x

 

+

Search Tips   |   Advanced Search

 

Overview

WebSphere Application Server V6.1.x requires Cloudscape to run at a minimal version of v10.1x, which differs radically from previous releases of the database.

Use Cloudscape v10.1.x as a test and development database only.

 

The new code base

Unlike versions 5.1.60x and earlier, the new Cloudscape is a pure Java database server. The Cloudscape v10.1.x code base, which the open source community calls Derby, is a product of the Apache Software Foundation (ASF) open source relational database project. The new Cloudscape includes Derby without any modification to the underlying source code. Learn more about Derby code at the Apache Derby website.

 

Support for two phase-commit transactions over the Network Server framework

Only the Network Server framework provides support for multiple JVMs, such as appservers, to access Cloudscape. Earlier versions of Cloudscape cannot conduct two phase-commit transactions over the Network Server framework. However, the new Cloudscape can conduct XA transactions over Network Server; the new Derby Client JDBC driver gives Cloudscape v10.1.x that capability.

 

New Tools

Cloudscape v10.1.x is equipped with the following .bat/sh tools:

sysinfo Displays database version information
ij Manipulates the database instances

For transitioning users. Use ij as an alternative for the old Cloudscape cview tool, which does not exist in version 10.1.x.trns

dblook Dumps DDL information
networkServerControl Controls the networkServer process (can be used for functions such as ping and trace)
startNetworkServer Starts the networkServer process
stopNetworkServer Stops the networkServer process

When you run ij, surround the dbname by double quotation marks (" ") if it includes the full path name; for example: ij> connect '"c:\temp;create=true"'

This is ' " " ' without spaces.

The new Cloudscape package that is bundled with WAS is backed by full IBM Quality Assurance (QA).

 

Continued support

Beginning with 6.1.0.17, updates to Apache Derby 10.1 are not automatically applied to WAS V6.1. Instead, Derby 10.1 updates are located in a separate directory.

Do not apply the Derby update unless there is a specific reason to apply it.

You might be directed to apply the Derby update by support documentation for the Application Server or other IBM product documentation. Do not apply the Derby update unless you are certain that you will not revert the current Derby version to a previous version.

 

Resolving the problem

The JAR file for Derby can be found in...

WAS_HOME/derby/lib

The Derby updates are now installed in...

WAS_HOME/derby/fixes/10.1/derby_build_number

...for WAS or in...

was_smpe_root/derby/fixes/10.1/derby_build_number

...for WAS for z/OS.

For example: WAS on the AIX, HP-UX, i5/OS, Linux, Solaris., and Microsoft Windows operating systems:

WAS_HOME/derby/fixes/10.1/10.1.3.2.639536

WAS for z/OS:

was_smpe_root /derby/fixes/10.1/10.1.3.2.639536

Updates to the Application Server will install the JAR files for Apache Derby in this directory path. In addition, a script is added that you can use to apply the fixes to the derby/lib directory.

The script name is:

For WAS on the AIX, HP-UX, Linux, and Solaris operating systems:

updateDerby.sh

For WAS on the i5/OS operating system:

updateDerby

For WAS on the Windows operating systems:

updateDerby.bat

For WAS for z/OS:

updateDerby.sh

To run the script...

  1. Change the working directory to the directory that contains the Derby fix.

    For example, for WAS on the AIX, HP-UX, Linux, Solaris operating systems:

    cd /opt/IBM/WAS/AppServer/derby/fixes/10.1/10.1.3.2.639536

    For WAS for z/OS, the fix resides in the read-only SMP/E file system. For example:

    cd /usr/lpp/zWebSphere/V6R1/derby/fixes/10.1/10.1.3.2.639536

    Be aware that the command to change the directory should be on the same command line. Do not insert carriage returns.

  2. Run the script.

    On non-z/OS operating systems, the script copies the necessary JAR files from the current directory to the WAS_HOME/derby/lib directory.

    With WAS for z/OS, the script resides in the read-only SMP/E file system and requires a parameter, which is the location in the writeable configuration file system that is referenced by the WAS_HOME variable.

    For example:

    updateDerby /WebSphere/V6R1/AppServer

    The script will convert...

    WAS_HOME/derby/lib

    ...to a directory that contains symbolic links to the JAR files and to other contents of the directory...

    was_smpe_root/derby/lib

    You can use the script with an -undo option, which converts...

    WAS_HOME/derby/lib

    ...back to a symbolic link and points to the directory...

    was_smpe_root/derby/lib

    Use the -undo option before the WAS V6.1 Fix Pack is removed from the SMP/E.

    For example:

    updateDerby -undo /WebSphere/V6R1/AppServer

This issue is addressed with APAR PK66013.

 

Related concepts

Transaction type and connection behavior

 

Related tasks

Verifying the Cloudscape v10.1.x automatic migration
Upgrading Cloudscape manually

 

Related Reference

Data source minimum required settings, by vendor