J2EE^TM Developer's Guide
Running the J2EE Tools

Cloudscape Server

The enterprise code examples in this manual have been tested with the Cloudscape DBMS, which is included in the J2EE SDK.

Starting and Stopping Cloudscape

Before your enterprise beans can access a Cloudscape database, you must run the Cloudscape server from the command line:

cloudscape -start

You should see output similar to the following:

Mon Aug 09 11:50:30 PDT 1999: [RmiJdbc] COM.cloudscape.core.JDBCDriver registered in 
DriverManager 
Mon Aug 09 11:50:30 PDT 1999: [RmiJdbc] Binding RmiJdbcServer... 
Mon Aug 09 11:50:30 PDT 1999: [RmiJdbc] No installation of RMI Security Manager... 
Mon Aug 09 11:50:31 PDT 1999: [RmiJdbc] RmiJdbcServer bound in rmi registry

To stop the server type the following command:

cloudscape -stop

You should see output similar to the following:

Attempting to shutdown RmiJdbc server 
RmiJdbc Server RmiAddr is: //buzz/RmiJdbcServer 
WARNING: Shutdown was successful!

Note: If you stop the server with Control-c, files will not be closed properly. When the server is started the next time, it must perform recovery by rolling back non-committed transactions and possibly applying the forward log.

Cloudscape Server Configuration

The default database used by the Cloudscape server is named CloudscapeDB. This database will reside in the $J2EE_HOME/cloudscape directory (where $J2EE_HOME is the directory where you've installed the J2EE SDK.) The CloudscapeDB database will be created automatically the first time it is accessed. The driver for the Cloudscape server is already configured in the $J2EE_HOME/config/default.properties file. No further changes by you are necessary.

Cloudscape ij Tool

The Cloudscape product includes an interactive SQL tool called ij. (This tool is not supported by Sun Microsystems, Inc.) You can run the ij tool by executing the cloudIJ.sh (UNIX) or cloudIJ.bat (Windows) script, which resides in the doc/guides/ejb/examples/util directory.

Prev | Next

TOC | Index