User Migration Utility

User Migration Utility

+
Search Tips | Advanced Search

Overview
Enable the User Migration Utility before using.
Enter the following URL to access the Migration Interface:
http://[HOST]:[PORT]/wps/wcm/jsp/migration/migration.jsp

The User Migration Utility is divided into the following sections:

User Information

WebSphere Portal administrator login name:

Enter a valid WebSphere Portal administrator name.

Connect user path:

Enter the path to the old WCM server...
[OLD_ILWWCM_HOME]\connect\users
.

User Repository Information

Select user repository type:

If LDAP is not enabled, select Default.

If LDAP is enabled, select LDAP.

If LDAP is selected, the following settings are available. These are used to add LDAP information to the current WCM users when they are migrated into an LDAP repository:

LDAP user prefix:

E.g. - uid .

LDAP user suffix:

E.g. - cn=users .

LDAP group prefix:

E.g. - cn .

LDAP group suffix:

E.g. - cn=groups .

LDAP suffix:

E.g. - dc=setgetweb,dc=com .

Migration Options

Remove old UI objects:

If selected, the User Interface from the old WCM server will be removed.

Import administrators group:

If selected, any users included in the old WCM Administrator Group will be mapped to the new 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.)

Remove invalid characters from ID:

If selected, any invalid characters contained in the old WCM users IDs will be removed. E.g. - "&" will be removed.

Migration Actions

Update WMM.

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 the WCM 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.

Generate user migration mapping file.

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

Use user migration mapping file.

After the User Migration Mapping file has been edited, select this action and run the User Migration Utility again.

Final Steps

Shut down the WebSphere Portal server that WCM is installed on.
Delete the contents of the WCM System directory:
PortalServer\wcm\ilwwcm\system

Restart the WebSphere Portal server.

Web Content Authoring Access Control

The Access Control section of the Authoring Portlet's (Web Content Authoring) configuration view is used to manage each User's access to the different views in the Web Content Authoring. ensure that all migrated users are granted access to the relevant views within the Web Content Authoring.

Verify Migration

Open WebSphere Portal administration to verify the creation of users and groups.
Open the Web Content Management Web Content Authoring to verify the update of Categories and Keywords.
Logon to the Web Content Authoring with different users to verify that security and access controls are working.
Logon to a rendered Site as different users to verify access to rendered content.
Run the Member Fixer tool in "non-update" mode to make ensure Web Content Management and Member Manager data matches. See the Web Content Management Tools topic for further information.

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.

User Information	WebSphere Portal administrator login name: Enter a valid WebSphere Portal administrator name. Connect user path: Enter the path to the old WCM server... [OLD_ILWWCM_HOME]\connect\users .
User Repository Information	Select user repository type: If LDAP is not enabled, select Default. If LDAP is enabled, select LDAP. If LDAP is selected, the following settings are available. These are used to add LDAP information to the current WCM users when they are migrated into an LDAP repository: LDAP user prefix: E.g. - uid . LDAP user suffix: E.g. - cn=users . LDAP group prefix: E.g. - cn . LDAP group suffix: E.g. - cn=groups . LDAP suffix: E.g. - dc=setgetweb,dc=com .
Migration Options	Remove old UI objects: If selected, the User Interface from the old WCM server will be removed. Import administrators group: If selected, any users included in the old WCM Administrator Group will be mapped to the new 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.) Remove invalid characters from ID: If selected, any invalid characters contained in the old WCM users IDs will be removed. E.g. - "&" will be removed.
Migration Actions	Update WMM. 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 the WCM 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. Generate user migration mapping file. If there are potential conflicts with existing WCM and Member Manager Users and Groups, you can Generate a User Migration Mapping file. You can then edit this file and map the WCM Users and Groups to the correct Member Manager Users and Groups. Use user migration mapping file. After the User Migration Mapping file has been edited, select this action and run the User Migration Utility again.