To Start and Stop Java DB

1. Set the classpath. The derby.jar, derbytools.jar, and derbynet.jar files must be in your classpath. By default, these JAR files are installed into /opt/SUNWjavadb/lib directory.

2. Set the system property derby.system.home to PortalServer-DataDir/derby.

3. Stop and start the database using Java DB NetworkServerControl class.

   For example, type:

   • java -Dderby.system.home=PortalServer-DataDir/derby org.apache.derby.drda.NetworkServerControl start to start the database.

   • java -Dderby.system.home=PortalServer-DataDir/derby org.apache.derby.drda.NetworkServerControl shutdown to stop the database.

   ---

   Note –

   By default, the Application Server's instance of Java DB uses the same port as Portal's (the Java DB default port of 1527). If you wish to run the Application Server's instance of Java DB, change the port from 1527 to some other value.

   If the Java DB process remains connected to a terminal, it will quit when the terminal exits, when the user logs out, or when the system in restarted. To detach the Java DB process from the terminal on UNIX-based systems, use the nohup command. On Windows system, make the Java DB process a Windows service.

   After the installation, Portal Server software can be configured to switch to Oracle. In that case, Java DB need not be running. It can also be stopped if use of Java DB is disabled for desktop and the portlet applications (such as wiki, fileshare, surveys) are not used in the deployed portal.

   ---