Configuring Rule Execution Server on WebSphere Application Server

To use Rule Execution Server on an instance of WebSphere® Application Server, you must establish your database credentials, deploy the provided archives for this server, and follow a number of configuration tasks.

Before you start
To configure Rule Execution Server on WebSphere Application Server, you must follow specific steps.
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: Restricting database user permissions
If Rule Execution Server data is stored in a database, the database administrator might require you to provide the specific permissions that you need when accessing this database.
Step 3: Establishing the database credentials
You must establish the credentials of the database dedicated to Rule Execution Server if you are using database persistence.
Step 4: Setting up a data source and connection pool
You must create a JDBC provider (data source) and connection pool for WebSphere Application Server.
Step 5: Activating security on WebSphere Application Server
WebSphere Application Server provides security infrastructure and mechanisms to protect sensitive Java™ EE resources and administrative resources and to address enterprise end-to-end security requirements on authentication, resource access control, data integrity, confidentiality, privacy, and secure interoperability.
Step 6: Deploying the Rule Execution Server Management EAR
After you have activated the security, you deploy the Rule Execution Server EAR to WebSphere Application Server.
Step 7: Creating a Rule Execution Server database schema
You can create the Rule Execution Server database schema by running SQL scripts, either from the Rule Execution Server console or from the SQL tool of your database.
Step 8: Deploying the Rule Execution Server MBean descriptors
To configure Rule Execution Server for WebSphere Application Server, you must also deploy the MBean descriptors.
Step 9: Deploying the XU RAR
After you have deployed the MBean descriptors, you deploy resource adapter archive (RAR) for the Execution Unit (XU) onto WebSphere Application Server. The RAR file contains the XU and the persistence layer.
Step 10: Deploying the hosted transparent decision service EAR
You can optionally deploy the EAR file for hosted transparent decision services.
Step 11: Setting the DecodeUrlAsUTF8 custom property
The hosted transparent decision service requires that you set the web container custom property DecodeUrlAsUTF8 to False to support a localized ruleset path.

Parent topic: Configuring Rule Execution Server on WebSphere Application Server