WebSphere Portal integration prerequisites for the WebSphere Commerce machine


+

Search Tips   |   Advanced Search

 


Software

Install...


Configuration

Ensure that the system meets the following requirements:


Prerequisite tasks

Decide what Distinguished Name (DN) you want to use for root organization and default organization. The WebSphere Commerce Member Subsystem can only access the root organization, and all entries that are descendants of it.

Since WebSphere Portal is sharing a user registry with WebSphere Commerce, both applications must be able to find the users therefore the users must be created anywhere beneath the WebSphere Commerce Root organization.

The WebSphere Commerce default organization (Default Organization) is a direct descendant of the WebSphere Commerce root organization (Root Organization), and is the parent of guest and B2C users.

B2B users should not be created under the Default Organization. Instead, they should be created under their respective buyer and seller organizations. If a user is manually created in the LDAP server, then when the user logs on to WebSphere Portal which triggers a single sign-on to WebSphere Commerce, the user will be automatically replicated into the WebSphere Commerce database. The attributes that are replicated is determined based on the ldapentry.xml file. When the user is created in the WebSphere Commerce database, the profile type of the user will be specified as 'C' (B2C user) if the parent organization of the user is Default Organization, and 'B' (B2B user) otherwise. This is important because only 'B' type users can be managed from the Organization Administration Console, whereas 'C' type users can be managed from the Accelerator.


Related concepts

WebSphere Commerce integration with WebSphere Portal Authentication types


Related tasks

Publishing a store archive Configure WebSphere Portal with WebSphere Commerce - - -