User guide

The steps that follow assume that the appropriate logical names have been set up and are
available for use by you and Oracle JDBC for Rdb.
If you only require private use then JOB level logical names should be used, in which
case the RDBJDBC_STARTUP.COM may be copied and/or modified to change the
logicals to JOB level. Each user of the Oracle JDBC for Rdb on your server system will
then need to invoke this startup procedure prior to carrying out operations such as
controller actions, starting or stopping or accessing the thin servers.
The RDBJDBC_STARTUP.COM file provides logical names that will be used by the
Oracle JDBC for Rdb components to locate JARS, images and command procedures and
where to write log and temporary files. See the Oracle JDBC for Rdb Release Notes for
more information on this command procedure and the JDBC specific logical names.
Server Configuration File
Server, session and connection options may be added individually on the DCL command
line when you invoke a server or the controller, but it may be more convenient to place
these options in a configuration file and then use this configuration file when you carry
out server operations.
See Configuration Files
for more information on what may be contained in the
configurations files and the format of the data within the file. Oracle recommends using
the XML-formatted form of the configuration files as it does allow greater flexibility of
option specification and allows more than one server definition to be defined in a single
configuration file.
During installation a generic configuration file RDBJDBCCFG.XML is copied to the
RDB$JDBC_HOME directory. You may use this file as a basis of your server
configuration file. The configuration file provides information to Oracle JDBC for Rdb
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
MY_SRV 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
146