The SMA is behaving differently in Production and Model Office environment.
The SMA is behaving differently in Production and Model Office environment. When we select "Credentials not required" option in SMA, in Production with this option one is not able to get in SMA but in Model Office one is able to get in SMA.
***Edited by Moderator Marissa to update categories***
Accepted Solution
nasco
US
I got the below response from Pega Support and it helped me out.
This kind of problem is discussed in the Product Support Community thread here: https://collaborate.pega.com/question/error-while-trying-access-node-system-management-application
Further information about the specific error will be found in the WebSphere SystemOut and SystemErr logfiles. Likely this difference between your Model and Production environments is based on configuration differences in WebSphere. I assume that in Production the unauthenticated user has no access to content and hence this error is produced. In Model the security is likely much less.
Please review this article and let me know if it provides a solution to your problem. If you would like to review the specific error that is in your WebSphere logs as well, please provide those and I can review. Thanks!
Pegasystems Inc.
US
Hi,
Can you please elaborate on what is seen in the scenario where you cannot access SMA? Are you prompted for credentials? Do you see an error message displayed? Please include screenshots if you can.
-Kurt
Pegasystems Inc.
US
It depends on how your SMA is setup to connect (Remote vs Local) to the PRPC JVM/Node. For "Remote" JVM Connection, Administrative Security Credentials are required and are mandated by the Application Server Container as per JEE specs for connecting to remote Platform MBeans.
Accepted Solution
nasco
US
I got the below response from Pega Support and it helped me out.
This kind of problem is discussed in the Product Support Community thread here: https://collaborate.pega.com/question/error-while-trying-access-node-system-management-application
Further information about the specific error will be found in the WebSphere SystemOut and SystemErr logfiles. Likely this difference between your Model and Production environments is based on configuration differences in WebSphere. I assume that in Production the unauthenticated user has no access to content and hence this error is produced. In Model the security is likely much less.
Please review this article and let me know if it provides a solution to your problem. If you would like to review the specific error that is in your WebSphere logs as well, please provide those and I can review. Thanks!