1.1

Table Of Contents
DescriptionOption
Use of locators is recommended for production systems.
Species an embedded locator in this server that is started and
stopped automatically with this server. The locator is specied as
-start-locator
<address>[<port>] (note the square brackets), or just <port>. When
address is not specied, the one specied in "-bind-address" is used,
if set. Otherwise the machine's default address is used.
If set to false, this peer does not host table data and acts as an accessor
member, still having the capability to route queries to appropriate
datastores and aggregating the results.
-host-data
Authentication mechanism for client connections. If
-server-auth-provider is not specied, then this
-auth-provider
same mechanism is also used for joining the cluster. Supported values
are BUILTIN and LDAP.
By default, no authentication is used.
Authentication mechanism for joining the cluster and talking to other
servers and locators in the cluster. Supported values are BUILTIN
-server-auth-provider
and LDAP. By default, SQLFire uses the value of
-auth-provider if it is specied, otherwise no
authentication is used.
If the servers or locators have been congured to use authentication,
this option species the user name to use for booting the server and
joining the distributed system.
-user
If the servers or locators are congured for authentication, this option
species the password for the user (specied with the -user option)
to use for booting the server and joining the distributed system.
The password value is optional. If you omit the password, sqlf
prompts you to enter a password from the console.
-password
Path of the le to which this member writes log messages (default
is sqlfserver.log in the working directory)
-log-le
Any other SQLFire boot property such as "log-level". For example,
to start a SQLFire server as a JMX Manager, use the boot properties
described in Using Java Management Extensions (JMX) on page 291.
See Conguration Properties on page 315 for a complete list of boot
properties.
-<prop-name>
Description
You can start servers that can host data (data stores) or those that do not host data (accessors) with the sqlf
utility, but either kind of member can service all SQL statements by routing them to appropriate data stores and
aggregating the results. Even for a member hosting data for a table, it is not necessary that all data be available
in the same member, for example, for DMLs that reference partitioned tables (PARTITION BY Clause). So
routing to other stores may be required. In addition it is possible for a member to be a data store but still not host
any data for a table due to no common SERVER GROUPS Clause.
385
sqlf Launcher Commands