Maintenance overview
WebSphere Commerce Version 8.0 provides maintenance packages that can include code fixes, security fixes, new features, or enhancements.
- The final fix pack for Mod Pack 0 is 8.0.0.19 and was released on January 24, 2017.
- The final fix pack for Mod Pack 1 is 8.0.1.14 and was released on June 29, 2017.
- The final fix pack for Mod Pack 3 is 8.0.3.6 and was released on August 9 2017.
- Going forward, HCL intends to release fix packs for Mod Pack 4 only.
WebSphere Commerce delivers two types of maintenance packages: fix packs and mod packs. A fix pack contains code fixes and security fixes. A mod pack contains new features and enhancements to existing features. A mod pack also contains most of the fixes that are available at the time of its release. Both types of maintenance packages are cumulative: a fix pack includes all previous fix packs and a mod pack includes all previous mod packs.
Maintenance package | Product number change example |
---|---|
Fix Pack | 8.0.0.1 |
Mod Pack | 8.0.1.0 Note: When you install a mod pack, the fix pack number is
reset to 0. |
Maintenance installation paths
You can install maintenance packages that are newer than your current version, but you cannot install maintenance packages that are older than your current version.I am on maintenance level ... | I want to upgrade to ... | Result |
---|---|---|
Mod Pack 1 (8.0.1.0) | Downgrade to Fix Pack 9 for base (8.0.0.9) | You cannot directly install a lower level maintenance package, but you can rollback to a previously installed maintenance package. For example, if you upgraded from 8.0.0.9 to 8.0.1.0, then you can rollback to 8.0.0.9. |
Mod Pack 1 (8.0.1.0) | Fix Pack 2 for Mod Pack 1 (8.0.1.2) | Installation successful. Your WebSphere Commerce level is changed to 8.0.1.2. |
Fix Pack 3 for base (8.0.0.3) | Fix Pack 2 Mod Pack 1 (8.0.1.2) | Installation successful. Your WebSphere Commerce level is changed to 8.0.1.2 and you get the features and enhancements that are included in Mod Pack 1. |
Maintenance release plan
Fix Pack | Mod Pack |
---|---|
Includes code fixes and security fixes only. No new functionality is included in a fix pack. | Includes code fixes, security fixes, new functionality, and enhancements. |
Might include database changes such as new database columns, tables, or indexes. | Might include database changes such as new database columns, tables, or indexes. |
Might include updates to database column sizes, but will never change database column data types. | Might include updates to database column sizes, or database column data types. |
Does not change your customized files. However, in some cases, you might need to merge new code into existing customizable files to enable a fix onto your environment. | Does not change your customized files. However, in some cases, you might need to merge new code into existing customizable files to enable a fix onto your environment. |
Does not change bootstrap files. For more information about bootstrap files, see Bootstrap files. | Might include changes to bootstrap files. For more information about bootstrap files, see Bootstrap files. |
Can be installed while maintaining high availability and with zero downtime. | Can be installed while maintaining high availability and with zero downtime. |
Can be installed by using the roll out update process for clustered environments. | Can be installed by using the roll out update process for clustered environments. |
If you migrated from WebSphere Commerce Version 7, you might want to review the following topic to understand the maintenance changes from Version 7 to Version 8, Maintenance strategy.
Maintenance hints and tips
IBM releases maintenance packages for both the WebSphere Commerce Developer (test) and WebSphere Commerce (runtime) environments. Ensure that you download both versions (Developer and Server). You want your test environment and runtime environment to be synchronized with the same code base. It is recommended that you first update WebSphere Commerce Developer and test to ensure that everything works as expected (including your customizations) before you update your WebSphere Commerce runtime environment.
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 | Use the IBM Installation Manager. | Use the WebSphere Commerce Update Installer. Note: You first need to update the product
installation directory, and then update the instance. |
Enablement steps after you install a maintenance package |
|
|
Enablement steps specifically for store-related fixes that are included in a maintenance package | 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 specifically for WebSphere Commerce search-related fixes that are included in a maintenance package | After you install a maintenance package, review the following topic for steps on how to enable specific search-related fixes, Additional steps for search-related interim fixes. | After you install a maintenance package, review the following topic for steps on how to enable specific search-related fixes, Additional steps for search-related interim fixes. |
Best practices to ensure that your customizations are not overwritten by a maintenance update. |
|
Submitting a Problem Management Request (PMR)
If you encounter a technical product issue, you can submit a PMR. For more information about PMRs, see What's a PMR?. If needed, the WebSphere Commerce development team will create a fix and deliver the fix in a future fix pack. WebSphere Commerce will not deliver interim fixes for your specific issue. You need to wait for a fix pack that includes your fix, and then install the applicable fix pack.
Whether your issue is resolved in the next immediate fix pack depends on the complexity of the issue and the time it takes for the development team to create and test the fix. WebSphere Commerce anticipates that most issues should be resolved and available within the next two fix pack releases. That is, depending on when WebSphere Commerce receives your PMR, expect to wait 2 to 5 weeks to get your fix.