Task 1: Checking the Rule Execution Server console

You start by opening the Rule Execution Server console and checking that it is running.

1. Start the sample server (see Starting and stopping the sample server).
2. Open the Rule Execution Server console by using one of the following methods:
   • Windows:
     • Windows 10 or later: Start > All Programs > <ODM> > Rule Execution Server Console
     • Windows 11: Start > All appss > <ODM> > Rule Execution Server Console

   • On all platforms, enter the following URL with the correct port number in a web browser: : http://localhost:<PORT>/res

3. Use resAdmin as the user name and password.
4. Click Sign In.

After you have opened the Rule Execution Server console, you can view the list of deployed RuleApps.

1. In the Rule Execution Server console, click the Explorer tab.
2. Check the RuleApps view.

   You can see that no rule application is deployed, unless one was already deployed from another tutorial or sample.

You can view, select, and clear ruleset execution trace information in the Rule Execution Server console Decision Warehouse tab.

1. Click the Decision Warehouse tab.
2. Use the tasks available to search decisions, select the trace configuration, and clear traces from the database.

   No trace information is available unless another tutorial or sample was run.

The results of application server diagnostics are displayed on the Rule Execution Server console Diagnostics tab.

1. Click the Diagnostics tab.
2. Diagnostics are run automatically, and you can see their results directly. Click the Rerun button to run the diagnostics again.

   All the steps in the diagnostics should have green check marks. If you want to see more detail, you can expand the results of each step or click Expand All to view all the results for all steps.

   Note: The local XU connectivity and two rule session execution entries are grayed out because the sample server uses the WebSphere® Liberty application server in J2SE mode. In J2SE mode, the eXecution Units (XUs) are embedded in the client applications, and the Rule Execution Server console does not have XUs.

Information about the application server is displayed on the Rule Execution Server console Server Info tab.

1. Click the Server Info tab.
2. Check the manage console messages.

   The messages provide information on the properties used for initialization, the connection, the log file, the applications under license, and similar facts. There are zero execution unit (XU) warnings and zero execution unit errors unless another tutorial or sample was run.

You use the REST API test tool to work with the Rule Execution Server REST API.

1. Click the REST API tab.
2. Click the subtabs for the REST resources and view the content: /ruleapps, /rulesets, /libraries, /xoms, /decisiontraces, /executionunits, and /utilities.

   To find a method by its name, use the browser search. For example, on Firefox press Ctrl plus F and find the method addRulesetProperty.