Installing SOA for Windows via the Command Line
Introduction
This page describes how to install Universal Agent for SOA using the Windows Installer command line interface.
A command line installation is useful in situations where:
- Several Universal Agent for SOA installations must be deployed across many different systems.
- It is not practical or convenient to perform a graphical interface installation.
- It is necessary to generate an installation log file.
Installing Universal Agent for SOA
Step 1 | Download the Universal Agent for SOA for Windows product distribution file, |
---|---|
Step 2 | Execute the distribution file from the command line, and include all appropriate command line switches and parameters. |
Command Line Syntax
The following illustrates the command line syntax used to install Universal Agent for SOA:
sb-soa-6.7.0.-windows-x64.exe [/v"command line parameters"] [/s] [/w] [/x]
In this syntax:
<level>
is the numeric package level.
The command line switches (/v, /s, /w, and /x) are processed directly by the distribution file to control behavior of the Windows Setup application.
The command line parameters are passed to the Windows Installer (msiexec) to control the extracted Windows installer package file (.msi) behavior during the install process.
Command Line Switches
The following table describes the command line switches available for a command line installation:
/v | Passes parameters to the Windows Installer (msiexec). |
---|---|
/s | Suppresses the initialization and extraction dialogs displayed before the product install Welcome dialog." |
/w | Instructs the Windows Setup application to wait until the installation completes. |
/x | Uninstalls Universal Agent for SOA for Windows. |
Command Line Parameters
The following table describes the parameters that are available for a command line installation.
The parameters can be specified in any order, with the following exceptions:
- If the Repair (/fom) or Remove (/x) parameter is used, it must be specified before all other parameters.
- If the Silent install (/q) and/or Log file (/L) parameters are used, they can be specified in any order, but they must be specified after all other parameters.
These parameters are preceded by the /v command line switch and must be enclosed in double (") quotation marks.
Parameter | Description | Default |
---|---|---|
/fom | Repairs a Universal Agent for SOA for Windows installation. | n/a |
/x | Removes a Universal Agent for SOA for Windows installation. | n/a |
INSTALLDIR=installdir | Sets the root installation directory to < | (none) |
/q | Suppresses the product installation dialogs. | n/a |
/L*v | Instructs the installation process to create an installation log file named <logfilepath> (full path name). If <logfilepath> contains spaces, you must enclose it with double ( " ) quotation marks. | n/a |
Command Line Installation Examples
The following examples illustrate different ways that Universal Agent for SOA for Windows can be installed from the command line.
Graphical User Interface Install, All Components
To install all Universal Agent for SOA components via the graphical user interface, issue the following command:
sb-soa-6.7.0.x-windows-x64.exe
Silent Install
To silently install all Universal Agent for SOA components, issue the following command:
sb-soa-6.7.0.x-windows-x64.exe /s /v"/qn"
Graphical User Interface Install, All Components, with Log File
To install all Universal Agent for SOA components using the Windows Installer graphical user interface and write a log file to C:\temp\install.log
during the installation, issue the following command:
sb-soa-6.7.0.x-windows-x64.exe /v"/l*v C:\Temp\install.log"
Silent Install, Different Installation Directory
To silently install all Universal Agent for SOA components to a non-default location, issue the following command:
sb-soa-6.7.0.x-windows-x64.exe /s /v"/qn INSTALLDIR=D:\Universal"
Detecting the Completion of a Silent Install
If the /q switch is used to perform a silent install, no graphical interface or user interaction is required. One drawback to this is that no feedback is provided indicating when the Windows Installer process (install, uninstall, or repair) finishes.
One method that can be used to detect when the Windows Installer process ends is to execute it using the system's start command. Using available command line switches, start can initiate the Windows Installer process and then wait for it to finish. When start returns control to its calling process (for example, the command prompt), the process will have ended.
For example, from the command prompt, issue the following command to start the Universal Agent for SOA installation and wait for it to finish:
start /b /wait sb-soa-6.7.0.x-windows-x64.exe /w /s /v"/qn"
- The /b switch prevents the start command from opening a new window.
- The /wait parameter causes the start command to start the application, sb-soa-6.7.0.x-windows-x64.exe, and then wait for it to finish.
You also can use the syntax above to execute the start command from within a script, such as a .bat file.
For more information on the start command, open a Windows command prompt and enter: start /?.