Installing final steps

After you installed a WebSphere Commerce fix pack, complete the following steps.

Procedure

  1. Reinstall APARs that are not included in this fix pack.
    To determine the APARs that are installed on your WebSphere Commerce machine, refer to the APARs fixed in WebSphere Commerce fix packs.
  2. WebSphere Commerce Version 7.0.0.6 or later For environments that are integrated with Sterling Order Management (for WebSphere Enterprise Service Bus integration) only.
    If you are upgrading a fix pack without upgrading the feature pack:
    From WebSphere Commerce, copy the following file:
    • WC_installdir/wc.ear/Order-DataObjects.jar/xsd/OAGIS/9.0/Overlays/IBM/Commerce/Resources/Nouns/Order.xsd
    to the following location on the WebSphere Enterprise Service Bus module:
    • ESB_INSTALL_DIR\IBM\WebSphere\ESB\profiles\ESB_PROFILE_NAME\installedApps\CELL_NAME\WCToSSFSMediationModuleApp.ear\WCToSSFSMediationModule.jar\xsd\OAGIS\9.0\Overlays\IBM\Commerce\Resources\Nouns\
    Failure to copy the Order.xsd file to the WebSphere Enterprise Service Bus module might cause integration errors.
  3. WebSphere Commerce - ExpressFeature Pack 7 or later If you are using WebSphere Commerce Express edition and you have a remote search server, deploy the search EAR (Search_eardir) to your remote search server.
  4. Optional: Update the database manually.

    It is recommended that you use the latest DB2 fix pack.

    If you chose not to update the database when you update your WebSphere Commerce instance to the fix pack level, it is recommended that you manually update the database. On the machine where you applied the fix pack, complete the following steps:

    1. It is recommended that you back up your database before you run updatedb.

      If you have a database performance concern, consider having your database administrator tune the database you run updatedb. If the database is poorly tuned, the updatedb might run a long time. Refer to your database manual for specifics of tuning the database.

    2. Complete one of the following actions:
      • SolarisLinuxAIXLog on as the non-root user.
      • For IBM i OS operating systemLog on with a user profile that has *SECOFR authority.
      • WindowsLog on as a user with Administrator privileges
    3. From a command prompt, run the following command:
      • WebSphere Commerce Version 7.0.0.3WebSphere Commerce Version 7.0.0.5WebSphere Commerce Version 7.0.0.7WebSphere Commerce Version 7.0.0.2WebSphere Commerce Version 7.0.0.4WebSphere Commerce Version 7.0.0.1WebSphere Commerce Version 7.0.0.6
        • SolarisLinuxAIXWC_installdir/bin/updatedb.sh instance_name [currentPropFile]
        • WindowsWC_installdir/bin/updatedb.bat instance_name [currentPropFile]
      • WebSphere Commerce Version 7.0.0.8 or later
        • SolarisLinuxAIXWC_installdir/bin/updatedb.sh instance_name [currentPropFile -DdbUserPassword dbUserPassword -DdbaPassword dbaPassword]
        • WindowsWC_installdir/bin/updatedb.bat instance_name [currentPropFile -DdbUserPassword dbUserPassword -DdbaPassword dbaPassword]
      Where
      instance_name
      The name of the WebSphere Commerce instance to be updated.
      DB2currentPropFile
      DB2

      The currentPropFile is the full path and name of the database properties file. The currentPropFile is used when a database, other than the one specified in the instance.xml file, is to be updated. For example, two databases might be configured; one for operational purposes and the other for content purposes. The currentPropFile takes the same format as the createInstance.properties found under directory WC_installdir/instances/instance_name/properties. The database section in the currentPropFile is used to acquire the parameters that are needed for the updatedb command.

      WebSphere Commerce Version 7.0.0.8 or laterdbUserPassword
      WebSphere Commerce Version 7.0.0.8 or laterThe WebSphere Commerce database user password.
      WebSphere Commerce Version 7.0.0.8 or laterDdbaPassword
      WebSphere Commerce Version 7.0.0.8 or laterThe WebSphere Commerce database administrator user password.
      Note: You cannot run updatedb against the Payments instance.
    4. When the update is complete, review the output that is displayed in the console window. Ensure that you 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=7,
      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=7
      [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 installed fix pack.
  5. Optional: WebSphere Commerce Version 7.0.0.9 or laterDB2 Run the RUNSTATS SQL file: WC_installdir/schema/db2/fixpackX/wcs.runstats.sql, where X is the number of the installed fix pack.

    For example, if you installed Fix Pack 9, run WC_installdir/schema/db2/fixpack9/wcs.runstats.sql only.

    The SQL file issues the RUNSTATS command against database tables that were affected by the fix pack installation. It is recommended that you issue RUNSTATS to prevent database performance issues and maintain current database table statistics.

  6. Optional: WebSphere Commerce Version 7.0.0.8 or laterRemove cascade deletion for database tables in the production environment.
    By removing this type of deletion, you can prevent data loss during a stagingprop operation. For more information, see Removing cascade deletion in the production environment to prevent data loss.
  7. Optional: WebSphere Commerce Version 7.0.0.8 or laterSplit the primary key ranges for your database tables between the staging and production environments.
    By splitting the key ranges, you can prevent a primary key collision during propagation of data from staging to production. For more information, see Key splitting.
  8. Optional: Remote web server tasks

    You must update the web server machine with a new Stores.war every time that you update the static web content inside the application.

    For example, update the web server machine when you publish a store, or upload a logo. The Stores.war is in the following directory:

    WC_profiledir/installedApps/cell_name/WC_instance_name.ear

    Ensure that the following statements are true:
    • The path to Stores.war is the same on the web server node and the WebSphere Commerce node.
    • The permissions of each directory in path WC_profiledir/installedApps/cell_name/WC_instance_name.ear have group read and execute.
    Note: Remove any JSP and JAR files from the WC_instance_name.ear directory on the web server. Ensure that only static-content files are in this directory on the web server.
  9. Optional: WebSphere Commerce Version 7.0.0.8Review your log configurations.

    Fix Pack 8 includes enhancements to logging configurations that might affect some loggers. Review the following topic to verify that the loggers are up to date, Missing information in log files after you install fix pack 8.

  10. Precompile your JSP files before launching your store.