After Upgrading to 12.2.x Customized OAF Pages will not work which were
worked in earlier versions. Starting Release 12.2.X, Oracle has provided
a new utility called adcgnjar, which allows developers to extend
Oracle classes for OAF Pages. This is required for deploying custom
Oracle Application Framework (OAF) Controllers/View Object /Entity
Object Extensions other wise you class file will not be recognized.
Option – 1
$ cd $JAVA_TOP
# run the command
adcgnjar
# Bounce the middle-tier services
Option - 2 ( If Option 1 doesn’t work)
1. cd $JAVA_TOP
2. zip -r customprod.zip XXDIR
3. Excute (give store pass and key pass)
adjava oracle.apps.ad.jri.adjmx -areas $JAVA_TOP/customprod.zip
-outputFile $JAVA_TOP/customprod.jar -jar $CONTEXT_NAME 1 CUST jarsigner -storePass -keyPass
4. rm $JAVA_TOP/customprod.zip
5. Follow below steps to make the custom jar available for WebLogic
a) Take a back-up of existing /admin/template/ebsProductManifest_xml.tmp
b) Modify /admin/template/ebsProductManifest_xml.tmp to add entry for customprod.jar (after customall.jar)
c) Run AutoConfig
d) Bounce the Mid-tier services
Option – 1
$ cd $JAVA_TOP
# run the command
adcgnjar
# Bounce the middle-tier services
Option - 2 ( If Option 1 doesn’t work)
1. cd $JAVA_TOP
2. zip -r customprod.zip XXDIR
3. Excute (give store pass and key pass)
adjava oracle.apps.ad.jri.adjmx -areas $JAVA_TOP/customprod.zip
-outputFile $JAVA_TOP/customprod.jar -jar $CONTEXT_NAME 1 CUST jarsigner -storePass -keyPass
4. rm $JAVA_TOP/customprod.zip
5. Follow below steps to make the custom jar available for WebLogic
a) Take a back-up of existing /admin/template/ebsProductManifest_xml.tmp
b) Modify /admin/template/ebsProductManifest_xml.tmp to add entry for customprod.jar (after customall.jar)
c) Run AutoConfig
d) Bounce the Mid-tier services
No comments:
Post a Comment