User guide

and the following command line statement:
$ java -jar rdbthinsrv.jar -cfg MY_CFG.XML -name "myServer"
A thin server with the name myServer will be started up on localhost listening to port 1799
with unlimited maxClients.
Contents
8.13 Named Databases
The XML-formatted configuration file allows the specification of known named databases,
allowing the Oracle JDBC for Rdb servers the ability to recognize alternate names for
databases served on the node the server is running on.
Similar to logical names and JNDI name spaces, the use of alternate names allows the
separation of the name the client uses for the database and the actual file specification of the
database.
Before requesting Oracle Rdb connect to a database, the thin server will check its list of
known databases for a match against the file specification portion on the given Connection
URL. If one matches, then the file specification portion of the URL property of the named
database will be used to provide the connection database specification.
Example
For example, given the following named database:
<database
name="mf_pers"
url="//localhost:1701/disk1:[databases]mf_personnel"
driver="oracle.rdb.jdbc.rdbThin.Driver"
URLPrefix="jdbc:rdbThin:"
/>
And the following connection statement:
Connection conn = DriverManager.getConnection(
"jdbc:rdbThin://bravo:1701/mf_pers",user, pass);
The client will be connected to the Oracle Rdb database
disk1:[databases]mf_personnel.rdb .
During the translation of the named database, the node and port part of the URL within the
named database definition is discarded.
Named database may also be used to restrict database access within the server. See
Restricting Database Access
for more information on this feature.
121