Installing a Universal Agent System Install via the Graphical Interface
Installing a Universal Agent for Windows System Install via the Windows Installer Graphical Interface
To install a Universal Agent for Windows System Install via the Windows Installer graphical interface, perform the following steps:
Step 1 | Download the desired Universal Agent for Windows System Install product distribution file to your work station:
|
---|---|
Step 2 | Execute the distribution file from the command line to begin the installation process, which first determines whether a Windows Installer update is needed (see Windows Installer). |
Step 3 | The installation starts after the files are extracted. It first will verify that your machine meets the minimum system requirements (see Installation Requirements and Summary - Windows). If the requirements are met, a Welcome dialog displays. |
Step 4 | Click the Next button. A list of Universal Agent components included in the installation package then displays. It is from this list that you can select which components to install. Note An X icon displays next to the Universal Controller Command Line Interface (CLI) component, indicating that, by default, it will not be installed. If you want to install the CLI, you must click the X icon and select the drive icon. For an upgrade installation, either of the following icons displays next to an item:
A Stonebranch Tip
|
Step 5 | The previous figure indicates that all Universal Agent components will be installed in their respective directories under the C:\Program Files\Universal directory.
|
Step 6 | If you do not want to install a component:
|
Step 7 | When you have selected the components (and their installation destinations) that you want to install, click the Next> button. The Universal Broker Service Account dialog then displays. |
Step 8 | Select an account to use to execute the Universal Broker service:
A default password provided for the account can be obtained by contacting Stonebranch support, although any password up to 256 characters can be specified.
The Broker service may also be run using a Windows domain account. The primary difference between using a local and domain account is that the domain account must already exist, and the installation will not configure it like it does a new local account. Required account privileges and file system access can be found in Service Security. Note For upgrades, if the Universal Broker service is already configured to run with a user account, the install dialog shows only the account name and omits the password fields. The Broker service's configuration in the Windows Service Control Manager is retained across upgrades, making it unnecessary to re-enter account information during an upgrade. The install provides the RUNBROKERASUSER, BROKERUID, and BROKERPWD command line options to override the default behavior described above.
When RUNBROKERASUSER=1, the BROKERUID and BROKERPWD command line options are provided to override the default or currently configured user ID and password. The BROKERUID option limits user IDs to 20 characters; the BROKERPWD option limits passwords to 14 characters. (See Windows Installer Command Line Parameters for more information). |
Step 9 | When you have selected an account, click the Next> button. The Security Options dialog then displays. |
Step 10 | When you have configured the security options, click the Next> button. The OMS Server Options dialog then displays. Note This dialog displays only for new Universal Agent installs and upgrades to Universal Agent from earlier releases. |
Step 11 | Select whether or not you want the Universal Message Service (OMS) Server to start up when Universal Broker starts up and, optionally, change the OMS Server port connection (the default port, 7878, is pre-selected). |
Step 12 | Click the Next> button. The Automation Center Configuration dialog displays. |
Step 13 | Enter a list of OMS Servers to specify how the Agent will connect to Universal Controller. |
Step 14 | Click the Next> button to continue the installation process. Depending on the components selected, the installation may prompt for additional values, such as working folders for Server components. Follow the directions provided with each dialog. |
Step 15 | Click the Finish button to exit Windows Installation. |
Windows Installer Package File Locations
The Windows Installer Package file (.msi
) is extracted to the following location:
Universal Agent for Windows package (64-bit) |
|
In this path:
<fname
> is a file name generated by Windows Installer and uniquely identifies the .msi
file cached to C:\Windows\Installer
.
For example: 44d82d08.msi
.
Note
To easily locate the .msi
file cached for the Universal Agent installation in Windows Explorer, view the contents of the C:\Windows\Installer
folder in Details mode and add the "Subject" column to the display.