PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
Go to start of metadata

On this page:

Related pages:

The Universal Agent can retrieve the runtime agent installation software from the Controller repository or from a local repository. This topic describes how to create each type of repository. 

Using a Controller Repository

This type of Universal Agent Repository is not available for SaaS Controllers. Use a local repository instead.

Using the Controller as the repository location gives the Universal Agents in your environment a single, central point for accessing the runtime agents. To use the Controller repository, you need to be able to access the Controller installation directory. 

  1. Create a subdirectory named agent_binaries in the Controller home directory.
  2. Download the runtime agent distribution ZIP files to the Controller home subdirectory agent_binaries from the download site.
  3. Rename the downloaded agents to the format expected by the Universal Agent. Use the following naming conventions where <version> is the agent version number:
    java-<version>.zip for non-IBM versions of the Java agent
    java-<version>-ibm.zip for IBM versions of the Java agent
    For example, java-4.3.0.0.zip or java-4.3.1.0-ibm.zip

    Your directory should look similar to the following: 

    <appdynamics_home>/
        Controller/
           agent_binaries/
              java-4.3.0.0.zip
              java-4.3.1.0-ibm.zip
              universalagent-4.3.0.1-64bit-linux.zip
  4. Specify the repository location to the Universal Agent, as described in Configure the Repository Location

Using a Local Repository

If putting the repository in the Controller directory structure is not feasible for any reason, you can serve the agent distribution files from a local repository. The likely location for the repository in this case would be a shared network directory. The directory would need to be mounted by the machines running the Universal Agent. 

The Universal Agent depends upon a defined directory structure within the repository directory and conventionally named runtime agent distribution files, as described in the following steps.  

To create your own local Universal Agent repository:

  1. Create the repository directory with the structure shown in the following example: 

    repository/
       monitor/
          java/
             4.2.0.0
                java-4.2.0.0.zip
             4.3.0.0
                java-4.3.0.0.zip
          machine/
             4.2.0.0
                machine-4.2.0.0-64bit-linux.zip

    Your local directory should similarly have a directory named monitor that contains subdirectories for the runtime agent types, java and machine and version, as illustrated by the example.   

  2. Download the agent files to the appropriate location in the directory based on the agent type and version.
  3. Rename the downloaded agents to the format expected by the Universal Agent. For example, rename AppServerAgent-version.zip to java-version.zip.
  4. Specify the repository location to the Universal Agent, as described in Configure the Repository Location.  

Agent Naming Format

The Universal Agent requires the runtime agent ZIP archive in the repository to have a specific name format. When placing runtime agent files in the repository, ensure that they are named as shown in the following table:

File Name Format Required for UA RepositoryExamplesDescription
java-<version>.zipjava-4.3.0.0.zipJava App Server Agent
machine-<version>-<bitness>bit-<os>.zipmachine-4.3.0.0-64bit-linux.zipMachine Agent for 64-bit Linux
 machine-4.3.0.0-32bit-linux.zipMachine Agent for 32-bit Linux
 machine-4.3.0.0-64bit-windows.zipMachine Agent for 64-bit Windows
 machine-4.4.0.0-32bit-windows.zipMachine Agent for 32-bit Windows

universalagent-<version>-<bitness>bit-<os>.zip

universalagent-4.3.0.0-64bit-windows.zipUniversal Agent for 64-bit Windows
universalagent-4.3.0.0-64bit-linux.zipUniversal Agent for 64-bit Linux
universalagent-4.3.0.0-32bit-linux.zipUniversal Agent for 32-bit Linux

 

Notice that the Universal Agent includes the bit number of the target operating system, since it bundles the JRE.   

Configure the Repository Location

The repository types and locations are defined in the Universal Agent configuration, universalagent.yaml

To configure a local repository, use the file:// protocol prefix for the location. For example, if the local repository is in the /Users/appduser/repository directory, configure the repository location as follows:

repositories:
- file:///Users/appduser/repository

Notice the extra slash "/" after file://

You can specify more than one repository location, in which case the Universal Agent will use the first agent file that matches a rule that it finds in the sequentially checked repositories. 

To use a combination of a local and Controller repository, include both, as follows: 

repositories:
- file:///Users/appduser/repository
- controller

The Universal Agent first checks the local repository and then the Controller for the runtime agent downloads.

  • No labels