Index
  Home
  Manuals
  Samples

solidDB(TM) 6.0
Development Kit for Linux glibc2

Version 06.00.1046
22 September 2008
SDK Build 0038

solidDB Evaluation Setup

This document contains instructions for setting up a solidDB environment. Instructions also cover running sample SQL scripts, and compiling sample C and Java programs with solidDB APIs.

1. Prerequisites

The prerequisite for completing the setup is that you have downloaded and successfully installed the solidDB Development Kit (SDK).  After a successful installation, you can find the following directories below your solidDB installation directory

soliddb-6.0/
    bin/
    ..
    eval_kit/
        standalone/
    ..

This "standalone" directory contains configuration and evaluation license files and it will hold your database once it is created in the way shown below.


The license file included with this release enables you to evaluate solidDB for 60 days each time you create a new database. All product options and features are available for evaluation. If you intent to purchase the product, see Orderme (or, orderme.txt)
 
In order to run samples, you must copy the license file into each of the sample run directories.  The license file (solid.lic) is in the root of the installation directory:

        soliddb-6.0/

The easiest way to copy of the license file is to execute the script
        copy_licenses.sh

This script copies the license file to all appropriate directories.

2. Creating the Database

2.1 Creating a Database in Unix Environments

A new database is automatically created when you start the database engine without an existing database. In order to create a new database in directory soliddb-6.0/eval_kit/standalone, enter the following command at the solidDB root directory:

  ./bin/solid -f -c ./eval_kit/standalone

Alternatively, you can start the database engine by running the unix bourne shell script named standalone_eval_server_start.

Next, you will get a message similar to:
"Database does not exist. Do you want to create a new database (y/n)?"

Answer 'y'.  Next, enter dba as the database administrator's username and password, and enter a suitable name for the System catalog. You can use any names for these fields, but be aware that there are NO defaults for these fields. You must remember the username and password to be able to access the database again. By default, solidDB uses "dba" for the username and password of evaluation databases, since "dba" is simple and easy to remember, and can be found in this document.  To use these values, type in "dba" as username and password, and type in any name you prefer as the catalog name. Press OK. A new database is created for you.

Tip1: in some Unix versions, you can type in the same terminal window where you started solidDB: 'ctrl-Z', and then 'bg', which will put solidDB running as a background process.  This helps to continue with the following steps (e.g. with 3.2).

Tip2: add the soliddb-6.0/bin directory to your path, and you can start solidDB executables regardless of which directory you are currently in.  

3. Verifying Evaluation Setup

If you successfully created the database, your solidDB process is now running, and you can connect to it from any client application by using the commmunication ports that the solidDB process is listening to.

You can verify your setup by trying to connect to the evaluation database. This can be done, for example, by using the command-line oriented Solid SQL Editor (solsql).

Tip: In Unix, if you have solidDB running as a foreground process, open a second terminal window, and start the solsql program from there.

3.1 Connecting to the Evaluation solidDB Server

  1. Start Solid SQL Editor by entering the following command at the solidDB root directory:
      ./bin/solsql "tcp 1315"
  2. Enter username and password (for example "dba", "dba").
      You are connected to the solidDB database.
  3. Enter any SQL query, for example:
      select table_name from tables;
      Note the use of semicolon at the end of the SQL command.
      For any solidDB database, you should receive a resultset of 79 rows.
  4. Close solsql by entering the command:
      exit;

3.2 Stopping the solidDB Server

Connect to the evaluation database as instructed in section 3.1. In solsql, give the following command (note the use of semicolon at the end of the commands, and note that you must use single quotes, not double quotes):

  admin command 'shutdown force';
  exit;

This command forces all users out of the server and shuts down the server gracefully.  

Note: when you shut down the server, it breaks the connection to solsql, and solsql may show an error message such as:

"14519: The user was thrown out from the server; connection lost "

The command 'exit' terminates the solsql tool.

Alternatively, you can stop the server by running the standalone_eval_server_stop.sh script.

3.3 Restarting the solidDB Server

If you have shut down the server, restart it by moving to the solidDB root directory and entering the following command:
     ./bin/solid -c ./eval_kit/standalone

Tip: if you have the solidDB "bin" directory in your path, you can go to the eval_kit/standalone directory to make it your current working directory, and start solidDB just by executing the command:
    solid

4. Running Samples

You can find sample programs and scripts in the "samples" directory, under the solidDB installation directory. There is a readme file in each "samples" subdirectory. Note that some sample scripts can remove and re-create database files residing in sample subdirectories. Only the database in the "standalone" directory is always left intact.

5. Continuing the Evaluation

At his stage, you have the initial setup ready.

Recommended next steps include:

  •    Install Solid JDBC driver (requires Java VM) (See JDBC Readme or jdbc_readme.txt).
  •    View the solidDB Getting Started Guide to learn more about basic usage of this product.
  •    View the solidDB Administrator Guide to learn more about administering this product.  

Copyright (c) 2008 Solid Information Technology, Ltd.  All Rights Reserved.