How to monitor Cognos 11 and avoid instrumentation failures.
search cancel

How to monitor Cognos 11 and avoid instrumentation failures.

book

Article ID: 8382

calendar_today

Updated On:

Products

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

Issue/Introduction

 Further guidance on monitoring Cognos 11 can be found in 

https://communities.ca.com/thread/241780500-cognos-11-monitoring 

 

Before opening a case, customer looked at: 

https://docops.ca.com/ca-apm/10-2/en/implementing-agents/java-agent/install-the-java-agent/configure-application-server-to-use-the-java-agent/websphere#WebSphere-ConfigureMonitoringofIBMWebSphereLibertyProfile  

https://communities.ca.com/message/242002070-re-cognos-11-monitoring?commentID=242002070#comment-242002070

https://communities.ca.com/message/241991362-cognos-11-monitoring

Environment

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

Resolution

  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>

      <param>"-Dcom.wily.introscope.agent.agentName=Cognos_Global_TST"</param>

      <param>"-Dcom.wily.introscope.agentProfile=E:/apps/CA/IntroscopeAgent10.1/Cognos10.2/wily/core/config/IntroscopeAgent.NoRedef.Cognos_TST.profile"</param>

      <param>"-Dorg.osgi.framework.bootdelegation=com.wily.*"</param>

      <param>"-javaagent:${install_path}/wlp/bin/tools/ws-javaagent.jar"</param>                            

      <param>-jar</param>

      <param>"${install_path}/wlp/bin/tools/ws-server.jar"</param> 

      <param>cognosserver</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.