Data Migration takes place in two ways:
Dynamic Migration takes place when an existing Messenger Express user logs in to Communications Express. The Users receive an email after the migration is completed.
In the dynamic migration process:
The application checks if migration has been enabled in the uwcuath.properties file by checking the pab_mig_required parameter.
If the pab_mig_required parameter is set to true, the migration process is initiated.
The login logic then compares the nswmextendedprefs attribute in the user's LDAP entry. It checks for the value of the mepabmigration parameter to determine whether the user’s data has been previously migrated.
Once PAB migration is completed, the Address Book Server sets the nswmextendedprefs, mepabmigration properties to 1 in the logged in user entry, to indicate the completion of the migration process.
The user receives a mail after the PAB data is successfully migrated to the Address Book Server.
To receive a mail, you are required to set the parameters in the migrate.properties file.
Table 7–1 PAB Migration Email Parameters
Parameters |
Default Value |
Description |
---|---|---|
emailReqd |
True |
Enables mail to be sent after the PAB data has been migrated successfully. Accepted values are “True” and “False”. |
smtphost |
local mail host For example: budgie.siroe.com |
Specifies the SMTP relay host name. |
smtpport |
25 |
Specifies the SMTP relay port. |
mailsubject |
PAB Migration Status |
Specifies the subject of the mail. |
from |
admin@hostname |
Specifies the sender’s name. |
It is recommended that the administrator sends an email to all users informing them that PAB data migration will be triggered during the first login and as a consequence they will not see the Address Book data during the initial sessions. Users should contact the administrator if they are unable to see their data after 2 or 3 days.
In the batch migration process, migration takes place at the server level without end user interaction. The administrator executes the runMigrate.sh batch script to migrate the mail users PAB data present in a given domain. For mail users present in multiple domains, the administrator will have to invoke the runMigrate.sh script for each domain to migrate users PAB data from the given inetDomainBaseDN to the Address Book Server.
Set the following parameters in the runMigrate.sh script. This script is available at uwc-deployed-path/WEB-INF/classes directory.
BASE_DIR: Set this parameter to the uwc-deployed-path of the Communications Express installation.
JAVA_HOME: Set this parameter to the directory where Java is installed.
o=siroe.com, o=isp: Replace the values for siroe.com and isp to the inetDomainBaseDN for your configured domain.
Execute the batch migration script.
# ./runMigrate.sh |
If the batch migration fails, exceptions are displayed at the command line prompt.
Using the migration script, administrators can migrate all the users, a single user, or a set of users. Running the batch migration script without any options migrates the entire set of users. To migrate a single user, you can specify the userid of the user. To migrate a set of users, you should provide the list of users in a text file. The runMigrate.sh command has the following syntax:
./runMigrate.sh{ [-u < [uid] | [-f <uids-file]} [-h]
where:
-u option tells the runMigrate script that you want to migrate a single user. The —u option should be followed by the userid of the user who you want to migrate. Here is an example:
./runMigrate.sh -u user1
-f option tells the runMigrate script that you want to migrate a set of users that have been specified in a file. The —f option should be followed by the name of the file that contains the userids of the selected set of users who you want to migrate. Here is an example:
./runMigrate.sh -f usersToMigrate.txt
The usersToMigrate.txt file should contain one userid on a single line. For example:
user1 user2 user3 ... .... and so on..