User guide

about the various servers you may be running. In addition it provides session information

for users of the controller.

For this walkthrough we have decided to create the definition for a thin server called

SQS1888 listening on port 1888. The generic configuration file was copied and changed

to add this information.

We have also chosen to place configuration and any other site specific files in the

RDB$JDBC_COM directory, mainly as this is a standard Oracle JDBC for Rdb directory

and the logical name should be already set up for us at the system level. The files may be

placed anywhere on your system, as long as the controller and server processes can

access them. Remember that a server process will be started up in much the same way as

a normal login to the system, so it is important that any logical names used in the file

specification be available to that process. The easiest way to ensure this is to have

system wide logical names.

In addition a control password, MySecretPassword has been chosen for control

access to the servers.

Although the controlpass can be stored in its plain text form in the configuration file,

Oracle recommends that you use the obfuscated form in the server characteristics section.

But make sure that you are consistent with the casing of the password as passwords are

case-sensitive

The controller may be used to provide this obfuscated password, but make sure that you

keep the casing correct by placing double quotations around the password phrase if you

use the controller in command mode.

Example

$ java -jar rdbthincontrol.jar -digest "MySecretPassword"

digest : 0x7315A012ECAD1059A3634F8BE1347846

See Password Obfuscation in Server Configuration Files

for more details.

We have chosen to create a configuration file using one of the standard file specification

used by the dispatcher when searching for configuration files. See Determining the server

configuration file on how the dispatcher locates a configuration file to use.

$type RDB$JDBC_COM:SQS1888_CFG.XML

As the port used by the server will be 1888 we will create a new configuration file called

SQS1888_CFG.XML and place it RDB$JDBC_COM directory:

<?xml version = '1.0'?>

154