About Object Migration

Object migration lets you copy resources from one portal to another. You might want to do this for several reasons. You might have multiple portals to handle a global deployment or you might want to create multiple portals to separate development, testing, and production.

You can copy resources from one portal to another by creating migration packages, which can be used to:

Export objects created in a development portal and import them to your production portal when they have been properly tested.
Import portal objects in order to install new features on your portal. For example, you might want to install a portlet suite and register those portlets in your portal.

There are several things you can do to make migration as easy and effective as possible:

Keep source and target portals as similar as possible to reduce the mapping required.
Create migration packages as soon as possible after approving objects. The object settings in a migration package are those present at package creation, not those present at object approval. Creating migration packages soon after approval minimizes the chance that object settings have changed since approval.
You can selectively import objects in a migration package, so if you want to import content crawlers and communities separately, you can import a package twice, and select different objects each time you import it.

The Migration - Export utility in the portal lets you create migration packages. To import objects from a migration package, you use the Migration - Import utility.

Migration Feature	Description
Portal objects that can be included in the package	All objects
Collaboration and Publisher information	Can migrate Collaboration or Publisher information
Requests and approval	Users with at least Edit access to objects can request migration, but only members of the portal administrators group can approve objects for migration. An administrator selects approved objects to add to a migration package, and can also add object to the package without making a migration request. Users with the Access Utilities activity right can check the status of their migration requests.
Creating a migration package	Only users with the Access Utilities activity right can create a migration package. An administrator can add objects that do not have migration requests to a migration package (bypassing the request and approval process).
Object dependencies	Dependencies always maintained. Dependent objects can be included in a migration package, but do not need to be.
Unique universal identifiers (UUIDs) and their effect on subsequent importing migration packages	By default UUIDs are maintained, so that subsequent migrations overwrite previously migrated objects. However, if you do not want to overwrite previously migrated objects, you have the option of creating a new instance of the same object, with a new UUID.

Requesting That an Object Be MigratedYou can request that an object be added to a migration package to be exported to another portal.
Approving Objects for MigrationWhen users want an object to be migrated, they submit a migration request. A portal administrator can then approve the request, and the object is added to the migration package.
Creating a Migration Package in the PortalYou can create a migration package that includes portal resources as well as Publisher and Collaboration information.
Creating a Migration Package Using the Command Line ToolYou can create a migration package to export portal objects from one portal to be imported into another portal.
Importing Objects in the PortalYou can import objects from another portal using the Migration — Import Utility..
Importing Objects Using a Command Line ToolYou can import objects from another portal with a migration package.

Parent topic: Migrating Portal Objects

AquaLogic Interaction Administrator Guide

About Object Migration