AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    Related pages:

    Your Rating:
    1 Star2 Star3 Star4 Star5 Star
    20 rates

    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.

    Configure the Repository Location

    The repository types and locations are defined in the Universal Agent configuration file, universalagent.yaml, using the repositories keyword. You can specify a list of repository URLs (in order of preference) for retrieving AppDynamics monitor (agent) binaries and Universal Agent updates. The format is as follows:

         - file:///local/path
         - http://host:port/path
         - https://host:port/path
         - https://<username>:<password>@<host>:<port>/<path>

    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:

        - file:///Users/appduser/repository

    Notice that there are three slashes after file:. The first two slashes indicate the file protocol, and the third slash refers to the root directory of the file system. All slashes should be forward slashes, even on Windows machines.

    To configure a local repository on an HTTP server. Define the URL in any of the formats below:

        - https://host:port/path
        - http://host:port/path

    You can also use basic authentication for an HTTP repository in the form:

        - https://<username>:<password>@<host>:<port>/<path>
        - http://<username>:<password>@<host>:<port>/<path>

    You can specify more than one repository location, in which case the Universal Agent uses 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:

        - file:///Users/appduser/repository
        - https://<username>:<password>@<host>:<port>/<path>
        - controller

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

    Using a Controller Repository

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

    Downloading the .NET Agent from a Controller repository is not supported. Place the .NET Agent distribution file in a local repository.

    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 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> for IBM versions of the Java agent
      For example, or
      Your directory should look similar to the following: 

    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, 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: 


      Your local directory should similarly have a directory named monitor that contains subdirectories for the runtime agent types, including java and machine and their respective versions, 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. See Agent Naming Format.
    4. Specify the repository location to the Universal Agent, as described in Configure the Repository Location.  

    Agent Naming Format

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

    java-<version>.zipjava- App Server Agent
    machine-< version >- < bitness >bit- < os >.zip machine- Agent for 64-bit Windows

    machine- Agent for 32-bit Windows

    machine- Agent for 64-bit Linux

    machine- Agent for 32-bit Linux


    universalagent- Agent for 64-bit Windows

    universalagent- Agent for 32-bit Windows

    universalagent- Agent for 64-bit Linux

    universalagent- Agent for 32-bit Windows

    Analytics Agent
    analytics-agent-bundle-<bitness>bit-<os>-<version>.zipanalytics-agent-bundle-64bit-linux- Analytics Agent
    dotNetAgentSetup<bitness>-<version>.msidotNetAgentSetup64- .NET Agent
    network-<version>-<bitness>bit-<os>.zipnetwork- Agent

    Notice that the Universal Agent and the Machine Agent include the bit number of the target operating system because the downloads bundle the JRE. 

    • No labels