Configuring Rule Execution Server on JBoss 5 and 6.1

To use Rule Execution Server on a new instance of JBoss, you must deploy the provided archives for this server and perform a number of configuration tasks.

Before you start
To configure Rule Execution Server on JBoss you must follow specific steps. Some steps are mandatory, while others apply in certain cases only.
Step 1: Selecting and applying the persistence type
You can change the default datasource RuleApp and Java XOM persistence settings by running an Ant script that generates a new Rule Execution Server management archive.
Step 2: Enforcing database user permissions
If Rule Execution Server data is stored in a database, you can restrict the type of operations that a user can perform on a database by defining access privileges.
Step 3: Creating an empty database schema
Create an empty database schema with an XA data source.
Step 4: Creating a data source and connection pool
If you use data source persistence, you must create a data source and a connection pool.
Step 5: Configuring security
You control access to Rule Execution Server and enforce security by defining user groups and associated roles.
Step 6: Deploying the Rule Execution Server management EAR
To deploy the Rule Execution Server management EAR archive, you must copy it to the deployment directory of your application server.
Step 7: Populating a Rule Execution Server database
You can populate the Rule Execution Server database from the Rule Execution Server console or from the Command Editor.
Step 8: Deploying the Execution Unit (XU) RAR file
Deploy the Execution Unit (XU) to your application server.
Step 9: Deploying the hosted transparent decision service
You can deploy the hosted transparent decision service on your application server. This step is optional.
Step 10: Verifying the configuration
Although this step is optional, it is good practice to verify that Rule Execution Server has been successfully configured.
Optional configuration steps
You can enhance your configuration with additional options, such as multiserver configuration, or deploying onto a server cluster.
Troubleshooting
Various paths are available for you in case of poor performance. You can configure the XU memory profiler, explore database driver issues, or allocate more memory for applications.

Parent topic: Configuring Rule Execution Server