User guide

Given the PORT_ID of 1888:
•
•
•
server name = SQS1888
configuration file = RDB$JDBC_COM:SQS1888_CFG.XML
setup file = RDB$JDBC_COM:RDBJDBC_SQS_ONSTARTUP.COM
If we had chosen not to use standard naming then we would have had to set up logical
names to point to the appropriate files. See Associating an Oracle SQL/Services JDBC
Dispatcher to a Server for more details.
However, we still need to tell the dispatcher what type of server it will be starting so we
have to create the appropriate logical name. For simplicity we shall place this logical
name in the SYSTEM logical name table. See Determining Server Type
for information
on server type associations.
Idle User Timeout: <none>
$DEFINE/SYSTEM RDB$JDBC_SQSTYPE_1888 STD
If we had chosen to start up a POOL server we would not have needed to create this
logical name as this is the default server type used by the JDBC dispatcher, but as the
server type is a normal thin server we must inform the dispatcher of this fact using the
logical name.
Step 5 Start the JDBC dispatcher
Now that the configuration files are in place and any logical names used by the dispatcher
have been defined we can now use the SQL/Services manager to start the JDBC
dispatcher.
SQLSRV> start dispatcher my_jdbc_disp;
SQLSRV> show disp my_jdbc_disp;
Dispatcher MY_JDBC_DISP
State: STARTING
Autostart: on
Max connects: 100 clients
Max client buffer size: 5000 bytes
Network Ports: (State) (Protocol)
TCP/IP port 1888 Inactive JDBC clients
Log path: SYS$MANAGER:
Dump path: SYS$MANAGER:
SQLSRV> show disp my_jdbc_disp;
Dispatcher MY_JDBC_DISP
State: RUNNING
Autostart: on
Max connects: 100 clients
Idle User Timeout: <none>
Max client buffer size: 5000 bytes
Network Ports: (State) (Protocol)
157