Supported Arguments for the Start-up Scripts
You can run the Update Manager start-up scripts (for the command line and graphic user interface) at the command line with the arguments described in the following sections. All of the supported arguments are optional.
Create Image
-createImage full/path/to/image.zipCreates an image file that contains all Update Manager components and starts the Update Manager application. From the Update Manager application, you can add product fixes to this image. If you do not include the -imagePlatform argument, by default the image is created for the same operating system as the machine, on which you run the start-up script. The image is created with the name and at the location you specify.
Example:
Update Manager connects to Empower to create the "SUM_image.zip" file in the specified directory and for the operating system on which you run the script. After the image is created and saved, the Update Manager application starts:
Windows syntax:
UpdateManagerGUI.bat -createImage C:\SUM_image.zip
*nix Syntax:
./UpdateManagerGUI.sh -createImage /opt/SUM_image.zip
-createImageOnly full/path/to/image.zip Creates an image file that contains all Update Manager components, but does not start the Update Manager application and you cannot add product fixes to this image. If you do not include the -imagePlatform argument, by default the image is created for the same operating system as the machine, on which you run the start-up script. The image is created with the name and at the location you specify.
Example:
Update Manager connects to Empower to create the "SUM_only_image.zip" file in the specified directory and for the operating system on which you run the script:
Windows syntax:
UpdateManagerGUI.bat -createImageOnly C:\SUM_only_image.zip
*nix Syntax:
./UpdateManagerGUI.sh -createImageOnly /opt/SUM_only_image.zip
-imagePlatform <OS_code> The operating system for which to create an image. If you do not include this argument, by default the image is created for the same operating system as the machine, on which you run the start-up script. The valid values are listed in the following table:
Value | Operating System |
OSX | Apple Mac OS X |
HP11IT | HP HP-UX Intel Itanium 2 |
LNXS390X | Linux RHEL and SLES IBM System z |
AIX | IBM AIX |
LNXAMD64 | Linux RHEL and SLES x86-64 (EM64T, AMD64) |
W64 | Microsoft Windows x86-64 (EM64T, AMD64) |
SOL | Oracle Solaris SPARC |
SOLAMD64 | Oracle Solaris x86-64 (EM64T, AMD Opteron) |
Example:
Update Manager connects to Empower to create an image with name "SUM_only_image.zip" for the Linux RHEL x86-64 operating system:
Windows syntax:
UpdateManagerGUI.bat -createImageOnly C:\SUM_only_image.zip -imagePlatform LNXAMD64
*nix Syntax:
./UpdateManagerGUI.sh -createImageOnly /opt/SUM_only_image.zip -imagePlatform LNXAMD64
Usage Notes:
If you are creating a fix image, you can specify any name for the image file; do not supply an extension. The directory that will contain the image file must exist, and no part of the path or file name can include spaces.
Install from Image
-installFromImage full/path/to/image.zip Update Manager updates itself and then installs product fixes using the specified image file.
Example:
Update Manager uses the "SUM_image.zip" to update itself and install product fixes:
Windows syntax:
UpdateManagerGUI.bat -installFromImage C:\SUM_image.zip
*nix Syntax:
./UpdateManagerGUI.sh -installFromImage /opt/SUM_image.zip
Configure Proxy Server Settings
Use the proxy arguments when you must use a proxy server to connect to Empower.
Argument | Description |
-proxyHost <host> | The host of the proxy server. |
-proxyPort <port> | The port of the proxy server. |
-proxyUsername <username> | The name of a user account that can access the proxy server. |
-proxyPassword <password> | The password of the user account you specified in -proxyUsername |
-proxyProtocol {HTTP|SOCKS} | The type of protocol over which to communicate with the proxy server. |
Example:
Update Manager connects to Empower through a proxy server with host "192.168.0.1" and port "8000", over the HTTP transport and uses the credentials of "MyUser":
Windows syntax:
UpdateManagerGUI.bat -proxyHost 192.168.0.1 -proxyPort 8000 -proxyUsername MyUser -proxyPassword secret -proxyProtocol HTTP
*nix Syntax:
./UpdateManagerGUI.sh -proxyHost 192.168.0.1 -proxyPort 8000 -proxyUsername MyUser -proxyPassword secret -proxyProtocol HTTP
Usage Notes:
When you specify the proxy server settings as arguments at the command line, Update Manager creates the <SAGUpdateManager_directory>/UpdateManager/conf/proxy.cnf file and saves the proxy settings in the file. Note that:
If the next time you start
Update Manager at the command line, you include the proxy configuration arguments with new settings,
Update Manager will overwrite the settings saved in the proxy.cnf file.
If you do not include the proxy configuration arguments,
Update Manager uses the proxy settings from the proxy.conf file.
Debug Update Manager Operations
Operation | Description |
-debug true|false | Starts Update Manager in debug mode. Default: true |