Install from a Script on Mac OS X System, Other UNIX System, or Windows System
To install from an installation script, specify the -readScript parameter on the command. For example:
java -jar SoftwareAGInstaller201504.{jar|zip}
-readScript full_path_to_existing_script_file
By default, you will see the installer run in wizard mode unless you are installing on a headless system. If you are installing on a headless system, the installer will run in console mode.
Important: | If you created the script from Empower, the product releases referred to in the script must be available on Empower or the script will fail. If you created the script from an image, the image must be in the location it was in when you created the script or the script will fail. |
If you are installing on a system that has a monitor, and you want to display the output on a console, specify the -console parameter. For example:
java -jar SoftwareAGInstaller201504.{jar|zip}
-readScript full_path_to_existing_script_file -console
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 SoftwareAGInstaller201504.{jar|zip} -socksProxyHost host
-socksProxyPort port -readScript full_path_to_existing_script_file -console
Note: | If you are installing on a Windows system and you logged in remotely, you might experience problems with the Windows graphics subsystem. Try adding -Djava.awt.headless=true as the first parameter on the command. Only do this if you experience an actual problem; configuring the installer as a headless application on Windows systems might trigger a known problem in Java (see Oracle bug JDK-6607186). |
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.
