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. You can avoid this problem by using the jar file instead of the exe file.
To use the exe file, do the following:
1. Log on as the installation user you created earlier.
2. Set the environment variable ZFUSION_INSTALL_ARGS to -readScript full_path_to_script_file. For example, enter:
set ZFUSION_INSTALL_ARGS= -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:
set ZFUSION_INSTALL_ARGS= -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
Note: If UAC is enabled on the machine, ZFUSION_INSTALL_ARGS might not be read properly, and your script might not start. Launch a command shell using Run as Administrator and execute the following from inside the shell:
SoftwareAGInstalleryyyymm.exe
To use the jar file, do the following:
1. Download the installer for UNIX as instructed by your installation email from Software AG.
2. Install a 64-bit JRE to run the installer and the uninstaller. For information on supported JDKs for Windows systems, see the product system requirements on the Software AG Documentation website.
3. Run this command:
java -jar SoftwareAGInstalleryyyymm.{jar|zip}
-readScript full_path_to_existing_script_file
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 except user name and password in the script. If you want to override the stored settings, or if you did not specify proxy information when you created the script, specify the appropriate parameters below.
To have the installer use an HTTP proxy server, specify these parameters on the command:
-proxyHost host -proxyPort port -proxyUser user -proxyPass password
To have the installer use a Socks proxy server, specify these parameters on the command:
-socksProxyHost host -socksProxyPort port
For example:
java -jar SoftwareAGInstalleryyyymm.{jar|zip} -socksProxyHost host
-socksProxyPort port -readScript full_path_to_existing_script_file
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.