OAF deployment steps used for 12.2 upgrade from 12.1.3

OAF deployment steps used for our upgrade.

Deploying custom OAF pages for upgrade 12.2.

If you want to carry out the changes on the current run mode, then you have to carry forward steps 7,8,9,13 & 14.

If you want to deploy the changes on the patch mode and do  a cutover, you have to follow steps 1,7,8,9,13,14,16 & 17

1. adop phase=prepare
2. run adsplice for xxcust schema
3. copy the folder structure of R12.1.3 $XXCUST_TOP into R12.2.5 $XXCUST_TOP
4. run adsplice for xxcnvr schema
5. copy the folder structure of R12.1.3 $XXCNVR_TOP into R12.2.5 $XXCNVR_TOP
6. copy the folder $JAVA_TOP/xxcust from R12.1.3 into $JAVA_TOP of R12.2.5
7. Create a zip file custom.zip as follows
a. zip –r custom.zip $JAVA_TOP/xxcust
8. Run the adcgnjar utility. The utility creates the jar files and signs it appropriately or execute below statement
a. adjava oracle.apps.ad.jri.adjmx -areas $JAVA_TOP/custom.zip -outputFile $JAVA_TOP/customall.jar -jar $CONTEXT_NAME 1 CUST jarsigner
9. delete the custom.zip file
a. rm $JAVA_TOP/custom.zip
10. create a directory custom under $FND_TOP/admin/template
a. mkdir $FND_TOP/admin/template/custom
11. copy the ebsProductManifest_xml.tmp from $FND_TOP/admin/template to $FND_TOP/admin/template/custom
a. cp $FND_TOP/admin/template/ebsProductManifest_xml.tmp $FND_TOP/admin/template/custom/ebsProductManifest_xml.tmp
12. Update both the files and add customall.jar entry into the file ebsProductManifest_xml.tmp available at $FND_TOP/admin/template & $FND_TOP/admin/template/custom
a. <library>customprod.jar</library> -- this entry has to be added
13. Run Autoconfig
14. Bounce the middle tier
15. Update the $APPL_TOP_NE/ad/custom/adop_sync.drv file for synchronization with the below entries
a. cp %s_current_base%/EBSapps/comn/java/classes/customall.jar %s_other_base%/EBSapps/comn/java/classes
16. adop finalize
17. adop cutover