Error when accessing a node via SMA
Attempting to access a node via SMA results in an error.
Failed to get mbean name.
Caused by: java.lang.Exception: Failed to get mbean name. objName: com.pega.PegaRULES:cell=HSSOBPMTTHAPP01Node01Cell,id="59e51b8a23917a93e5892b309233998d",name=com.pega.pegarules.management.internal.DatabaseTableInfo,node=HSSOBPMTTHAPP01Node01,process=server1,type=enterprise
Exception occured trying to invoke the getter on the MBean
Steps to Reproduce
1. Configure Node in SMA.
2. Try to connect to the node via SMA.
If WebSphere Application Server's Global/Administrative Security is enabled in any environment, the Local Connection option in SMA does not work as this cannot transmit admin credentials. If Administrative security is enabled, then, Remote Connection option has to be selected.
Here is brief explanation of two options:
- Local Connection: Connects directly to the platform MBean server via java interface (does not travel over network). User can do this if SMA and PRPC have been deployed on the same server/running in the same JVM. Note: This cannot be used with WAS Administrative security enabled.
- Remote Connection: Connects to WAS's MBean server using the WAS admin client. User needs to specify the SOAP port for WebSphere (this is not the port that PRServlet runs on) and the host name or IP Address of the node. This is the only the option that can be implemented with WAS Administrative security enabled.
This issue is resolved by making the following change to the operating environment:
Use the Remote Connection in SMA Node configuration. User needs to specify the SOAP port for WebSphere (this is not the port that PRServlet runs on) and the host name or IP Address of the node. This is the only option with WAS Administrative security enabled.