User guide

See Configuration Files

for examples of configuring a pool server.

Contents

4.3 Configuration Files

Instead of setting the switches on the command line, you can specify a configuration file

that details the settings.

Two formats of configuration files are recognized:

 Standard Java Properties load file

 XML-formatted file

4.3.1 Standard Properties File

The following section describes the use of configuration file formatted as a standard Java

Properties load file. See XML Formatted Configuration File

for details on using an XML-

formatted configuration file.

The same server configuration options as specified in Server Configuration Options

and

Pool Server Configuration Options

can be used but with the following changes:

1. Each keyword requires a value, even those that do not have values on the command

line, these options are considered Booleans and thus should have the appropriate

‘TRUE’ value.

2. Each keyword must be separated from its value by an equals sign (=)

The –cfg switch on the command line allows you to specify the file specification of this

configuration file:

Format

java –jar rdb$jdbc_home:rdbthinsrv.jar –cfg thinsrv.cfg

Example

Java style comments and empty lines may be included in the file, for example:

// configuration file for our thin server

// the default port for the thin server is 1701 but we

// want it to listen on another port

port=1708

// allow anonymous connections