Customization overwrite after adop cutover phase in Release 12.2.4
If your customizations like forms/reports deployed on Oracle EBS Release 12.2.4 on run system lost after adop phase=cutover as run and patch file system synch.
Do the following:
Edit: /opt/oracle/TEST/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv file and add below entry within Start and End Customizations.
rsync -zr %s_current_base%/EBSapps/appl/fpms %s_other_base%/EBSapps/appl/fpms
Worked Example
------------------------------
#
# $Header: adop_sync_drv.tmp 120.2.12020000.9 2014/11/03 09:00:11 cgautam ship $
# +============================================================================================+
# | Copyright (c) 2005, 2014 Oracle and/or its affiliates. |
# | All rights reserved. |
# | Version 12.0.0 |
# +============================================================================================+
# | -------------------------------------------------------------------------
# | | IMPORTANT: You may only edit the Customization Section of this file, |
# | | between the "#Begin Customization" and "#End Customization" tags. |
# | -------------------------------------------------------------------------
# |
# | This file is maintained to add/preserve the actions to be done in addition to the process
# | of normal synchronization between RUN and Patch file systems. User would edit this file
# | to add the actions within '#Begin Customization' and '#End Customization' section.
# | The actions would be performed during ADOP synchronization phase.
# |
# | The custom sync up driver file named adop_sync.drv and would be present in the
# | %s_ne_base%/EBSapps/appl/ad/custom directory. Users are recommended to edit
# | only this adop_sync.drv file for such customization/synchronization.
# |
# | A template file for the same would be present under %s_adtop%/admin/template/adop_sync.tmp.
# | The template can be patched.
# | The ADOPCustomSyncUP API would check the version of this template and compare with
# | adop_sync.drv file.
# | into template within '#Begin Customization' and '#End Customization'.
# |
# | If template version and adop_sync.drv version are same then adop_sync.drv would be read and
# | the actions would be performed/executed.
# |
# |
# | Customers are allowed to use context variables while defining the actions. The syntax to define
# | Context variable in action is %s_sample_var%.
# | ADOPCustomSyncUp API would take care of instantiating these context variables while executing the actions.
# |
# | If passwords need to be piped-in to the scripts then those need to be mentioned as shown in
# | Scripts section in the sample mentioned below.
# | All stdin agruments need to be specified as STDIN_ARGS={%s_appsPass%, %s_wlsPass%}, and this
# | need to delimited by '|' after action like below:
# | command|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
# |
# | ----------------------------------------------------------------------------
# | Custom synchronization which is called during PREPARE phase of ADOP will use
# | values from RUN context file.
# | All the custom commands used in this driver should have PATHs relative to
# | s_current_base and s_other_base ONLY.
# | -----------------------------------------------------------------------------
# |
# +============================================================================================+
#Begin Customization
#Copy Starts
#Sample copy action. This copy could be anything like simple file copy from user home.
#
#For Unix Platform
#rsync -zr /d01/oracle/TEST/fs1/EBSapps/appl/some_dir /d01/oracle/TEST/fs2/EBSapps/appl/some_dir
rsync -zr %s_current_base%/EBSapps/appl/fpms %s_other_base%/EBSapps/appl/
rsync -zr %s_current_base%/EBSapps/appl/ggl %s_other_base%/EBSapps/appl/
#For Windows Platform
#xcopy /dieqy /d01/oracle/TEST/fs1\EBSapps\appl\some_dir /d01/oracle/TEST/fs2\EBSapps\appl\some_dir
#Copy Ends
#JSP Start
#Sample syntax to compile custom JSP using ojspCompile.pl
#For Unix Platforms
#perl /d01/oracle/TEST/fs2/EBSapps/appl/fnd/12.0.0/patch/115/bin/ojspCompile.pl --compile -s "a.jsp, b.jsp" --flush
#perl /d01/oracle/TEST/fs2/EBSapps/appl/fnd/12.0.0/patch/115/bin/ojspCompile.pl --compile -s "diff.jsp" --flush
#For Windows Platform
#perl /d01/oracle/TEST/fs2\EBSapps\appl\fnd\2.0.0\patch\115\bin\ojspCompile.pl --compile -s "a.jsp, b.jsp" --flush
#perl /d01/oracle/TEST/fs2\EBSapps\appl\fnd\2.0.0\patch\115\bin\ojspCompile.pl --compile -s "diff.jsp" --flush
#JSP End
#Scripts Start
#Sample syntax for custom scripts.
#The scripts could be a shell OR CMD or perl OR WLST script
#For Unix Platforms
#sh /d01/oracle/TEST/fs2/EBSapps/appl/ad/12.0.0/bin/custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#sh /d01/oracle/TEST/fs2/FMW_Home/wlserver_10.3/common/bin/wlst.sh custom.py -appspwd %s_appsPass%
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\appl\ad\12.0.0\bin\custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#sh /d01/oracle/TEST/fs2/EBSapps/appl/ad/12.0.0/bin/custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#sh /d01/oracle/TEST/fs2/FMW_Home/wlserver_10.3/common/bin/wlst.sh custom.py -appspwd %s_appsPass%
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\appl\ad\12.0.0\bin\custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#/d01/oracle/TEST/fs2\FMW_Home\wlserver_10.3\common\bin\wlst.cmd custom.py -appspwd %s_appsPass%
#Scripts End
#SQL Starts
#Sample SQL script
#For Unix Platforms
#/d01/oracle/TEST/fs2/EBSapps/10.1.2/bin/sqlplus APPS/%s_appsPass% @test.sql
#/d01/oracle/TEST/fs2/EBSapps/10.1.2/bin/sqlplus /nolog @/d01/oracle/TEST/fs2/EBSapps/test.sql|STDIN_ARGS={APPS, %s_appsPass%, TWO_TASK}
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\10.1.2\bin\sqlplus APPS/%s_appsPass% @test.sql
#SQL ends
#Forms Start
#Sample to compile custom forms.
#Copy the generated fmx into <FORMS_PATH>
#For Unix Platforms
#/d01/oracle/TEST/fs2/EBSapps/10.1.2/bin/frmcmp <some Location>/custom.fmb APPS/%s_appsPass%
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\10.1.2\bin\frmcmp <some Location>/custom.fmb APPS/%s_appsPass%
#Froms End
#End Customization
104,1 Bot
If your customizations like forms/reports deployed on Oracle EBS Release 12.2.4 on run system lost after adop phase=cutover as run and patch file system synch.
Do the following:
Edit: /opt/oracle/TEST/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv file and add below entry within Start and End Customizations.
rsync -zr %s_current_base%/EBSapps/appl/fpms %s_other_base%/EBSapps/appl/fpms
Worked Example
------------------------------
#
# $Header: adop_sync_drv.tmp 120.2.12020000.9 2014/11/03 09:00:11 cgautam ship $
# +============================================================================================+
# | Copyright (c) 2005, 2014 Oracle and/or its affiliates. |
# | All rights reserved. |
# | Version 12.0.0 |
# +============================================================================================+
# | -------------------------------------------------------------------------
# | | IMPORTANT: You may only edit the Customization Section of this file, |
# | | between the "#Begin Customization" and "#End Customization" tags. |
# | -------------------------------------------------------------------------
# |
# | This file is maintained to add/preserve the actions to be done in addition to the process
# | of normal synchronization between RUN and Patch file systems. User would edit this file
# | to add the actions within '#Begin Customization' and '#End Customization' section.
# | The actions would be performed during ADOP synchronization phase.
# |
# | The custom sync up driver file named adop_sync.drv and would be present in the
# | %s_ne_base%/EBSapps/appl/ad/custom directory. Users are recommended to edit
# | only this adop_sync.drv file for such customization/synchronization.
# |
# | A template file for the same would be present under %s_adtop%/admin/template/adop_sync.tmp.
# | The template can be patched.
# | The ADOPCustomSyncUP API would check the version of this template and compare with
# | adop_sync.drv file.
# | into template within '#Begin Customization' and '#End Customization'.
# |
# | If template version and adop_sync.drv version are same then adop_sync.drv would be read and
# | the actions would be performed/executed.
# |
# |
# | Customers are allowed to use context variables while defining the actions. The syntax to define
# | Context variable in action is %s_sample_var%.
# | ADOPCustomSyncUp API would take care of instantiating these context variables while executing the actions.
# |
# | If passwords need to be piped-in to the scripts then those need to be mentioned as shown in
# | Scripts section in the sample mentioned below.
# | All stdin agruments need to be specified as STDIN_ARGS={%s_appsPass%, %s_wlsPass%}, and this
# | need to delimited by '|' after action like below:
# | command|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
# |
# | ----------------------------------------------------------------------------
# | Custom synchronization which is called during PREPARE phase of ADOP will use
# | values from RUN context file.
# | All the custom commands used in this driver should have PATHs relative to
# | s_current_base and s_other_base ONLY.
# | -----------------------------------------------------------------------------
# |
# +============================================================================================+
#Begin Customization
#Copy Starts
#Sample copy action. This copy could be anything like simple file copy from user home.
#
#For Unix Platform
#rsync -zr /d01/oracle/TEST/fs1/EBSapps/appl/some_dir /d01/oracle/TEST/fs2/EBSapps/appl/some_dir
rsync -zr %s_current_base%/EBSapps/appl/fpms %s_other_base%/EBSapps/appl/
rsync -zr %s_current_base%/EBSapps/appl/ggl %s_other_base%/EBSapps/appl/
#For Windows Platform
#xcopy /dieqy /d01/oracle/TEST/fs1\EBSapps\appl\some_dir /d01/oracle/TEST/fs2\EBSapps\appl\some_dir
#Copy Ends
#JSP Start
#Sample syntax to compile custom JSP using ojspCompile.pl
#For Unix Platforms
#perl /d01/oracle/TEST/fs2/EBSapps/appl/fnd/12.0.0/patch/115/bin/ojspCompile.pl --compile -s "a.jsp, b.jsp" --flush
#perl /d01/oracle/TEST/fs2/EBSapps/appl/fnd/12.0.0/patch/115/bin/ojspCompile.pl --compile -s "diff.jsp" --flush
#For Windows Platform
#perl /d01/oracle/TEST/fs2\EBSapps\appl\fnd\2.0.0\patch\115\bin\ojspCompile.pl --compile -s "a.jsp, b.jsp" --flush
#perl /d01/oracle/TEST/fs2\EBSapps\appl\fnd\2.0.0\patch\115\bin\ojspCompile.pl --compile -s "diff.jsp" --flush
#JSP End
#Scripts Start
#Sample syntax for custom scripts.
#The scripts could be a shell OR CMD or perl OR WLST script
#For Unix Platforms
#sh /d01/oracle/TEST/fs2/EBSapps/appl/ad/12.0.0/bin/custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#sh /d01/oracle/TEST/fs2/FMW_Home/wlserver_10.3/common/bin/wlst.sh custom.py -appspwd %s_appsPass%
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\appl\ad\12.0.0\bin\custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#sh /d01/oracle/TEST/fs2/EBSapps/appl/ad/12.0.0/bin/custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#sh /d01/oracle/TEST/fs2/FMW_Home/wlserver_10.3/common/bin/wlst.sh custom.py -appspwd %s_appsPass%
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\appl\ad\12.0.0\bin\custom.pl -contextfile=<CONTEXT_FILE_PATH>|STDIN_ARGS={%s_appsPass%, %s_wlsPass%}
#/d01/oracle/TEST/fs2\FMW_Home\wlserver_10.3\common\bin\wlst.cmd custom.py -appspwd %s_appsPass%
#Scripts End
#SQL Starts
#Sample SQL script
#For Unix Platforms
#/d01/oracle/TEST/fs2/EBSapps/10.1.2/bin/sqlplus APPS/%s_appsPass% @test.sql
#/d01/oracle/TEST/fs2/EBSapps/10.1.2/bin/sqlplus /nolog @/d01/oracle/TEST/fs2/EBSapps/test.sql|STDIN_ARGS={APPS, %s_appsPass%, TWO_TASK}
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\10.1.2\bin\sqlplus APPS/%s_appsPass% @test.sql
#SQL ends
#Forms Start
#Sample to compile custom forms.
#Copy the generated fmx into <FORMS_PATH>
#For Unix Platforms
#/d01/oracle/TEST/fs2/EBSapps/10.1.2/bin/frmcmp <some Location>/custom.fmb APPS/%s_appsPass%
#For Windows Platform
#/d01/oracle/TEST/fs2\EBSapps\10.1.2\bin\frmcmp <some Location>/custom.fmb APPS/%s_appsPass%
#Froms End
#End Customization
104,1 Bot
Thank you for giving valuable info
ReplyDelete