A framework is the environment in which Cloudscape runs. The framework in which you run Cloudscape affects how you run applications against Cloudscape.
The frameworks directory contains subdirectories for each framework with supporting files. Depending on the framework, the subdirectory includes:
bin Subdirectory
All subdirectories in this directory contain a bin subdirectory that has scripts that serve as examples of how to run some of the basic Cloudscape tools and utilities tailored for the particular framework. For server frameworks, start and stop scripts are also provided.
To use the scripts for a particular framework, modify the scripts as necessary and put that framework's bin subdirectory first in your path.
For an easy-to-follow example of how to run an application in the two frameworks, see the simple example.
For more information about frameworks, see Getting Started with IBM Cloudscape.
An embedded framework is the most basic framework. Cloudscape runs embedded in a Java application. When the application loads the local JDBC driver, it starts up the Cloudscape engine. When the application shuts down, it shuts down the Cloudscape engine. Only a single application can access a database at one time.
The bin subdirectory in frameworks/embedded contains scripts for running some of the Cloudscape tools in an embedded environment. For working in an embedded environment, put the frameworks/embedded/bin subdirectory first in your path.
A server framework is a continuously running Java application that allows multiple, remote JDBC applications to connect to Cloudscape.
The Cloudscape Network Server is a server framework that comes with Cloudscape. The Cloudscape Network Server works with the DB2 JCC JDBC driver; please read the Cloudscape documentation on the differences between this driver and the embedded driver.