Applying an interim fix to the WebSphere Commerce instance interactively

Update the WebSphere Commerce instance to complete the interim fix package installation.

Before you begin

Ensure that you have the proper system administration rights:
- Log in as the root user.
  Note: If you are a non-root user, you can apply interim fixes only if you installed WebSphere Commerce Update Installer as a non-root user.
  - Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a
    If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited
  - Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192
- Log in as a user that has QSECOFR authority.
- Log in with a Windows user ID that is a member of the Administrator group.
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.
- If WebSphere Commerce Search is managed by WebSphere Application Server Deployment Manager (DMGR), start the deployment manager and all node agents. Optionally, your cluster can also be started.
- If WebSphere Commerce Search is not managed by WebSphere Application Server Deployment Manager (DMGR), start the WebSphere Commerce Search Server (for example solrServer).
Ensure that the database is started.

Procedure

Open a command line, navigate to the UPDI_installdir directory and type the following command:
- ./update.sh
- update.bat
On the Welcome panel, review the information and click Next to continue.
Specify the WebSphere Commerce installation directory or click Next to accept the WebSphere Commerce product that is found on your computer.
Ensure that the correct directory is listed for the WebSphere Commerce product. Enter the correct directory and then click Next.
When prompted, from the drop-down list, select the instance name to which you want to apply the interim fix. Click Next.

Note: If you have additional instances created, you can update the additional instances by relaunching the installer.
Select Install maintenance package. Click Next.
Select the appropriate .pak file from UPDI_installdir/maintenance/ directory and click Next.
Ensure that you select interim fixes only and do not select fix pack packages.
Note: You cannot install fix packs and interim fixes at the same time.
You are prompted to start exporting the WebSphere Commerce enterprise application that you have selected. Click OK to export the application. This might take several minutes.
On the summary page, review the information and then click Next to begin the installation.
Ensure that the installer displays the message Success: The following maintenance package was installed. If you do not see this message then UPDI indicates which log files to check for errors. Click Finish.
Restart the WebSphere Commerce application from within the WebSphere Application Server Administration Console.
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.