Configuring Rule Execution Server on WebSphere Application Server

To use Rule Execution Server on a new instance of WebSphere® Application Server for distributed platforms or for Linux on System z®, you follow a sequence of configuration steps. On WebSphere Application Server for distributed platforms, you can configure a cluster by using a profile template.

Operational Decision Manager 8.5.1 supports WebSphere Application Server 8.0, 8.5, and 8.5.5.

The steps or actions that are specific to Linux on System z are indicated separately.

Before you start: Opening the administration console
To configure Rule Execution Server on WebSphere Application Server, you must follow specific steps. Some of them depend on the persistence type.
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 that you provide the specific permissions to access the database.
Step 3: Setting up your database
If you are using database persistence, you must first create an empty schema for the database that is dedicated to Rule Execution Server and establish the credentials.
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 MBean descriptors
To configure Rule Execution Server for WebSphere Application Server, you must also deploy the MBean descriptors.
Step 7: Deploying the XU RAR
After you have deployed the MBean descriptors, you deploy the resource adapter archive (RAR) for the execution unit (XU) to WebSphere Application Server.
Step 8: Deploying the Rule Execution Server management EAR file
After you have activated the security and deployed the XU RAR, you deploy the Rule Execution Server EAR to WebSphere Application Server.
Step 9: 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 10: Deploying the hosted transparent decision service EAR file
If you want to enable hosted transparent decision services, you deploy the specific EAR file on the same node as the execution unit (XU).
Step 11: Setting the DecodeUrlAsUTF8 custom property
If you have deployed the hosted transparent decision service EAR file to enable those services, you must set the web container custom property DecodeUrlAsUTF8 to false to support a localized ruleset path.
Optional configuration steps
After completing the steps to configure Rule Execution Server, you can enhance your configuration by adding support for WebSphere MQ for example, or by setting up a multiserver configuration.
Verifying the deployment and configuration
It is good practice to verify that Rule Execution Server is successfully deployed and configured by running the diagnostics.

Parent topic: Configuring Operational Decision Manager on WebSphere Application Server