Download Quest One Quick Connect Virtual Directory Server

10.3. CONFIGURATION
instpagetitle: WRAS Instance Control
logrefresh_secs: 5
logdisplay_rows: 30
logdisplay_cols: 150
popupwidth: 1125
popupheight: 540
sleepsecs: 1
logmaxsize: 200000
logdbgblocksize: 50000
loglivblocksize: 8000
default_url: /
session_timeout: 1200
wras_hdr:<<<admrem/templates-wras/wras_hdr.html
wras_top:<<<admrem/templates-wras/wras_top.html
wras_bot:<<<admrem/templates-wras/wras_bot.html
wras_cpr:<<<admrem/templates-wras/wras_cpr.html
You can customize the following items by changing the values for the described attributes:
PORT Sets the port number where the RAS instance is listening.
installdir Stores the root installation directory of the product.
configdir Sets the directory where configurations will be stored. All the configurations that an instance of RAS
will manage are stored in this directory. If you set this directory to the same one that you are using
for local configurations, and launch a local RAS instance, then all of those configurations will also be
accessible remotely.
allowdir Controls the roots where DSGUI can additionally modify or link files. This allows you to control where
DSGUI can link to or store files that are not local to a configuration. This allows you to create shared
script libraries common to multiple configurations, and also to log to a common log directory. Please note
that using allowdir to store files, will result in your configuration NOT being automatically portable across
servers.
checkCredDebug, auditDebug, adminDebug, wrasDebug Debug level of the different RAS functionality
stages. Its value is the integer obtained from the bitmask defined as follows:
#define
#define
#define
#define
#define
#define
#define
#define
L_CRITICAL
L_WARNING
L_INFO
L_TRACE
L_PROCESSING
L_PDU
L_DEBUGGING
L_DUMPING
0
1
2
4
8
16
32
64
/*
/*
/*
/*
/*
/*
/*
/*
Errors causing running stops */
Errors that let the processing go on */
Informational messages for administrators */
Enter o exit functions */
Branch decisions and other info messages */
PDU entering and exiting a function */
Variable contents and other debugging info */
High verbosity in debug */
For instance, the checkCredDebug value would be 3 if you wanted Critical, Warning and Info messages in the
Credentials Check stage. All possible messages would be enabled with a value of 127.
auditloglevel Set of operations to be audited. Allowed values are "none", "changes", "operations", and "debug"
User Reference Manual
122