HOW TO: Debug a remote JSP

Question

<h1>HOW TO: Debug a remote JSP</h1>
<strong>Note: </strong>The process of debugging a remote JSP on an Apache/Jserv
installation involves a couple extra steps that were not covered in the JDeveloper
3.2 documentation. </p>
<strong>Introduction</strong></p>
You use JDeveloper to debug JavaServer Pages (JSP) deployed and running on
a server that includes a JSP container, such as Apache Jserv. Your JSP container
will need to be configured to enable remote JSP debugging using JDeveloper.</p>
JDeveloper allows you to use one of two protocols for JSP debugging - the
Oracle Java Virtual Machine (OJVM) debugging protocol or the Sun Java Platform
Debugging Architecture (JPDA). Before you start your remote debugging session,
you will have to choose which method to use. If you use the OJVM protocol, your
debugging session will run more quickly and you will have some additional features
to assist you. You can only use OJVM on a Windows NT system. If your server
is running UNIX or another operating system, you <strong>must</strong> use the
&quot;classic&quot; JVM.</p>
<strong>Setting up your project for remote JSP debugging</strong></p>
Once you have created a JSP project, you need to set your project options
so that remote debugging is enabled: </p>
<ol>
From the <strong><u>P</u>roject</strong> menu, select <strong><u>P</u>roject
Properties</strong>. </p>
</li>
Click the <strong>Run/Debug</strong> tab.</p>
</li>
From <strong><u>D</u>ebug Files As:</strong> dropdown list, select <strong>Remote
Debugging</strong>. </p>
</li>
Click <strong>OK</strong>. </p>
</li>
</ol>
<strong>Configuring the Remote Server</strong></p>
The following options must be changed on the host running the Apache/Jserv
server. These instructions assume the server is running Windows NT: </p>
<strong>Changes to jserv.properties</strong></p>
These options control which Java Virtual Machine is used and how it is loaded.
</p>
<ol>
For <em>The Java Virtual Machine interpreter</em> parameter <tt>wrapper.bin</tt>:
</p>
</li>
<ul>
[*]Comment out any existing entries by putting a <tt>#</tt> at the beginning
of the line.
<blockquote>
<pre>#wrapper.bin=C:\java1.1.8\bin\java.exe</pre>
</blockquote>
</li>
[*]Add a new entry with the full path of the <tt>java.exe</tt> that you want
to use. To use the JDeveloper 1.3 OJVM, put
<blockquote>
<pre>wrapper.bin=C:\Program Files\Oracle\JDeveloper 3.2\java1.2\bin\java.exe</pre>
</blockquote>
</li>
</ul>
For the <em>Arguments passed to Java interpreter</em> parameter <tt>wrapper.bin.parameters</tt>:
The value you put for this parameter depends on which Debugging Protocol
you will choose in the <strong>Remote Debugging Dialog</strong> in JDeveloper
when you start debugging.</p>
</li>
<ul>
[*] If you want to use the JDeveloper 3.2 OJVM, put </li>
<blockquote>
<pre>wrapper.bin.parameters=-ferrari -XXdebugondemandquietport4000</pre>
</blockquote>
[*]If you want to use Java Platform Debugging Architecture, put
<blockquote>
<pre>wrapper.bin.parameters=-classic -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=4000 -Xdebug -Xnoagent -Djava.compiler=NONE</pre>
</blockquote>
The <tt>4000</tt> parameter defines the port number which the JDeveloper
debugger will use to communicate with the server. You can specify a different
port number, but it must match the port which you will enter in the <strong>Remote
Debugging Dialog</strong> in JDeveloper when you start debugging. </p>
</li>
</ul>
[*] For the <em>PATH environment value passed to the JVM</em> parameter <tt>wrapper.path</tt>
enter the location of <tt>jdwp.dll</tt>, which is part of the <em>Java Platform
Debugging Architecture</em>.
This parameter is only necessary if you will choose the <em>Java Platform
Debugging Architecture</em> debugging protocol:</p>
<blockquote>
<pre>wrapper.path=C:\jpda\bin</pre>
</blockquote>
</li>
For the <em>CLASSPATH environment value passed to the JVM</em> parameter
<tt>wrapper.classpath</tt>: </p>
<ul>
Keep the location of <tt>ApacheJServ.jar</tt>. If it is not already
there, add it. </p>
<blockquote>
<pre>wrapper.classpath=C:\Program Files\Apache\JServ\ApacheJServ.jar</pre>
</blockquote>
</li>
Comment out the location of <tt>jsdk.jar</tt>. </p>
<blockquote>
<pre>#wrapper.classpath=C:\jsdk2.0\lib\jsdk.jar</pre>
</blockquote>
</li>
[*]Add the location of <tt>servlet.jar</tt> from JDeveloper 3.2.
<blockquote>
<pre>wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\servlet.jar</pre>
</blockquote>
</li>
[*] Add the locations of <code>jdeveloper.zip</code> and <code>ojsp.jar</code>
from JDeveloper.
<blockquote>
<pre>
wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\jdeveloper.zip
wrapper.classpath=C:\Program Files\Oracle\JDeveloper 3.2\lib\ojsp.jar
</pre>
</blockquote>
</ul>
</ol>
<strong>Changes to jserv.conf</strong></p>
<ol>
For the <em>ApJServAction</em> parameter: </p>
<ul>
[*] Comment out any existing <tt>ApJServAction .jsp</tt> entries by putting
a <tt>#</tt> at the beginning of the line. </li>
<blockquote>
<pre>
#ApJServAction .jsp /servlets/org.gjt.jsp.JSPServlet
</pre>
</blockquote>
[*]Add a new <tt>ApJServAction .jsp</tt> entry like this.
<blockquote>
<pre>
ApJServAction .jsp /servlets/oracle.jsp.JspServlet
</pre>
</blockquote>
</li>
</ul>
</li>
</ol>
<strong>Changes to zone.properties</strong></p>
<ol>
In the <em>Servlet Init Parameters</em> section: </p>
</li>
<ul>
Add the following lines. </p>
<pre>
servlet.oracle.jsp.JspServlet.initArgs=emit_debuginfo=true
servlet.oracle.jsp.JspServlet.initArgs=jspcompiler=oracle.jdeveloper.jsp.JspOjcCompiler
servlet.oracle.jsp.JspServlet.initArgs=classpath=C:\Program Files\Oracle\JDeveloper 3.2\java1.3\jre\lib\rt.jar
</pre>
</li>
</ul>
</ol>
<strong>Copying the JSP to the Apache/Jserv Server</strong></p>
Once you have restarted the server with the modified parameters, you need to
copy your JSP to the server's HTML root directory. For most Apache installations
this is <tt>C:\Program Files\Apache\htdocs</tt>. </p>
You also need to make sure the JSP is in your HTML directory in the JDeveloper
tree, typically <tt>C:\Program Files\Oracle\JDeveloper 3.2\myHTML</tt>. The
reason for this is JDeveloper uses the folder name as its package name.</p>
<strong>Debugging a JSP</strong></p>
Debugging a JSP is very similar to debugging any other Java program.</p>
<ol>
From the <strong><u>R</u>un</strong> menu, select <strong><u>D</u>ebug
"<em>filename</em>.jsp"</strong>. </p>
Start the JSP running (for example, start your web browser and open a
connection to the JSP). </p>
Debug as normal. </p>
</ol>
If you are using the JDeveloper OJVM debugging protocol, you will be able
to disconnect from the JSP container. This allows you to stop debugging, but
leave the JSP container running. In addition, you will be able to use two extra
debugging functions that are not available using the JDPA protocol - <strong>Run
to End of Method</strong> and <strong>Set Next Statement</strong>.</p>
If you using JPDA, you must use <strong>Stop</strong> to end your debugging.
Using this method will also stop the JSP container.</p>
<blockquote>
<strong></strong></p>
</blockquote>
null

Answer 1

Hi,
It again same as you do in your local server...You can monitor the BPEL process flow in the em console and debug..if its not sufficient....u can also monitor the logs located at
<SOA_Home>\user_projects\domains\domain1\servers\soa_server1\logs to debug.