How to configure your application server for debugging

In order to debug your Web application or Web service with Grasshopper, your application server must be configured to run in debug mode.

Configuring WebSphere Application Server or WebSphere Portal for debugging
To configure the WebSphere Application Server or WebSphere Portal for debugging, please do the following:

Use the administrative console to select your working server.

In Application Servers, select your server.

In Additional Properties, click Debugging, and then select the check box Startup.


Configuring BEA WebLogic for debugging
For WebLogic 8.1:

The default cgServer is running in debug mode. If you create your own server, use the wizard and select extending existing server and choose type workshop server.

For WebLogic 9:

Open the file \weblogic90\common\bin\commEnv.cmd .

After the last 'set WEBLOGIC_CLASSPATH' command, add the following line:

set debugFlag=true

Configuring JBoss for debugging
To configure the JBoss application server for debugging:

Open the run.bat file, which is located in the \bin directory.

Locate the rem JPDA options line in run.bat, and then add the following immediately afterwards:


set JAVA_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE -
Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n %JAVA_OPTS%


Save run.bat.

Configuring Apache Tomcat for debugging
To configure the Apache Tomcat application server for debugging, enter the following commands in a Command Prompt window:


set JAVA_HOME=
set JPDA_ADDRESS=8009
set JPDA_TRANSPORT=dt_socket
cd \bin
catalina.bat jpda start