Our SAP Team wants to know what parameters they use in testing which caused JCO calls slow down and make whole application slow.
Is there any way to see what are input parameters to these JCO calls from CA APM?
Are you using an SED or RTV agent?
WE don't have SED or RTV agent but we have some SEDA98 agent. check the s screenshot
if SMD agent help I can ask SAP team to enable them.
If you are able to create metric grouping and alerts on this agent data then it must be SED.
So if you have RTV,it means you are using read only license come up with SAP for free to use.
Otherwise you have to buy SED license to use it in write mode.
You should use transactions traces to find out root cause analysis of slowness.it will give you what all jco call are responding slow.
The Tomcat agent above looks to be an SED agent which was probably uploaded and deployed from SWPM. You should be able to validate this from SolMan.
If it was manually deployed, then it's still SED because I don't rightly remember there being a Tomcat agent in SWPM by default.
In either case, we'll need your agent logs to see what is happening that you're not seeing those JCO calls. Please open a ticket to help us with root cause.
Converting to a discussion since about SAP and is a broader question
Retrieving data ...