Installing final steps
After you install a WebSphere Commerce fix pack, complete the following steps.
Procedure
- 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:
- It is recommended to back up your database before
you run the updatedb utility.
If you have a database performance concern, consider having your database administrator tune the database before you run the updatedb utility. If the database is poorly tuned, the updatedb might run a long time. See your database manual for specifics of tuning the database.
- Complete one of the following actions:
- Log on as the non-root user.
- Log on as a user with Administrator privileges
- From a command prompt, enter the following command:
- WC_installdir/bin/updatedb.sh instance_name [currentPropFile]
- WC_installdir/bin/updatedb.bat instance_name [currentPropFile]
- WC_installdir/bin/updatedb.sh instance_name [currentPropFile -DdbUserPassword dbUserPassword -DdbaPassword dbaPassword]
- WC_installdir/bin/updatedb.bat instance_name [currentPropFile -DdbUserPassword dbUserPassword -DdbaPassword dbaPassword]
Where- instance_name
- The name of the WebSphere Commerce instance to be updated.
- currentPropFile
- 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 thecreateInstance.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. - dbUserPassword
- The WebSphere Commerce database user password.
- DdbaPassword
- The WebSphere Commerce database administrator user password.
Note: You cannot runupdatedb
against the Payments instance. - 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:
Where X is the number of the installed fix pack.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
- It is recommended to back up your database before
you run the updatedb utility.
- Optional: Split 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.
- 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. - The path to
- Precompile your JSP files before launching your store.