Including Object Personalization Data
Transport capabilities enable the creation, export, and import of portal content, contained in transport packages, between different portal systems. However, the PCD objects in themselves do not carry user personalization data, which is associated with the user, not the object. For this purpose, you use a transport personalization page to include user personalization data with the export of the package.
To prevent confusion, the difference between PCD personalization data and user data must be emphasized. The personalization data included in the export refers to user-specific modifications to PCD objects, such as changes to iView properties or the creation of personal pages. Only this kind of data can be included in the personalization transport. User master data - such as name or address, which is maintained by the AS Java user management engine - is not included.
The users, whose personalization data is included, exist on the target system.
-
In the Portal Catalog, in the context menu of the transport package, choose
Open 
Package Content 
. The
Transport Package Content editor opens. -
From the link bar of the Transport Package Content editor, choose Personalization to open the Personalization Data editor.
-
Search for users, groups, or roles whose personalization data should be included with the package.
-
Whether you searched for users, groups, or roles, make sure that you move the users, whose personalization data you want to transport, from the Available Users list to the Selected Users list.
Partial personalization data cannot be included. The data file containing the user personalization information includes all the personalization information of the user.
The overwrite behavior during import is the same as for normal content - existing objects on the target system are replaced by the data of the import file. Merge is not possible.