Install WebSphere Commerce Developer fix packs

WebSphere Commerce fix packs should be installed and then tested. Fix packs contain fixes that correct known problems and hence might prevent a service call from being placed. Before installing a WebSphere Commerce fix pack, review this information.

Complete the following steps to install the fix pack:

  1. IBM WebSphere Commerce maintains a Web page that links to several fix pack related documents. This page is a central resource for information related toWebSphere Commerce v6 fix pack. The master technote summarizes the known fix pack issues, and which version of the fix packs they apply to. It provides information on how to sign up for automatic notification of new fix packs and flashes. Technotes can be found by using the technote number to search the IBM Web site at: www.ibm.com.

    Refer to the WebSphere Commerce v6 fix pack master technote for more information.

  2. This fix pack updates many files. Refer to the Files Changed link on each WebSphere Commerce fix pack download page. This file lists all the files, altered by the fix pack, including the JSP files for starter stores

    If you have made any custom modifications to any of the files listed in the Files Changed document, you must back them up before applying the fix pack. After the fix pack is applied re-implement your customization against the updated files. For example the fix pack updates the starter store archive files which are used only at store publish time. If you have a published store, review the Files Changed list to see if any of the file changes are relevant to the store you have published.

  3. A fix pack overwrites certain JSP files related to the WebSphere Commerce tools pages. Refer to the text file 600X_tools_jsps_changed.txt for a list of the JSP files that are overwritten. A link to the Tools JSPs changed file is located on each WebSphere Commerce fix pack download page.

  4. Download and install the WebSphere Commerce Update Installer.

  5. Download the required WebSphere Commerce fix pack.

  6. Save the fix pack to the UPDI_installdir/maintenance directory.
    Notes:

    • Do not save the fix pack to a directory whose name contains spaces. If you attempt to apply the fix pack from a directory whose name contains spaces, the installer will fail.

    • Ensure that the fix pack maintains the proper file extension. The file must be named 6.0.0-WS-WCDeveloper-FP00X.pak where X is the number of the fix pack you will install.

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

    • You must log in with a Windows user ID that is a member of the Administrator group.

    • Stop all instances of the WebSphere Commerce Developer.

  7. Select an installation method:

    Option Description
    Interactive installation

    1. Use the command line, navigate to the UPDI_installdir directory and type the update.bat command.

    2. Select a language and then click OK.

    3. On the Welcome page, review the information and click Next to continue.

    4. Specify the WebSphere Commerce Developer installation directory, and click Next.

    5. Select Install Maintenance Package. Click Next.

    6. Select the UPDI_installdir/maintenance directory and click Next.

    7. Select the 6.0.0-WS-WCDeveloper-FP00X.pak file and click Next.

    8. You are prompted to update the database.

      • Select Yes to update your database automatically.

      • If you select No, then manually update the database after you complete the installation.

    9. On the summary page, review the information and click Next.

    10. The installer displays this, or a similar, message 
      Success: The following maintenance package was installed:  WebSphere Commerce 
6.0.0.X - WebSphere Application Developer  
6.0.0.X on the following product: IBM WebSphere Commerce C:/WCToolkitEE60
      where X is the number of the fix pack installed

    11. If you do not see this, or a similar, message the installer will indicate which log files to check. Click Finish.

    12. If you encounter problems, refer to Troubleshoot: WebSphere Commerce Developer fix pack issues.

    13. Restart WebSphere Commerce Developer.

    Silent installation

    1. Use the command line, navigate to the UPDI_installdir/responsefiles directory and open the install.txt file in a text editor.

    2. Complete the following steps:

      1. Update the W maintenance.package entry with the directory name that contains the maintenance package.

      2. Update the W product.location entry with the location of WebSphere Commerce Developer.

      3. Set the -W update.db="true" entry. If you set this entry to false then manually update the database after you complete the installation.

    3. Navigate to the UPDI_installdir and run the following command:
      update.bat -silent -options UPDI_installdir/responsefiles/install.txt
      When the prompt returns, wait for the Java process associated with the Update Installer to finish.

    4. Refer to the log files in the following directory to verify that your installation was successful: WCDE_installdir/logs/update.

    5. If you encounter problems or errors, refer to Troubleshoot: WebSphere Commerce Developer fix pack issues

    6. Restart WebSphere Commerce Developer.

  • Optional: Update the database manually If you chose not to update the database automatically during the application of the WebSphere Commerce fix pack, manually update your database. Complete the following steps:

    1. Ensure you have a backup of the database.

    2. From a command prompt, launch the following command:

      • WCDE_installdir/bin/updatedb.bat cloudscape database_name

      • (DB2) WCDE_installdir/bin/updatedb.bat db2 database_name database_user_name database_user_password

      • (Oracle) WCDE_installdir/bin/updatedb.bat oracle database_name database_user_name database_user_password database_host server_port

      • I5/OS:

        WCDE_installdir/bin/updatedb.bat iseries database_name database_user_name database_user_password database_host

      Where:

      database_name

      The name of your WebSphere Commerce Developer database. For Cloudscape databases, the database_name must be fully qualified. For example, WCDE_installdir/db/mall

      database_user_name

      The name of your WebSphere Commerce Developer database user.

      database_user_password

      The WebSphere Commerce Developer database user password.

      database_host

      The database server host name.

      server_port

      The database server host port number.

    3. When the update is complete, review the output displayed in the console window and ensure that you have successfully updated the database to the correct fix pack level. For example: 
      UpdateSiteTable: [EchoNL] Updating database fixpack level ... 
[eCDatabaseVersionInfo] UPDATE SITE SET EDITION='ENT', VERSION=6, RELEASE=0, MOD=0, FIXPACK=X WHERE COMPNAME='BASE' 
[eCDatabaseVersionInfo] SELECT COUNT(*) FROM SITE 
[eCDatabaseVersionInfo] SELECT * FROM SITE 
[eCDatabaseVersionInfo] Columns in SITE table: 
[eCDatabaseVersionInfo] COMPNAME=BASE 
[eCDatabaseVersionInfo] EDITION=ENT 
[eCDatabaseVersionInfo] VERSION=6 
[eCDatabaseVersionInfo] RELEASE=0 
[eCDatabaseVersionInfo] MOD=0 [eCDatabaseVersionInfo] FIXPACK=X 
[eCDatabaseVersionInfo] Updated SITE table successfully. 
[EchoNL] Completed database fixpack update.  BUILD SUCCESSFUL
      where X is the number of the fix pack installed.

  • Optional: Update your version control systems with these files:


     

    Related tasks


    Uninstall WebSphere Commerce Developer fix packs

     

    Related Reference


    Troubleshoot: WebSphere Commerce Developer fix pack issues
    WebSphere Commerce APARs