Introduction:
In Oracle E-Business Suite (EBS) R12.2, encountering BBM (Business Intelligence and Business Process Management) JAR issues can disrupt normal operations. This blog post provides a step-by-step guide to address and fix the specific problem related to the “jxl-2.6.jar” file.
Solution :
Step 1 : Check the existence of file “jxl-2.6.jar” in “$JAVA_TOP” (Both file system Run & Patch)
(i) echo $FILE_EDITION –> run
ls -l $JAVA_TOP/jxl-2.6.jar
(ii) echo $FILE_EDITION –> patch
ls -l $JAVA_TOP/jxl-2.6.jar
Step 2 : Add entry for “jxl-2.6.jar” in file “ebsProductManifest_xml.tmp” (Both file system Run & Patch)
Navigate to the custom templates directory:
(i)
echo $FILE_EDITION –> run
cd $FND_TOP/admin/template/custom
Edit the “ebsProductManifest_xml.tmp” file using a text editor (e.g., vi) and Insert the following lines
vi ebsProductManifest_xml.tmp
<libraries>
<library>customall.jar</library>
<library>jxl-2.6.jar</library>
</libraries>
(ii)
echo $FILE_EDITION –> patch
cd $FND_TOP/admin/template/custom
Edit the “ebsProductManifest_xml.tmp” file using a text editor (e.g., vi) and Insert the following lines
vi ebsProductManifest_xml.tmp
<libraries>
<library>customall.jar</library>
<library>jxl-2.6.jar</library>
</libraries>
Step 3 : Compile, re-generate and sign “customall.jar” file
cd $JAVA_TOP
adcgnjar
Step 4: Run “autoconfig” and bounce services
(i) Shutdown DMZ node application services
(ii) Shutdown PRIMARY node application services
(iii) Run “AUTOCONFIG” only in EBS primary node.
(iv) Start PRIMARY node application services.
(v) Start DMZ node application services.
Step 5: Test if the issue persists
After completing the above steps, thoroughly test the EBS system to ensure that the BBM JAR issue has been resolved.
Conclusion:
By following these steps, you can effectively address and fix the BBM JAR issue in Oracle E-Business Suite R12.2. These solutions aim to restore normal functionality and ensure a seamless user experience
Recommended Posts
