Monitored transparent decision services
To access Rule Execution Server through a web service, you can also create a monitored transparent decision service from Rule Designer.
A monitored transparent decision service contains management and runtime information about the web service to Rule Execution Server. You create a monitored transparent decision as a project from the Rule Designer Client Project for RuleApps wizard. Then, you install it on the application server. As the web service is based on JAX-WS RI, the supported servers are the Liberty profile, WebSphere® Application Server, Tomcat, and JBoss.
The following figure shows the Operational Decision Manager architecture for a monitored transparent decision service.
- The ruleset path that is used by the monitored transparent decision service
- Runtime statistics: the number of successful calls, the number of calls with faults, the average processing time, the last processing time, and the initialization date and time
- Metadata: author, version, name, and description of the service, server name and IP address, version number of the Decision Server execution components
- Metadata for compatible RuleApps and rulesets
- Rules debug level
- Rules audit or tracing level
- Name-value pairs for the custom attributes that the monitored transparent decision service contains
Like hosted transparent decision services, monitored transparent decision services manage rulesets that use an XML schema or a Java™ XOM with any object types. XML parameters are represented by a String in the Web Service Description Language (WSDL) file.
- A monitored transparent decision service project from your RuleApp project
- The code generator generates two projects: the transparent decision (or web) service project and the client project, which can be used to test the code that is generated in the transparent decision service project. After the client has executed the ruleset, the Rule Execution Server console can monitor the transparent decision service.
- A web service project from your rule project
- The code generator generates a client project that can be used to test the code that is generated in the web service project. The Rule Execution Server management model cannot detect this project. As a consequence, Rule Execution Server console does not monitor rulesets that are executed by the provided client or by any other client.