IBM Rules Engine (ODM) Primer Series II: Rule Execution Server (RES) Service installation

Today begins the ODM Starter Series II, in this series I will talk about the installation of rule execution services, the packaging of rule sets, and how to publish post-deployment rule sets as Web services for use by other services or applications.

First, let's look at a picture:

This is the one I drew. The relationship between the various components of ODM, in which the Web app is our own project or application that can invoke the Ruleapp package already deployed on RES in the form of a Web service to execute the rule.

Take another look at the picture:

(Screenshot from IBM website)

This is a diagram on the IBM website that describes how the different components of the ODM interact.

As you can see from these two graphs, res plays a very important role in the ODM entire product-executing the rule set, which is why res is the rule engine, so today we'll build the Res service together.

ODM provides us with a different web container corresponding to the RES installation service package, you can open the following directory to view "{Installpath}\ibm\odm815\odm\executionserver\applicationservers", where { InstallPath} is your ODM installation path, where you can see several types of Web container-named folders:

Here, I weblogic12 for example, to install, open the Weblogic12 folder:

These are some of the service installation packages and resource scheduling installation packages, and the ones that must be installed, what are these two packages for? As can be seen from the name, the first is the management rule set includes view, test, modify, execute, storage and so on functions of the service package, the second can be considered as a resource scheduling function package.

Next, create a new domain on WebLogic, named Res_domain, to launch and log in to WebLogic:

First, configure the data source, click services → data source:

On the right, select New → general data source

Data source name must be "Resdatasource", the Jndi name must be "Jdbc/resdatasource",

Database here I am using Oracle, click Next:

Select the JDBC driver and click Next:

Do not change by default, click Next:

Fill in the Database connection configuration, click Next,

This step can test whether the database can be connected, click the "Test Configuration" button, display "Connection Test Success", click "Finish" button to complete the configuration of the data source.

Note that it is important to have the following database operation permissions for the configured data source User:

Next, we need to do some configuration work, configure the RES user group and the user, the user group (that is, the role) in the following table:

Group name	Description	Default User and Password
Resadministrators	Administrator privileges	resAdmin resAdmin
Resdeployers	Deploy, browse, modify Ruleapp, test rule set permissions	resDeployer resDeployer
Resmonitors	Browse Ruleapp, monitor decision history and Access Decision Center reporting permissions	resMonitor resMonitor

The specific configuration process takes resadministrators as an example:

1. Click on "Security Field", then click Myrealm

2. Select "Users and Groups" and select "group":

3, click the "New" button, enter the name: Resadministrators and Description: Administrator group:

4. Click "OK" button, prompt to create a successful

5. Create another two groups in the same way.

After the group is created, we need to create the user, the user table is as follows:

resmonitor

user	password	group
resadmin	resadmin1	resadministrators, Resdeployers, Resmonitors, Administrators
resdeployer	resdeployer1	resdeployers, resmonitors
resmonitor1	resmonitors

Create the steps below, taking Resmonitor as an example:

1, as the above configuration "group", through the "security Area" → "myrealm" → "Users and Groups" → "users" to enter the User Configuration page

2. Click the "New" button to fill in the information:

3. Click "OK" button.

4, back to the user list, click the "resmonitor" user just added, go to the User Information configuration page, click on the "Group" tab page:

5. Select "Resmonitoers" in "parent group" to add to the right "selected" list

6. Click the "Save" button.

7, in the same manner, according to complete the user table in the creation and configuration of all users.

Both the group and the user are configured, and the next step is to "Enable anonymous service Manager", which is why the IBM website:

To use rule execution server and WebLogic servers, You must activate the Anonymous Management query option that is enabled on WebLogic server. This option provides read-only access to the Mbean API WebLogic Server Mbean. Register This access is required for the complete Rule execution Server and resource Mbean.

1, click "Res_domain" → "Security", select "General Information", tick "start anonymous admin find"

2. Restart WebLogic

And then one last configuration: "Run a non-administrator run diagnostics", which is how to add run diagnostic permissions for users of the "Resmonitors" and "resdeployers" groups? Configure theJMX Policy Editor with the following steps:

1. Click "Security field" → "Myrealm" → "General Information", tick "protect JMX access using authorization provider" and restart WebLogic

2. After the server restarts, click on the "Roles and Policies" tab and select "Domain Policy":

3. Click the JMX Policy Editor

4. On the JMX Policy Editor page, check that the global scope is selected, and then click Next

5. On the next page, check that all Mbean types are selected and click Next

6. In the Properties and Actions table, select " Action: Invoke Permission", then click "Create Policy" button

7. Click Add Condition, select the role in the verbs list, and click Next

8. Enter admin, click Add, click Next

9. Return to the Edit Jmx Policy Editor page, click Add Condition, select "group" in the verb list and click Next

10 . Add a group without administrator privileges and you are allowed to run diagnostic tests. For example, add all resdeployers and resmonitors groups to follow these steps:

A, enter resDeployers， Click to add

b, input resMonitors， Click to add

C, click Finish

Shown below:

　　

11. Click "Save" button

12. Restart WebLogic

At this point, we finally finished all the preparation of the configuration work, next, you can install Jrules-res-management-wl12.ear, or step-by:

1. Click "deploy" → "Install"

2. Find the Jrules-res-management-wl12.ear Service Pack and click Next

3. Select "Install this deployment as an application" and click Next:

4, the following steps by default.

The resource scheduler installs the same as jrules-res-management-wl12.ear and then looks at the service when it is installed:

Next, visit the following to see the access address: "Localhost:7007/res", the login page is as follows:

Log in using the configured user name, and log in to the console page as follows:

If you can go to this interface and prove that your res is basically installed successfully, you can diagnose the server:

Click "Run Diagnostics" to see how the server is running:

After viewing, the server is found to be functioning properly.

Okay, this post is here, and the next article will show you how to package and publish the rule project to the Res service, and how to test the ruleset on res, as well as the various features that RES provides.

If you have any questions about this blog post, please leave a message, I will be the first time to reply to you!

At the same time, welcome reprint, benefit others, but please specify the source, thanks!

IBM Rules Engine (ODM) Primer Series II: Rule Execution Server (RES) Service installation