User guide

Each Oracle SQL/Services JDBC dispatcher must be associated with an Oracle JDBC for

Rdb server. The PORT_ID specified in the dispatcher creation is the key to this relationship.

The PORT_ID specifies the TCPIP port that will be used by the Oracle JDBC for Rdb server

and is used by the dispatcher start up procedures to determine information about the

associated server.

In addition to which port the server will listen on, the PORT_ID may be used by the

dispatcher to determine:

• What type of Oracle JDBC for Rdb server to start

• The name that will be given to this server

• What configuration file to use for this server

• Any DCL command to run during the server startup procedure

The overloading of the use of the PORT_ID by the JDBC dispatcher is necessary as the

amount of information stored for a JDBC dispatcher is minimal keeping it in line with the

information stored for other SQL/Services Dispatcher types.

• RDB$JDBC_SQSNAM_<port>

• RDB$JDBC_SQSCMD_<port>

• RDB$JDBC_SQSTYPE_<port>

In the above logical names the <port> will be substituted by the PORT_ID of the JDBC

dispatcher prior to logical name translation

When determining the server information required to correctly start the associated Oracle

JDBC for Rdb server, the dispatcher will carry out the following steps in the order specified:

1. First the dispatcher will create a name for the server

2. Any DCL command required to be executed during server start up is then determined

4. The server type for the server is then determined.

In the process of determining the server attributes the dispatcher may try to translate the

following logical names:

• RDB$JDBC_SQSCFG_<port>

If no such logical names exist, the dispatcher will then use alternate methods to provide the

server with a name and will to try to locate a suitable command procedure and configuration

file. The following sections detail how these determinations are carried out.

3. The file specification of the configuration file to provide to the server is then

determine

7.1.2.1 Determining the server name