On this page: Related pages:
On this page:
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.
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.
agent_binariesin the Controller home directory.
agent_binariesfrom the download site.
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-184.108.40.206.zip or java-220.127.116.11-ibm.zip
Your directory should look similar to the following:
Specify the repository location to the Universal Agent, as described in Configure the Repository Location.
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:
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,
machine and version, as illustrated by the example.
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 Repository||Examples||Description|
|java-<version>.zip||java-18.104.22.168.zip||Java App Server Agent|
|machine-<version>-<bitness>bit-<os>.zip||machine-22.214.171.124-64bit-linux.zip||Machine Agent for 64-bit Linux|
|machine-126.96.36.199-32bit-linux.zip||Machine Agent for 32-bit Linux|
|machine-188.8.131.52-64bit-windows.zip||Machine Agent for 64-bit Windows|
|machine-184.108.40.206-32bit-windows.zip||Machine Agent for 32-bit Windows|
|universalagent-220.127.116.11-64bit-windows.zip||Universal Agent for 64-bit Windows|
|universalagent-18.104.22.168-64bit-linux.zip||Universal Agent for 64-bit Linux|
|universalagent-22.214.171.124-32bit-linux.zip||Universal Agent for 32-bit Linux|
Notice that the Universal Agent includes the bit number of the target operating system, since it bundles the JRE.
The repository types and locations are defined in the Universal Agent configuration,
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:
Notice the extra slash "/" after
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:
The Universal Agent first checks the local repository and then the Controller for the runtime agent downloads.