Install > Installing maintenance > WebSphere Commerce


Install WebSphere Commerce fix packs


Overview

A fix pack installs on top of a specific version or release. For example, applying Fix Pack 2 to v7.0.0.0 changes the version to 7.0.0.2.

A fix pack is first installed to the product installation directory and then installed to a WCS instance.

Review: Fix packs for WebSphere Commerce.

Ensure the required Program Temporary Fixes (PTFs) have been applied to the WebSphere Commerce system.

WC fix packs are tested with the WebSphere Application Server maintenance levels available when the WC fix pack is released. You can install a WC fix pack on these maintenance levels, or on later maintenance levels.

Review the technote: Recommended fixes for WebSphere Commerce.

WC v7 for IBM i includes the fixes provided by fix pack 1. Therefore it does not need to be applied.

For new WC v7.0.0.1 installations, if using DB2 v9.7, install DB2 v9.7 fix pack 1 before WC. WC v7.0.0.1 does not automatically install DB2 v9.7.1. Once you have installed DB2, install WC using a custom installation.

For existing WC v7.0.0.0 users, to migrate from DB2 v9.5 fix pack 4 to DB2 v9.7 fix pack 1, install WC v7 fix pack 1 first.

After completing the installation of the WC fix pack, migrate the database from DB2 V9.5 Fix Pack 4 to DB2 V9.7 Fix Pack 1.


db2_adminotm.bnd

For remote DB2, manually copy the DB2 bind file from the DB2 server to the DB2 client before creating a WCS instance. Copy db2_adminotm.bnd from the server to the client bnd directory. By default, the bnd file resides...

This error, DB2 v9.7 APAR IC62106, has been fixed as of Fix Pack 3.


Miscellany

Ensure that both the server and client are the same fix pack level when you copy the files.

WebSphere Commerce Payments is deprecated in WebSphere Commerce v7, you cannot use DB2 v9.7 with WebSphere Commerce Payments.

The DB2 v9.7 registry variable DB2_COMPATIBILITY_VECTOR is not supported.

WebSphere Commerce Payments is deprecated in WebSphere Commerce v7, you cannot use DB2 v9.7 with WebSphere Commerce Payments.


Addition of support for WebSphere Application Server 64-bit

To review the supported 64 bit versions of WebSphere Application Server see WebSphere Commerce v7 software requirements.


Cache information

For any existing WCS instances, delete all the old disk cache files prior to installing a fix pack...

  1. Stop the WebSphere application server V70-WC_demo.

  2. Delete the contents of the disk offload cache found in one of these directories:

    • Default location:

      WC_PROFILE/temp/node_name/server1/_dynacache

    • Offload location

      Offload location directory is set in the WebSphere Application Server Administration Console. Click...

      Servers | Server Types | WebSphere Application Servers | server1 | Container Settings | Container Services | Dynamic Cache Service | Disk cache settings | enable disk offload

      Cancel the enable disk offload.

  3. Start the application server.

  • Correct data in the MSGTYPES table, if necessary.

    If you have created the own table that references the MSGTYPES table, using MSGTYPE_ID as foreign key, and if there are records in the table with MSGTYPE_ID = 1002, 1003, or 1004, take steps to ensure that the fix pack installation succeeds.

    1. Back up the records in the table with MSGTYPE_ID = 1002, 1003, 1004, then delete them from the original table.

    2. After you apply Fix pack 1 to the WebSphere Commerce v7.0 instance, we will need to reinsert the backup records into the table, but change the MSGTYPE_ID values to 620, 621, 622.

    To minimize downtime, apply the fix pack at a time that will least impact the operation of the business.

    Apply the fix pack to the development environment first, to ensure that you do not negatively impact the production environment.

    Verify the WebSphere Commerce and WebSphere Commerce Developer environments are at the same fix pack level.

    In a staging environment, ensure you run stagingprop utility before installing the fix pack.

    In a staging environment both the staging and production machines must satisfy the following conditions:

    • the WebSphere Commerce Application and the WebSphere Commerce database are at the same fix pack level.

    • the same APARs are applied to both staging and production.

    Disable the firewall, or allow access to the WebSphere Application Server administrative server. If you have installed a firewall on the machine, it can interfere with the application of the fix pack.

    If any new components are installed from the WebSphere Commerce base (7.0) DVD images, reinstall the fix pack in order to upgrade that component to the current fix pack level. For example, if you have installed the WebSphere Commerce remote management utilities on a separate node from the WebSphere Commerce Server, install the fix pack on that node as well. If you do not install the fix pack on that node, you are not able to use the Configuration Manager client.

    If you are operating a clustered environment, apply the fix pack on the machine where WebSphere Commerce is installed. The WebSphere Commerce Update Installer stops the WebSphere Commerce application of the selected WCS instance.

    Ensure that you have sufficient disk space to install the fix pack. If the temporary and installation file systems are on the same partition then the amount of space required is the sum of the space required on the temporary and installation file systems.

    The user running the update installer should have the authority 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.

    A fix pack overwrites certain JSP files related to the WebSphere Commerce tools pages. See the text file 7.0.0.x files changes for a list of the files that are overwritten during the install of the fix pack. A link to this text file is found on each WebSphere Commerce fix pack download page. The Fix packs for WebSphere Commerce technote provides links to the fix pack download pages.

    If you have customized the WCS instance, ensure that you have followed the documented deployment procedure in the WebSphere Commerce Information Center, otherwise the customizations are removed when the fix pack is installed. For more information about customized code, see Customized code deployment.


    Procedure

    1. For each new fix pack you install, download and install the latest WebSphere Commerce Update Installer.

    2. Download the required WebSphere Commerce fix pack.

    3. Save the fix pack to directory:

      Verify the fix pack maintains the proper file extension. The file must be named 7.0.0-WS-WCServer-FP00X.pak where X is the number of the fix pack we will install.

      IBM recommends that no other maintenance files reside in directory: UPDI_installdir/maintenance.

    4. Before applying the fix pack to the machine, you should backup the following objects:

    5. Review the following information concerning WCS instances:

      Option Description
      Existing WCS instances You must apply the fix pack to the WebSphere Commerce product installation directory first. After the fix pack is applied to the product, then apply it to the WebSphere Commerce or WebSphere Commerce Payments instances.
      New WCS instances Each new WebSphere Commerce or WebSphere Commerce Payments instance that you create after you have applied the fix pack to the WebSphere Commerce product 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.

    6. Select an appropriate installation method for the WebSphere Commerce fix pack.

      Option Description
      WebSphere Commerce Developer Install WebSphere Commerce Developer fix packs with the IBM Installation Manager
      GUI installation

      1. Update the installation directory interactively

      2. Update the instance interactively
      Silent installation

      1. Update the installation directory silently

      2. Update the instance silently


    See also

    1. Install WebSphere Commerce fix packs interactively
    2. Install WebSphere Commerce fix packs silently
    3. Install final steps
    4. Migrate the database from DB2 V9.5 Fix Pack 4 to DB2 V9.7 Fix Pack 1
    5. Update the WebSphere Commerce Build and Deployment tool after installing a WebSphere Commerce fix pack


    +

    Search Tips   |   Advanced Search