Server User Manual
Table Of Contents
- Developing Applications for J2EE™ Servers
- Contents
- Ch 1: Introduction
- Ch 2: Programming for the Java 2 Platform, Enterprise Edition
- Ch 3: Creating applications with J2EE technologies
- Ch 4: Configuring the target server settings
- Ch 5: Using JBuilder with Borland servers
- Configuring Borland servers in JBuilder
- Making the ORB available to JBuilder
- Configurations, partitions, partition services, and J2EE APIs
- Starting the configuration or server
- Remote deploying
- Remote debugging
- Web module workarounds
- Displaying the Borland Management Console in JBuilder
- International issues
- Borland servers and JDataStore 7.0
- Ch 6: Using JBuilder’s CORBA tools
- Ch 7: Using JBuilder with BEA WebLogic servers
- Ch 8: Using JBuilder with IBM WebSphere servers
- Ch 9: Using JBuilder with JBoss servers
- Ch 10: Using JBuilder with Tomcat
- Ch 11: Editing J2EE deployment descriptors
- Ch 12: Integrating with Enterprise Information Systems
- Ch 13: Building J2EE modules
- J2EE modules
- Setting module build properties
- Adding custom file types
- Sample build scenarios
- EJB JAR without any bean classes
- EJB JAR with custom files
- EJB JAR without EJB designer XML descriptors
- WAR with custom descriptor(s) in the WEB-INF directory
- WAR without any classes
- WAR with custom class filters
- WAR with custom file types
- EAR with custom files
- RAR with classes and dependencies
- Application client module with classes and dependencies
- Improving module build performance
- Index
80 Developing Applications for J2EE Servers
Enabling remote debugging
2 Edit the launch script and add the following remote debug parameters to the java
command line:
-Xdebug
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,address=3999,suspend=n
3 Launch the server using the script.
4 In JBuilder, choose Project|Project Properties. If you have not yet created a server
run configuration, choose New and create a new configuration of type Server. If you
already have a server run configuration, choose Edit.
5 Select Debug|Remote in the tree and check the Enable Remote Debugging and
Attach options and click OK.
Click the down arrow next to the Debug Project icon ( ) on the JBuilder toolbar and
select the debug run configuration you just created or edited. You will now be able to
set breakpoints in Java code, such as in EJBs, servlets, and so on.
WebSphere Single Server 4.0
If you are using WebSphere Single Server 4.0, follow these steps to enable remote
debugging:
1 Launch the server with the -script option:
WEBSPHERE_HOME/bin/startserver -script
This command should write a script called launch in the WEBSPHERE_HOME/bin
directory.
2 Edit the launch script and add the following remote debug parameters to the java
command line:
-Xdebug
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,address=3999,suspend=n
3 Launch the server using the script.
4 In JBuilder, choose Project|Project Properties. If you have not yet created a server
run configuration, choose New and create a new configuration of type Server. If you
already have a server run configuration, choose Edit.
5 Select Debug|Remote in the tree.
6 Check the Enable Remote Debugging and Attach options and click OK.
Click the down arrow next to the Debug Project icon ( ) on the JBuilder toolbar and
select the debug run configuration you just created or edited. You will now be able to
set breakpoints in Java code, such as EJBs, servlets, and so on.
WebSphere Server Advanced Edition 4.0
WebSphere Server Advanced Edition 4.0 launches another Java virtual machine for
debugging, so you must follow instructions so you can debug your enterprise beans:
1 Start the WebSphere Server 4.0.
2 Start the WebSphere Server 4.0 console application (which you’ll find at
<ws4_ae home>\bin\adminclient.bat if you’re running on Windows.)
3 When the console application appears, expand the tree on the left until you see the
Application servers node. Select this node.
4 In the panel on the right side of the console, click the JVM Settings tab. Click the
Advanced Settings button. (You might need to scroll the panel to see this button.)