Filter
Top Products
Chapter 3. Migration Strategy and Planning 39
Draft Document for Review July 28, 2004 7:33 pm 6320ch_planning.fm
3.1.4 External product and user management
If you manage your persistent data externally, then there may be little benefit
derived from performing a migration. Some examples may include:
Third-party or custom catalog management systems
LDAP authentication
Order status and history retrieved on-demand from an external source
3.1.5 How does custom code impact the process?
Regardless of the approach chosen for the migration, you will have to recreate
and test your custom code to account for changes in the new version.
WebSphere Commerce V5.6 introduces the concept of a “Master Catalog”. The
Master Catalog must be a true tree with no loops in the structure. Items must
now have parents and the parent products can only exist in a single category in
the Master Catalog. If you manage your product information in an external
system, consider how these new requirements will impact your integration code.
Several changes in the structure and deployment of custom code will require
your attention.
String Converters in Access Beans are no longer supported
Security Roles are now required for Enterprise Java Beans
Fine Grained Access Control methods have changed
Command parameter validation methods have changed
User registration and logon mechanisms have changed
Calculation framework customization is now policy based
Access to OrderItems through the OrderItemAccessBean has been changed
to use a new Item Bean instead
3.1.6 Prepare a detailed Plan
Review with your development team the requirements and then prepare a
detailed migration plan that includes the refactoring and testing effort required to
implement these changes on your site. The following section cover Planning
more in detail.
Note: For further details refer to the product information center at the following
URL:
http://publib.boulder.ibm.com/infocenter/wc56help/index.jsp