|
Parameter
|
Description
|
|
User
|
The user name for the database account.
|
|
Password
|
The password for the database account.
|
|
Connection
|
The string that identifies the database to which you are
connecting.
|
|
RDBMS
|
The RDBMS type you are connecting to. Choose from the dropdown
list.
|
|
Application
|
This application name is used in the JDBC connection string of
the Rules Service. So, you have to specify the same application
name that you defined when publishing the web application from Web
Designer.
Only those applications are
listed for which the Owner is set to the user name for the database
account. You can set the Owner in the Authorizer.
|
|
Auto start with Service
|
Specifies whether Rules Engines are automatically started when
the Rules Service is started.
|
|
Definitions from
|
Specifies where the Rules Engine reads its definitions from.
This can be one of the following:
|
·
|
Automatic: If an application flat file can be found in the
filesearch path it is used. |
|
·
|
Database: Specifies that the application will always run from
repository, even if flat files exist in the filesearch path. |
|
·
|
Specify Location: Specifies the folder where flat files are
located. If flat files cannot be found at this location the
application will not run. |
|
|
Flat File folder
|
Specifies the folder where the flat file of the application is
located. This parameter can only be specified if the "Definitions
from" parameter is set to "Specify Location".
|
|
Language
|
The language of the application.
|
|
Iterated Decision
|
A single Decision to be iterated. The decision can be chosen
from a list of all decisions. Only decisions that do not reference
parameters are valid. Any messages will be directed to the log
file.
|
|
Decision Interval
|
The decision interval is used for the iterated Decision; the
default "NEVER" indicates that no decision should be executed.
|
|
Idle Timeout
|
The idle time interval. When the Rules Service has no activity
during the time specified in the Idle Timeout, it automatically
shuts down. The default is 'Never'. If set to some value, it is
advised to be set to a high value, because the restart of a Rules
Service can take a quite long time.
When the idle timeout expires,
the Rules Service frees all cached data and exits. In this case,
service recovery options on Windows, or a shell script on Unix,
must be used to automatically restart the service. The Auto Start
with service flag must be set to "Yes" for this.
These settings should be used
to restart the Rules Service automatically during the night when
the Rules Service has no activity.
|
|
Connection Timeout
|
This setting is not relevant within the USoft Web
architecture.
When a connection is made to
the Rules Service (via a JDBC connection), and the connection is
idle too long, this setting allows the Rules Service to
automatically break the connection. Within the USoft Web
architecture, as the Page Engine establishes a connection just for
the time period of a client request, and disconnects immediately
afterwards, this setting is not relevant.
|
|
Messages
|
Specifies the type of messages that are to be displayed:
|
·
|
Developer messages: specifies that all messages are displayed
in their entirety: these can sometimes be very technical. |
|
·
|
Enduser messages: specifies that some technical messages are
completely filtered out and others are replaced with the text
'internal error'. This setting has no effect on messages in the log
file. |
|
|
Log Level
|
This parameter specifies the information logged in the log
file.
|
·
|
With 'Error' (the default), only Rules Service or Rules Engine
errors are logged. |
|
·
|
With 'Info', not only errors, but also all information messages
are logged, for example about starting and stopping Rules Engines,
and violation messages generated by the Rules Engines. |
|
·
|
With 'Debug', all requests to a Rules Engine are logged. Each
logged request is preceded by the message: "credential validation
of user <username>". There is no other hidden credential
validation taking place. This is a manner to check which user is
actually performing a request on the rules service. |
|
|
Log Directory
|
You can set the location of the log file when configuring the
Rules Service. By default, the log file is stored in the location
specified during USoft setup
The log file name is: <App
name><RulesService port>_<RulesService process
id>_log.xml.
For example: APP17777_3452_log.xml for a Rules
Service running for application APP1 on port 7777 and started
on PID 3452.
Tip: If there are multiple log
files in the log folder, click Date Modified to see the file that
has been changed most recently.
The log file is in XML format.
When you click log file (a hyperlink) in the configuration pages,
the log files of all running Rules Services are transformed using
XSL technology. You can change these XSL transformations, defined
in:
<USoft installation
folder>\Templates\URE\
CompileLogFile.xsl
If you have changed the XSL
file, and you want to know the XML format of the original log file,
click the Peer Rules Services tab page in the Overview
configuration page, and then click the LogFile button of a Peer
Rules Service.
|
|
Log file name Prefix
|
By default this is the application name. It is useful to use
this differentiate between log file names if there are multiple
applications running. The prefix is added to the log file name, for
example, for the prefix APP1:
APP17777_3452_log.xml
|
|
Minimum/
Maximum Number of Rules Engines
|
At startup, the Rules Service starts the specified minimal
number of Rules Engines, and if needed (if a new request must be
handled, but all Rules Engines are busy with other requests), then
a new Rules Engine is automatically started up to the specified
maximal number of Rules Engines.
|
