Tutorial: Migrating Oracle WebCenter Portal with WebCenter Content from On-Premises Install to Oracle Cloud Infrastructure (Lift and Shift to OCI)
(Doc ID 2907549.1)
Last updated on MAY 31, 2023
Applies to:
Oracle WebCenter Portal - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Purpose
This document will show how to do Lift and Shift to migrate an Oracle WebCenter Portal (WCP) and WebCenter Content (WCC) installation from an On-Premises install to Oracle Cloud Infrastructure (OCI).
This exercise can be used as a proof of concept to migrate an On-Premise install to the Cloud.
Scope
This document was tested with the following configuration:
- WebCenter Portal (WCP) and WebCenter Content (WCC) version 12.2.1.4.
- WebCenter Content including Content Server, Inbound Refinery and the WebCenter Content ADF UI.
- Both WebCenter Portal and WebCenter Content were installed in the same ORACLE_HOME and domain.
- This document assumes that the external LDAP has already been installed or migrated to the Cloud.
e.g. Oracle Internet Directory (OID), Oracle Unified Directory (OUD), etc.
- This document will not cover the reconfiguration for Single Sign On solutions such as Oracle Access Manger (OAM), Security Assertion Markup Language (SAML) or Kerberos.
You should still be able to migrate the WebCenter Portal and Content.
- This was a simple setup (not High Availability (HA)).
Similar approach can be used to migrate an HA setup.
- This migration was tested on Oracle Linux.
Similar steps could be performed to migrate on other operating systems like Windows.
- In this document the migration from On-Premises to OCI shows how to use a different Middleware Home and Domain Home after the migration.
For an easier transition, the same Middleware Home and Domain Homes could be used.
- In this migration, the On-Premises instance version was 12c.
The Cloud Database version was 19c.
The migration of schemas was done using expdp and impdp which allows migration between different versions of the database.
NOTE:
Support for the different products used in this tutorial is provided by different teams. If assistance is needed, contact Oracle Support and ensure to open a Service Request for the related product.
Support for the different products used in this tutorial is provided by different teams. If assistance is needed, contact Oracle Support and ensure to open a Service Request for the related product.
- The Repository Configuration Utility (RCU) is supported by the Fusion Middleware/WebLogic Server team.
- Export/Import from and to the database is supported by the Database team
- Installation and Configuration of WebCenter Portal is supported by the WebCenter Portal team.
- Installation and Configuration of Oracle WebCenter Content is supported by the WebCenter Content Team.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| 1. Introduction to the Migration Process |
| 2. Assumptions for the On-Premises Fusion Middleware Home, Domain Home and Schema Prefix |
| 3. Prerequisites |
| 3.1. Prepare the On-Premises instance |
| 3.2. Prepare the Cloud Instance |
| 4. Backing Up the On-Premises Instance |
| 4.1. Backup the Database Schemas |
| 4.1.1. Create a Directory to Hold the Database Exported Data |
| 4.1.2. Identify the Schemas to be Exported |
| 4.1.3. Export the Schemas |
| 4.1.4. Create a Compressed File with the Files from the Exported Schemas |
| 4.2. Backup the Domain |
| 4.2.1. Shutdown the Domain to Perform Backup Actions that Require the Domain to be Down |
| 4.2.2. Create a Directory to Hold the Exported Domain Data |
| 4.2.3. Set Environment Variables for the Fusion Middleware Home and Domain |
| 4.2.4. Backup the WebCenter Content files |
| 4.2.5. Prepare Files For Exporting the Policy Store and Credential Store |
| 4.2.6. Export the Policy Store |
| 4.2.7. Export the Credential Store |
| 4.2.8. Create a Domain Template |
| 4.2.9. Start the Domain to Perform Backup Actions that Require the Domain to be Up |
| 4.2.10. Export the WebCenter Portlet Metadata |
| 4.2.11. Export the Audit Policies and Audit Repository Configuration |
| 4.2.12. Create a Compressed File with the Files from the Domain Backup |
| 4.3. Export the Users and Groups from the External LDAP Associated to the Domain |
| 4.4. Export Custom Users and Groups from the Embeded LDAP (Only if Required) |
| 5. Restoring the On-Premises Instance to the Oracle Cloud (OCI) |
| 5.1. Check connection to the database as sysdba |
| 5.2. Create Directories to Hold the Exported Database Schemas and Domain Data |
| 5.2.1. Create a Directory in the Database Cloud Instance to Hold the Database Exported Data |
| 5.2.2. Create a Directory in the WebCenter Portal and Content Cloud Instance to Hold the Domain Exported Data |
| 5.3. Import the Custom Database Schemas |
| 5.4. Import the Users and Groups from the External LDAP to the New External LDAP in the Cloud |
| 5.5. Create and Configure the Domain for WebCenter Portal and WebCenter Content |
| 5.5.1. Create new Database Schemas for WebCenter Portal and WebCenter Content in the Cloud Database using the Repository Configuration Assistance |
| 5.5.2. Configure the Domain for WebCenter Portal |
| 5.5.3. Set Environment Variables for the Fusion Middleware Home and Domain |
| 5.5.4. Update the jps-config.xml and jps-config-jse.xml Files with the New Hostname. |
| 5.5.5. Import the Domain Database Schemas |
| 5.5.6. Prepare Files For Importing the Credential Store and the Policy Store |
| 5.5.7. Update the Bootstrap Credential in the jps-config.xml File |
| 5.5.8. Import the Credential Store |
| 5.5.9. Import the Policy Store |
| 5.6. Complete the Content Server Migration |
| 5.6.1. Start the Domain (AdminServer and Content Managed Servers) |
| 5.6.2. Shutdown the domain |
| 5.6.3. Restore the content server files |
| 5.6.4. Fix the Middleware Home Path in Content Files (Only if the Middleware Home Path Changed) |
| 5.6.5. Fix the Java Home Path in Content Files (Only if the Java Home Path Changed) |
| 5.6.6. Fix the Domain Path in Content Files (Only if the Domain Home Path Changed) |
| 5.6.7. Fix JDBC Connections in Content Files (Only if you have JDBC Connections Configured) |
| 5.6.8. Fix the Hostname in Content Files |
| 5.6.9. Start the Domain (AdminServer and Content Managed Servers) |
| 5.6.10. Test Content Server and Inbound Refinery |
| 5.7. Complete the WebCenter Content ADF UI Migration. |
| 5.7.1. Start the WCCADF_server1 Managed Server |
| 5.7.2. Update the WebCenter Content ADF UI Connections to Use the FQDN from the WebCenter Portal and Content Compute Instance |
| 5.7.3. Test the WebCenter Content ADF UI |
| 5.8. Complete the Portlet Migration |
| 5.8.1. Start the WC_Portlet and WC_Portal Managed Servers |
| 5.8.2. Import the WebCenter Portlet Metadata |
| 5.8.3. Test the Portlet Producers |
| 5.9. Complete the WebCenter Portal Migration |
| 5.9.1. Import the Audit Policies and Audit Repository Configuration |
| 5.9.2. Update the WebCenter Portal Connections to Use the FQDN from the WebCenter Portal and Content Compute Instance |
| 5.9.3. Reconcile the References to the Content Server Connection After the Changes |
| 5.10. Import Custom Users and Groups from the Embedded LDAP to the New Domain (Only if Required) |
| 5.11. Reconfigure Elasticsearch |
| 5.11.1. Delete the Elasticsearch Connection. |
| 5.11.2. Install Elasticsearch |
| 5.12. Test WebCenter Portal |
| A. Appendix |
| A.1. Start the Domain |
| A.1.1. Start the Node Manager |
| A.1.2. Start the Administration Server |
| A.1.3. Start the WebCenter Portal Managed Servers |
| A.2. Stop the Domain |
| References |