The attribute psRoot in the User’s LDAP entry is an Addressbook Server compliant URL that defines the LDAP location from which the user’s Personal Address book entries are stored and retrieved. The psRoot attribute enables the administrator provision users so that PAB data for all users is spread across multiple directory locations.
For existing webmail users, if PAB Migration is enabled, the psRoot attribute is constructed using the existing pabURI attribute and a mapping table is defined in uwc-deploy-dir/WEB-INF/config/migrate.properties .
The lookup table in the migrate.properties file consists of the pabhost and pabport entries in the following format:
pabhost.pabport.abhostport = abldaphost:abldapport
where pabhost.pabport refers to the source directory instance and abldaphost and abldaport the target directory instance to which the PAB data is required to be migrated.
Thus, if you want to migrate the pab data from the directory running at pab.example.com:389 to address book directory running at abs.example.com:389 the entry in migrate.properties file should appear as:
pab.example.com.389.abhostport = abs.example.com:389
You may have as many lookups as found necessary in the migrate.properties file. If the pabURI attribute for a user uses pabhost and pabport, the psRoot constructed using the default psRoot pattern will be in the format:
If the lookup is not defined for a pabURI value, that is, no entry is provided in the mapping table that matches the pabURI, the pabhost and pabport values are used as the default values for abldaphost and abport. Implying that in the absence of a mapping table, the PAB entries from Messaging Server is migrated to another root in the same directory instance as per the Address Book Schema. In this scenario, the [Target] Directory Instance will be the same as the [Source] Directory Instance.
The lookup table is not defined by the patch installer. You need to define the lookup table after a patch install, and restart the web server.
Ensure that abldaphost:abldapport directory Server instance is defined in the db_config.properties file pointed to by the personalstore.properties of that domain.