WebSphere Portal integration prerequisites for the WebSphere Commerce machine
Software
Install...
- WebSphere Commerce Feature Pack 2.
Update the fix pack level to DB2 8.1 fix pack 11 (also referred to as DB2 8.2 fix pack 4) or higher.
Configuration
Ensure that the system meets the following requirements:
- Functioning WebSphere Commerce instance at the 6.0.0.2 level.
- You are able to log on to the Administration Console using the WebSphere Commerce Site Administrator user ID.
You are able to log on to the WebSphere Commerce machine using the WebSphere Commerce non-root user.
- A WebSphere Commerce consumer direct store has been published. Refer to the STOREENT table and record the storeID value. For example, run the following command...
-
select * from storeent
- The system clocks of the WebSphere Portal machine and the WebSphere Commerce machine should be synchronized.
- The IP addresses of the WebSphere Commerce Server and WebSphere Portal Server are registered in a DNS server, and that they can access each other by hostname.
Prerequisite tasks
- Enable WebSphere Commerce services
- If you are using the basic authentication type, complete the instructions found in Prepare Lightweight Directory Access Protocol with WebSphere Commerce and WebSphere Commerce Portal.
If you are using simulated single sign-on you are not required to complete this step.
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.