Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SMA Node Configuration issue



Regarding the nodes configuration in AES we are able to create the multiple nodes in SMA at our server as NODE1,NODE2 and NODE3, and when we try to open the NODE2 we are getting error as "No MBeans found for the node NODE2" we have search for MBeans file( in server but we are not able to locate, as in pdn regarding the MBeans file they have mention some configuration we need to done as below

#Default mBean security configuration.
deny.DatabaseManagement.DatabaseConnectionDetails = false
deny.RequestorManagement.RequestorDetails = false
deny.RequestorManagement.Clipboard = false

as per the PDN in some articles they have mention as we need to change the property values to false, please let us know we need to create the "prmbeans.propeties" and need to add in "Tomcat 7.0_Tomcat7New\webapps\prweb\WEB-INF\classes" folder or there is any workaround for this issue.

Please find the attachment for your reference.

Error Messages

No MBeans found for the node NODE2

Steps to Reproduce

Tried to create the Node in SMA

Root Cause

Not able to run more than one tomcat instances.

Gave user the tomcat directory and installed at users end and changed setenv.bat file as follows:

Restarted the server and all other nodes and Created two nodes one for each instance .
It worked fine.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us