Starting and Shutting Down Cloudconnector,
Page 2 of 3


[top]
[prev]
[next]
Index for This Book
Table of Contents
Documentation Top
Global Index

Starting Cloudconnector

Start Cloudconnector by running one of the included scripts and setting some basic properties. You need to modify these scripts for your environment.

Checklist of Startup Tasks

Step One: Open a Command Window for Starting the Server

Open a command window. You will set up the server environment in this window with scripts (or by running the commands found in those scripts).

Step Two: Set Path

For the scripts to work properly, PATH must point to the appropriate directory: $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin. This directory should appear before any of the other Cloudscape bin directories in PATH.

Step Three: Modify the setServerCloudscapeCP Script

The Cloudconnector installation includes scripts for starting up the server and for setting class path. They are located in $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin. You will modify the appropriate script for your platform and later run it to start Cloudconnector on the server machine.

If your platform does not support scripts, these files serve as examples.

  • setServerCloudscapeCP.bat
    Sets the classpath for the server. An example only. For Windows.
  • setServerCloudscapeCP.ksh
    Sets the classpath for the server. An example only. For UNIX.

This script sets a Cloudscape environment variable, CLOUDSCAPE_INSTALL, to the location of the Cloudscape installation directory.

Modify the script to alter the value of this variable so that it points to the location of the Cloudscape installation directory on your machine.

The script uses the value of that environment variable to set the class path for the current window to all the libraries needed to run Cloudconnector, as listed in “Libraries”. You may need to add application-specific libraries for Java data types as described below.

To summarize the information presented in“Libraries”, Cloudconnector’s class path must include:

  • frameworks/cloudconnect/classes
  • frameworks/cloudconnect/lib/weblogicaux.jar
  • frameworks/cloudconnect/license

NEW: The requirement to add frameworks/cloudconnect/license to the class path is new in Cloudconnector Version 3.0.

  • lib/cloudscape.jar or lib/cloudsync.jar
  • the application’s .zip, .jar, or class files if used as Java types referred to in SQL-J statements, work units, views, or tables

Step Four: Modify the startCS Script

The Cloudconnector installation includes scripts for starting up the server. They are located in $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin. Modify the appropriate script for your platform.

Overview

You may need to alter the script to:

  • modify the setting for weblogic.system.home
  • set cloudscape.system.home if necessary

When unaltered, the script sets weblogic.system.home to the current directory (the directory from which you run the script). It doesn’t set cloudscape.system.home.

For more details, see “Setting cloudscape.system.home and weblogic.system.home”.

For example, when you have finished altering the startCS.bat script, it might read:

java -ms16m -mx32m -noasyncgc - Dweblogic.system.home=c:\myweblogichome
-Dcloudscape.system.home=d:\mydatabases COM.cloudscape.core.CloudscapeServer

Setting cloudscape.system.home and weblogic.system.home

You can modify the appropriate startCS script to set two system properties: cloudsape.system.home and weblogic.system.home. If you do not want the default layout of directories, files, and databases (see “Default Directory and Properties Files Layout”), modify the system properties. Figure 3-1 illustrates how you would modify the following system properties:

  • weblogic.system.home
    Set to the directory holding the weblogic.properties file and the Cloudscape-WebLogic server directory, which by default is CloudscapeServer. The directory to which weblogic.system.home points must exist at the time the server starts up, because the WebLogic server looks for in it for the server-specific weblogic.properties file.
  • cloudscape.system.home
    Set to the directory in which the optional cloudscape.properties file and your Cloudscape databases are located. This directory can reside inside the directory to which the weblogic.system.home property points, be the same directory, be the parent directory, or be non-overlapping.

NOTE: The directory to which weblogic.system.home points must contain a directory called CloudscapeServer and the weblogic.properties file at startup.

Set these system properties using the -D command-line option to the JVM command in the script. For example:

java -Dweblogic.system.home="c:\serverstartup"
-Dcloudscape.system.home="C:\myHomeDirectory"

Figure 3-1 . The cloudscape.system.home and weblogic.system.home directories

Default Directory and Properties Files Layout

