Cloning a J2EE and WebCache Install Connected to an Existing Farm (File Based Repository)

Enterprise Manager Cloning allows you to deploy one or more Application Server instances similar in configuration to a source instance.

You can clone a J2EE and WebCache Install connected to an existing farm (File Based Repository) Application Server Home to the following:

• Another J2EE and WebCache setup connected to the same farm (File Based Repository).

• Another J2EE and WebCache setup connected to the same farm (File Based Repository) and to the same cluster the original instance is a part of.

Prerequisites for Cloning

Ensure that the following prerequisites are met before cloning:

• You have setup the Grid Control properly to manage the source and target hosts.

• You have a valid source Oracle home with read / write privileges. Ensure that OH/config/ias.properties file has read privileges.

• If the source instance is a part of a cluster, ensure that you leave the cluster before starting with the clone operation.

• If the cloned instance is required to connect to a cluster, ensure that such a cluster already exists in the farm in which that instance is expected to join.

• You have a Central Agent (10.2 or above) monitoring all the destination hosts.

Cloning to Another J2EE and WebCache Setup Connected to the Same Farm (File Based Repository)

To clone a J2EE and WebCache Install connected to an existing farm (File Based Repository) to another J2EE and WebCache setup connected to the same farm (File Based Repository):

1. Select a J2EE and WebCache Application Server 10.1.2 home from the list of clonable homes and click Next.

2. At the Source Settings page, enter the working directory location, host credentials and the files to be excluded from the Oracle home archive and click Next.

3. The credentials provided are verified and the ias.properties file is read to check the configuration. The AS Product Settings page is rendered accordingly, asking for the new instance name and the old and new ias_admin passwords. Click Next.

4. Provide the destination Oracle home information along with the destination host credentials. Ensure that these credentials are correct as these are not verified here and the job may fail later if these are wrong. Click Next.

5. Specify the pre/post/root scripts or commands to be executed before/after the cloning operation. The same script will be executed parallely on each destination. The user may choose to execute pre/post scripts with sudo privileges, but the host credentials previously specified should have sudo privileges on the destination host for this to succeed. Failure of this step will not affect the overall status of the job. Click Next.

Note: If root.sh is not running through the job, you must run it manually for the cloning operation to complete.

6. Schedule the job immediately or at an appropriate time. You can also change the name of the job, from the default one that uses the time stamp. Click Next.

7. Review your selection and click Finish.

Note: The cloned instance will automatically join back to the same farm as the source after the clone operation.

Cloning to Another J2EE and WebCache Setup Connected to the Same Farm (File Based Repository) and to the same cluster the original instance is a part of

To clone a J2EE and WebCache Install connected to an existing farm (File Based Repository) to another J2EE and WebCache setup connected to the same farm (File Based Repository) and to the same cluster the original instance is a part of:

1. Select a J2EE and WebCache Application Server 10.1.2 home from the list of clonable homes and click Next.

2. At the Source Settings page, enter the working directory location, host credentials and the files to be excluded from the Oracle home archive and click Next.

3. The credentials provided are verified and the ias.properties file is read to check the configuration. The AS Product Settings page is rendered accordingly, asking for the new instance name and the old and new ias_admin passwords. Click Next.

4. Provide the destination Oracle home information along with the destination host credentials. Ensure that these credentials are correct as these are not verified here and the job may fail later if these are wrong. Click Next.

5. Specify the pre/post/root scripts or commands to be executed before/after the cloning operation. The same script will be executed parallely on each destination. The user may choose to execute pre/post scripts with sudo privileges, but the host credentials previously specified should have sudo privileges on the destination host for this to succeed. Failure of this step will not affect the overall status of the job. To add the cloned instance to the OracleAS Cluster, create a post script file with the following content and execute it:
   
   • On UNIX:

     cd $ORACLE_HOME/dcm/bin
./dcmctl joinCluster -cl cluster_name

   • On Windows:

     cd ORACLE_HOME\dcm\bin
dcmctl joinCluster -cl cluster_name

   Click Next.

Note: If root.sh is not running through the job, you must run it manually for the cloning operation to complete.

6. Schedule the job immediately or at an appropriate time. You can also change the name of the job, from the default one that uses the time stamp. Click Next.

7. Review your selection and click Finish.

Note: The cloned instance will automatically join back to the same farm as the source after the clone operation.

Related Topics

Enterprise Manager Information Roadmap

Copyright © 1996, 2007, Oracle. All rights reserved.