Remote JPDA interactive debugging of mod_plsql application with JDeveloper

Question

We have an existing application running on Oracle DB v10.1.0.4 which we want to debug insitu in order to analyse its operation and functions. The application is best described as a 3-tier Oracle PL/SQL Web–Enabled Application implemented using the specialised mod_plsql module of the Oracle HTTP Server [Apache 1.3].
We want to be able to interactively debug the pls/sql code whilst a user is
using the live application [from the web browser] using the JPDA remote
listening facilities of JDeveloper 10.1.2. How can this be done ?
After extensive research , I have found only two online resource that briefly
indicate this can be done: viz
1. http://www.oracle.com/technology/tech/pl_sql/pdf/Paper_30720_Ppt.pdf
- The debugging user sets a cookie via the browser UI –specifying JDWP host and
port Causes mod_plsql to call Connect_Tcp before its normal calls and
disconnect after these.
2. http://web51-01.oracle.com/oowsf2004/1401.pdf
Web mod_plsql applications
– Create a UI form to set a cookie in the browser
– Pass the hostname and port to the owa_debug package
– owa_debug transparently calls the server-side PL/SQL to connect with the
debugger listener for each subsequent page requested by that browser
This information is not enough for me to actually be able to do this. I need
more details/ example etc. I also have not been able to find ANY additional
info on the owa_debug package- which is critical to the whole solution. Any help appreciated.

Answer 1

These are the steps to set up the database and JDeveloper for debugging your mod_plsql Web applications.
--- Database setup ---
1. Load additional PL/SQL gateway debug packages:
cd $ORACLE_HOME/wwg/admin/owa
sqlplus "sys/... as sysdba"SQL> @pubowad.sql
SQL> @privowad.plb
SQL> @pubjdwp.sql
2. Grant debug connect session privilege to DAD database user:
sqlplus "sys/... as sysdba"SQL> grant debug connect session to <DAD-database-user>;
3. Create the Web HTML interface to initiate debugging in the DAD database user's schema:
cd $ORACLE_HOME/wwg/admin/owa
sqlplus DAD-database-user/...SQL> @owaddemo.sql
4. Recompile your application procedures with debug information:
sqlplus DAD-database-user/...SQL> alter session set plsql_debug=true;
SQL> create or replace procedure XXXX ...;
5. Sets DAD attributes for debugging:
In the DAD setting inside dads.conf, add
PlsqlOWADebugEnable On
PlsqlMaxRequestsPerSession 1
PlsqlExclusionList \#None\#
and restart your Oracle HTTP (Apache) listener.
--- JDeveloper setup ---
6. For remote debugging (e.g. debugging a PL/SQL Web application executed by mod_plsql), choose "remote debugging" as follows:
* Choose Tools -> Default Project Properties... menu.
* Select Profiles -> Development -> Debugger -> Remote tree node.
* Check Remote Debugging option.
* Select Listen for JDWP option.
* For Database Connection for Locating PL/SQL Source:, select the database connection just created.
7. Set a breakpoint in your application procedure:
* In Connections tree, expand Database node. Expand the new database connection node. Expand the database user node. Expand Procedures, Functions, or Packages node. Double-click the library unit you want to set a breakpoint in.
* In the program source of the library unit, single-click at the left-margin of the source line you want to break.
8. Start remote debugging:
* Start the debugger listener from Debug -> Debug Project menu. Specify the TCP/IP port number the debugger should listen for JDWP (debug) connection.
--- Invoke Web application in debug mode ---
9. In your browser, go to the URL http://<host>:<port>/<DAD-virtual-path>/owa_debug_demo.main_form. Check the "Enable JDWP Debugging" box, enter the "JWDP Debugger Host" as the host of your JDeveloper machine, enter the "JDWP Debugger Port" as the TCP/IP port that JDeveloper is set up to listen for JDWP (debug) connection. Then hit "Create Debug Session". This will create a cookie for you which will be used to track your "Debug Session" preferences.
10. In your browser, invoke your Web application's URL. You should your application session being connected to your JDeveloper for you to debug.