A Cloudscape framework is the environment in which it 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, its subdirectory includes:
Server Framework Libraries
Some frameworks are servers and so provide libraries for the server and clients and other resources.
/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 (ij, Cloudview, etc.) 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 each of the three frameworks, see the simple example.
For more information about frameworks, see Getting Started with 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.
RmiJdbc Server is a server framework that comes with Cloudscape. It is a customized version of freeware software. We recommend that you use only this customized version of the software and that you read the Cloudscape documentation on the customized driver.
RmiJdbc relies on JavaSoft Java RMI to transport a client's JDBC requests to a JDBC server that binds itself to a database JDBC driver. Cloudscape runs embedded inside the RmiJdbc server, and the client makes calls to a local RmiJdbc client driver. The only type of requests supported by RmiJdbc Server are JDBC requests.
The RmiJdbc JDBC Driver runs on the client side. The JDBC classes it implements contact the RmiJdbc Server to access databases.
NOTE: Read this section only if you have installed Cloudconnector.
Cloudconnector is a server framework purchased separately. It is a JDBC and HTTP server with compatible client software that allows multiple client applications to connect to a single instance of Cloudscape.
Cloudconnector software consists of a customized version of software provided by WebLogic. For details about the software, read the Cloudconnector release notes.
To get started with Cloudconnector, read the Cloudscape Server and Administration Guide.
NOTE: This section applies only to users on the Windows NT platform.
The Windows installers automatically install executables that allow you to use one of the server frameworks as an NT service. This section describes how to start such a service.
The system directory for the server (the location of cloudscape.LOG, the default database directory, and the directory from which to specify relative URLs) is %cloudscape_install%/frameworks/RmiJdbc/bin.
The system directory for the server (the location of cloudscape.LOG, the default directory for databases, and the directory from which to specify relative URLs) is %cloudscape_install%/frameworks/cloudconnect.
To stop either service, select the service and click stop.
Scripts are provided in %cloudcape_install%/service for uninstalling and re-installing services.
Stop any Cloudscape NT services you may have started before attempting to uninstall Cloudscape or Cloudconnector.