Universal Agent for Windows - System Installation Requirements

Owned by Stonebranch
Last updated: Mar 12, 2024
5 min read

Windows Versions

To install Universal Agent for Windows, you must have one of the following versions of Windows:

  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

Additional Requirements

  • An account with administrative privileges.
  • Possible reboot: a reboot is required if the Windows Installer service is not installed, a version of the Windows Installer prior to 3.1.4000.1823 is installed, or if required files are in use at the time of the installation.
  • TCP/IP.
  • About 325 megabytes of disk space.

Platform Requirements

Since platform requirements may change with new releases of a product, please consult the Platform Support for Universal Controller 7.5.x and Universal Agent 7.5.x page to make sure that your platform is supported before performing an installation.

Third-Party Requirements

Some Universal Agent components may rely on vendor-supplied resources whose runtime dependencies are not known to the Agent before execution. One such component is the Universal Connector for SAP (USAP), which relies on libraries provided by SAP. If the runtime dependencies for those libraries are not available on your Agent system, attempts to run USAP will fail. Where such dependencies exist, use information provided by the vendor to determine runtime requirements. For example, to review runtime requirements for the NetWeaver RFC SDK version 750, refer to the information on this page.

Installation Account

The account used to install the package must have administrative privileges.

Universal Broker Service

The Universal Broker service runs either with an Administrative account or with the Local System account.

If you are using an Administrative account, the account must have the following privileges:

  • Act as part of the operating system
  • Adjust memory quotas for a process
  • Bypass traverse checking
  • Debug programs
  • Deny log on as batch job
  • Deny log on locally
  • Deny log on through Terminal Services
  • Log on as a service
  • Impersonate a client after authentication
  • Increase scheduling priority
  • Replace a process level token
  • Take ownership of files and other objects

UBrokerService: The Default Universal Broker Service Account

The Universal Agent for Windows installation will create an account with the privileges listed above, if the account does not already exist. The name of this account is UBrokerService. A default password provided for the account can be obtained by contacting Stonebranch support. We strongly suggest that you set this password at install time via the installation dialogs or via the BROKERPWD command line option.
 

Note

If the UBrokerService account already exists, its password cannot be changed from the install.


See Installing a Universal Agent System Install via the Graphical Interface for detailed information about setting up the Universal Broker service account at install time.

Using a Windows Domain Account to Execute Universal Broker

The Universal Broker Service may be configured to execute with an existing Windows domain account, provided that account has been granted the privileges listed in this section, above, on the local system and the account has the file system permissions described in Service Security.
 

Note

Depending on your environment, it may be necessary to add this account to the Domain Admins group. This will ensure the account has sufficient access to domain resources and is recognized as a true administrative account on all domain member systems that run the Universal Broker service as that account.

Spool Directory

The spool directory is used to store the following types of information:

  • Execution information for Universal Agent components started by Universal Broker.
  • Event definitions and event handlers managed by Universal Broker and used by Universal Event Monitor.
  • Results of events tracked by Universal Event Monitor.
  • Redirected standard I/O files (stdin, stdout, and stderr) captured by Universal Command when run with Manager Fault Tolerance enabled.
  • Configuration information for Universal Agent components, when a local Universal Broker is operating in managed mode.

The default location for the spooled standard I/O files is .\Universal\spool\ucmdsrv.

The default location for the other database files is .\Universal\spool\ubroker.

Universal Command Server

Location

The spool directory must reside on a local device. It cannot reside on any network device, including network drives that may be mapped to a local drive. By default, the spool files are located in directory .\Universal\spool\ucmdsrv.

Space

You must have approximately 50 megabytes of disk space for the installation.

The amount of disk space required for the spool directory depend on the following factors:

  • Number of spooling user processes that will be executing simultaneously. A user process is created for each command requested by a Universal Command Manager. The default maximum number is 50.
  • When a user process ends and a Manager has received all the spool files, the spool files themselves are deleted.
  • Average size of the user processes standard input, output, and error files. Keep in mind that spooling is not a feature for file transfer purposes. File transfer-related processes should execute without spooling enabled.

When these numbers have been determined, the average amount of disk space is calculated with the following formula:

MAX-PROCESSES x AVERAGE-STDIO-SIZE x 2 = required disk space.

For example, if the maximum number of simultaneous user processes is estimated at 20 and the average size of processes standard I/O files is 100,000 bytes, the average amount of required disk space is 4MB (20 x 100000 x 2).

The Universal Command Server is configured with spooling disabled to prevent unintentional disk utilization. This feature can be enabled through the Universal Configuration Manager.

For more information on the Manager Fault Tolerant feature, spooling of redirected standard I/O files, and Universal Configuration Manager, see the Universal Agent 7.3.x User Guide.

Security

Universal Broker and Universal Command Server require read/write access to the spool directory. No other Universal Agent components access the spool directory directly.

UAG Cache

UAG cache is used by Universal Automation Center Agent (UAG) for storing standard I/O files.

Space

Cache files are located, by default, in directory .\Universal\UagSrv\cache.

Cache files are created for each job that is run by Universal Agent. They remain in the cache until they are purged by an automated purge process scheduled nightly by Universal Controller. You can configure the number of days that files remain in the cache using the Agent Cache Retention Period in Days Universal Controller system property.

The amount of disk space required for the cache directory depends on:

  1. Number of jobs you estimate will run during the cache retention period you specified.
  2. These files remain until they are purged by the automated cache purge process scheduled by the Controller daily at midnight.
  3. Average size of the user processes standard output and error files.

When these numbers have been determined, the average amount of disk space is calculated with the following formula:

(RETENTION PERIOD x MAX-JOBS) x (AVERAGE-STDOUT-SIZE + AVERAGE-STDERR-SIZE) = required disk space.

For example:

If the files are purged every 7 days, and you run 1200 jobs on that agent server daily, and the average size of the STDOUT + STDERR files is 3,000 bytes, the average amount of required disk space is 25MB (7 x 1,200 x 3000).

UAG automatically redirects the standard output and standard error files to the cache directory with no required user input.

Security

Universal Automation Center Agent (UAG) requires read/write access to the UAG cache directory. No other Universal Agent components access the cache directory. No general user access is required.