Install > Installing maintenance > WebSphere Commerce > Installing WebSphere Commerce fix packs

Commerce fix pack post-install steps

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

1. Reinstall APARs not included in this fix pack.

2. If you chose not to update your database when updating your WCS instance to the fix pack level, manually update the database.

   On the machine where you have applied the fix pack...

   1. Backup the database

      The updatedb might run a long time if the database is poorly tuned.

   2. Log on as the non-root user and run....

      WC_INSTALL/bin/updatedb.sh instance [currentPropFile]

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

      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

      WC_INSTALL/instances/instance/properties/ createInstance.properties

      The database section in the currentPropFile is used to acquire the parameters required for the updatedb command.

   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=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 fix pack installed.

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

   Stores.war is located in...

   WC_PROFILE/installedApps/cell_name/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_PROFILE/installedApps/cell_name/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.

4. Precompile your JSP files before launching the store.
   

+

Search Tips   |   Advanced Search