User guide

<session
name="DEFAULT"
tracelevel="0"
srv.mcBasePort="5517"
srv.mcGroupIP="239.192.1.1"
/>
<!-- SERVERS -->
<servers>
<!-- DEFAULT server characteristics-->
<server
name="DEFAULT"
type="RdbThinSrv"
url="//localhost:1701/"
maxClients="-1"
srv.bindTimeout="1000"
srv.idleTimeout="0"
srv.mcBasePort="5517"
srv.mcGroupIP="239.192.1.1"
tracelevel = "0"
autostart = "false"
autorestart = "false"
restrictAccess = "false"
anonymous = "false"
bypass = "false"
tracelocal = "false"
relay = "false"
srv.startup="rdb$jdbc_home:rdbjdbc_startsrv.com"
/>
<!—My new server -->
<server
name="SQS1888 "
controlUser="SQS_CONTROL"
controlPass="0x7315A012ECAD1059A3634F8BE1347846"
type="RdbThinSrv"
url="//localhost:1888/"
/>
</servers>
</config>
Note
The server definition for SQS1888 is fairly minimal allowing most of the DEFAULT
characteristics to inherited. Also that the session section is used to ensure that the
broadcast IP the controller will check will be the same as the server uses.
Server Setup File
The JDBC dispatcher may require environmental setup for JAVA and the correct Oracle
Rdb version to run. This setup can be done in a command procedure that will be
executed just prior to starting the
actual server image.
As the setup is fairly generic we have decided to create the file
RDBJDBC_SQS_ONSTARTUP.COM and place it RDB$JDBC_COM directory. By
155