If you do not modify the script before running it to set system properties, the directory from which you run it effectively becomes both the cloudscape.system.home and the weblogic.system.home directories. It must therefore contain the following files and directories, as illustrated in Figure 3-2:

  • cloudscape.properties (optional)
  • the Cloudscape database(s) that you want to access
  • weblogic.properties
  • the directory for Cloudconnector
    The name in the Cloudconnector/WebLogic integration is CloudscapeServer. You can choose a different name by resetting the weblogic.system.name property (see “Setting Cloudconnector Properties”).

When the scripts are run from frameworks/cloudconnect, the weblogic.properties file provided with the distribution is used, no cloudscape.properties file is used, and the current directory becomes the system directory—that is, it holds Cloudscape database directories and the named CloudscapeServer directory.

Figure 3-2 . The default layout of directories and properties files.

Step Five: Modify weblogic.properties If Necessary

You may need to modify the weblogic.properties file that will be used by Cloudconnector upon startup. If you set weblogic.system.home to %CLOUDSCAPE_INSTALL%/frameworks/cloudconnect, Cloudconnector uses the weblogic.properties file in that directory.

Setting a Password

Modify the weblogic.properties file to select a password for the weblogic.password.system property (or use the default password as it exists in the file).

Modifying the Port Number

By default, Cloudconnector listens for client requests on port 7001. You can change this number by changing the value of weblogic.system.listenPort in the weblogic.properties file.

NOTE: Do not use the same port number for client requests and for incoming synchronization refresh messages (determined by the cloudscape.DataComm.port variable).

Step Six: Update the Path to the Cloudscape Home Directory

The weblogic.properties file has c:/cloudscape hard-coded as the path to the cloudscape base directory. This path is used by properties such as weblogic.httpd.documentRoot that affect the way the administrative servlet displays HTML pages.

Do a search and replace to replace this text with the actual path to your cloudscape base directory (and to uncomment it).

Step Seven: Run the Two Scripts

  1. Run the setServerCloudscapeCP script in the open command window. On Windows:

    setServerCloudscapeCP

  2. Run the startCS script. On Windows:
c:\> startCS

If you have not altered the weblogic.properties file, you should see messages showing that Cloudconnector is starting. The final message is that it is listening on port 7001. Once Cloudconnector starts, you can access it from a client application or applet, using the WebLogic client tools or simply the client JDBC driver and database connection URL.

An excerpt of an example of the messages you will see:

Fri Sep 10 13:28:22 PDT 1999:Opened log file .\CloudscapeServer\weblogic.log
Fri Sep 10 13:28:22 PDT 1999:<I> <WebLogicServer> Read global properties .\weblogic.properties
Fri Sep 10 13:28:22 PDT 1999:<I> <WebLogicServer> No per-server properties files found
Fri Sep 10 13:28:22 PDT 1999:<I> <WebLogicServer> ************ WebLogic Server (
4.5.0 07/29/1999 01:25:14 #49037) 'CloudscapeServer' from directory path .
Fri Sep 10 13:28:22 PDT 1999:<I> <WebLogicServer> ************ (c) 1995, 1996, 1997, 1998 WebLogic, Inc., (c) 1999 BEA Systems, Inc.
Fri Sep 10 13:28:22 PDT 1999:<I> <Config> Current properties list
Fri Sep 10 13:28:22 PDT 1999:<I> <Config> [0=Current 1=Command line 2=Per-server properties file 3=Global properties file 4=Embedded defaults ]

Verifying Startup

You can use the WebLogic utility class utils.t3dbping to verify that Cloudconnector is up and that the desired database services are available through it. For example, if you have a database pingDB available at the cloudscape.system.home location for Cloudconnector running on your machine on port 7001, the following should succeed:

java utils.t3dbping t3://hostname:portnumber "" "" "" COM.cloudscape.core.JDBCDriver jdbc:cloudscape:pingDB

Enter this command in a single line. The "" arguments are needed to satisfy the utils.t3dbping command line.

To test only the availability of the WebLogic services:

java weblogic.T3Admin t3://hostname:portnumber Connect 1
[top]
[prev]
[next]


Cloudscape Version 3.0
For technical support, go to: www.cloudscape.com and click Support.
Copyright © 1998 and 1999 Cloudscape, Inc. All rights reserved.