Installing maintenance
WebSphere Commerce
maintenance includes installing fix packs, interim fixes (APARs), and cumulative interim
fixes.
Before you begin
Note: Some fixes require steps after installation to enable or turn on new behavior
that is introduced with the fix. Every maintenance package includes instructions in a
*readme.htm file that describes how to install and, if necessary, how to enable
the fix. Ensure that you follow the instructions in the
*readme.htm.
The following table provides hints and tips for
installing and enabling certain fixes.
Refer to the following subtopics for instructions on how to install a maintenance
package.WebSphere Commerce Developer | WebSphere Commerce | |
---|---|---|
Environment-specific packages | Ensure that you install the developer version of the fix onto WebSphere Commerce Developer environments. WebSphere Commerce Developer packages include the text developer in the file name. For example, JR53164.fep_6.0.0.0_developer.zip. | Ensure that you install the server version of the fix onto WebSphere Commerce runtime environments. WebSphere Commerce packages include the text server in the file name. For example, JR53164.fep_6.0.0.0_server.zip. |
How to install a maintenance package |
|
|
Enablement steps after you install a store-related fix | To ensure that your store customizations are not overwritten, fixes that update starter store
JSP files or widgets are not automatically updated for your published store. Instead:
|
To ensure that your store customizations are not overwritten, fixes that update starter store
JSP files or widgets are not automatically updated for your published store. Instead:
|
Enablement steps after you install a Management Center-related fix | Updates to the Management Center framework are automatically applied but you might need to
rebuild the OpenLaszlo project to see the changes.
|
Updates to the Management Center framework are automatically applied and the installation
process recompiles LOBTools for you. If you followed all guidelines on how to
extend Management Center, your updates will not be lost so you do not have to redeploy
LOBTools. If for some reason you have to redeploy LOBTools, see Packaging Management Center files for deployment. If you do not see the expected changes to Management Center after you install a fix, try clearing the browser cache and then relaunch Management Center. |
Enablement steps after you install a WebSphere Commerce search-related fix | Refer to the *readme.htm that is included in the maintenance package that you downloaded. You might need to rebuild the search index (run the di-buildindex utility) or you might need to set up a new search index (run the setupSearchIndex utility). | Refer to the *readme.htm that is included in the maintenance package that you downloaded. You might need to rebuild the search index (run the di-buildindex utility) or you might need to set up a new search index (run the setupSearchIndex utility). |
Best practices to ensure that your customizations are not overwritten by a maintenance update. |
|