I vaguely recall that it worked for ASPX but not ASP. I tried to find this without success. It should worked if configured correctly. Turning on DEBUG on Agent may help.
I created these steps awhile back -- https://comm.support.ca.com/kb/an-approach-to-resolve-apm-cem-introscope-integration-to-generate-a-transaction-trace/kb000019743
Failing this, please open a case.
Why not getting a trace
APMCM and Introscope problem resolution triage integration (transaction traces) works for non-Web Service transactions. It does not work for
Web Service transactions when APMCM is matching on XML elements in the SOAP body. When removing the XML matching criteria in the APMCM Web Service business transactions and matching only on the URL, the integration works again- APMCM is able to trigger transaction traces on the agent successfully.
APM does not support XML in the transaction tracing integration due to the high overhead inherent with parsing XML. It is not on the roadmap to support XML tracing. What is on the roadmap is generic/improved webservices/XML support consisting of generic matching of text inside the request body.
Typically, most users do XML matching in APMCM using custom http plugins.