Why and when to perform this task
Cloudscape Version 5.1 provides the following two separate frameworks for running Cloudscape with WebSphere Application Server:
You must use the embedded framework if you are running XA. Cloudscape does not support XA on Network Server.
Note: 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.
The following steps describe how to configure and run the Network Server framework.
Steps for this task
To start the Network Server, run the startNetworkServer.bat file, which is located in the WAS_HOME/cloudscape51/bin/networkserver directory. On UNIX platforms, the file is startNetwokServer.sh.
Cloudscape should work without any modifications to this file.
Use the entries in the db2j.properties file 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.
For more information on this file, see the Cloudscape documentation at www.ibm.com/software/data/cloudscape/pubs/collateral.html .
You can find this file in the WAS_HOME/cloudscape/bin/networkserver directory. On UNIX platforms, the file is stopNetworkServer.sh.
Find these tools in the WAS_HOME/cloudscape/bin/networkserver directory. These tools are:
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.
Note: You cannot run a new version and an older version of Cloudscape in the same WebSphere Application Server environment. For datasources created under the old version of Cloudscape, you must 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.
Note: 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.