Applying an interim fix to the WebSphere Commerce instance silently

You can use a silent method to install an interim fix on a WebSphere Commerce instance.

Before you begin

  • For IBM i OS operating systemEnter the QShell by typing QSH at the OS/400 or i5/OS command prompt.
  • Ensure that the WebSphere Commerce administrative server is started. During the application of maintenance to the WebSphere Commerce instance, the Update Installer stops the WebSphere Commerce application automatically. For example:
    • If WebSphere Commerce is managed by WebSphere Application Server Deployment Manager (DMGR), ensure that this server is started.
    • If WebSphere Commerce is not managed by WebSphere Application Server Deployment Manager (DMGR), ensure that the WebSphere Application Server (for example, server1) is started.
  • Ensure that the database is started.

Procedure

  1. Navigate to the UPDI_installdir/responsefiles/ directory and open the install.txt file in a text editor.
  2. Update a WebSphere Commerce instance:
    1. Update the -W maintenance.package entry with the name of the maintenance package.
    2. Update the -W product.location entry with the location of the WebSphere Commerce install.
    3. Update the -W update.instancename entry with the instance_name. If -W update.instancename does not exist, add the entry to the end of the file.
  3. Run the following command from the UPDI_installdir:
    • SolarisLinuxAIX./update.sh -silent -options UPDI_installdir/responsefiles/install.txt
    • For IBM i OS operating systemupdate -options UPDI_installdir/responsefiles/install.txt
    • Windowsupdate.bat -silent -options UPDI_installdir/responsefiles/install.txt
  4. Refer to the log files in WC_installdir/logs/update/ to verify that your install was successful.
  5. Restart the WebSphere Commerce application from within the WebSphere Application Server Administration Console.
    Note:

    If you have additional instances created, you can update them by updating the response file, and repeating the installation.

  6. WebSphere Commerce - ExpressFeature Pack 7 or later If you are using WebSphere Commerce Express edition and you have a remote search server, deploy the search EAR (Search_eardir) to your remote search server.

What to do next

Important: Review the readme file that is included with the interim fix package. The readme file might contain additional steps that are required for the specific interim fix.