Installing WebSphere Commerce interim fixes

WebSphere Commerce interim fixes and cumulative interim fixes can be installed with the WebSphere Commerce Update Installer (UPDI).

Important:
  • Ensure that you created the instance before you install any interim fixes to the product. If you install an interim fix to the product and then create an instance, you might encounter dependency issues when you install another interim fix in the future.
  • If you are installing an interim fix on top of a Feature Pack, ensure that features are enabled before you install the interim fix. For more information about features, see Enabling features.
Feature Pack 5WebSphere Commerce Version 7.0.0.7WebSphere Commerce Version 7.0.0.6Attention: IBM is aware that some interim fixes that were released for Feature Pack 5, Fix Pack 6, and Fix Pack 7 might cause issues when you install the fixes individually. As a result, IBM bundled the interim fixes and released the following cumulative interim fixes:JR53048 automatically resolves all conflicts and dependency issues that might occur if you were to install the interim fixes individually. If you are on Feature Pack 5, Fix Pack 6, or Fix Pack 7, it is highly recommended that you install the applicable cumulative interim fixes immediately.
Each individual iFix and cumulative iFix package contains a different readme file. Each readme file might include specific installation instructions. For example:
  • Some iFixes might require manual modifications to source code after you install the fix
  • For runtime environments, some iFixes might be applicable to the base WebSphere Commerce product only and not the instance.
You do not need database access to install an iFix because these fixes do not make any database changes during installation. However, some iFixes might require that you manually update the database to enable the fix after installation. Review the readme file to ensure that you install and enable the interim fix successfully.
If multiple interim fixes exist in your package, UPDI automatically determines the order by which the interim fixes are installed. UPDI resolves any dependencies or prerequisites as long as all the necessary interim fixes are downloaded to a location that UPDI can access, for example UPDI_installdir/maintenance.

About this task

Maintenance packages can be delivered as individual interim fixes, and cumulative interim fixes. A WebSphere Commerce cumulative interim fix is composed of every individual interim fix available up to the date that the cumulative interim fix is created. The following information applies to cumulative interim fixes:
  • You do not need to uninstall any previously installed interim fixes to apply a cumulative interim fix.
  • Any interim fixes that are released after a cumulative interim fix require the latest cumulative interim fix as a prerequisite.
  • Each cumulative interim fix contains all of the fixes from any previous cumulative packages. Therefore, you can install the latest cumulative interim fix without installing earlier ones.
You can install interim fixes by using the Update Installer (UPDI) graphical interface, or silently by using a response file. Both installation methods require the following steps before you can install an interim fix.

Procedure

  1. Obtain the necessary interim fix installation package (.pak) and place it in a location that is accessible to the WebSphere Commerce Update Installer.
    For example, the UPDI_installdir/maintenance/ directory.
  2. Optional: Verify the installation package.
    It is recommended that you verify the interim fix package before you proceed to install. IBM provides an MD5 file so that you can verify the installation package by validating its MD5 checksum values. Most UNIX and Linux operating systems include utilities to generate an MD5 hash. Microsoft Windows does not include an MD5 utility, but many third-party options are available. The following are high-level instructions to verify the download package:
    1. Obtain the MD5 file from a trusted IBM source. The MD5 file is a text file that contains the MD5 hash signature of the interim fix package.
    2. View the MD5 file in a text editor. It contains one line of characters.
    3. Use your MD5 hash utility to generate a hash signature of your copy of the interim fix package (*.pak).
    4. Compare the signature hash MD5 file that IBM provides, with the signature hash that you generated.

    If the values are identical, then proceed to install the package. If the values are not identical, then the installation package might be corrupted. Try to download the package again from the trusted IBM source. If the issue is not resolved, contact IBM Support.

  3. Ensure that WebSphere Commerce is at the necessary feature pack or fix pack level before you apply the interim fix.
    For example, JR50553.fep requires you to be at the Feature Pack 7 level.
  4. Introduced in Feature Pack 1 Ensure that customizations were deployed correctly and can be redeployed if necessary.
    If you are installing a fix on a WebSphere Commerce instance with IBM Management Center for WebSphere Commerce enabled, and you customized Management Center, ensure that the customized assets are properly deployed before you proceed. The customizations must be present and properly deployed on the target system (specifically the OpenLaszlo source code) before you install on the instance. Management Center (ManagementCenter.swf) is recompiled during the installation. If the customizations are not properly deployed, then you might lost customizations during the installation. For information on properly deploying Management Center customizations, see:IBM has taken many steps to ensure that the IBM Management Center for WebSphere Commerce Compile will complete successfully when IBM code is present only. IBM cannot ensure that the compile will be successful if you customized OpenLaszlo code. If the compile is not successful, you must consult with Management Center developers who implemented the customizations.
  5. Feature Pack 5 or later If you are using the Aurora starter store, it is recommended that you create a backup your store archive file (Aurora.sar) before you apply a cumulative interim fix.
    You can find the .sar file in the ConsumerDirect or ExtendedSites subdirectory in WCDE_installdir/starterstores/:
  6. Ensure that you are using the latest version of WebSphere Commerce Update Installer.
  7. Install any applicable prerequisite cumulative interim fixes.
    For example, before you can install Feature Pack 8 cumulative interim fix JR55049.fep, you must install the Fix Pack 9 cumulative interim fix JR55049.fp. Consult the readme file that is included in your interim fix package. The readme file provides special instructions that are required for your specific interim fix.

What to do next

You can now install the interim fix by using one of the following methods:For clustered environments, you can use a roll out process.