Before you start

To configure Rule Execution Server on WebSphere® Application Server, you must follow specific steps.

The first 4 steps pertain to setting up a dedicated database and datasource. Then you activate security and deploy the Management Ear.

The Rule Execution Server console includes an Installation Settings wizard. If you sign in as the administrator, you can use it to create the database schema and run SQL drop statements that clear an existing Rule Execution Server database.

Note: Specific integration extensions are available from this URL: WebSphere Operation Decision Management Integration SupportPacs

The following table summarizes the steps that you follow to configure Rule Execution Server on WebSphere Application Server, depending on the type of persistence that you choose.

Installation Steps Persistence
File Data source JDBC
Step 1: Selecting and applying the persistence type
Check
Default persistence mode
Check
Step 2: Restricting database user permissions
Check
Check
Check
Step 3: Establishing the database credentials Not applicable
Check
Check
Step 4: Setting up a data source and connection pool Creating a JDBC provider Not applicable
Check
Check
Creating a data source and connection pool Not applicable
Check
Check
Creating J2C authentication data Not applicable
Check
Check
Setting custom properties Not applicable
Check
Check
Testing the connection to the database Not applicable
Check
Check
Step 5: Activating security on WebSphere Application Server Creating users and groups
Check
Check
Check
Mapping the resAdministrators group to the Monitor role
Check
Check
Check
Security policies for the Rule Execution Server console
Check
Check
Check
Step 6: Deploying the Rule Execution Server Management EAR
Check
Check
Check
Step 7: Creating a Rule Execution Server database schema Not applicable
Check
Check
Step 8: Deploying the Rule Execution Server MBean descriptors
Check
Check
Check
Step 9: Deploying the XU RAR
Check
Check
Check
Step 10: Deploying the hosted transparent decision service EAR Optional Optional Optional
Step 11: Setting the DecodeUrlAsUTF8 custom property Required if you deployed the EAR file for hosted transparent decision services (previous step). Required if you deployed the EAR file for hosted transparent decision services (previous step). Required if you deployed the EAR file for hosted transparent decision services (previous step).
Verifying the deployment and configuration Optional Optional Optional