![]() |
Starting and Shutting Down the Cloudconnector Server
|
|
Starting Cloudconnector on the ServerStart Cloudconnector by running the included scripts and setting some basic properties. You need to modify these scripts for your environment. To successfully complete the steps in this chapter, you will need to know the following:
This chapter is divided into two major sections: Startup Tasks
Step One: Open a Command Window for Starting the ServerOpen a command window. You will set up the server environment in this window using commands in the provided scripts. Step Two: Include Cloudconnector in the PATH VariableFor the scripts to work properly, the PATH variable must include the Cloudconnector installation directory: $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin (where $CLOUDSCAPE_INSTALL is the directory in which you installed Cloudscape). This directory should appear in the path before any other Cloudscape directories. Step Three: Modify the class path Script (setServerCloudscapeCP)In this step, modify the script that sets the class path on the server. While you can set the class path directly from the command line, you may find it easier to use the included scripts. They are located in $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin. Modify the appropriate script for your platform:
NOTE: If your platform does not support scripts, use these files as examples. The setServerCloudscapeCP script sets the CLOUDSCAPE_INSTALL variable to point to the Cloudscape installation directory, and then modifies the CLASSPATH variable to include that directory.
Step Four: Modify the Startup Script (startCS)In this step, modify the script that you will use to start up the server. While you can start up the server directly from the command line, you may find it easier to use the provided scripts. They are located in $CLOUDSCAPE_INSTALL/frameworks/cloudconnect/bin. To view a printout of startCS, see The Cloudconnector Scripts. Modify the startCS script to reflect the correct settings for two properties in the java command line: If you do not set these system properties, Cloudscape assumes you intend the current directory for both (see Default File Configuration).
NOTE: At the time the server starts, the directory to which weblogic.system.home points must contain a directory called CloudscapeServer and the weblogic.properties file. To specify these properties, modify the JVM -D command-line options in the startCS script. For example: -Dweblogic.system.home=c:\srvStartDir The following figure illustrates how you would modify these system properties. Figure 3-1 The cloudscape.system.home and weblogic.system.home directories When you have finished altering the startCS script, it should look similar to the following: java -ms16m -mx32m -noasyncgc Default File ConfigurationIf you run the startCS script without modifying it, the directory from which you run it effectively becomes the location for the cloudscape.system.home and the weblogic.system.home properties. It must therefore contain the following files and directories, as illustrated in Figure 3-2:
If startCS is run from the frameworks/cloudconnect subdirectory, the weblogic.properties file provided with Cloudscape 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 CloudscapeServer directory. Figure 3-2 The default layout of directories and properties files. Step Five: Optionally Modify weblogic.propertiesYou may need to modify the weblogic.properties file that will be used by Cloudconnector upon startup. Two common customizations are: There are numerous other customizations you can make, described in Setting Cloudconnector Properties. NOTE: If you will be using the weblogic.httpd.documentRoot property, you will need to uncomment and customize the default entry for the directory path in the weblogic.properties file. This property affects the way the administrative servlet displays HTML pages. Setting a PasswordA password is required for Cloudconnector. You can locate and use the default password provided in the weblogic.password.system property of the weblogic.properties file, or you can modify this property to reflect a different password. Modifying the Port NumberBy 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 both client requests and incoming synchronization refresh messages (determined by the cloudscape.DataComm.port variable). For more information, see the Cloudscape Synchronization Guide. Step Six: Run Both ScriptsAfter you have modified both scripts to reflect your environment, run them in the following order to start up the Cloudconnector server:
Typically, you should see messages showing that Cloudconnector is starting. 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. Following is a sample excerpt of messages you might see: Fri Sep 10 13:28:22 PDT 1999:Opened log file .\CloudscapeServer\weblogic.log
Verifying StartupYou can use the WebLogic utility class utils.t3dbping to verify that Cloudconnector is running and that 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 "" "" "" Enter this command in a single line. The "" arguments are needed to satisfy the utils.t3dbping command. To test only the availability of the WebLogic services: java weblogic.T3Admin t3://hostname:portnumber Connect 1 |
|
![]() Cloudscape Version 3.6 For information about Cloudscape technical support, go to: www.cloudscape.com/support/.Copyright © 1998, 1999, 2000 Informix Software, Inc. All rights reserved. |