IBM SG24-6320-00 User Manual
6320ch_sum_of_changes.fm
Draft Document for Review July 28, 2004 7:33 pm
30
Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide
The Product Management tooling
The Product Management tooling in WebSphere Commerce Accelerator allows
you to update your catalog merchandise information directly. It also allows you to
create bundles, dynamic kits and pre-built kits.
you to update your catalog merchandise information directly. It also allows you to
create bundles, dynamic kits and pre-built kits.
2.6.8 Business Models
Where as WebSphere Commerce 5.1 started with B2C sample store
(InFashion), the Business Edition of WebSphere Commerce released a little later
added B2B sample store (ToolTech) to the list. The concept of business models
was introduced into WebSphere Commerce V5.5. Business models are
discussed more in detail in 2.5, “WebSphere Commerce Business models” on
page 22.
(InFashion), the Business Edition of WebSphere Commerce released a little later
added B2B sample store (ToolTech) to the list. The concept of business models
was introduced into WebSphere Commerce V5.5. Business models are
discussed more in detail in 2.5, “WebSphere Commerce Business models” on
page 22.
2.6.9 Access Control
The WebSphere Commerce’s authorization model is based upon the
enforcement of access control policies. Access control policies are enforced by
the access control Policy Manager. In general, when a user attempts to access a
protected resource, the access control policy manager first determines what
access control policies are applicable for that user and then, based upon the
applicable access control policies, it determines if the user is allowed to perform
the requested operation on the given resource. In WebSphere Commerce V5.6
the access control is implemented by:
enforcement of access control policies. Access control policies are enforced by
the access control Policy Manager. In general, when a user attempts to access a
protected resource, the access control policy manager first determines what
access control policies are applicable for that user and then, based upon the
applicable access control policies, it determines if the user is allowed to perform
the requested operation on the given resource. In WebSphere Commerce V5.6
the access control is implemented by:
Access control policies and roles: Hierarchical policy and role based
system defined during site creation and then enforce during server runtime
system defined during site creation and then enforce during server runtime
Subscription based model: When an organization subscribes to policy
groups, only the policies in those policy groups will apply to the organization’s
resources. Its ancestor organization’s policies will not apply.
groups, only the policies in those policy groups will apply to the organization’s
resources. Its ancestor organization’s policies will not apply.
2.6.10 Collaboration
WebSphere Commerce supports two types of collaboration functionality. To use
one, or both features, you must first install the supporting software associated
with each type of collaboration.
one, or both features, you must first install the supporting software associated
with each type of collaboration.
Collaborative workspaces (Business Edition): Collaborative workspaces
support asynchronous communication by way of Lotus QuickPlace.
Collaborative workspaces also requires that member data be on an LDAP
server used with WebSphere Commerce, not in a relational database.
support asynchronous communication by way of Lotus QuickPlace.
Collaborative workspaces also requires that member data be on an LDAP
server used with WebSphere Commerce, not in a relational database.
Customer care: Customer care provides real-time customer service support
through a synchronous text interface using the Lotus Sametime server.
through a synchronous text interface using the Lotus Sametime server.