RajKumar786
Depends on what component of CA SSO are we trying to monitor.
CA SSO Policy Server
JMX will only suggest / monitor the JAVA side of the code and not provide an overall health of the entire CA SSO Policy Server. There is blog in communities that Mark has published for JMX monitoring in CA SSO Policy Server.
Most of the federated solutions that CA SSO Policy Server provides, fall under the Java Code stream. However the core CA SSO Policy Server, is still "C". It further uses JNI to interact between C coded side of the house and Java Coded side of the house.
There are various ways we could monitor CA SSO Policy Server.
- Crude Ways (Looking at connection counts, smpolicysrv -stats, smpublish, CPU utilization, Process Memory Growth [VSZ / RSS] etc).
- OneView Monitor.
- SNMP Monitoring.
- CA APM for CA SSO (licensed separately from CA APM License and CA SSO License).
CA SSO Access Gateway
I believe most of CA AG is Java. So JMX here may be a better suite. There is a blog in communities that Mark has published in for JMX Monitoring in CA AG.
There are various way we could monitor CA AG.
- CA APM (using the EPAgent that is shipped along with CA APM). No need to have the additional CA APM for CA SSO product / license.
- JMX Monitoring.
Reference Notes :
Debugging Java via JMX Console in CA Single Sign On (CA Siteminder)
Debugging Java via JMX Console in CA Access Gateway (CA Secure Proxy Server)
CA Access Gateway Performance Monitoring: Even Simpler Than 1-2-3
Data Monitoring Using CA Application Performance Management - CA Single Sign-On - 12.7 - CA Technologies Documentation
Regards
Hubert