It is good practice to verify that Rule Execution Server is
successfully deployed and configured by running the diagnostics.
About this task
Important: - To let a scalable number of users access resources through the
Java components, JCA assigns the task of implementing connection pooling
to application server vendors.
- If the diagnostics are performed before any Execution Units (XU)
are started, the test is passed and a message reports that no Execution
Unit (XU) are initialized.
- On WebSphere® Application Server,
the pool size is not instantiated beforehand and therefore prevents
the server diagnostics from validating a Rule Execution Server before
the first execution of a rule engine. The diagnostics remain useful
to validate a configuration, especially in a cluster, and to check
which Execution Units are registered with the management model.
Procedure
- Open the Rule Execution Server console
by typing res at the root URL on the host machine:
http://<machine_name>:<PORT>/res
If
security is enabled, the prefix is https://.
To
find the value of <PORT>:
- In the Integrated Solutions Console,
click .
- Select the name of your server.
- Under Communications, click Ports.
- Sign in to the Rule Execution Server console.
- Click the Diagnostics tab.
- Click Run Diagnostics.
Results
You see a report listing the diagnostic tests. A check
mark is shown next to each test to indicate whether the test is successful.
Click Expand All to show more details about
the tests.