ILOG JRules User Guide > Managing Rule Execution Server > Tasks > Administering Rule Execution Server > Decision Service MBean

A transparent decision service is visible in the Rule Execution Server Console as soon as the IlrDecisionServiceMBeanManager.register method has been called. The Web service generator in Rule Studio generates a Listener class that implements ServletContextListener and calls this method.

For example:

MBEAN_MANAGER = new IlrDecisionServiceMBeanManager(jmxprops);
try {
   MBEAN_MANAGER.register(
   "MyruleappMyrulesetDecisionService",
   "/Myruleapp/Myruleset", props);
} catch (IlrDecisionServiceMBeanException e) {
   System.err.println("Decision service MBean registration error:");
   e.printStackTrace();
}

images/IlrDecisionServiceMBeanManager.png

The management console retrieves all transparent decision services across linked application servers (for example all servers in the same cell for WebSphere, or in a domain for WebLogic). The only way to remove a transparent decision service is to call IlrDecisionServiceMBeanManager.unregister.

The management console calculates statistics at the transparent decision service level based on information passed to IlrDecisionServiceMBeanManager.addMeasurement and IlrDecisionServiceMBeanManager.addError.

The following figure shows the methods available on the decision service MBean (IlrDecisionServiceMBean):

images/IlrDecisionServiceMBean.png

The activation/deactivation of the transparent decision service is a flag on the decision service MBean, the client must check the state of this flag before launching the execution.

Related Concepts

Transparent Decision Services
RuleApp Execution Code Generators

Related Tasks

Creating a Web Service or Monitored Transparent Decision Service Project for RuleApps

Related Samples and Tutorials

Tutorial: Executing a Hosted Transparent Decision Service