My Oracle Support Banner

Using T2P copyConfig for Webcenter Content (Doc ID 1578881.1)

Last updated on OCTOBER 04, 2018

Applies to:

Oracle WebCenter Content - Version 11.1.1.6.0 to 12.2.1.2.0 [Release 11g to 12c]
Information in this document applies to any platform.

Goal

This is not a step by step guide to cloning a Webcenter Content (WCC) domain from one environment to another. For a general step by step guide, see Note 1451025.1

The documentation for cloning Webcenter Content are covered in Note 1507480.1

This KM contains some information when using the copyConfig to clone a WCC.

Note: The below is only supported for Webcenter Content 11g, 12.2.1.0.0, 12.2.1.1.0 and 12.2.1.2.0. It is no longer supported in Webcenter Content 12.2.1.3.0 and above. See Note 2196564.1

 

 

Solution

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
Goal
Solution
 1. The source WCC domain cannot be in Edit mode
 2. All Managed Servers must be running
 3. Doing copyConfig when Unix machines are configured
 4. If the vault and weblayout directories are under the WCC managed server directory, the physical content will be included in the jar file
 5. If the vault and weblayout directories are not under the WCC managed server directory, the physical content will not be included in the jar file
 6. If the WCC is clustered the physical content will not get included in the jar file
 7. If the Admin server and the WCC managed server are on different servers
 8. copyConfig.sh script fail with this error:   GC overhead limit exceeded
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.