Skip Headers
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Interaction
10g Release 4 (10.3.3.0.0)

Part Number E26810-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Migration and Staging

This chapter summarizes migration capabilities for Oracle WebCenter deployments. The purpose of this chapter is to assist in planning development, QA, and production environments. By utilizing its migration capabilities you can stage the Oracle WebCenter deployment in a testing environment where you can test quality and gain acceptance prior to pushing it to production.

The following table summarizes migration capabilities.

Component Migration Guidelines

Portal and Image Service

Follow the guidelines in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.

Search

Search should not be migrated. The Search Update Agent job indexes new portal objects and documents.

Identity Services, Content Services, and Portlet Suites

Do not migrate these services. Import the original product .pte package and complete configuration as described in the installation guide for the specific product.

Oracle-BEA AquaLogic Interaction Publisher

Follow the guidelines in the Administrator Guide for AquaLogic Interaction Publisher.

Oracle WebCenter Collaboration

Follow the guidelines in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration.

Oracle-BEA AquaLogic Interaction Studio

Follow the guidelines in the Administrator Guide for AquaLogic Interaction Studio.

Notes:

  • Migration is only relevant when the source and destination portals have distinct Oracle-BEA AquaLogic Interaction Studio installations.

  • Portlets must be created with a compatible version of Oracle-BEA AquaLogic Interaction Studio.

  • Do not include dependencies when creating the migration package.

  • Data in the source Oracle-BEA AquaLogic Interaction Studio portlet database is not migrated. Use the Oracle-BEA AquaLogic Interaction Studio data export/import functionality to move data.

  • If multiple Oracle-BEA AquaLogic Interaction Studio portlets share and underlying database, migrate these portlets in batch. This maintains the relationship between the portlets and their shared database.

Oracle WebCenter Analytics

Do not migrate Oracle WebCenter Analytics. Install and configure Oracle WebCenter Analytics in the production environment.