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.
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 |
Oracle WebCenter Collaboration and Oracle-BEA AquaLogic Interaction Publisher information | Can migrate Oracle WebCenter Collaboration or Oracle-BEA AquaLogic Interaction 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. |