Installer 10.7 | Complete Installation and Upgrade Information for Software AG Products | Using the Software AG Installer | Using GUI Mode to Install | Use Installation Scripts | Install from a Script Using the Command Line on Windows Systems
 
Install from a Script Using the Command Line on Windows Systems
If you run a script on a machine with the Windows firewall enabled, you might get warnings during script execution, which would cause your script to hang or fail.
To use the exe file, do the following:
1. Log on as the installation user you created earlier.
2. Use the -readScript full_path_to_script_file parameter. For example, enter:
SoftwareAGInstalleryyyymm.exe -readScript C:\myScript.txt
When you created the script, you might have provided a master password to encrypt the stored Empower password. If so, provide that master password so the installer can decrypt the Empower password. For example, enter:
-readScript c:\myScript.txt -masterPassword password
3. Open a command window, go to the directory that contains the installer, and execute the following:
SoftwareAGInstalleryyyymm.exe
If your company connects to the Internet through an HTTP or Socks proxy server, you must use that proxy server to install. If you specified proxy information when you created the script, the installer stored all settings, including ProxyUser and ProxyPassword in the script. If you want to override the stored settings, or if you did not specify proxy information when you created the script, set the appropriate parameters below:
*To have the installer use an HTTP proxy server:
SoftwareAGInstalleryyyymm.exe -proxyHost host -proxyPort port -proxyUser user
-proxyPass password
*To have the installer use a Socks proxy server:
SoftwareAGInstalleryyyymm.exe -socksProxyHost host -socksProxyPort port
When you created the script, you might have provided a master password to encrypt the stored Empower password. If so, provide that master password as [masterPassword password so the installer can decrypt the Empower password.
After a script runs successfully, by default, the installer exits immediately. If you want the installer to instead allow you to choose when to exit after the script completes, specify the -scriptNoExit parameter at the end of the command.
If errors occur while a script is running, installation fails. By default, the installer shows the errors and does not exit. If you want the installer to exit immediately with a non-zero exit value, specify the -scriptErrorInteract no parameter at the end of the command. If you want the installer to show the errors and pause for a specified number of seconds before exiting, specify the -scriptErrorInteract number_of_seconds parameter at the end of the command.