Configuring Rule Execution Server on WebSphere Application Server for Linux on System z

To be able to use Rule Execution Server on an instance of WebSphere® Application Server for Linux on System z®, you must set up the persistence for the resources, create a JDBC provider, deploy the provided archives for this server, and activate security.

Before you start
Review the tasks that you must perform to complete the configuration of WebSphere Application Server for Linux on System z.
Step 1: Setting up the DB2 database
Customizable scripts are provided to create your DB2® database schema, but you must first create an empty database.
Step 2: Creating a JDBC provider
To enable Rule Execution Server, you create a JDBC provider in WebSphere Application Server, as the first step in creating a data source.
Step 3: Setting up Java 2 connection security
After you have created your data source and connection pool in WebSphere Application Server, you can secure your enterprise information system by creating J2C authentication data.
Step 4: Creating a data source and connection pool
After you have created your JDBC provider, you create a connection pool and a data source in WebSphere Application Server to enable Rule Execution Server.
Step 5: Creating users and groups
Create users and groups that map to the Rule Execution Server security roles.
Step 5a: Mapping the resAdministrators and resDeployers groups to the Monitor role
When creating user groups, you might have to map the resAdministrators and resDeployers users to the Monitor role.
Step 6: Deploying the Rule Execution Server Management EAR
Deploy the Rule Execution Server EAR on WebSphere Application Server.
Step 7: Creating the Rule Execution Server database schema
After you have created an empty database, you can create the Rule Execution Server database schema by running SQL scripts, either from the Command Editor or from the Rule Execution Server console.
Step 7a: Testing the connection to the database
After you have created a data source and connection pool, and set the custom properties, you can test the connection to the 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.
Step 10: Deploying the hosted transparent decision service EAR
If you require the hosted transparent decision service, you must deploy the EAR on the same node as the XU.
Step 11: Setting the DecodeUrlAsUTF8 custom property
After you have deployed the hosted transparent decision service EAR, you define the web container custom property DecodeUrlAsUTF8 to support localized ruleset paths.

Parent topic: Configuring Rule Execution Server on WebSphere Application Server