SolarisLinuxAIXWindows

Installing WebSphere Commerce fix packs interactively

You can install your fix pack using an interactive method which uses a graphical install wizard. After navigating through the install panels, your fix pack is installed.

For IBM i OS operating systemNote: You cannot install WebSphere Commerce fix packs interactively. Instead, you should follow the steps for installing the fix pack silently

Before you begin

  • Download and extract the WebSphere Commerce V7.0.0.x installation package to a temporary location. For example:
    • C:\temp\FPx
    where x is the fix pack level.
    Download the appropriate fix pack for the feature pack you plan to install:
    • Feature Pack 1WebSphere Commerce version 7.0.0.1 or higher
    • Feature Pack 2WebSphere Commerce version 7.0.0.2 or higher
    • Feature Pack 3WebSphere Commerce version 7.0.0.3 or higher
    • Feature Pack 4WebSphere Commerce version 7.0.0.5 or higher
    • Feature Pack 5WebSphere Commerce version 7.0.0.6 or higher
    • Feature Pack 6WebSphere Commerce version 7.0.0.7 or higher
    • Feature Pack 7WebSphere Commerce version 7.0.0.8 or higher
    • Feature Pack 8WebSphere Commerce version 7.0.0.9
    To download, see Fix packs for WebSphere Commerce.

About this task

Complete this section to install the WebSphere Commerce fix pack. If you have already created a WebSphere Commerce or WebSphere Commerce Payments instance, you must apply the fix pack to the WebSphere Commerce product installation directory first. After the fix pack is applied to the product, you must then apply it to your WebSphere Commerce or WebSphere Commerce Payments instances.

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

Procedure

  1. Download the required WebSphere Commerce fix pack.
  2. Save the fix pack to directory:
    • UPDI_installdir/maintenance
    Notes:
    1. Ensure that 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 that you plan to install.
    2. Do not put any other maintenance files in the UPDI_installdir/maintenance directory.
  3. Before you apply the fix pack to your machine, back up the following objects:
    WC_profiledir directory
    See Backing up and recovering the application server environment.
    Database
    The database updates that are included in this fix pack cannot be undone. If you want to undo the database update after you apply the WebSphere Commerce fix pack, you must restore your database backup. See your database documentation for information about backing up your database.
    JSP files
    A fix pack overwrites certain JSP files that are 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 installation 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.
  4. If you use a staging server, you must ensure that your production server and staging server stay synchronized.
    To keep them in sync, apply fix packs using the following steps:
    1. Optional: It is recommended that you run the stagingprop utility before you install the fix pack.
      To ensure that stagingprop is run successfully:
      1. Check the stagingprop log file.
      2. Check the STAGLOG table in the staging database and confirm that no unprocessed records exist. An unprocessed STAGLOG record is a record in which the STGPROCESSED column has a value of 0.
    2. Stop all activities on the staging server. Any data changes on the staging server are neither captured nor propagated from this point until installation is completed.
    3. WebSphere Commerce Version 7.0.0.3WebSphere Commerce Version 7.0.0.2WebSphere Commerce Version 7.0.0.1Issue the following SQL statement and make note of the number of the latest record in the STAGLOG table in the staging database
      SELECT MAX(STGRFNBR) FROM STAGLOG
    4. Install the fix pack on the staging server and update the instance.
    5. WebSphere Commerce Version 7.0.0.3WebSphere Commerce Version 7.0.0.2WebSphere Commerce Version 7.0.0.1Mark all the STAGLOG records inserted during fix pack installation 
      UPDATE STAGLOG SET STGPROCESSED=1 where STGRFNBR > lastnum
      where lastnum is the number you made note of in step c.

      As the database is updated on the staging server, corresponding staging triggers will get fired, and these changes are captured in the STAGLOG table. If this STAGLOG data is not clean up, it will cause duplicate exceptions the next time that stagingprop is run because the production server will have the same data after the fix pack is installed and the production database is updated.

    6. Install the fix pack on the production server.
    7. By default Access Control Policy tables are not staged. If you manually added Access Control Policy tables to the staging configuration, you need to run the stagingcopy utility.
  5. Review the following information about WebSphere Commerce instances:
    OptionDescription
    Existing WebSphere Commerce instances
    Important: If you customized your WebSphere Commerce instance, ensure that you followed the documented deployment procedure in the IBM Knowledge Center, otherwise your customizations are removed when the fix pack is installed. For more information about customized code, see Customized code deployment.
    1. You must apply the fix pack to the WebSphere Commerce product installation directory first. After the fix pack is applied to the product, you must then apply it to your WebSphere Commerce or WebSphere Commerce Payments instances.
    2. If any new components are installed from the WebSphere Commerce base (7.0) DVD images, you must reinstall the fix pack in order to upgrade that component to the current fix pack level. For example, if you installed the WebSphere Commerce remote management utilities on a separate node from your 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.
    3. Delete all the old disk cache files before you install a fix pack.
      1. Stop the WebSphere Application Server V70-WC_instance_Name.
      2. Delete the contents of the disk offload cache that can be found in one of these directories:
        Default location
        WC_profiledir/temp/node_name/server1/_dynacache
        Offload location
        This 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.
    4. Correct data in the MSGTYPES table, if necessary.

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

      1. Back up the records in your table with MSGTYPE_ID = 1002, 1003, 1004, then delete them from your original table.
      2. After you apply Fix Pack 1 to the WebSphere Commerce Version 7.0 instance, reinsert the backup records into the table, but change the MSGTYPE_ID values to 620, 621, 622.
    New WebSphere Commerce instances Each new WebSphere Commerce or WebSphere Commerce Payments instance that you create after you applied the fix pack to your 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.

What to do next

Note: If you encounter an error that says Unhandled exception, Type=Segmentation error while running installing the fix pack, you might need to install one of the following:
  • DB2 V9.5 Fix pack 6a, or higher
  • DB2 V9.7 Fix pack 3a, or higher
See Troubleshooting: Massload error when using DB2 for details.