Configure Cloudscape V5.1

 

Overview

Cloudscape V5.1 provides the following two separate frameworks for running Cloudscape with WebSphere Application Server:

Embedded:	To use this framework, define a Cloudscape JDBC provider See the Cloudscape section in the minimum required settings article. You must use the embedded framework if you are running XA. Cloudscape does not support XA on Network Server.
Network Server:	This framework is a new feature in Cloudscape V5.1, and removes these limitations that existed in earlier versions of Cloudscape

If you plan to use Cloudscape 5.1 Network Server, see Problems accessing a Cloudscape database for details about a security problem that has been discovered in that version.

• inability to access a remote Cloudscape instance
• only one JVM can boot up the same database instance

 

sysinfo

Use Cloudscape's sysinfo tool to check the versions of Cloudscape products. Once you have the bin directory in your PATH, you can run sysinfo by typing the following command in a command window:

sysinfo

 

ij

You can use the ij tool to connect to a Cloudscape database. Once you have the bin directory in your PATH, you can execute the ij command by typing the following:

ij

The ij script sets up environment variables like class path and executes the ij program.

To create a database with ij, type the following command:

ij> connect 'jdbc:derby:testdb;create=true';

This command creates the database called testdb in the current directory and populates the system tables. You can then execute any SQL statements from the ij command line. When you are ready to leave ij, type:

ij> exit;

 

Network Server framework

1. To start the Network Server, run

   WAS_HOME/cloudscape51/bin/networkserver/startNetwokServer.sh

2. If necessary, update...

   WAS_HOME/cloudscape/db2j.properties

   Cloudscape should work without any modifications to this file.

   Use the entries in db2j.properties to turn on trace, change the port number on which Network Server listens, and enable other functions of the Network Server framework. The default port number on which the Network Server listens is port 1527.

3. Define a Cloudscape Network Server using Universal JDBC driver to connect Cloudscape V5.1 with WAS using the Network Server framework.

4. Stop the Network Server by invoking...

   WAS_HOME/cloudscape/bin/networkserver/stopNetworkServer.sh

5. Review additional tools available in the Network Server framework. These tools are:
   • sysinfo
   • cview
   • ij
   • dropSYSIBM (Drop the SYSIBM schema and its contents)

6. Create a SYSIBM schema.

   If you do not create the SYSIBM schema, you cannot see the datatypes when you create tables using the cview graphical user interface. The db2j.drda.loadSYSIBM property in the db2j.properties file controls whether the schema is created on the first connection to the database. The db2j.drda.loadSYSIBM property default value is true.

   You cannot run a new version and an older version of Cloudscape in the same WAS environment. For datasources created under the old version of Cloudscape, change the classpath in these datasources to point to the new version of Cloudscape; otherwise, the jar files from both versions of Cloudscape are loaded in the same environment. This might result in undesirable consequences or exception situations.

   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.

---

JDBC providers
Data sources
Connection pooling

Verifying a connection

Vendor-specific data sources minimum required settings

 

---