Publishing a WebSphere Commerce version 5.6.1 store archive in WebSphere Commerce version 6.0
To publish a WebSphere Commerce version 5.6.1 store archive in WebSphere Commerce version 6.0, first migrate the store archive to WebSphere Commerce version 6.0.
New features and enhancements in the WebSphere Commerce version 6.0 runtime architecture have made version 5.6.1 store archives incompatible with version 6.0.
- The WebSphere Commerce Web application moved from a proprietary model-view-controller implementation to the Struts open source implementation. Struts is a well documented framework for J2EE Web application development, which has become an industry standard for deploying model-view-controller applications.
- The stack move from WAS version 5.x to WAS version 6.0 took advantage of the new J2EE 1.4 which includes the JSP 2.0, Servlet 2.4, and JSTL 1.1 specifications.
For more information on these changes, see What's new in this release.
Since you cannot publish a store archive that is based on WebSphere Commerce version 5.6.1 in WebSphere Commerce version 6.0, migrate your version 5.6.1 store archive to version 6.0, and then publish the store archive in version 6.0.
To migrate a version 5.6.1 store archive to version 6.0:
- Remove all references to the URLREG and VIEWREG database tables.
- Apply the correct JSP files to the version 6.0 store archive.
- Identify the new store archive as a version 6.0 store archive.
Now that you have migrated your version 5.6.1 store archive to version 6.0, you can publish the store archive in WebSphere Commerce version 6.0. After you publish the store archive, migrate your payments to use payment plug-ins.
Related tasks
Remove references to the URLREG and VIEWREG database tables
Applying the correct JSP files to the version 6.0 store archive
Identifying the new store archive as a version 6.0 store archive