User Migration Scenarios

When a Web Content Management User or Group is migrated to Member Module, there are two possible results:

  • If the Web Content Management User or Group name does not exist in Member Manager, a new User or Group is created in Member Manager. All references to the Web Content Management User or Group in Web Content Management data (Authors, Owners, Approvers, Live Users etcetera) are changed to the new Member Manager User or Group.
  • If the Web Content Management User or Group name already exists in Member Manager, all references to the Web Content Management User or Group in Web Content Management data (Authors, Owners, Approvers, Live Users etcetera) are changed to the existing Member Manager User or Group.
This process has some potential issues. For example:

  • The Web Content Management User, "John Smith", may also have a Member Manager user name of "John A Smith". The migration process would result in John Smith having two user IDs in Member Manager.
  • There may be two users with the name of "Penelope Jones" in your organization, one a Web Content Management user, and one a Member Manager User. The migration process would result in all the references to the Web Content Management "Penelope Jones" in Web Content Management data being changed to the Member Manager "Penelope Jones". Web Content Management "Penelope Jones" would no longer have access to her Web Content Management data.

There are two possible migration scenarios when migrating Web Content Management Users and Groups to Member Manager:

Migrating directly to Member Manager If you know of no potential conflicts with existing Web Content Management and Member Manager Users and Groups, you can migrate your Web Content Management Users and Groups directly to Member Manager.
Migrating via a User Migration Mapping file If there are potential conflicts with existing Web Content Management and Member Manager Users and Groups, you can Generate a User Migration Mapping file.

You can then edit this file and map your Web Content Management Users and Groups to the correct Member Manager Users and Groups.

 

Migrating Users directly to Member Manager

If you know of no potential conflicts with existing Web Content Management and Member Manager Users and Groups, you can migrate your Web Content Management Users and Groups directly to Member Manager.

  1. Enter the following URL to access the Migration Interface: 
    http://[HOST]:[PORT]/wps/wcm/jsp/migration/migration.jsp
  2. Enter the WebSphere Portal Administrator name.
  3. Enter the path to the [ILWWCM_HOME]\connect\users folder from your old Web Content Management server.
  4. If migrating the Administrator Group, check the Administrator Group box. The Administrator Group will be mapped to the Administrator Group defined in connect.cfg. The default value for this group is wcmadmins. (See the User Management topic for more information on the Administrators Group.)
  5. Select Update WMM

Important: User and Group Names

To use the Update WMM command, the user and group names in Web Content Management should match the users in Member Manager exactly. If not, "Update WMM" will create a new user and group for all users and groups that do not match.

E.g. - If your Web Content Management users or groups include spaces in their names, or if they use a different case from the equivalent name in Member Manager, "Update WMM" will create a new user and group for each of these occurrences.

If any user or group names do not match, use the "Generate and Use Migration Mapping File" option. See below.

 

Migrating via a User Migration Mapping file

If there are potential conflicts with existing Web Content Management and Member Manager Users and Groups, you can Generate a User Migration Mapping file. You can then edit this file and map your Web Content Management Users and Groups to the correct Member Manager Users and Groups.

Generating a User Migration Mapping file

  1. Enter the following URL to access the Migration Interface: 
    http://[HOST]:[PORT]/wps/wcm/jsp/migration/migration.jsp
  2. Enter the WebSphere Portal Administrator name.
  3. Enter the path to the [ILWWCM_HOME]\connect\users folder from your old Web Content Management server.
  4. If migrating the Administrator Group, check the Administrator Group box. The Administrator Group will be mapped to the Administrator Group defined in connect.cfg. The default value for this group is wcmadmins. (See the User Management topic for more information on the Administrators Group.)
  5. Select Generate User Migration Mapping File

Reviewing and Editing the User Migration Mapping File

Before processing the User Migration Mapping file, modify the migrationUsers.properties file located at <wcm_home>/migration/migrationUsers.properties

The original Web Content Management Users and Groups are listed on the left, and the Member Manager names are listed on the right. You should only change the proposed Member Manager names. use a Distinguished Name when entering the Member Manager name on the right hand side. For example:

  • uid=username,o=default organization
  • cn=group name,o=default organization

Ensure that you do not use the "&" character in user or group names as this will cause errors: Example: To change a group named "All Staff" to "All WP Staff", edit the property as follows:

  • All\ Staff=All\ WP\ Staff
  • To use distinguished names: All\ Staff=cn=All_WP_Staff,ou=groups,dc=ibm,dc=com

 Processing the User Mapping file

  1. Enter the following URL to access the Migration Interface: 
    http://[HOST]:[PORT]/wps/wcm/jsp/migration/migration.jsp
  2. Enter the WebSphere Portal Administrator name.
  3. Select Use User Migration Mapping File
  4. Your current Web Content Management Users and Groups will be updated to match the entries in the edited Mapping file.

Adding new Users or Groups to Member Manager When you process the User Mapping File it only updates the names of the Users and Groups in Web Content Management. If any of your current Web Content Management Users and Groups do not exist in Member Manager, also run the xmlaccess command.

  1. Open a command prompt.
  2. Go to /PortalServer/bin
  3. Run the following command: 
    Windows: 
xmlaccess.bat -in /path/PortalServer/wcm/migration/migrationUsers.xml 
-user portalAdmin -pwd password -url http://host:port/wps/config 

UNIX and i5/OS: 
xmlaccess.sh -in /path/PortalServer/wcm/migration/migrationUsers.xml 
-user portalAdmin -pwd password -url http://host:port/wps/config
Ensure you replace "path", "portalAdmin", "password", "host" and "port" with the actual setting of you Web Content Management installation.

Note: Folder and file locations under i5/OS

In i5/OS installations, Web Content Management files are located in the "wp user root" directory, not "/PortalServer/wcm/". E.g. -

  • WAS 5.1.1.3 - /QIBM/UserData/WEBAS51/Base/instance name/PortalServer51

  • WAS 6 - /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/instance name/PortalServer51

Parent topic: User Migration

IBM Workplace Web Content Management - V5.1.0.1 -

 

Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.