IBM SG24-6320-00 Manuel D’Utilisation

Page de 306
6320ch_planning.fm
Draft Document for Review July 28, 2004 7:33 pm
38
 
Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
3.1  Migration Strategy considerations
Migration to WebSphere Commerce 5.6 is a complex undertaking. Regardless of 
the migration approach you choose, it will require a significant investment in time 
and resources. It will often be cost effective to include any pending site redesign 
or feature addition projects along with your migration effort. Here are some of the 
factors to consider.
3.1.1  Add or replace functionality
Consider adding new features and functionality that are available in WebSphere 
Commerce V5.6. Many of the marketing, advertising and convenience features 
built into the new version provide mechanisms to increase revenue and improve 
the customer experience.   
Additionally, if you have custom implementations that provide similar functionality 
to those new built-in features, you may want to consider the advantages of using 
the “stock” implementations provided in the product.
By rebuilding your store based on one of the new “Starter Store” models you can 
take advantage of the new functionality rather than implementing or maintaining 
these features in your existing site. Often you can reduce the amount of 
customization you have to manage which translates directly into lower operating 
costs.
3.1.2  Take advantage of DynaCache
Redesigning JSPs to utilize the DynaCache page and fragment caching 
technology may result in measurable improvements in throughput by reducing 
the load on the application server and database.   If you employ personalization, 
isolating the personalized content within JSP fragments is recommended to 
ensure the efficient operation of the site. Consider using the new “Starter Stores” 
as a model.
3.1.3  Optimization
Customers that are satisfied with their existing set of features and functionality 
and are interested in moving their existing implementation to the current version 
without any changes may still benefit from a site redesign if the load on the 
application server and database components can be reduced.