WebCenter Portal Domain Still Points To Old Domain After Cloning (Doc ID 2775474.1)

Last updated on JUNE 07, 2024

Applies to:

Symptoms

ACTUAL BEHAVIOR

After cloning a 12.2.1.3 domain and then upgrading to 12.2.1.4, some paths in the new domain have the following issues:

• Some libraries are pointing to the applications folder rather than the fmw home.
   
• Some paths in the domain-info or domain config files are pointing to the 12.2.1.3 fmw home or domain home.
   

EXPECTED BEHAVIOR

Expect all path references in the new domain point to the proper location in the 12.2.1.4 Fusion Middleware home or applications path.

STEPS

The issue can be reproduced at will with the following steps:

1. Clone a 12.2.1.3 domain as follows:
    
   
   • Create a wls domain template from the original domain using config_builder.
      
   • Create new schemas in the target database using RCU.
      
   • Install the FMW and WebCenter Portal binaries in a new server.
      
   • In the new server create a new domain based on the wls domain template from the source instance.
     When creating the new domain provide the connection details to the new schemas.
      
   • Export/import the original domain schemas (with exception of the STB schema to the cloned domain).
      
   • Update the new domain jps-config.xml and jps-config-jse.xml files with the connection information for the new database.
      
   • Run modifyBootStrapCredential wlst command to update bootstrap credential to the new opss shema.
      
   • If having a HA setup then run Pack and Unpack to Extend the Domain to other Nodes.
     
     
2. Review the new domain config.xml file.
   Here you will notice some library paths still point to the original FMW Home and applications home or domain.

Cause

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