Directory Structure and Permissions for .NET Agent

Learn about the .NET agent directories, files, and user permissions.
apmdevops106
Learn about the .NET agent directories, files, and user permissions.
2
2
.NET Agent Directory Structure
After you install the .NET agent, the following 
<Agent_Home>
 directory structure is created in the root installation directory:
  • wily
    Contains the IntroscopeAgent.profile, ProbeBuilder Directive files (
    .pbd
    ), and ProbeBuilder List files (
    .pbl
    ) files that control agent operations, metric data collection, and the instrumentation process. The IntroscopeAgent.profile properties that are deployed and referenced in the agent depend on choices you make during and after installation.
    Within the 
    <Agent_Home>
     directory, subdirectories provide the libraries and extension files that enable various features of the .NET agent.
  • bin
    Contains the core .NET agent libraries.
  • dynamic
    Contains the PBD files for dynamic instrumentation.
  • examples
    Contains folders and files for optional agent extensions, such as CA APM for SOA platform extensions. If an extension was not enabled at installation, use the files in this directory to configure and enable the extension.
  • ext
    Contains the files for enabled agent extensions or features. For example, the directory contains files for LeakHunter.
  • hotdeploy
    This directory is empty by default. You can place PBD files in this directory to deploy new directives without editing the IntroscopeAgent.profile or restarting applications. However, use caution before placing files in this directory. If custom PBDs contain invalid syntax or too many metrics, instrumentation can fail or application performance can suffer.
  • logs
    Stores the .NET agent log files.
  • readme
    This directory is only created if you enabled extensions during the installation. If the directory exists, it contains Readme information for the extensions enabled.
  • tools
    Contains the Network Interface integration utility and the Tagscript tools files:
    TagScript.jar
    ,
    TagScript.bat
    , and
    TagScript.sh
    command-line scripts
  • version
    Contains the version information for optional agent extensions, whether you enable them or not.
User Permissions to the <Agent_Home> Directory
By default, the installer program grants read access to everyone on the
<Agent_Home>
directory as follows:
  • Read permission to 
    <Agent_Home>
  • Read and execute permissions to 
    <Agent_Home>\bin
    and 
    <Agent_Home>\ext
  • Read and write permissions to 
    <Agent_Home>\logs
    and 
    <Agent_Home>\dynamic
You can restrict access to this directory by modifying the default permissions. Configure the permissions to allow only the user accounts that run the IIS worker process to access the
<Agent_Home>
directory.  If no user is specified, the utility detects the default IIS user for the application and grant permissions to that user.
Follow these steps:
  1. Navigate to the 
    <
    Agent_Home
    >
     directory.
  2. Run 
    wilypermissions.exe
     from a command line as shown in the example. The process name must include the file extension. If the process name is not specified, the IIS worker process name is the default.
    wilypermissions.exe <Agent_Home>
     
    [
    process name
    ]
    The utility executes, granting permission to the 
    <
    Agent_Home
    >
     directory to the user, and giving access to Performance Monitor counters.