Update the instance silently

After installing the WebSphere Commerce fix pack, use the silent method to update any existing instances to the same fix pack level.

Prerequisite Ensure the following task is completed:


  1. If you have a database performance concern, consider having your database administrator tune the database before the fix pack update. The update command might run a long time if the database is poorly tuned. Refer to your database manual for specifics of tuning the database.

  2. Each new WebSphere Commerce or WebSphere Commerce Payments instance that is created after you have applied the fix pack to your WebSphere Commerce installation directory, is created at that specific fix pack level. You are not required to update the WebSphere Commerce or WebSphere Commerce Payments instance to the fix pack level.

  3. If you have multiple WebSphere Commerce or WebSphere Commerce Payments instances created repeat the install, of the fix pack, for each instance.


Complete the following steps to install the fix pack to the WebSphere Commerce instance.

  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. AIX|Linux|Solaris|Windows:

    Ensure your database server is started.

  5. Ensure that your WebSphere Commerce administrative server is started. For example:

    • If WebSphere Commerce is managed by WAS Deployment Manager (dmgr), start the deployment manager and all node agents. Optionally, your cluster can also be started.

    • If WebSphere Commerce is not managed by WAS Deployment Manager (dmgr), start the WAS server1.


    During the application of maintenance to the WebSphere Commerce instance, the Update Installer stops the WebSphere Commerce application automatically.

  6. Navigate to the UPDI_installdir/responsefiles directory and open the install.txt file in a text editor. Edit the following lines:

    1. Update the W maintenance.package entry with the directory name that contains the maintenance package.

    2. Update the W product.location with the location of the WebSphere Commerce install directory.

    3. Complete one of the following steps:

      • If you are updating a WebSphere Commerce instance, add the following lines to the end of the install.txt file
        -W update.instancename="instance"
        -W update.db="true"
        
        
        

        If you set -W update.db="false" update the database manually. Refer to Install final steps.

      • If you have a WebSphere Commerce Payments instance without WAS security enabled, add the following line to the end of the install.txt file
        -W update.instancename="payments_instance"
        
        
        

      • If you have a WebSphere Commerce Payments instance with WAS security enabled, add the following lines to the end of the install.txt file
        -W update.instancename="payments_instance"
        -W update.wassecurityenable="true" 
        -W update.wasuserid="WAS_user" 
        -W update.wasuserpassword="WAS_password"
        
        
        

        where WAS_user is a user defined in the user registry and WAS_password is the associated password for the user.

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

  8. Run one of the following commands from the UPDI_installdir directory:

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

    • I5/OS|update -devkit14 -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.

  9. Check the log files for errors. The log files are located in the following directories:

  10. Complete one of the following steps:

    • If you have a WebSphere Commerce instance, restart the WebSphere Commerce application.

    • If you have a WebSphere Commerce Payments instance with no security enabled, restart the WebSphere Commerce Payments application.

    • If you have a WebSphere Commerce Payments instance with security enabled...

      1. Linux|AIX|Solaris|Log in as the non-root user.

      2. Navigate to directory WC_installdir/payments/bin.

      3. Run the following command:

        • AIX|Linux|Solaris|./IBMPayServer payments_instance payment_password

        • I5/OS|Windows:

          IBMPayServer payments_instance payment_password


Refer to Install final steps to complete the fix pack installation.

 

Related Reference


WebSphere Commerce APARs
Troubleshoot: WebSphere Commerce fix pack issues