Select the host name by clicking the 
icon and enter the home location, user name, password, working directory, and the files to be excluded and click Next.
You can clone a packaged J2EE and WebCache (standalone) Install Application Server Home to the following:
Another J2EE and WebCache (standalone) setup.
Another J2EE and WebCache (standalone) setup connected to an existing farm (File Based Repository).
Another J2EE and WebCache (standalone) setup connected to an existing farm (File Based Repository) and to an existing cluster.
For more information on Software Libraries refer to Configuring the Software Library
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 $ORACLE_HOME/config/ias.properties file has read privileges.
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.
To create a new Software Library Component:
From the Enterprise Manager Home page, click Deployments and then Provisoning sub-tab.
In the Provisioning : Components page, click Create Component.
The Create Component : Describe page appears.
Select Oracle iAS Clone option from the drop-down list and click Next.
The Create Component : Configure page appears.
Select the host name by clicking the
The Create Component : Review Page appears.
Review your selection and click Finish.
To clone a packaged J2EE and WebCache Install Application Server home to another J2EE and WebCache (standalone) setup:
Select a packaged Application Server 10.1.2 J2EE and WebCache (standalone) from the list of clonable homes and click Next.
The Product Settings page is rendered accordingly, asking for the new instance name and the old and new ias_admin passwords. Click Next.
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.
Note: If root.sh is not running through the job, you must run it manually for the cloning operation to complete.
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.
To clone a packaged J2EE and WebCache Install Application Server home to another J2EE and WebCache (standalone) setup connected to an existing File Based Repository farm:
Select a packaged Application Server 10.1.2 J2EE and WebCache (standalone) from the list of clonable homes and click Next.
The Product Settings page is rendered accordingly, asking for the new instance name and the old and new ias_admin passwords. Click Next.
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.
Note: If root.sh is not run through the job, you must run it manually for the cloning operation to complete.
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.
Note: The cloned instance will automatically join back to the same farm as the source after the clone operation.
To clone a packaged J2EE and WebCache Install Application Server home to another J2EE and WebCache (standalone) setup connected to an existing File Based Repository farm and to an existing cluster:
Select a packaged Application Server 10.1.2 J2EE and WebCache (standalone) from the list of clonable homes and click Next.
The Product Settings page is rendered accordingly, asking for the new instance name and the old and new ias_admin passwords. Check Join, and specify the cluster name to which the new instance should join and click Next.
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.
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. You 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.shis not run through the job, you must run it manually for the cloning operation to complete.
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.
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.