Context parameters for the Rule Execution Server console

The Rule Execution Server console is a web application. You can configure it by modifying the values of the context parameters in the web.xml deployment descriptor.

In the following table, the context parameters are listed in alphabetical order (ignoring the ilog.rules.res prefix where it exists). The parameters are documented within the web.xml deployment descriptor file itself. You can modify their values from any text editor.

Parameter name	Default value	Description
defaultDWConfiguration		The default Decision Warehouse configuration. Traces are saved in the `datawarehouse` database that you created when you configured Rule Execution Server.
filePersistenceDirectory		Used only when you set the persistenceType parameter to file. It is the root directory ruleset archives are stored (absolute or relative path).
fileXomPersistenceDirectory		Used only when you set the xomPersistenceType parameter to file. It is the root directory where rulesets with managed Java™ XOMS are stored (absolute or relative path).
ilog.rules.res.trace.DECISIONWAREHOUSE_CONFIGURATIONS		A comma-separated list of the Decision Warehouse configuration that are available in the Rule Execution Server console. For each Decision Warehouse configuration, you must declare a context-param parameter with the same name in the 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, the value can be followed by a semicolon (;) and the list of properties to initialize the trace DAO factory. Each property in the list is defined as `PROPERTY_NAME=PROPERTY_VALUE` and the properties are separated by a semicolon (;).
ilog.rules.res.HTDS_CONTEXT		The context root for hosted transparent decision services
JMX_XU_QUERY_PART		Specifies a subset of execution units (XU) that are visible from the console.
JMX_DS_QUERY_PART		Specifies a subset of decision services that are visible from the console. The possible keys and values depend on the application server.
management.protocol	jmx	Set this parameter to specify the protocol for communication with Rule Execution Server run time. The valid values are jmx or tcpip. Set the parameter to the tcpip value to enable communication outside an application server, for example for Java SE instances of the execution unit (XU).
management.tcpip.port	1883	When you enable the TCP/IP management mode, use this parameter to specify the port to which the management server must connect.
persistenceType	Depends on your application server	The persistence type for regular rulesets. The possible values are datasource or file.
xomPersistenceType	Depends on your application server	The persistence type for rulesets with managed Java XOM. The possible values are datasource or file.