Parameter |
Description
|
Default Value |
LICENSEMONITOR |
This parameter specifies the attribute to
log user names in the access log during log on and log out
and includes the License Monitor information in
the access log. |
false |
CLUSTER_MODE |
This parameter specifies whether the server
is running in CLUSTER mode. |
false |
CLUSTER_URL |
This parameter specifies the url for the
cluster of nodes. It is used by the AdminServer for a
cluster of node servers. It is valid only if the
CLUSTER_MODE flag is set to true and
CLUSTER_ADMIN_URL has a valid
address. |
none |
CLUSTER_ADMIN_URL |
This parameter specifies the url of the
Admin
Server for a J2EE cluster of nodes. This
parameter is valid only if the
CLUSTER_MODE flag is set to true. |
none |
CLUSTER_ADMIN |
This parameter specifies the Admin Server
for a J2EE cluster of node servers. This flag is valid only
if CLUSTER_MODE flag is set to true. |
false |
SERVER_ROOT |
This parameter specifies the directory where
CES Java Server is installed. All other file paths in CES
Java Server are relative to the server root directory. To
avoid configuration problems, do not alter this parameter
after installing CES Java Server. |
none |
ENVFILE |
This parameter specifies the path to the
file (usually envfile.txt ) that contains
user-defined/configurable environment variables used for
image service applications. |
admin/configs/envfile.txt |
CONFIG_DIR |
This parameter specifies the path to the
directory that contains CES Java Server configuration files.
The configuration files include appserver.cfg,
dbinfo.cfg , dbload.cfg ,
timeragents.cfg , and lang.map . |
admin/configs/ |
META_QUERY_DIR |
This parameter specifies the relative path
for the directory that stores the meta-query files.
Meta-query files contain SQL statements which are static in
nature and usually used to retrieve meta-data information
from an
CES database. |
admin/configs/ |
ERROR_MESSAGES |
This parameter specifies the name of the
resource that contains localized error messages. User
friendly messages suppress the cryptic messages thrown by
either the database or Java Run-time exceptions. These
messages
are typically used by end user applications to display
errors.
The error message file is this setting plus
an option local code, plus .properties.
For example, for English users, by default
we have appserver as an entry for this parameter. For French
users, we have appserver_fr as an entry for
this parameter. |
appserver |
LICENSEFILE |
This parameter specifies the relative path
to the file that stores the license key for CES Java Server.
The name of the file is usually license.txt .
The license key contains information such as the number of
users that
can connect to CES Java Server, the expiration date of the
license, and permissions for edits of the CES database. |
admin/license/license.txt |
LOG_DIR |
This parameter specifies the relative path
used by CES Java Server to store server log files. Log files
are created by CES Java Server at runtime. CES Java Server
records errors, debug, and access information based on the
options chosen during administration setup. The
options will persist when CES Java Server goes down and
these options are
restored when CES Java Server is restored. |
admin/log/ |
MIN_EXP_POOL_SIZE |
This parameter specifies the number of
Python interpreters that are initialized and used by the
Expression Engine to execute Python script. Whenever a
client requests a Python interpreter, the Expression Engine
releases one
from the pool. The client gives it back to the pool after
the successful execution of the script. |
10 |
MAX_EXP_POOL_SIZE |
This parameter specifies the maximum number
of Python Interpreters that are created on demand. Whenever
the number of clients requesting Python Interpreters is more
than the MIN_EXP_POOL_SIZE, the Expression
Engine creates new Python Interpreters and gives them to the
client who requested them. All of the Interpreters that are
created on demand will be nullified after their use. This is
to have a MIN_EXP_POOL_SIZE number of
Interpreters at any given point of time.
The parameters MIN_EXP_ POOL_SIZE
and MAX_EXP_ POOL_SIZE were introduced to
optimize the number of python interpreters at the CES Java
server. |
1000 |
EXPRESSION_ENGINE |
This parameter specifies whether an
expression is executed when a record is
inserted/updated in an CES database.
If this parameter is set to true,
expressions are executed whenever records are
inserted/updated in the class to which the expressions are
attached.
If this parameter is set to false,
expressions are not executed when records are
inserted/updated in any class. |
true |
IGNORE_EVV_CASCADE_FOR_QUERY |
This parameter specifies the flag to turn on
or off the EVV cascade for query. |
false |
KEEP_CONNECTION_ALIVE |
This parameter specifies the option to keep
the database connections alive. This flag is useful when a
firewall exists between the CES Java Server and Database
Server. |
false |
J2EE_SERVER |
This parameter specifies the j2ee server for
which the CES Java Server is deployed.
|
|
MAIL_SERVER |
This parameter specifies the hostname for
the default SMTP mail server that is used by the
XDCFMailMessage class. Check with your system
administrator to find out the name of the mail server. The
default MAIL_ SERVER
can be overridden using the XDCFMailMessage.
setMailHost method. The
default value is...
Custom functions that need to send e-mail can use the
XDCFMail Message class for composing and sending mail
messages. |
mail.ds.com |
ADMIN_USER |
To log into the Administration utility, a
user name and a correct password are required. The
ADMIN_USER parameter specifies the user log on name
used by the Administration utility. |
admin |
SESSION_IDLE_TIME |
This parameter specifies the time interval
of an idle session to be removed from the session pool in
CES Java Server. The value is specified in minutes and has a
suggested minimum value of five minutes. This value can be
changed using the Administration utility at runtime. Idle
sessions occupy
resources and are periodically cleaned up based on the
values entered here. The optimum value for most interactive
applications users is usually about thirty minutes.
This value maybe over ridden by the client
side time out. For example, excalibur.html
client would time out based on the value in
web.xml and not this value. |
1440 |