Issue Details (XML | Word | Printable)

Key: GLASSFISH-7187
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: kumara
Reporter: msreddy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

use javadb provided by Java SE 6.x (or higher) or GlassFish update tool

Created: 17/Feb/09 03:56 PM   Updated: 22/May/13 03:59 PM
Component/s: admin
Affects Version/s: V3
Fix Version/s: future release

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: Sun


Issuezilla Id: 7,187
Tags:
Participants: kumara, msreddy and Tom Mueller


 Description  « Hide

CCC Proposal:

  • to use javadb provided by Java SE 6.x or higher or GlassFish update tool.

Rationale:

  • reduce distribution size inline with v3 modular architecture
  • provide for starting/stopping databases on remote instances
  • in future, the database on remote instance can be different from javadb

Impact:

  • in rare circumstances the database may not be installed, for ex. mac
  • impact on CTS, QA and quicklook

Fix:

  • install javadb separately and update the config/asenv.conf with the correct
    location of javadb

Process:

>asadmin start-database

>asadmin start-database --target <target-name>

For remote start/stop of database, the asadmin command will take --target option
with the name of remote instance, for ex. asadmin start-database --target
<target-name>, where the target-name is one of the remote server instances. If
no --target option is specified then the command is assumed to be local which
will try to start the local database similar to v2 in a separate jvm process. In
case of remote instance, the database will be started in embedded mode.

The algorithm for looking up javadb will be as follows:

01 Use the javadb defined by AS_DERBY_INSTALL property of asenv.conf.

02 If javadb is not found based on AS_DERBY_INSTALL property then check if the
corresponding jvm has it. If yes, then use the embedded database.

03 If embedded database is not found, then look for javadb installation based on
the operating system name. Pl. see the following for default locations of javadb
based on the type of installer and operating system.

All Platforms: javadb installer (javadb-10_4_1_3.zip)
expands under javadb, can be installed any where

Windows:
jdk6 installer (jdk-6u12-windows-i586-p.exe):
C:\Program Files\Sun\JavaDB, possible to exclude javadb from installation
ips package thru glassfish update tool:
installed javadb relative to ips image under glassfish
javadb installer (javadb_10_4_1_3.msi)
C:/Program Files/Sun/JavaDB (can be changed)

Solaris (x86/sparc):
jdk6 installer
/opt/SUNWjavadb
jdk-6u12-solaris-i586.sh
${JAVA_HOME}/db
ips package thru glassfish update tool:
installed javadb relative to ips image under glassfish
javadb installer (javadb-10_4_1_3-solaris-sparc.sh
installs under javadb wherever the script was run from
javadb pkg installer (javadb-10_4_1_3-solaris-sparc-pkg.sh)
/opt/SUNWjavadb

Linux:
jdk6 installer
/opt/sun/javadb
jdk-6u12-linux-i586.bin
${JAVA_HOME}/db
ips package thru glassfish update tool:
installed javadb relative to ips image under glassfish

Mac:
ips package thru glassfish update tool:
installed javadb relative to ips image under glassfish

04 If it is still not found based on the above, then display a message for
installing and updating the asenv.conf with javadb location.



Tom Mueller added a comment - 17/May/10 01:04 PM

Lowering priority as this is not expected in 3.1.