User guide

Both Rdb and JAVA provide mechanisms by which you can set up your environment for
a specific version or variant. The Rdb version set up and the JAVA VM set up may be
carried out manually by you prior to invoking a thin server from the DCL command line.
•
•
•
•
•
•
Alternatively there are ways of providing the appropriate set up during the thin server
start-up when you choose to start the server using SQL/Services JDBC Dispatcher or by
using the controller. An example of this type of set up can be seen in the steps that
follow.
For the purpose of this walkthrough we will use the following on the server machine:
Oracle Rdb V7.2
JAVA 1.4.2 FAST VM
Step 3 Setup server-side configuration files and command procedures
Oracle JDBC for Rdb uses various command procedures to carry out server operations
and set up its environment. These command procedures may have to be altered to suit
your organizational and operational needs.
You may be required to:
Modify RDBJDBC_STARTUP.COM
Add an invocation RDBJDBC_STARTUP.COM from your system startup
procedure
Create a XML-formatted configuration file for your server definitions
Create a server set up command procedure
In addition Oracle recommends that XML-Formatted configuration files should be used
to maintain server and other information. These configuration file will have to be created
by you. An example of a server configuration file may be found below and in Sample
configuration file MY_SERVERS.XML.
RDBJDBC_STARTUP.COM
During installation a RDBJDBC_STARTUP.COM file will be created which may be
used to set up the required system wide logical names for Oracle JDBC for Rdb to
function correctly. You may choose to use this command procedure with or without
changes to set up the JDBC environment.
If the JDBC servers and drivers are to be used system wide then system logical names
should be used. In this case it may be appropriate to add the
RDBJDBC_STARTUP.COM command procedure to your system startup procedure.
145