Unable to See Coherence MBean in Enterprise Manager Configured for WebCenter Portal Content Presenter

Introduction

After configuring Coherence Cache for WebCenter Portal Content Presenter customer was not able to see the Coherence MBeans in the Enterprise Manager. Futher investigation revealed that the issue was due to configuration in WebLogic Server.

Main Article

After configuring Coherence Cache for WebCenter Portal Content Presenter customer was not able to see the Coherence MBeans in the Enterprise Manager to verify the installation. Further investigation shown that this was due to WebLogic Server configuration. When starting the WebCenter Portal managed server following message was noticed in the logs:

<Warning> <Management> <BEA-141277> <The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WLS security infrastructure. The Platform MBeanServer will NOT be used and Platform MBeans will NOT be available via the WLS Runtime or Domain Runtime MBeanServers. This can occur if you have defined Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement).
To allow the Platform MBeanServer to be used, you must either remove the system properties/JVM options or start WLS with the following system property:
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
If you want to eliminate this log error and do not need Platform MBeans to be available via WLS, then set the PlatformMBeanUsed attribute in the JMXMBean to false.>

The above message was also the main cause of the problem. To fix this issue you should provide following configuration within the Managed Server start-up parameters:

-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

You could add this to your setDomainEnv.sh like shown on the screen shot bellow:

managementbuilderinitial

It is also important that there are no repeatable coherence configurations. For example if you start the Managed Server with the Node Manager, you should make sure that the coherence configuration exist only in the Managed Server Start arguments:

 

coherencestartupparameters

After restart of the Managed Server and load WCP Page where the content presenter was used, you should be able to see the Coherence MBean in the Enterprise Manager, it should look like shown in the screenshot bellow:

emcoherencembean

Add Your Comment