Embedding Servers
Page 2 of 4

Overview

Since Cloudscape is written in Java, you have great flexibility in configuring your deployment. For example, you can run Cloudscape, a server framework, and another application in the same JVM as a single process. In this scenario, the server framework, like Cloudscape, is embedded in the application. Multiple client threads in the same JVM as Cloudscape can access a Cloudscape database through the local JDBC driver, and multiple external clients can access the same Cloudscape database by connecting to the embedded server framework.

The following are two typical scenarios that use embedded servers:

  • Occasional Remote Access or Occasional JDBC/ODBC Access

    Most work is done locally, but administrators want occasional remote access. You can embed a small footprint, lightweight server framework (like the provided RmiJdbc) in the same JVM as Cloudscape and the embedding application to handle the occasional access from outside the JVM. Another reason for providing occasional access through the lightweight server framework is that the main application may not provide JDBC access (for example, servlets provide only http access). Loading the server framework allows the administrator to use JDBC or ODBC tools.

  • Frequent Remote Access

    Many remote connections are needed, but local administration is also occasionally necessary. You can embed a robust server framework (like Cloudconnector) in the same application as Cloudscape and the embedding application. External connectivity goes through Cloudconnector, and local administration is handled by the embedding application through the local JDBC driver.