How To Add Classes To The Classpath In The 12.2 E-Business Suite File System (Doc ID 1331703.1)

Last updated on MAY 10, 2024

Applies to:

Goal

You may have been asked by development to test a manual fix or to enable debug classes, if you are, and the code involves java classes then this document will assist you with implementing and testing the new classes.

In EBS R12.0.X and 12.1.X, JAVA_TOP points to a directory which contains each product's compiled java code i.e. COMMON_TOP/java/classes. EBS OC4J applications such as oacore and oafm access the EBS product team java code from within the JAVA_TOP.

In OC4J (12.0.X and 12.1.X) the orion-application.xml file has a property named "library". Any directory or jar file specified in the library directive will be included in the classpath of the application.

Example : <library path="<JAVA_TOP>" />
This adds all class files in the JAVA_TOP to the system classpath

In Weblogic 10.3, which is used in EBS 12.2, there is no equivalent property to the OC4J concept of declaring a library. The best way of adding the JAVA_TOP to the classpath is via a Shared library.

In EBS 12.2, jars are generated from class files for each product's java code present under JAVA_TOP/oracle/apps/<product name> using adadmin and then copied to <COMMON_TOP>/java/classes/oracle/apps/fnd/jar and a shared library (webapp) is deployed in <COMMON_TOP>/shared-libs/ebs-product/WEB-INF/lib/.  The manifest file used to run most of ebs is ebsProductManifest.jar. The shared library includes a reference to all the product team jars. The EBS applications reference this shared library.

As the javacode is in archived format (Signed jars generated through ADADMIN), we need to identify how to load the debug classes into the classpath before the original product jar files so that they override the original and picked up during runtime.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.