WebSphere Commerce best practices, Building an extensible and flexible WebSphere Commerce multi-store deployment

From the developerWorks archives

Howard Borenstein, Ross McKegney, and Darshanand Khusial

Date archived: January 3, 2017 | First published: May 17, 2006

You can think of the organizational structure in WebSphere® Commerce as the skeleton that strings together business artifacts of the commerce system, such as catalogs and fulfillment centers. This structure plays a key role in determining business and functional privileges to these artifacts. This article describes how organizational structure decisions impact store assets, authorization, contracts, and LDAP integration.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=112100
ArticleTitle=WebSphere Commerce best practices: Building an extensible and flexible WebSphere Commerce multi-store deployment
publish-date=05172006