This topic describes how to create an agent bundle for use with the Unified Agent Installer.
This topic contains the following sections:
An agent bundle maps target platform types to their corresponding agent installers. Optionally, an agent bundle can also specify the contents of the following agent configuration files: exports, users.local, and secure (optionally different settings for each platform).
For example, suppose you want to install agents on Microsoft Windows 32-bit servers. Following the instructions in Adding agent installer packages to the Depot, you would create a depot software object for the Windows 32-bit agent installer package, and this object would be based on the installer file RSCD86-WIN32.msi. When you create an agent bundle, you include a line that says: for each Windows 32-bit target system, use the RSCD86-WIN32.msi package to install an agent.
You may need to create only one agent bundle to specify the installers and settings for all your platforms. However, there are some situations where you need to create more than one bundle:
When you create an agent bundle, it is stored in the file server.
To create and use agent bundles, your role must be granted the following authorizations:
When you create an agent bundle, you do not have to specify the contents of the exports, users.local, and secure files. If you omit these settings, the system uses the defaults from the agent installer package.
However, if you want to specify these configuration settings in the agent bundle, familiarize yourself with the various options and syntax for these files. See Setting up configuration files. Use care when defining non-default configurations. The installation process does not validate configuration settings. An incorrect setting can prevent an agent from starting or block users from accessing the agent.