Detailed steps are given below:

A) Create a temporary custom.zip file which contains all the custom application'
s directories/files at non-standard location. Please follow the following steps:
1) cd $JAVA_TOP
2) zip -r customprod.zip. Where the list of all directory paths are present,
relative to $JAVA_TOP, for custom application's java files at non-standard loca
tion.
3) Generate & sign customprod.jar file.

Command: adjava oracle.apps.ad.jri.adjmx -areas $JAVA_TOP/customprod.zip -output

File $JAVA_TOP/customprod.jar -jar $CONTEXT_NAME 1 CUST jarsigner -storePass -ke
yPass

NOTE: The <KeyStore Password> and <Key Password> are the passwords used to extra
ct the key from key store which is located at $APPL_TOP_NE/ad/admin/adkeystore.d
at. This key is used tosign the Jar files.
When these two parameters are not supplied to adjmx tool, default pas
swords will be used for extracting the key. So unless and otherwise one change t
he default passwords, there is no need to supply these passwords to adjmx tool.
And, one can change the keystore password and key password via adjkey
tool. Please refer to the bottom section of the note for the same.
4) Delete temporary customprod.zip.
Command: rm $JAVA_TOP/customprod.zip
5) Follow below steps to make the custom jar available for WebLogic
a) Take a back-up of existing $FND_TOP/admin/template/ebsProductManifest_
xml.tmp
b) Modify $FND_TOP/admin/template/ebsProductManifest_xml.tmp to add below
entry for customprod.jar (after customall.jar)
customprod.jar
c) Run AutoConfig
d) Bounce the Mid-tier services
NOTE: These changes will be lost in case ebsProductManifest_xml.tmp is patched
in future and changes have to be done again.
2) In order to to synchronize the changes (during next PREPARE) between both t
he file systems fs1 and fs2 follow below steps:
a) Custom Sync driver file which is located at /ad/custom/adop_sync.drv sh
ould be used to achieve this.
Above file has the required documentation on how to put an entry for
a file which needs to be synched between both the file systems.

b) If there are custom java class files under /oracle//* directory and if
the files under this directory needs to be synched between fs1 & fs2, then user
should be putting the following entry in the custom synch driver file as below:
cp -r %s_current_base%/EBSapps/comn/java/classes/oracle/ %s_other_bas
e%/EBSapps/comn/java/classes/oracle
c) To copy the custom jar file below entry should be added:
cp %s_current_base%/EBSapps/comn/java/classes/customprod.jar %s_other
_base%/EBSapps/comn/java/classes
d) To sync the custom changes done to the template below entry should be a
dded:
cp %s_current_base%/EBSapps/appl/fnd/12.0.0/admin/template/ebsProduct
Manifest_xml.tmp %s_other_base%/EBSapps/appl/fnd/12.0.0/admin/template
e) After changes are synchonized, ensure Autoconfig is run for the latest
template changes to take affect.

Additonal Details
=============
Changing the Keystore and Key Password
===============================
If you do not know the passwords, you can change them using the following steps
Change Your Keystore Passwords
------------------------------------------If required, you can change your Keystore passwords by running the two command
s below and entering your new password when prompted. The new password must be
at least six (6) chars long.
Change your keystore (store) password
Run the following command substituting the values in bold as applicable:
$ adjkey -storepasswd
Enter the APPS username: <appsusername>
Enter the APPS password: <appspassword>
Enter the new keystore password: <new store passwd>
Change your key password
--------------------------------Run the following command substituting the values in bold as applicable:
$ adjkey -keypasswd
Enter the APPS username: <appsusername>
Enter the APPS password: <appspassword>
Enter the new key password: <new key passwd>

How to deploy customizations that are created in the package oracle.apps.xxprod.

* rather than xxprod.oracle.apps.* or xxprod.oracle.apps.xxprod.* on EBS 12.2.X?
(Doc ID 1609939.1)