Professional Documents
Culture Documents
1
Weblogic Cloning:
In Weblogic, we have the pack/unpack utility using which we can migrate the domain configurations.
To extend the domain to multiple machines, we use the pack utility to create an archive of the domain configuration from the source
and then we use the unpack utility to copy the archive on the new machines (the targets).
Now, on Weblogic, if we have multiple domains, then we need to use pack/unpack to copy all these domains individually.
But we still need to install the Weblogic software on these targets, only after which we can use the pack/unpack utilities.
Also, on a new installation of Weblogic, we again need to make sure that the patch levels and other Weblogic configurations on the
targets are matching the source. Weblogic supports a huge stack of products and if there are multiple products installed on the
Weblogic, then we need to make sure that the patches are applied to the product home and Weblogic home on the new targets.
Oracle Weblogic also provides movement scripts using which we can clone the entire environment including the Weblogic binaries
and create an archive. This archive can then be moved to the new machines and we need not worry about matching the new targets
with the source.
Here we are creating an image of the existing MW home and deploying it to many hosts.
This process is in contrast to installing Weblogic and applying patches to Weblogic and product homes on new targets.
We can say that these movement scripts are a super set of the pack/unpack utility.
Java Components: The domain configuration containing the java components like the SOA, IPM, OIM etc.
System Components: The domain configuration containing the components like the Oracle HTTP server, OID etc.
Scenario:
Creating a copy of the Production instance having the Oracle SOA Suite installed and creating a Test instance on a unix system.
Pre-Requisites:
The supporting DB needs to be cloned first on the new hardware.
All required mount points and admin user must be created on the new MT’s with proper read/write permissions.
All the network configurations need to be in place like opening the ports between MT & DB including the Admin/Managed server
ports.
The targets need to have the same operating system as the source.
2
Cloning Steps:
1. Move MW Home and Binary files
Moving the MW Home and Binary Files (Weblogic & SOA Binaries)
2. Execute the “copyBinary” script, which copies the middleware home, the Weblogic home and the Oracle homes within the
middleware home.
To copy the MW home that is located at /scratch/Oracle/Middleware1, execute the following command.
4. From the source, import the “pasteBinary” script and the “cloningclient.jar” file to the target and ensure that they have
execute permission.
ORACLE_COMMON_HOME/bin/pasteBinary.sh
ORACLE_COMMON_HOME/jlib/cloningclient.jar
5. Create an oraInst.loc file specifying the group whose members are given access to write the oraInventory, and where you
want to put the Oracle Inventory.
inst_group=dba
inventory_loc=/<Path>/oraInventory
6. Tar the java home at the source, copy the tar file to the target and untar the java home on the target.
3
The Middleware home is extracted to /scratch/oracle/MW_Home_prod and the WebLogic Server home and all of the
Oracle homes are extracted under it with the same names as that of the source Oracle home names.
ORACLE_HOME/oracleRoot.sh
9. At the target, delete the Node Manager directory and the files in it. The default location of the directory is:
WL_HOME/common/nodemanager
1. At the source, make sure that the AdminServer and the managed servers are Running.
ORACLE_COMMON_HOME/bin/copyConfig.sh
To copy the configuration of the Oracle weblogic component in the Middleware home /scratch/Oracle/Middleware1.
4. At the source, extract the move plan from the archive using the “extractMovePlan” script.
ORACLE_COMMON_HOME/bin/extractMovePlan.sh
For example:
5. Edit the move plan, modifying the properties to reflect the values for the target environment. See Appendix to find the list
of properties for the type of component you are moving.
7. At the source, run the following script to generate obfuscated password files required by the move plan. Run the script for
each password file.
4
ORACLE_COMMON_HOME/bin/obfuscatePassword.sh
The script prompts you to enter the password and the location where the password file is to be written.
8. At the target, extract the files from the archive using the pasteConfig script
ORACLE_COMMON_HOME/bin/pasteConfig.sh
To apply the archive to the Middleware home /scratch/Oracle/Middleware1, use the following command:
9. At the source, copy the Node Manager configuration, by executing the copyConfig script.
ORACLE_COMMON_HOME/bin/copyConfig.sh
11. At the source, extract the move plan from the archive, using the extractMovePlan script.
ORACLE_COMMON_HOME/bin/extractMovePlan.sh
For example:
12. Edit the move plan, modifying the properties to reflect the values for the target environment.
14. At the target, run the following script to generate obfuscated password files required by the move plan. Run the script for
each password file.
ORACLE_COMMON_HOME/bin/obfuscatePassword.sh
The script prompts you to enter the password and the location where the password file is to be written.
15. At the target, extract the files from the archive using the pasteConfig script.
5
The pasteConfig script is located in:
ORACLE_COMMON_HOME/bin/pasteConfig.sh
ORACLE_COMMON_HOME/bin/copyConfig.sh
To copy the Oracle instance located in /scratch/Oracle/Middleware1/ohs1, use the following command:
For Example:
3. At the source, extract the move plan from the archive, using the extractMovePlan script.
ORACLE_COMMON_HOME/bin/extractMovePlan.sh
For example:
4. Edit the move plan, modifying the properties for the particular components to reflect the values for the target environment.
6. At the target, run the following script to generate obfuscated password files required by the move plan. Run the script for
each password file.
ORACLE_COMMON_HOME/bin/obfuscatePassword.sh
The script prompts you to enter the password and the location where the password file is to be written.
6
7. At the target, extract the files from the archive using the pasteConfig script.
ORACLE_COMMON_HOME/bin/pasteConfig.sh
To apply the archive to the Oracle instance ohs1, use the following command:
For Example:
7
Appendix
Common Move Plan Properties for Java Components
8
Move Plan Properties for Oracle HTTP Server
9
Move Plan Properties for Node Manager
Default
10