Update the installation directory silently

Installing the fix pack, using the silent method, updates the WebSphere Commerce product to that fix pack level.

Prerequisite Ensure the following tasks are completed:

  1. Download and install the WebSphere Commerce Update Installer

  2. Download the required WebSphere Commerce fix pack.

  3. Save the fix pack to directory:

  4. Ensure the WebSphere Commerce Configuration Manager server is stopped.

  5. Stop the WebSphere Commerce Help Server.


Complete the following steps to install the fix pack to the WebSphere Commerce product directory.

  1. Windows: Ensure that you are logged in with a user ID that is a member of the Windows Administration group.

  2. AIX|Linux|Solaris|Ensure that you are logged in as the root user. Use one of the following methods:

    • Sign on with the root user.

    • If you are already signed onto the system, issue the command su - root. Do not use the command su root. This command does not load the root user's profile and environment which is required for fix pack installation.

  3. I5/OS|Ensure that your user has *SECOFR authority.

  4. Navigate to the UPDI_installdir/responsefiles directory and open the install.txt file in a text editor.

  5. Edit the install.txt file, ensuring the following sections are edited appropriately and are not commented out:

    To uncomment a line, remove the # character from the beginning of the appropriate entry.

    • The W maintenance.package contains the directory name for the fix pack. For example:

      • I5/OS|-W maintenance.package="/QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI/maintenance"

      • AIX|-W maintenance.package="/usr/IBM/WebSphere/UpdateInstaller/V61/UPDI/maintenance"

      • Linux|Solaris|-W maintenance.package="/opt/IBM/WebSphere/UpdateInstaller/V61/UPDI/maintenance"

      • Windows: -W maintenance.package="C:\Program Files\IBM\WebSphere\UpdateInstaller\V61\UPDI\maintenance"

    • The W product.location contains the full path name of the WebSphere Commerce installation directory. For example:

      • I5/OS|-W product.location="/QIBM/ProdData/CommerceServer60"

      • AIX|-W product.location="/usr/IBM/WebSphere/CommerceServer60"

      • Linux|Solaris|-W product.location="/opt/IBM/WebSphere/CommerceServer60"

      • Windows: -W product.location="C:\Program Files\IBM\WebSphere\CommerceServer60"

      Verify that the W update.instancename and W update.db entries do not exist or are commented out. Save the file and exit.

  6. I5/OS|Start a QShell session by typing QSH at the command prompt.

  7. Run the following command from the UPDI_installdir :

    • I5/OS|update -devkit14 -options UPDI_installdir/responsefiles/install.txt

    • AIX|Linux|Solaris|./update.sh -silent -options UPDI_installdir/responsefiles/install.txt

    • Windows: update.bat -silent -options UPDI_installdir/responsefiles/install.txt

    Windows:

    When the prompt returns wait for the Java process associated with the Update Installer to finish.

  8. Check the log files for errors. The log files are located in directory WC_installdir/logs/update.


If you have a WebSphere Commerce or WebSphere Commerce Payments instance created, first update the WebSphere Commerce product, then relaunch the installer. Refer to Updating the instance silently.

If you do not have an existing WebSphere Commerce or WebSphere Commerce Payments instance then the installation of the fix pack is complete. Refer to Install final steps.

AIX|Solaris|Linux|If you plan to create a new instance and you have recently upgraded your WAS fix pack level, complete the following steps before creating a new WebSphere Commerce or WebSphere Commerce Payments instance:


 

Related Reference


WebSphere Commerce APARs
Troubleshoot: WebSphere Commerce fix pack issues