Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java System Communications Express 6 2004Q2 Administration Guide  

Chapter 8
Migrating PAB Data to Address Book Server

Previously   Personal Address Book (PAB) was used to store user’s contacts in Sun ONE Messaging Server and PAB could be accessed only by web-based clients deployed on Sun ONE Messaging Server. To enable other modules such as calendar access the user’s address book, Sun Java System Messaging Server for Communications Express uses the Address Book Server instead of PAB to store users’ contact details. Because of this, users accessing Communications Express using existing Sun ONE Messaging Server installations must migrate their PAB data to the Address Book Server.

This chapter contains the following sections:


Migration Process

PAB data residing in different directories can be migrated to Address Book Server using the address book migration tool. The migration tool is a standalone executable that migrates user’s Messenger Express address book data to the Address Book Server that is part of Communications Express.


Note

Sun Java System Messenger Express uses a different directory server for maintaining PAB Data from the one used by Address Book in Communications Express. The migration utility migrates all the data from PAB to Address Book when the user logs in for the first time. However, once data is migrated to Address Book, new contacts or groups created using Messenger Express will not be shown in the Address Book of Communications Express. The reverse is also true.


Figure 8-1  Overview of the Data Migration Process

Diagrammatic  representation of the data  migration process.

Data migration can take place in two ways:

Batch Migration

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.

Before running the runMigrate.sh script, the administrator should provide the following command line arguments required by the MigratePab utility in runMigrate.sh:

Dynamic Migration

In the dynamic migration process, data migration is initiated when the user logs into Communications Express for the first time. For dynamic migration to occur, the administrator must enable dynamic migration when configuring Communications Express.

The Migration process depends on:

Data migration occurs when:

Preliminary steps to be performed by the administrator after installing Communications Express are:

  1. Configuring Communications Express to enable dynamic migration.

  2. Note

    If dynamic migration is not enabled in uwcauth.properties file, PAB data will not get migrated to the Address Book Server.


  3. Configuring the Address Book Server with the PAB Server details. For example, you need to configure the Host Name, Port Number, BindDN, BindDN Credentials, PAB Host Path and Host Machine names to which the data is to be migrated.
  4. Based on the user's mail host, the PAB configuration entries listed in Table 8-1 are retrieved and the connection to the PAB Server established.

Dynamic Migration Process

Dynamic Migration occurs when the user logs into Communications Express.


Tip

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.



Migration Thread

During migration, the migration thread confirms whether the user is a mail user and then finds the PAB details from uwcconfig.properties file for the mail user. The uwcconfig.properties file contains the default PAB host name or multiple PAB host names (if the user is present on multiple domains). Based on these entries, Address Book determines the appropriate PAB host to which the data should be migrated and establishes the connection.

Example

When User1 in the domain siroe.com has an entry in PAB such as Entry1 that needs to be migrated, the entry is located in the PAB tree under ou=User1 as shown in green in Figure 8-2.

Figure 8-2  Location of Entry1 in the PAB tree

Location of Entry1 in the PAB tree

After migration, the newly created Address Book Server Entry is added to the Address Book Server tree under o=siroe.com, cn=Entry 1 as shown in red in Figure 8-3.

Figure 8-3  Location of Entry 1 in the Address Book Server tree.

Location of Entry 1 in the Address Book Server  tree.

A new configuration file is added in the Address Book Server called migrate.properties that has the following details:

To migrate data the migration tool needs to know whether:


Migration Scenarios

Migration can be performed from:

  1. A single Messenger Express instance pointing to the default single PAB host.
  2. A single Messenger Express instance pointing to multiple PAB hosts.
  3. A single Messenger Express instance pointing to multiple PAB hosts with the default PAB host set.
  4. Multiple Messenger Express instances pointing to single PAB host.
  5. Multiple Messenger Express instances pointing to multiple PAB hosts.



Previous      Contents      Index      Next     


Copyright 2004 Sun Microsystems, Inc. All rights reserved.