User guide

The PORT_ID is also used to determine the configuration file to use on server startup. This

file can be a CFG or an XML-formatted configuration file and is used to provide information

to the server about what characteristics it should use when running. See Configuration Files

for more details on the use of configuration files.

You may choose to provide a separate configuration file for the server associated with each

JDBC dispatcher, or you may choose to use a single XML-formatted configuration file

containing the server attributes for all your servers.

The appropriate configuration file is determined by the dispatcher by trying to translate the

logical name RDB$JDBC_SQSCFG_<port> where PORT_ID is substituted for <port> prior

to logical name translation. If the logical name is not there then the dispatcher will try use a

configuration file from the JDBC system directories.

1. The file pointed to by the RDB$JDBC_SQSCFG_<port> if it exists.

3. RDB$JDBC_COM:SQLSRV_JDBC_SERVER_CFG.XML

4. RDB$JDBC_COM:RDBJDBCCFG.XML

Example 1

$ show log RDB$JDBC_SQSCFG_1888

The following is the precedence for this file search

2. RDB$JDBC_COM:<server name>_CFG.XML where the server name as

determined in previous steps is substituted for <server_name>

Logical name not defined and file

RDB$JDBC_COM:SQLSRV_JDBC_SERVER_CFG.XML does exist:

%SHOW-S-NOTRAN, no translation for logical name RDB$JDBC_SQSCFG_1888

$ MCR SQLSRV_MANAGE71

SQLSRV> CONNECT SERVER;

SQLSRV> CREATE DISPATCHER JDBC_DISP NETWORK_PORT TCPIP PORT_ID 1888

PROTOCOL JDBC;

The file

RDB$JDBC_COM:SQLSRV_JDBC_SERVER_CFG.XML

will be used.

Example 2

Logical name defined:

$ DEFINE/SYSTEM RDB$JDBC_SQSCFG_1888 RDB$JDBC_COM:MY_SRV1888_CFG.XML