Sun Java System Application Server Enterprise Edition 8.2 Release Notes for Microsoft Windows

Derby Database Used by Samples Script Created in Wrong Location (ID 6377804)

There are two aspects to this bug:

  1. When sample application setup scripts that use the Derby database are run, the Derby database is created in the current directory or in the <install_root>/bin.

  2. The sample build Ant script creates a password.txt file that stores the admin password file in the current directory, which will not be writable in nonroot and sparse zones scenarios.

Solution

  1. Derby database location – Use the --dbhome option with the start-database command to create the database at the value specified for --dbhome. For example, the following is the asadmin command syntax for start-database.


    start-database [--dbhost 0.0.0.0] [--dbport 1527] [--dbhome db_directory] [--echo=false] 
    [--verbose=false]
  2. Location of the password.txt file – By design, the samples directory is expected to be writable because all the build commands include the creation of a password.txt file in that directory. Be sure to install a working copy of the samples in a writable location.