Question
Last activity: 18 Jul 2017 10:48 EDT
Error while trying to access Node from System Management Application
Hi,
When I am clicking on the node name on SMA, it throws this error:
MSG:
com.pega.jmx.ui.util.JMXClientException: Fail to instantiate WASJMXConnector
Failed to get mbean server connection
SMA ERROR: Failed to create admin client
ADMC0016E: The system cannot create a SOAP connector to connect to host N/A at port N/A.
Stack Trace:
Hi,
When I am clicking on the node name on SMA, it throws this error:
MSG:
com.pega.jmx.ui.util.JMXClientException: Fail to instantiate WASJMXConnector
Failed to get mbean server connection
SMA ERROR: Failed to create admin client
ADMC0016E: The system cannot create a SOAP connector to connect to host N/A at port N/A.
Stack Trace:
com.pega.jmx.ui.util.JMXClientException: Fail to instantiate WASJMXConnector Failed to get mbean server connection SMA ERROR: Failed to create admin client ADMC0016E: The system cannot create a SOAP connector to connect to host N/A at port N/A. at com.pega.jmx.ui.util.JMXClientException.wrap(JMXClientException.java:49) at com.pega.jmx.ui.action.AuthenticateAction.execute(AuthenticateAction.java:346) at com.pega.jmx.ui.action.AuthenticateAction.executeWithoutValidation(AuthenticateAction.java:86) at sun.reflect.GeneratedMethodAccessor347.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:450) at com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:289) at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:252) at org.apache.struts2.interceptor.DeprecationInterceptor.intercept(DeprecationInterceptor.java:41) at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246) at org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:256) at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246) at com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:167) at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98) at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246) at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:100) at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246) at com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:138) at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:246)
Surprisingly, this works for some and for some others, it doesn't. As we all know, we can access SMA from here: XXX/prsysmgmt/getnodes.do (XXX is the host name and port). When I try to access SMA even from this link, it behaves similarly. For some other users (Without logging into PRPC), this URL produces desired result and shows them everything related to a node, when they click on the node name.
Can anybody please help?
Thanks.
***Updated by moderator: Lochan to add Categories***
***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
GB
Hi Arijit,
When running System Management Application on Websphere, the Node should have the following configuration:
1) Configue SMA with Remote connection
2) Specify the Host Name
3) Specify the port number which should be the SOAP_CONNECTOR_ADDRESS.
4) The credentials should be the same as Websphere Administrator's credentials.
Pegasystems Inc.
GB
Hi Arijit,
What Application Server is your system using? Please be aware that the Application Server type needs to be the same. If your PRPC Nodes are running on Websphere, then the SMA application must also be using Websphere as well.
Have you checked the resolution in SR-A457? Does that help?
Regards
Simon
Mphasis
US
Hi Simon,
The other account doesn't seem to be functional, so I have to reply to you with this new account. I am not able to check the resolution of the SR you mentioned. We are using WebSphere and SMA application is using the same as well.
Accepted Solution
Pegasystems Inc.
GB
Hi Arijit,
When running System Management Application on Websphere, the Node should have the following configuration:
1) Configue SMA with Remote connection
2) Specify the Host Name
3) Specify the port number which should be the SOAP_CONNECTOR_ADDRESS.
4) The credentials should be the same as Websphere Administrator's credentials.
Mphasis
US
When you add the node, you should see a couple of fields Remote Connection host and port. You will also see a dropdown where you can select if you want to configure SMA through a remote connection or a local connection. Hope this helps.
Infosys
US
We are getting below error while accessing individual nodes configured in SMA.
Access is denied for the getName operation on enterprise MBean because of insufficient or empty credentials
And below error in logs:
The user UNAUTHENTICATED (unique ID: unauthenticated) was not granted any of the following required roles: deployer, operator, configurator, monitor, administrator, adminsecuritymanager, auditor.
Looks like role based access has been configured somewhere @ server level. We are using web sphere server. Any idea about this error?
Mphasis
US
Is it possible to share a connection of your node configuration page if allowed? It seems the access you using doesn't have proper privilege to be able to complete the configuration.
Infosys
US
Hi Arjit,
Do you know where do we configure privilege to access SMA?
It seems security constrains are defined in web.xml file. and role is assigned to individual users in the application server‘s user definitions file. (TOMCAT_HOME/conf/tomcat-users.xml)
We are using Web Sphere and not sure where is the setting to assign role to user.