User guide

specification be available to that process. The easiest way to ensure this is to have
system wide logical names.
In addition a control password, MySecretPassword has been chosen for control
access to the servers.
Although the controlpass can be stored in its plain text form in the configuration file,
Oracle recommends that you use the obfuscated form in the server characteristics section.
But make sure that you are consistent with the casing of the password as passwords are
case-sensitive
The controller may be used to provide this obfuscated password, but make sure that you
keep the casing correct by placing double quotations around the password phrase if you
use the controller in command mode.
Example
$ java -jar rdbthincontrol.jar -digest "MySecretPassword"
digest : 0x7315A012ECAD1059A3634F8BE1347846
See Password Obfuscation in Server Configuration Files
for more details.
name="DEFAULT"
/>
The new configuration file called MY_CFG.XML :
<?xml version = '1.0'?>
<!-- Configuration file for MY servers -->
<config>
<!-- SESSION -->
<session
tracelevel="0"
srv.mcBasePort="5517"
srv.mcGroupIP="239.192.1.1"
url="//localhost:1701/"
<!-- SERVERS -->
<servers>
<!-- DEFAULT server characteristics-->
<server
name="DEFAULT"
type="RdbThinSrv"
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"
147