1.1.1

[-log-file=<path> (default sqlfserver.log)]
[-property_name=property_value]*
The sqlf server command uses default values for any options that you do not specify on the command line.
However in most cases you will want to specify non-default values for each server that you start. The sections
that follow describe some of the most commonly-used options and configuration properties.
Stop SQLFire Servers
You can use two additional command forms to stop a running SQLFire server or display the status and process
ID of a running server:
sqlf server stop [-dir=working_directory]
sqlf server status [-dir=working_directory]
Specify the Server Working Directory
As a best practice, create a dedicated directory for each server that stores SQLFire log and status files.
Both the sqlf server command and FabricServer interface use a working directory to read input
configuration files and to write log files, disk store files, and the server status file. By default, a new SQLFire
server reads or creates files in the directory from which you run the sqlf server command or execute the
FabricServer.start method (the server working directory). As a best practice, create a dedicated directory
for each server and specify the working directory for the server at startup using the dir option at boot time. For
example:
mkdir server1
sqlf server start -dir=./server1
Input configuration properties can be defined in a properties file, specified as command-line options to the sqlf
server command, or specified as Java system properties using the -property_name=property_value syntax.
You can also rely on default property values for many aspects of the configuration. SQLFire uses different
conventions for defining properties in each location. See Configuration Properties on page 319.
Specify Client Connection Information
You need to specify thin client connection properties to avoid port conflicts at boot time.
By default, the SQLFire server that you start with the sqlf server command supports connectivity to thin
client applications over a unique bind address and port number combination. If you do not specify an address
and port, the server binds to the default address (usually localhost) on port 1527. Because each server must bind
to a unique address and port combination, you should specify the exact client connection properties to use at
boot time to avoid port conflicts. For example:
sqlf server start -dir=./server1 -client-bind-address=localhost
-client-port=1528
As an alternative, you can disable network services if you do not need to support thin client connections to the
server:
sqlf server start -dir=./server1 -run-netserver=false
Define Server Groups
Each server that you start with the sqlf server command is configured to host data by default and is
automatically added to the default server group. As you create partitioned or replicated tables in your cluster,
you will also want to configure servers to participate in different server groups to control where table data is
distributed.
vFabric SQLFire User's Guide228
Deploying vFabric SQLFire