Exporting Personalization Data 

Use

The Export Package Editor enables the encapsulation of portal content into exportable and importable packages. This allows for the transport of content objects between different portal systems. However, the PCD (Portal Content Directory) objects in themselves do carry user personalization data, which is associated with the user, not the object. For this purpose, the Export Package Editor has available a personalization transport page that allows for the inclusion of user personalization data with the export package.

About PCD Personalization Data:

To prevent confusion, the difference between PCD personalization data and user data must be pointed out and emphasized. The personalization data being exported are user‑specific modifications to PCD objects, for example, changes to iView properties or creating personal pages; only this kind of data can be included in the PCD personalization transport. User master data, such as name or address, which is maintained by the AS Java User Management, is not included here.

Prerequisites

The administrator knows for which users or groups personalization data is to be transported. The same users must exist on the target system to which personalization data is imported.

A transport package for export has been created and portal content added to it. See Creating a Transport Package.

Procedure

...

       1.      From the Display drop-down list in the Export Package Editor, choose Personalization Transport to go to the Personalization Transport Settings page.

       2.      In the Available Personalization Data area, you can search for users and/or groups for whom you want to transport personalization data.

       3.      Choose Add to include the users from the Available Personalization Data table to the Selected Personalization Data table.

       4.      Return to the Static Content page and choose Export. (See Performing an Export.)

The Export Preview page appears. The users for whom personalization data was added to the export appear in the table.

If a group was added to for personalization export, all its constituent users appear in the table, not the group, and the personalization data of all the users is exported.

In the Status column of the Export Preview page, the value “Available” appears for each user in the table. In the event that no personalization information is found for any user, the Status field will show the value “Not Found”.

Also, personalization data cannot be included in part. The data file containing the user personalization information includes all personalization information of the user.

The overwrite behavior during import is the same as for normal content—existing objects on the target system is replaced by the data of the import file. Merge is not possible.