Deploying Customizations in Oracle E-Business Suite Release
12.2
This article describes how to
deploy customizations in an Oracle E-Business Suite Release 12.2 environment.
A little bit background before we move onto the exact steps
required to move the customization.
An Oracle E-Business Suite
Release 12.2 installation now includes two editions (versions) of the
application code and seed data.
The "Run Edition"
is the code and data used by the running application. As a developer, you will
connect to the Run Edition whenever you are engaged in normal development
activity on the system.
The "Patch Edition"
is an alternate copy of Oracle E-Business Suite code and seed data that is
updated by Online Patching. End users cannot access the Oracle E-Business Suite
Patch Edition, but as a developer you may need to connect to the Patch Edition
of a system when applying patches or debugging problems with Online Patch
execution.
The Oracle E-Business Suite
application-tier files are installed in a base directory of the customer's
choosing. Within that base directory you will now find three important
sub-directories:
fs1 - file system 1 (either run or patch edition)
fs2 - file system 2 (alternate of file system 1)
fs_ne - non-editioned file
system, for data files
The fs1 and fs2 directories
contain the Run Edition and Patch Edition files for Oracle E-Business Suite.
The "run" and "patch" file system designation will switch
back and forth between fs1 and fs2 for each patching cycle.
Connecting to the Run Edition
Oracle E-Business Suite Release
12.2.2 and higher includes a script to set the run or patch edition environment
by edition type. The script is called "EBSapps.env" and is
found in the base directory of an Oracle E-Business Suite application-tier
installation.
Login to Putty:-
1. Connect to the run edition
file system on your development environment. Run EBSapps.env to find the run
instance.
$ source
/u01/R122_EBS/EBSapps.env run
E-Business Suite Environment
Information
----------------------------------------
RUN File System : /u01/R122_EBS/fs2/EBSapps/appl
PATCH File System : /u01/R122_EBS/fs1/EBSapps/appl
Non-Editioned File System :
/u01/R122_EBS/fs_ne
DB Host: slc04axp.us.oracle.com
Service/SID: gbzd122x
Here you can see that FS2 is the RUN instance so we have to move
our Controller/View Object/Any Java/Xml file to FS2.
cd /u01/R122_EBS/fs2/EBSapps/appl
cd
$JAVA_TOP/xx_top/oracle/apps/fnd/framework/webui/
As an instance I am moving
xxEmpCo (Controller) file to above path. Once files is moved you can run JAVAC
to compile the JAVA file.
2. After you copy any custom files
under the $JAVA_TOP directory, run the adcgnjar
utility.
The adcgnjar utility does not
require any parameters on the command line. When prompted, enter the user name
and password of the APPS user.
3.Stop & Start managed
servers using using the command. When prompted enter the weblogic password.
$ $ADMIN_SCRIPTS_HOME
admanagedsrvctl.sh stop oacore_server1
$ $ADMIN_SCRIPTS_HOME
admanagedsrvctl.sh start oacore_server1
Note : If for any reason you have
modified seeded .JSP/XML/JAVA file the we need to run "Generate product
JAR files" from adadmin which will regenerate product jar
files for Oracle applications.
We use the adcgnjar utility for any custom Java or BC4J
code for Oracle Application Framework, Oracle CRM Technology Foundation (JTT),
Oracle Web Applications Desktop Integrator (BNE), custom servlets, or other
custom Java code. This utility generates and signs a file named customall.jar
file containing the custom Java and BC4J code and extensions.
Thanks,
Anil
