res-setup

The res-setup Ant task provides an alternative method for you to configure or modify the Rule Execution Server installation.

For example, you can use the res-setup Ant task for the following configuration tasks:

To run this Ant task, you call it from the Ant script file <InstallDir>/executionserver/bin/ressetup.xml.

res-setup element attributes

The following table describes the attributes of the Ant task elements and specifies whether they are mandatory or optional.

Table 1. res-setup element attributes
Element attribute Description Mandatory/optional
console.war.in The path to the input Rule Execution Server console WAR file

Pair C

At least one of the 4 pairs, A, B, C, or D, is required.

console.war.out The path to the output Rule Execution Server console WAR file.
console.ear.in The path to the input management EAR file.

Pair D

At least one of the 4 pairs, A, B, C, or D, is required.

console.ear.out The path to the output management EAR file
management.protocol Set this parameter to specify the protocol for communication with Rule Execution Server runtime. The valid values are jmx or tcpip. Set the parameter to the tcpip value to enable communication outside an application server. Example: Java SE XU instances

jmx is the default value.

If you enable the tcpip value, the JMX management mode remains enabled. You cannot disable it.

management.tcpip.port When you enable the TCP/IP management mode, use this parameter to specify the port to which the management server must connect. Optional

The default value is 1883.

persistence.type
The persistence type:
  • file for file persistence in Java SE
  • datasource for database persistence in Java EE
  • jdbc for database persistence in Java SE

Optional

If you choose to define the persistence type, set the attribute to the appropriate configuration value.

persistence.jdbc.user The login to use with the database connection for Java SE. Configuration jdbc
persistence.jdbc.password A password to use with the database connection for Java SE
persistence.jdbc.url The JDBC URL used to connect to the database
persistence.jdbc.crypted.password.enabled The password is encrypted in the XU configuration file.
persistence.jdbc.driver A driver implementation class to establish a connection with the database.
persistence.datasource.jndi The JNDI name of the data source. Configuration datasource
persistence.file.directory The path to the top directory that contains rulesets. Configuration file
xom.persistence.type
The persistence type:
  • file for file persistence in Java SE
  • datasource for database persistence in Java EE
  • jdbc for database persistence in Java SE

Optional

If you choose to define the persistence type, set the attribute to the appropriate configuration value.

xom.persistence.jdbc.user The login to use with the XOM database connection for Java SE

Configuration XOM jdbc

The default value is false.

xom.persistence.jdbc.password A password to use with the XOM database connection for Java SE.
xom.persistence.jdbc.url The JDBC URL used to connect to the XOM database.
xom.persistence.jdbc.crypted.password.enabled If you set this attribute to true, the password is encrypted in the XU configuration file for the XOM database.
xom.persistence.jdbc.driver A driver implementation class to establish a connection with the database that contains XOM resources
xom.persistence.datasource.jndi The JNDI name of the data source that contains XOM resources. Configuration XOM datasource
xom.persistence.file.directory The path to the top directory that contains XOM resources. Configuration XOM file
xu.in The path to the input XU RAR file

Pair A

At least one of the 4 pairs, A, B, C, or D, is required.

xu.out The path to the output XU RAR file
xu.config.in The path to the input XU ra.xml file

Pair B

At least one of the 4 pairs, A, B, C, or D, is required.

xu.config.out The path to the output XU ra.xml file
eventplugin.secured If you set this attribute to true, the connection to the event bus is done using credentials. The default value is true. By default, the initial resAdmin credentials are used for the connection.
eventplugin.username The login for the connection to the event bus.
eventplugin.password The password for the connection to the event bus. The password is stored as an encrypted string.