Introduction

---

There are no extra steps required in order to use the TDBISAMEngine component in DBISAM as a client engine since the default value of the EngineType property is etClient. However, in order to use the TDBISAMEngine component in DBISAM as a database server you will need to make some property changes before starting the engine.

Configuration Properties

---

The TDBISAMEngine component has several key properties that are used to configure the database server, which are described below in order of importance:



Starting the Server

---

Once you have configured the database server using the above properties, starting the server is quite simple. All you need to do is set the Active property to True. The following shows an example of how one might configure and start a database server using the default global Engine function in the dbisamtb unit (Delphi) or dbisamtb header file (C++):

with Engine do
   begin
   ServerName:='MyTestServer';
   ServerDescription:='My Test Server';
   { Only listen on this IP address }
   ServerMainAddress:='192.168.0.1';
   ServerConfigFileName:='mytest.scf';
   ServerConfigPassword:='test123456';
   Active:=True;
   end;

Default Login Information

---

The default user ID and password for the database server are:

User ID: Admin (case-insensitive)
Password: DBAdmin (case-sensitive)

This user has full administrator privileges and is widely known, so it is recommended that you delete it as a user once you have established another administrative user on the database server.

Database Servers Provided with DBISAM

---

DBISAM comes with an application (GUI) database server project for Delphi called dbsrvr.dpr and a command-line (console) database server project for Delphi called dbcmd.dpr. You can examine the source code of these projects to see how you would go about setting up a TDBISAMEngine component as a database server in a project. Both of these projects are also provided in compiled form with DBISAM.


The dbsrvr database server can be run as a normal application or as a Windows service. When running the dbsrvr database as a normal application, the server will display an icon in the system tray that can be right-clicked to obtain general information about the server, as well as start and stop the server. You can find the dbsrvr database server in the \servers\dbsrvr sub-directory under the main installation directory for the version of DBISAM that you installed.

If you wish to run the dbsrvr database server as a Windows service you must first install it as a service by running the database server with the /install command-line switch set. For example, to install the database server as a service using a command prompt window under Windows (2000 or higher) you would specify the following command:

dbsrvr.exe /install

To uninstall the dbsrvr database server as a Windows service you must run the database server with the /uninstall command-line switch set. For example, to uninstall the dbsrvr database server as a service using a command-prompt window under Windows (2000 or higher) you would specify the following command:

dbsrvr.exe /uninstall

After installing the dbsrvr database server as a Windows service, you can run the database server by starting the service interactively via the Windows Services management console, or by using the net start command-line command:

net start dbsrvr

You can stop the database service interactively via the Windows Services management console, or by using the net stop command-line command:

net stop dbsrvr

The dbcmd database server can only be run as a normal (console) application. You can find the dbcmd database server in the \servers\dbcmd sub-directory under the main installation directory for the version of DBISAM that you installed.

The database servers will accept commmand-line switches that affect their behavior. The following switches are supported when starting up either database server:


The only difference between starting the dbsrvr database server as a normal application and starting the dbsrvr database server as a Windows service is in the way the switches are specified. When the dbsrvr database server is started as a normal application, you may specify the switches directly on the command-line that you are using to start the database server. For example the following command will start the dbsrvr database server using port 13000 for the main port and 13001 for the administration port:

dbsrvr.exe /sp13000 /ap13001

When the dbsrvr database server is started as a Windows service, you may specify the switches via the Startup Parameters in the properties for the service in the Services management console, or directly on the command-line that you are using to start the dbsrvr database server with the net start command. For example the following command will start the database server as a service with it using port 13000 for the main port and 13001 for the administration port:

net start dbsrvr /sp13000 /ap13001

In addition to using command-line parameters, you may also use an .ini file to specify the parameters for the database server. The following is a sample .ini file that can be used with either the dbsrvr or dbcmd database servers:

; Sample DBISAM Database Server Parameters INI File

[Server Parameters]
; Default server name is the EXE name
Server Name=Test Server
; Default server description is DBISAM Database Server
; plus the Server Name
Server Description=Test Server Description
; Default server IP address is all addresses on the machine
Server Address=127.0.0.1
; Default server port is 12005
Server Port=10001
; Default server thread cache size is 10
Server Thread Cache Size=20
; Default admin IP address is all addresses on the machine
Administration Address=127.0.0.1
; Default admin port is 12006
Administration Port=10002
; Default admin thread cache size is 1
Administration Thread Cache Size=4
; Default configuration file name is dbsrvr
Configuration File=Test
; Default configuration file password is elevatesoft
Configuration Password=cannotguessme
; 0=main server allows unencrypted connections (default)
; 1=main server allows only encrypted
Encrypted Only=0
; Default encryption password is elevatesoft
Encryption Password=cannotguessme
; 0=overwrite log file (default) 1=append to log file
Append To Log=0

; SQL performance logging

; 0=no SQL performance logging (default) 1=log all statements with execution times above the min execution time (below)
SQL Performance Tracking=0
; Minimum execution time, in seconds, required before an SQL statement is logged (default is 30 seconds)
Min SQL Performance Execution Time=30
; SQL performance log file name
SQL Performance File Name=
; Max SQL performance log file size (default is 128MB)
Max SQL Performance File Size=134217728
; 0=no auto-incrementing of SQL performance log file name 1=auto-increment SQL performance log file name
Auto-Increment SQL Performance File Name=0
; Max SQL performance log file autoinc (default is 64)
Max Auto-Increment SQL Performance File Name=64

Multiple instances of the database server can be started on the same physical machine. The root name of the database server executable is used to determine the name of the log and parameters (.ini) files to use when the database server is started. Also, when running as a Windows service the dbsrvr database server relies on the root name of the database server executable to determine the service name. What this means is that to have multiple instances of the database server running on the same machine you must put them in separate physical directories if running them as a normal application, or copy the database server to different executable files with a different root name if running them as a service. For example, if you wanted to run two instances of the database server as services, you would copy the dbsrvr.exe to two separate executable files called dbsrvr1.exe and dbsrvr2.exe. Then you would install and run them as follows:

First database server

dbsrvr1.exe /install

net start dbsrvr1

Second database server

dbsrvr2.exe /install

net start dbsrvr2