Troubleshooting
Problem
Explain how to resolve a Rule Execution Server diagnostic failure of the MBean execution on WebSphere Application Server.
Symptom
A Rule Execution Server diagnostic fails on the execution of an MBean (as shown in the attached screen capture).
Cause
To access the MBeans of the Rule Execution Server model, an application must have sufficient security credentials, restricted to the Monitor role in the WebSphere authentication system.
Diagnosing The Problem
Refer to the server log file, which shows the following error:
javax.management.JMRuntimeException: ADMN0022E: Access is denied for the notifyRulesetArchiveChanged operation on IlrXUManagement MBean because of insufficient or empty credentials.
at com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImpl.java:2074)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1116)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1032)
at ilog.rules.res.mbean.util.IlrMBeanManagerImpl_websphere.invokeDispatcher(IlrMBeanManagerImpl_websphere.java:124)
at ilog.rules.res.mbean.util.IlrMBeanManagerImpl_websphere$3.run(IlrMBeanManagerImpl_websphere.java:104)
at ilog.rules.res.mbean.util.IlrMBeanManagerImpl_websphere$3.run(IlrMBeanManagerImpl_websphere.java:80)
at java.security.AccessController.doPrivileged(AccessController.java:192)
at ilog.rules.res.mbean.util.IlrMBeanManagerImpl_websphere.invoke(IlrMBeanManagerImpl_websphere.java:79)
at ilog.rules.res.mbean.util.IlrMBeanManagerImpl.invoke(IlrMBeanManagerImpl.java:135)
at ilog.rules.res.model.mbean.IlrXUMBeanUtil.notifyRulesetArchiveChanged(IlrXUMBeanUtil.java:106)
at ilog.rules.res.model.mbean.IlrJMXMutableRulesetArchiveInformationImpl.notifyRulesetRemoved(IlrJMXMutableRulesetArchiveInformationImpl.java:106)
at ilog.rules.res.model.mbean.IlrJMXMutableRulesetArchiveInformationImpl.linked(IlrJMXMutableRulesetArchiveInformationImpl.java:177)
at ilog.rules.res.model.impl.IlrMutableRuleAppInformationImpl.linked(IlrMutableRuleAppInformationImpl.java:201)
at ilog.rules.res.model.mbean.IlrJMXMutableRuleAppInformationImpl.linked(IlrJMXMutableRuleAppInformationImpl.java:96)
at ilog.rules.res.model.impl.IlrMutableRuleAppInformationImpl.setRepository(IlrMutableRuleAppInformationImpl.java:193)
at ilog.rules.res.model.impl.IlrMutableRepositoryImpl.removeRuleApp(IlrMutableRepositoryImpl.java:89)
at ilog.rules.res.console.diagnostic.IlrConsoleDiagnostic.testRemoveRuleApp(IlrConsoleDiagnostic.java:408)
at ilog.rules.res.console.diagnostic.IlrConsoleDiagnostic.execute(IlrConsoleDiagnostic.java:128)
at ilog.rules.res.console.jsf.bean.DiagnosticBean.execute(DiagnosticBean.java:56)
...
Resolving The Problem
Map your administrator group (resAdministrators by default) to the Monitor role in the WebSphere Application Server administration console.
See our documentation for the detailed steps : for example section WebSphere ILOG JRules BRMS V7.1: Java EE add-ons > Installing on WebSphere Application Server > Installing Rule Execution Server > Installing Rule Execution Server on WebSphere Application Server V7.0 > Activating security on WebSphere V7.0 > Mapping the resAdministrators group to the Monitor role for JRules V7.1 on WAS V7.
Related Information
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21461650