Install final steps

+

Search Tips   |   Advanced Search

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

  1. Required: If you have just installed WebSphere Commerce Fix Pack 4, install APAR LI73187. Refer to Technote 4018526 for more details.

    You are not required to install APAR LI73187 if you have just installed WebSphere Commerce Fix Pack 5.

  2. 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 WebSphere Commerce APARs.

  3. Optional: Update the database manually

    If you chose not to update the database when updating your WebSphere Commerce instance to the fix pack level, you should manually update the database. On the machine where you have applied the fix pack, complete the following steps:

    1. IBM recommends to backup your database before running updatedb.

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

    2. Windows: Complete one of the following actions:

      • AIX|Linux|Solaris|Log on as the non-root user.

      • I5/OS|Log on with a user that has *SECOFR authority.

      • Windows: Log onto the system that you are logged in with a user ID that is a member of the Windows Administration group.

    3. From a command prompt launch the following command:

      • AIX|I5/OS|Linux|Solaris|WC_installdir/bin/updatedb.sh instance [currentPropFile]

      • Windows: WC_installdir/bin/updatedb.bat instance [currentPropFile]

      Where instance is the name of the instance to be updated.

      (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/properties. The database section in the currentPropFile is used to acquire the parameters required for the updatedb command.

    4. 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.

  4. 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. Store Publishing and Upload Logo actions are examples of when you should update the Web server machine.

    The Stores.war is located in the following directory:

    WC_profiledir/installedApps/cell/WC_instance.ear

    Ensure the following:

    • 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/WC_instance.ear has group read and execute.

    Remove any JSP and JAR files from the WC_instance.ear directory on the Web server. Only static-content files should be in this directory on the Web server.

  5. Precompile your JSP files before launching your store.

Related tasks

Install WebSphere Commerce fix packs
Uninstall WebSphere Commerce fix packs

 

Related Reference


Troubleshoot: WebSphere Commerce fix pack issues