By Vijay Shanmugam-Oracle on Mar 07, 2016
Oracle Workflow Notification system provides ability to use OA Framework regions to show content within a notification body in Worklist. This provides following benefits:
- Reuse application code to display content inside workflow notifications
- Consistent look and feel of notification content with OA Framework pages
Refer to Oracle Workflow Developer Guide for more information.
A challenge for application developers had been to setup JDeveloper to develop, embed and test their OA Framework regions using OA Framework JDeveloper Extension within workflow notifications before deploying it to an EBS environment. Most developers complete development of a standalone OA Framework region, migrate it to EBS, embed to workflow notifications and test it from actual workflow notification pages. Troubleshooting issues with such embedded regions had been extremely difficult.
This blog post provides instructions to develop, embed, test and troubleshoot embedded framework regions within JDeveloper.
Using OA Extension
Refer to chapter "Setting Up Your Development Environment" in OA Framework Developer's Guide for details on setting up OA Framework JDeveloper project against an E-Business Suite env.
Use below instructions to setup the OA Framework JDeveloper environment with required Worklist run-time files.
- From the corresponding Apps env's web tier, copy following directories
- $JAVA_TOP/oracle/apps/fnd/wf/directory to $JDEV_USER_HOME/myglobalclasses/oracle/apps/fnd/wf/directory
- $JAVA_TOP/oracle/apps/fnd/wf/utilities to $JDEV_USER_HOME/myglobalclasses/oracle/apps/fnd/wf/utilities
- $JAVA_TOP/oracle/apps/fnd/wf/worklist to $JDEV_USER_HOME/myglobalclasses/oracle/apps/fnd/wf/worklist
- PLEASE NOTE:
- These are all the seeded Oracle Workflow's run-time Java class files that are executed by worklist pages when rendering
- All classes under myglobalclasses directory take precedence over the default libraries loaded by JDeveloper
- From the corresponding Apps env's web tier, copy directory
- $FND_TOP/mds/wf/worklist/webui to $JDEV_USER_HOME/myprojects/oracle/apps/fnd/wf/worklist/webui
- PLEASE NOTE:
- These are all the seeded Oracle Workflow's run-time OAF page definitions used to render worklist pages
- All JRAD XML files have to be copied under myprojects. These are automatically pulled by JDeveloper into the project when you refresh it.
- Update config file application.xml under $JDEV_USER_HOME/system/oracle.j2ee./embedded-oc4j/config to remove the line containing wf.zip. This zip file is very old and contains Workflow UI files that may not be compatible with the target EBS env you are working against.
- For 11i, the application.xml is under $JDEV_USER_HOME/system9.0.3.x.x/oc4j-config/
- Setup the compile and run directories to use myglobalclasses folder instead of the default myclasses folder
- Go to Project Properties -> Project Content -> Output Directory. Change myclasses to myglobalclasses
- Go to Project Properties -> Run/Debug -> Select Default -> Edit -> Run Directory. Change myclasses to myglobalclasses
- To verify that the worklist is setup correctly to run from JDeveloper, you can now run AdvancWorklistPG.xml from the project. This should display the Advanced Worklist page.
- In the same JDeveloper, setup your application specific OAF regions that you want to embed into workflow notifications.
- Complete required setup to embed the region into Workflow Notifications as per Workflow Developer Guide.
- Now run AdvancWorklistPG.xml again and test your notification.
Such JDeveloper setup would save a ton of time for developers since all testing is done within the JDeveloper env itself without going to the EBS env.