Preparing to install WebSphere Commerce maintenance

These steps prepare you to install WebSphere Commerce fix packs and interim fixes (iFixes). Review all of the following information before you continue with your WebSphere Commerce maintenance installation.


  1. Obtain the maintenance package that you want to install.
    • If you are installing an interim fix then you need to obtain it from IBM Fix Central or, if the interim fix is not available on Fix Central, from IBM Support.
    • If you are installing a fix pack, you can review Fix packs for WebSphere Commerce. The technote contains links to the download page for each fix pack. Each download page provides information about how to sign up for automatic notification of new fix packs and flashes.
  2. Apply any relevant fixes.
    • WebSphere Commerce fix packs are tested with the WebSphere Application Server maintenance levels available when the WebSphere Commerce fix pack is released. You can install a WebSphere Commerce fix pack on these maintenance levels, or on later maintenance levels. Ensure that you applied the Required and recommended fixes for WebSphere Commerce.
    • If you are installing an individual interim fix, ensure that the latest cumulative interim fix is installed (if one exists for your fix pack or feature pack level).
      Note: A cumulative iFix is a fully tested, downloadable package that includes all of the individual iFixes that have accumulated since the release of a feature pack or fix pack. These packages are designed to simplify installation and standardize the code level of an environment. All additional iFixes that are released after the cumulative iFix are tested and verified on the latest code base. Therefore, if a cumulative interim fix exists for your feature pack or fix pack level, then you need to install the latest cumulative interim fix before you install any additional iFixes.
      For information about the latest cumulative interim fix releases, see Interim fixes and cumulative interim fixes.
  3. Ensure that you have sufficient disk space to install the maintenance package.
    It is recommended that the amount of free disk space is at least two times the size of your wc.ear file. If your temporary and installation file systems are on the same partition, then more disk space might be needed.
  4. Ensure that you are using the latest version of the WebSphere Commerce Update Installer.
    To obtain the latest version of the update installer, see WebSphere Commerce Update Installer Versions 6.1 and 7.0.
  5. Ensure that the user that is running the Update Installer has the proper authority.
    • SolarisLinuxAIXThe user must be able to successfully execute chmod and su - non-root_user without any prompt for a password when applying a fix package to a WebSphere Commerce or WebSphere Commerce Payments instance.
    • For IBM i OS operating systemThe user must have *SECOFR authority.
  6. Disable your firewall, or allow access to the WebSphere Application Server administrative server.
    If you installed a firewall on your machine, it can interfere with the application of the fix pack.
  7. WebSphere Commerce Version or laterFirewall considerations for STMP servers.

    Some firewalls might be configured to introduce a delay after receiving several NOOP messages to protect against Denial of Service attacks. You must either validate the firewall and SMTP configurations for NOOP messages, or set mail.smtp.userset to true.

    For more information, see Configuring validation for No Operation (NOOP) messages.

  8. Ensure that your custom assets are properly deployed. See Deploying.
  9. Back up your database if you are installing a fix pack.
  10. Back up your WebSphere Application Server configuration and EAR files in the following circumstances:
    • If you are installing a fix pack
    • If you are installing an interim fix that results in changes to the WebSphere Commerce EAR or WebSphere Commerce Payment Manager EAR. See the readme file that is included in the fix package to determine whether any of these EAR files are affected. For example, if you created an instance and the readme file includes instructions to update existing WebSphere Commerce instances, then back up your WebSphere Application Server configuration and WebSphere Commerce EAR files.
    • If you are installing a cumulative interim fix
  11. Back up the configuration of your node using the backupConfig command.
  12. Perform a file system backup of InstalledApps:
    Back up the following EAR files.
    • (WebSphere Commerce) WAS_profiledir\installedApps\cell_name\WC_instancename.ear
    • (WebSphere Payment Manager) WAS_profiledir\installedApps\cell_name\WC_payments_instance_name.ear
  13. Install the maintenance package.