Windows Installation
Introduction
These pages provide information on the installation of Stonebranch, Inc.'s Universal Agent on Microsoft Windows operating systems. Unless otherwise specified, all references to Universal Agent for Windows refer to one of the 7.6.x versions (for example: 7.6.0.0).
Installation Packages
Universal Agent is installed with one required installation package and three optional installation packages.
To obtain a Universal Agent package, you must download the corresponding product distribution file from the Stonebranch Customer Portal.
Note
A customer user name and password - provided by Stonebranch, Inc. - are required to access this area.
The following table lists the packages available, their supported platforms, distribution file names, and whether or not the package is required.
Package | Distribution File | Required |
|---|---|---|
Universal Agent (system installation) |
| Yes |
Universal Agent (user mode installation) |
| No |
| No | |
| No | |
| No |
The word LEVEL in each distribution file name is a numeric value representing the product maintenance level contained in the distribution file.
Distribution File Format
The product distribution files are in a Windows self-extracting archive file format.
The names of the distribution files have the following format:
PROD-VRML-OS-HW.exe
PRODis the package contentVRMLis the version, release, modification, and maintenance levels (for example, 7.6.0.0)OSis the name of the operating system supportedHWis the hardware type supported
Universal Agent Installation Methods
There are two installation methods available for Universal Agent for Windows packages:
Detailed information for each method can be found on the following pages.
System Installation
The system installation method uses a traditional Windows Installer-based package. This installation method "assumes" that it is the only Universal Agent instance on a system, and has the following distinguishing characteristics:
The application is listed in Programs and Features, under the Windows Control Panel.
Application files default to traditional install locations (for example, C:\Program Files).
Universal Manager and Utility components are installed in the Windows System32 directory.
Configuration and component definition files reside in in common, well-known locations (for example, C:\ProgramData).
The installation contains the logic necessary to create a new account for running the Universal Broker service.
The Universal Broker service name is not configurable. Its display name is
Universal Broker, its registered service name isUBrokerService, and its Application event log message source isubroker.The install contains logic to support upgrades from any prior release.
Removal requires a proper Uninstall, via the Windows Control Panel.
The installation is compatible with enterprise deployment tools (for example, SMS).
The installation may install system libraries that the Universal Agent requires.
The installation can automatically configure the Agent to simplify integration with other Stonebranch applications.
Pre-Installation Guidelines
Before starting the Universal Agent for Windows system installation, it is recommended that you close all other Windows programs. Active programs may be using system files that the Universal Agent installation may update.
If a system file is in use during the installation, it is placed in a temporary location. A reboot is required to free the file and move it from the temporary location to its final destination. Closing all programs before the installation reduces the possibility that a file will be in use and that you will have to reboot your computer.
You must be able to write to the directory from which the installation is launched.
External Runtime Dependencies
Additionally, 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 Path
The default installation path for most packages is:
"
C:\Program Files"
For the remaining 32-bit packages, the default installation path is:
"
C:\Program Files (x86)"
Installation Summary
Step 1 | Download the distribution file from the Stonebranch Customer Portal. |
|---|---|
Step 2 | Log on to Windows using an Administrative account or an account that can be elevated to Administrative authority. |
Step 3 | Exit all running programs to reduce the likelihood of a reboot. |
Step 4 | Execute the installation file. |
Step 5 | Follow installation instructions: |