Process: Import member data
Flow
Objective
To allow for importing member data.
Description
There are many use-cases where it may be desirable to load member data. For example, to keep the list of users in the commerce instance synchronized with some other system, or to load a list of member profiles to be used in an email campaign. The member subsystem therefore supports the concept of loading users, organizations, and member groups.
Features
The member subsystem supports loading member data either using the Loader package.
Customization
If the database user registry is used for storing userids and passwords, then any new users loaded through the massload process will need to be assigned a new password. A way to achieve this would be to load the users, then invoke the reset password command on each new user - to assign a new random password and send an email notification that the password has been changed.
Edition
Professional, Enterprise
Tasks
| Task | Description | Role |
|---|---|---|
| Load member data |
The member data can be loaded into the system using either the massload capability (see the Loader package information in the WebSphere Commerce development online help for more details) or through a custom tool using one of the enterprise integration adapters. |
Site Administrator |
| Prepare member data (external) |
The process of converting the data into a format that WC member subsystem is done external from the system. This typically includes mapping attributes from attributes in the external system to WebSphere Commerce attributes, and generating customer passwords. |
Site Administrator |
Business artifacts
(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.