search cancel

How to monitor Cognos 11 and avoid instrumentation failures.


Article ID: 8382


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE


 Further guidance on monitoring Cognos 11 can be found in 


Before opening a case, customer looked at:


Cognos 10.2 running on WebSphere Application Server Java 1.7 Windows Server 2012 R2 (6.3; amd64) (en_US) APM Java Agent is 10.1


  The steps for successful instrumentation is the following:

  1. Stop the application server (Cognos).
  2. Save the existing “bootstrap_wlp_winx64.xml” file (Copy it and call it “bootstrap_wlp_winx64_orig.xml” and put/move it somewhere safe)
  3. Edit “bootstrap_wlp_winx64.xml” file. Insert the following bold lines lines before the existing “-javaagent…” lines (as shown below):
    • <param>"-javaagent:E:/apps/CA/IntroscopeAgent10.1/Cognos10.2/wily/AgentNoRedefNoRetrans.jar"</param>








  4. Save the file
  5. Startup app server (Cognos)


The key workaround was to put the Introscope agent args "BEFORE" the existing args which were there by default.