How can we install the .NET Agent for 64-bit .NET Applications on Windows Server 2008 R2 by using NoInstaller files?

Document ID : KB000009387
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Installing NET Agent for 64 bit NET Applications on Windows Server 2008 R2 by using NoInstaller Files

Environment:
APM 9.6 and 9.7
Instructions:

Steps to install the 64-bit v9.6 or v9.7 .NET Agent manually

  1. Use a clean reference copy of the "wily" directory (from DotNetAgentFiles-NoInstaller.x64.9.0.6.5.zip) downloaded from the CA website (file ISCP_AG_FILE9065.zip). A copy of the "wily" directory from an existing 64-bit v9.0.6.5 .NET Agent installation may also work.

  2. Identify a local directory to be the "Wily Home" directory and place the .NET Agent "wily" directory as its subdirectory:

    1. C:\WilyIntroscope\wily

  3. Register wily.Agent.dll into GAC:

    1. Open command prompt as administrator (right click)

    2. Execute: explorer C:\Windows\assembly

    3. Execute: explorer "Wily Home"\wily\bin

    4. Drag and drop wily.Agent.dll from "Wily Home"\wily\bin into C:\Windows\assembly

  4. Register wily.NativeProfiler.dll:

    1. Open command prompt as administrator (right click)

    2. Execute: C:\Windows\system32\regsvr32.exe "Wily Home"\wily\bin\ wily.NativeProfiler.dll

  5. Update IntroscopeAgent.Profile file:

    1. introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=X.X.X.X (Enterprise Manager IP Address or Hostname)

  6. Run wilypermission.exe, grant permission to the "Wily Home" directory to the user performing the installation, and give access to performance monitoring (PerfMon) counters. Ensure the process for the .NET applications to be monitored, e.g. w3wp.exe, is up and running first:

    1. Execute: "Wily Home"\wily\wilypermission.exe "Wily Home"\wily w3wp.exe

  7. Adding new environment system variables:

    1. com.wily.introscope.agentProfile="Wily Home"\wily\IntroscopeAgent.profile

    2. Cor_Enable_Profiling=0x1

    3. COR_PROFILER={5F048FC6-251C-4684-8CCA-76047B02AC98}

  8. Restart IIS (command resetIIS)
Additional Information: