| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction 10g Release 4 (10.3.3.0.0) Part Number E14107-04 |
|
|
View PDF |
| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction 10g Release 4 (10.3.3.0.0) Part Number E14107-04 |
|
|
View PDF |
This chapter describes the steps you take to migrate (export and import), back up, and restore portal objects.
It includes the following sections:
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 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.
Note:
User preferences for associated with add-on products, such as Oracle WebCenter Collaboration, are not migrated with the user.
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 information |
Can migrate Oracle WebCenter Collaboration information |
|
Requests and approval |
Users with at least Edit access to objects can request migration, but only members of the 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 must 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. |
This section describes the following tasks:
You can request that an object be added to a migration package to be exported to another portal.
Note:
You must have at least Edit access to the object for which you want to request migration.
Search for the object or click Administration and navigate to the object.
Select the object and click the Migrate icon.
In the Script Prompt dialog box, describe why you want this object migrated and click OK.
To view the status of your migration request, open the object's editor and click the Migration History and Status page. Under Migration Status, you see whether your request is waiting for approval, has been approved, or has been rejected, as well as your comments and any comments from the portal administrator approving or rejecting the object.
When 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.
There are two ways to approve objects for migration: in the object's editor or using the Approve Objects for Migration Utility.
To approve a single object requested for migration, use the object's editor.
To approve all objects requested for migration, use the Approve Objects for Migration Utility.
See Approving Objects for Migration Through the Administrative Utility.
When 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.
Open the object's editor by creating a new object or editing an existing object.
Click the Migration History and Status page.
Under Migration Status, you see whether this object has been requested for migration, and, if so, whether it is waiting for approval, has been approved, or has been rejected.
If you are a member of the Administrators group, and you want to add this object to the migration package to be migrated to another portal, select Approve this object for migration.
Note:
Users who are not members of the Administrators group do not see this option.
After approving objects for migration, you can use the Migration - Export Utility to create a migration package.
When 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.
To use the Approve Objects for Migration Utility you must be a member of the Administrators Group.
You can create a migration package that includes portal resources as well as Oracle WebCenter Collaboration information.
To create a migration package, you must be a member of the Administrators group.
Click Administration.
In the Select Utility list, click Migration - Export.
On the Portal Resources page, perform tasks as necessary:
On the Package Settings page, perform tasks as necessary:
On the Add Existing Package Resources page, perform tasks as necessary:
Click Finish.
A status message is displayed as the migration package is being created. When the migration package is created, you can download it to your desktop.
Note:
If you are also migrating Oracle WebCenter Collaboration objects, those will be written to a .zip file on the computer where Oracle WebCenter Collaboration is installed. You must move this file from this location to the target location.
You can now use the migration package to import the migrated resources into another portal.
You must specify a name, description, and contact person for a migration package.
To create a migration package, you must have at least Edit access to the objects you want to add to the package.
If the Migration — Export Utility is not already open, open it now.
Click the Package Settings page.
In the Package name box, type the name for the package file that will be created when you click Finish (this file is given a .pte extension).
In the Package description box, type a description that clarifies the purpose of this export package to other portal administrators.
In the Publisher name box, type the person to contact with any questions about this export package.
You can select objects to export on the Portal Resources page of the Migration — Export Utility.
To create a migration package, you must have at least Edit access to the objects you want to add to the package.
If the Migration — Export Utility is not already open, open it now and display the Portal Resources page.
Under Resources, select the objects you want to add and what you want to export.
To select individual objects, select the type of object from the Select Resources list, then, in the dialog box, select the objects you want to add and click OK.
To add all objects that have been approved for migration, click Add All Approved.
If the object is a folder and you want to export the folder's contents, select Export Contents.
To export the object's dependencies, select Export Dependencies.
Dependencies are any other objects that are required by the object you are exporting.
To remove an object, select the object and click the Remove icon.
To select or clear all of the object check boxes in a column, select or clear the check box above the column.
To toggle the sort order of the objects, click Resources.
Under Export Settings, select the check box if you also want to export parent folders of objects you marked for Export Dependencies.
If you do not select this option, only references to those parent folders will be exported.
You can add objects from an existing migration package to the package you are creating on the Add Existing Package Resources page of the Migration — Export Utility.
To create a migration package, you must have at least Edit access to the objects you want to add to the package.
Note:
If the portal settings on an object in the existing migration package have changed since the package was created, the current portal settings on the object will be exported.
If the Migration — Export Utility is not already open, open it now and display the Add Existing Package Resources page.
Under Migration Package, specify the package from which you want to add objects.
To browse to a package on your computer or in your network, click Browse, select the migration package file (a .pte file), and click Open.
To get the package from a Web address, select Web Address and type the URL to the package.
If you must enter login credential to access the Web address, type the information in the Username and Password boxes.
Click Load Package.
Note:
Only objects that are currently in the portal will be displayed on the Portal Resources page.
Select resources from this package on the Portal Resources page.
You can create a migration package to export portal objects from one portal to be imported into another portal.
Note:
You cannot export Oracle WebCenter Collaboration objects using the command line tool. To export those objects, use the Migration - Export Utility in the portal. See Creating a Migration Package in the Portal.
Log in to the host computer for the portal as the user who owns the portal installation.
Use the command ptmigration.bat (for Windows) or ./ptmigration.sh (for UNIX) with the following parameters:
./ptmigration.sh [username] [password] -export [migration_package_name] [log_file_name] <-exportdependencies>
Where the parameters are as follows:
| Parameter | Description |
|---|---|
|
migration_package_name |
Required. The name and path of the migration package to be created |
|
log_file_name |
Required. The name and path of the log file to be created. The path to the log file must be different from that of the migration package. |
|
-exportdependencies |
Optional. Use this parameter to export any additional objects upon which the objects you are exporting depend. |
Press ENTER.
All objects approved for migration are exported into the migration package. The migration utility updates the migration status in the source portal.
You can import objects from another portal using the Migration — Import Utility.
Before you import a migration package (.pte file), place the package to a location that is accessible over your network.
Notes:
If you are also importing Oracle WebCenter Collaboration objects, you must place the .zip file in the same location as the .pte file.
If you are importing a migration package created with a previous version of Oracle WebCenter Interaction and the migration package includes users, you must either manually edit the user's password in the administrative user interface or you must export the users and import them again. Previously passwords were saved as clear text and are therefore not supported in the current version.
To import a migration package you must be a member of the Administrators group.
Click Administration.
In the Select Utility list, click Migration - Import.
On the Package Settings page, perform tasks as necessary:
Click the Unresolved Dependencies page and complete the following task:
Note:
This page appears only if there is an unresolved dependency.
On the Portal Resources page, perform tasks as necessary:
Click Finish.
A status message is displayed as the migration package is being created. When the migration package is created, you can download it to your desktop.
To import objects you specify the location of the migration package and what you want you want to import.
To import a migration package, you must have at least Edit access to the objects you want to add to the package.
Under Migration Package, specify the package from which you want to add objects.
To browse to a package on your computer or in your network, click Browse, select the migration package file (a .pte file), and click Open.
To get the package from a Web address, select Web Address and type the URL to the package.
If you must enter login credential to access the Web address, type the information in the Username and Password boxes.
Click Load Package.
Under Import Settings, select options for import.
| Option | Description |
|---|---|
|
Import ACLs |
Select this to import the Access Control Lists (user and group security settings) for all the objects you are importing. |
|
Overwrite Remote Servers |
Specifies that existing remote server objects should be overwritten by remote server objects in the migration package. The default is that existing remote servers are not overwritten. |
|
Remember Dependency Settings |
Select this if, on subsequent imports, you want the objects you are now importing to retain the new dependencies that you select in the importing portal. (You select new dependencies on the Unresolved Dependencies page.) |
|
Always Create New Object Instances (Create Duplicates of Existing Objects) |
Select this if you want to create new object instances instead of overwriting objects that may already exist on the importing portal. |
You can select objects to import on the Portal Resources page of the Migration — Import Utility.
To import a migration package, you must have at least Edit access to the objects you want to add to the package.
This page displays the objects contained in the migration package you loaded. All objects will be imported when you click Finish, unless you remove them.
If the Migration — Import Utility is not already open, open it now.
Click the Portal Resources page.
Remove objects you do not want to import by selecting them and clicking the Remove icon.
If there are objects to import from Oracle WebCenter Collaboration, you can choose those objects on the Collaboration Resources page.
If any of the objects you are importing depend on resources that are not included in the package, those missing resources are listed on the Unresolved Dependencies page of the Migration — Import Utility. For example, in your migration package you may have a portlet that depends on a Web service, which is not included in the package. You can resolve those dependencies by pointing to existing objects in your portal.
To create a migration package, you must have at least Edit access to the objects you want to add to the package.
Note:
This page appears only if there is an unresolved dependency.
If the Migration — Import Utility is not already open, open it now.
Click display the Unresolved Dependencies page.
Any missing resources are displayed in the Dependency column. The associated object in the migration package is listed under each missing dependency.
Click the Edit icon beside the dependency.
Select a replacement object from this portal and click OK.
The replacement object is displayed in the Replacement column.
You can import objects from another portal with a migration package.
Copy the migration package to the target portal host computer.
Log in to the host computer for the portal as the user who owns the portal installation.
Use the command ptmigration.bat (for Windows) or ./ptmigration.sh (for UNIX) with the following parameters:
ptmigration.bat [username] [password] -import [migration package name] [log file name] <-noacl> <-overwriteremoteservers> <-createnewobjectinstances>
Where the parameters are as follows:
| Parameter | Description |
|---|---|
|
migration package name |
Required. The name and path of the migration package to be created |
|
log file name |
Required. The name and path of the log file to be created. The path to the log file must be different from that of the migration package. |
|
-noacl |
Optional. Use this parameter if you do not want to import the Access Control Lists (security data) associated with the objects you are importing. |
|
-overwriteremoteservers |
Optional. Specifies that existing remote server objects should be overwritten by remote server objects in the migration package. The default is that existing remote servers are not overwritten. |
|
-createnewobjectinstances |
Optional. Use this parameter if you want to create new object instances instead of overwriting objects that may already exist on the importing portal. |
Press ENTER.
All the objects in the migration package are imported. The imported objects are located in the same folders on the target portal as on the source portal. Objects with missing dependencies will be skipped and not imported. Check the migration log to see which ones were skipped.
You can back up your system without taking it offline.
Back up your database according to your database vendor documentation and best practices.
Create a snapshot of your search collection and back it up to another location or tape backup.
Back up your document repository files and log files to another location or tape backup.
Stop the Web service on all computers hosting the portal application.
Stop the Oracle WCI Automation Service on all computers hosting Automation Services.
Stop the Oracle WCI Search service.
If you must rebuild your portal database, use your database software to restore from a previously saved database.
Replace your search collection with backups as close as possible to the time of the database backup you are using.
Your database backup might not exactly match your search collection backup, so the restored database and search collection will be out of sync. To correct this, rebuild the search collection.
Your search index might get out of sync with your database if, during a crawl, the Search Service became unavailable or a network failure prevented an indexing operation from completing. Another possibility is that a Search Service with empty indexes was swapped into an existing portal with pre-existing documents and folders.
To rebuild the search collection you must have the following rights:
Access Administration activity right
Access Search Results Manager activity right
The Search Service Manager lets you specify when and how often the Search Update Agent repairs your search index. Rather than synchronizing particular objects, the repair synchronizes all objects in the database with the search index. Searchable objects in the database are compared with IDs in the search index. If an object ID in the database is not in the search index, the Search Update Agent attempts to re-index the object; if an ID in the search index is not in the database, the Search Update Agent removes the object from the search index.
Run the Search Update Agent for purposes of background maintenance or complete repopulation of the search index.
Configure the Search Service to repair itself.
Click Administration.
From the Select Utility list, choose Search Service Manager.
Under Search Repair Settings, change Next Repair Date to a time in the past.
Click Administration again.
Wait one minute for the setting to update.
Run one of the Search Update jobs in verbose mode.
Open the Intrinsic Operations folder.
Open one of the Search Update jobs.
The Job Editor opens.
Change the Logging Level to Verbose and click Finish.
Note:
Make note of the logging mode before you change it, so that you can change it back after the repair is complete.
Select the job you just edited and click Run Once.
By running the job this way, you avoid having to go back into the job and revert to the previous schedule settings.
Ensure that the job is running in repair mode.
Open the job you just created; it should be called something like Search Update 1 — Run Once.
The Job Editor opens.
Click the Job History page.
Click the job name.
The job log opens.
Ensure that the job is running in repair mode.
The second line of the job log should be similar to this:
Mar 1, 2008 9:10:02 AM- PTIndexer.ctor : Indexing will extract at most 1000000 encoded bytes of text from each document.
About half-way down the first page of the log you should see a message that should be similar to this:
Mar 1, 2008 9:10:02 AM- Search Update Agent is repairing the directories...
Reinstall the Search Service and select Overwrite the existing search index. For details on installing the Search Service, refer to the Oracle Fusion Middleware Installation Guide for Oracle WebCenter Interaction for Windows or the Oracle Fusion Middleware Installation Guide for Oracle WebCenter Interaction for Unix and Linux.
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
