This topic covers following points as per certification track explained under A, B, C… iii) Similarly in Portal and Wireless only middle tier can be cloned (You can’t clone infrastructure tier) both source and target instances share same infrastructure database (as described in fig)<\/p>\n iv) During cloning source ORACLE_HOME is copied to destination ORACLE_HOME , then a set of scripts is used to update information in key configuration files of oracle application server middle tier (like hostname).<\/p>\n Key points in OAS cloning ?<\/strong> B) Customize the cloning process <\/strong> i) Customizing ports during cloning<\/strong> When you update this line in cs.properties while cloning , OUI will pick staticportlist.ini file and assign ports based on above file to target instance.<\/p>\n ii) Updating custom data<\/strong> C) Use cloning to expand an OracleAS Cluster <\/strong> Few points related to using cloning to expand OracleAS Cluster D) Move J2EE applications from a test middle tier to a new production environment. <\/strong> i) You already have J2EE and Webcache type test & production inastance–> Use “dcmctl redeployApplication” or iAS console “Deploy EAR File” method. E) Move OracleAS Portal metadata from test to production <\/strong>
\nA) Clone Oracle Application Server installations
\n=========================================<\/strong>
\ni) Cloning is process of creating replica of existing installation to differnt location while preserving its configurations.
\nii) You can create a clone using command line cloning scripts or OEM 10g Grid control<\/p>\n
\n![](\"http:\/\/bp2.blogger.com\/_LrtEX0cTLgI\/RlHxwP9zeNI\/AAAAAAAAAjA\/S4p5hhgON1c\/s1600-h\/clone_2.jpg\")
<\/a>
\nYou can clone J2EE and Web Cache middle tier which is not connected to Infrastructure,<\/p>\n<\/a><\/p>\n
\n—————————————
\n–You can clone middle tier installation of (J2EE & Webcache, Portal & Wireless and BI & Forms)
\n–You CANNOT<\/strong> clone
\n—–i)Infrastructure Tier (MR & IM)
\n—–ii)OAS Integration, BPEL Process Anaytics or BPEL process manager
\n—–iii) Developer kit and SDK
\n—–iv) Installation that includes workflow
\n–Cloned instance must have different name than source instance.
\n— You can clone MT (Middle Tier) that is member of OracleAS Cluster or Farm but you must remove instance<\/strong> from OracleAS Cluster and Farm before beginning cloning operation.
\n— Cloning process does not configure Load Balancer Router, If you use one, you have to configure it manually including invalidation port
\n— If in source webcache instance is member of cache cluster, then target webcahe should be manually added in to cache cluster (or delete other cache cluster member info manually if you don’t wish to target cloned instance as cache cluster)
\n— If source webcache instance is configured to forward requests to more than one origin server on same host as source web cache instance, then cloning will fail.
\nCloning Process in Oracle Application Server<\/strong>
\n———————————————————-
\ni) On source instance run prepare_colne.pl<\/strong> (in $OH\/clone\/bin) (parses files, create archives using DCM, backs up required files, and run wireless clone assistant if wireless is enabled)
\nii) Copy ORACLE_HOME to destination location
\niii) ON target instance run clone.pl<\/strong> (invokes OUI which repeats all actions done during source instance installation time)
\niv) post clone phase , clone.pl also does following post clone steps<\/strong> to make target cloned instance to a working state. These are
\n—-a) setting new ORACLE_HOME in DCM
\n—-b) update configuration file
\n—-c) calls chgiphost command to change hostname and IP address in cloned instance
\n—-d) If source instance was connected to OID (Portal\/BI) then add information about clone in OID
\n—-e) After cloning start services on target instance on unix you have to run root.sh after cloning (from root)<\/p>\n
\n=============================<\/strong>
\nYou can customize various aspects of cloning like specify custom port during cloning or preserve custom settings<\/p>\n
\nAs mentioned above, cloning oracle application server in turn calls Oracle Universal Installer (OUI), Though you don’t see OUI calls; still OUI calls can be customized by configuration file cs.properties<\/strong> in $ORACLE_HOME\/clone\/ias\/config
\nFor example – To configure custom ports (to target instance) during cloning
\nclone_command_line = oracle.iappserver.iapptop:szl_PortListSelect=”{\\”YES\\”,<\/strong>
\n\\”\/location_of_port_list\/portlist.ini\\”}” <\/strong><\/p>\n
\nYou can update custom data (custom files) that is not updated by default during cloning.
\nYou can change\/customize following data in target cloned instance
\n—Change hostname in a file<\/strong><\/em> -> Add full path name of file in which hostname needs to be cahnged to
\n$ORACLE_HOME\/chgip\/config\/hostname.lst
\n—Update occurance of ORACLE_HOME in a file<\/em><\/strong> from old value to new OH value -> Use replace tag in fixup_script.xml.tmpl under
\n$ORACLE_HOME\/clone\/ias\/config
\n—Extract value from file1 and use it to replace value<\/em><\/strong> in file2 -> Use alter tag in fixup_script.xml.tmpl under
\n$ORACLE_HOME\/clone\/ias\/config<\/p>\n
\n==================================
\n<\/strong>The most common example of cloning Oracle Application Server is expanding a Oracle AS cluster. For example you have a cluster of J2EE and Webcache Middle tier with identical configuration and wish to add another J2EE and webcache node with identical configuration and deployemt. Assume source Oracle Application Server is connected to file based repository and member of farm and OracleAS Cluster following are cloning steps to expand this OracleAS Cluster
\ni) Remove Source isnatnce from Farm and Cluster (Use dcmctl or iasConsole); dcmctl leaveFarm and dcmctl leaveCluster
\nii) Run preclone on source Instance (“perl prepare_clone.pl”)
\niii) Copy oracle_home and associated files from source to target instance
\niv) Run clone on target instance “perl clone.pl”
\nv) Add source isntance to Farm & Cluster (“dcmctl joinFarm” & “dcmctl joinCluster”)
\nvi) Add target instance to Farm & Cluster using same command mentioned above<\/p>\n
\n–Cloning Oracle AS Clusters, If source cloned instance is member of Cluster\/Farm as mentioned in past remove it from cluster add it back to cluster after cloning.
\n–If source instance (clustered) is connected to file based repository in separate instance (it is not host of file based repository), cloned instance will be member of same farm as source instance
\n–If source instance (clustered) is connected to file based repository in same instance (it is host of file based repository), cloned instance will be host of new file based repository.<\/p>\n
\n==========================================
\nTheir are various ways\/options (depending on your requirement)
\nin which you can move J2EE application from Test to Production Instance<\/p>\n
\nii) You already have J2EE and Webcache (without IM) Test Instance but no prod instance –> Use middle tier clone method (mentioned in previous post) or Install J2EE and Webcache type middle tier on production and deploy J2EE application (using dcmctl or iASConsole)
\niii) You already have J2EE and WebCache (with IM & MR) Test Instance but no prod instance –> Install Infrasturure tier on prod instance, install J2EE and Webcache type middle tier and deploy J2EE application by method mentioned above in point ii)<\/p>\n
\n==========================================<\/strong><\/p>\n