Rule Execution Server console and parameters

Use these parameters to customize the behavior of the hosted transparent decision service (HTDS), and the Rule Execution Server console.

Disabling compression of test results
This Java™ Virtual Machine (JVM) parameter disables the compression of test results that are sent from Decision Runner to Decision Center. By default, the results are compressed (.zip), which can improve performance when a heavy load of test results are transferred. This compression can be disabled by setting the parameter to true. When disabled, Decision Runner sends results as plain text. The parameter must be set in the JVM that runs Decision Center, Decision Runner, or both features.
Table 1. Test result compression parameter
Name Default value Platform
jrules.cdi.disable.compressed.test.results false Operational Decision Manager, container
HTDS context root
This parameter shows the context root of the HTDS. It can be changed.
Table 2. HTDS context root parameter
Name Default value Platform
ilog.rules.res.HTDS_CONTEXT /DecisionService Operational Decision Manager, container
Managed XOM
This parameter shows the managed XOM in the RuleApp download.
Table 3. Managed XOM parameter
Name Default value Change default value Platform
ilog.rules.res.XOM_IN_RULEAPP_ARCHIVE false Yes Operational Decision Manager, container
Configuration file for the Rule Execution Server console log file
This parameter shows the configuration file for the Rule Execution Server console log file of the server information view. The param-value can be modified.
Table 4. Configuration file for the Rule Execution Serverr console log file parameter
Name Default value Platform
resconsole-logging-config-filename resconsole-logging.properties Operational Decision Manager
Maximum logger size
This parameter shows the maximum size of the logger in the server information view in KVB/MB. It can be changed.
Table 5. Maximum logger size parameter
Name Default value Platform
server-info-max-length 100 Operational Decision Manager
Persistence type
This parameter shows the persistence type, either data source or file. It can be modified.
Table 6. Persistence type parameter
Name Default value Platform
persistenceType datasource Operational Decision Manager
Root directory for the file persistence
This parameter is used only when the parameter persistenceType is file. It is the root directory for the file persistence, either absolute or relative path. It can be modified.
Table 7. Root directory for the file persistence parameter
Name Default value Platform
filePersistenceDirectory res_data Operational Decision Manager
XOM persistence type
This parameter shows the XOM persistence type, either data source or file. It can be modified.
Table 8. XOM persistence type parameter
Name Default value Platform
xomPersistenceType datasource Operational Decision Manager
Root directory for the file XOM persistence
This parameter is used only when the parameter xomPersistenceType is file. It is the root directory for the file XOM persistence, either absolute or relative path. It can be modified.
Table 9. Root directory for the file XOM persistence parameter
Name Default value Platform
fileXomPersistenceDirectory res_xom Operational Decision Manager
Calendar type
This parameter shows the type of calendar to be used for date display and input. Values: gregorian, islamic, hebrew, buddhist, chinese, coptic, indian, japanese, or taiwan. It can be modified.
Table 10. Calendar type parameter
Name Default value Platform
calendarType gregorian Operational Decision Manager, container
Decision Warehouse configurations
This parameter shows the list of decision warehouse configurations available in the Rule Execution Server console. It uses a list of names that are separated with commas. For each Decision Warehouse configuration, a context-param with the same name must be declared in this web.xml file. The value of this parameter is a string that begins with factoryClassname=FULLY_QUALIFIED_NAME_OF_THE_TRACE_DAO_FACTORY_FOR_THIS_CONFIGURATION, optionally followed by a semicolon (;) and the list of properties to initialize the trace Data Access Object (DAO) factory with. Each property in the list is defined as PROPERTY_NAME=PROPERTY_VALUE, and the properties are separated with semicolons.
Table 11. Decision Warehouse configurations parameter
Name Default value Platform
ilog.rules.res.trace.DECISIONWAREHOUSE_CONFIGURATIONS defaultDWConfiguration Operational Decision Manager
Default Decision Warehouse configuration
This parameter shows the default Decision Warehouse configuration. Traces are saved in the datawarehouse database that is created when you install Rule Execution Server.
Table 12. Default Decision Warehouse configuration parameter
Name Default value Platform
defaultDWConfiguration 
factoryClassname=ilog.rules.res.persistence.impl.jdbc.
IlrDatasourceTraceDAOFactory;JNDI_NAME=jdbc/resdatasource
 Operational Decision Manager
Management protocol
This parameter shows the management protocol, which collects and organizes information about managed devices.
Table 13. Management protocol parameter
Name Default value Platform
management.protocol jmx Operational Decision Manager
Management TCP/IP protocol port
This parameter shows the port used by the management Transmission Control Protocol/Internet Protocol (TCP/IP) protocol.
Table 14. Management TCP/IP protocol port parameter
Name Default value Platform
management.tcpip.port 1883 Operational Decision Manager
Management TCP/IP protocol timeout
This property states the amount of time in seconds before terminating a management TCP/IP protocol connection.
Table 15. Management TCP/IP protocol timeout parameter
Name Default value Platform
management.tcpip.timeout 20 Operational Decision Manager
Host HTTP header protection configuration
When enabled, this parameter provides a list of trusted hosts separated by semicolons. Each host must be a valid regular expression, for example, enableHostsAllowlist=true,hosts=host1.com;.*\.company\.com;myserver.
Table 16. Host HTTP header protection configuration parameter
Name Default value Platform
ilog.rules.res.TRUSTED_HOSTS_CONFIGURATION enableHostsAllowlist=false,hosts= Operational Decision Manager, container
SOAP compatibility modes
Deprecated feature:

Deprecation icon The SOAP compatibility modes 7.0, 7.1 and 7.1.1.3 are deprecated as of V9.6.0.0. See Deprecated and removed features for details.

When enabled, the SOAP compatibility mode is available for generating an HTDS descriptor file.
Table 17. SOAP compatibility mode parameter
Name Default value Platform
soap.compatibility.modes.enabled false Operational Decision Manager, container