How to monitor Cognos 11 and avoid instrumentation failures.

Document ID : KB000008382
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:
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.