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
Chapter 5: Using JBuilder with Borland servers 41
Remote debugging
Remote debugging
Before you can debug your application remotely, you need to configure the partition.
You can do this before you start the server or while the server and partition are already
running. See these sections for more information:
■
“Preparing to remote debug partitions that are not managed in JBuilder” on page 41
■
“Preparing to remote debug partitions that are managed in JBuilder” on page 41
■
“Preparing to remote debug before the Borland Enterprise Server AppServer Edition
5.2.1 is running” on page 42
■
“Preparing to remote debug when the Borland Enterprise Server AppServer Edition
5.2.1 is already running” on page 42
Once the configuration is complete and the server and partition are started, follow the
instructions in “Remote debugging in JBuilder” on page 43.
Remote debugging for Borland Enterprise Server 6.0
Preparing to remote debug partitions that are not managed in JBuilder
To prepare to remote debug partitions that are not managed in JBuilder,
1 Start the Borland Management Console.
2 Start the server.
3 Locate the partition you wish to debug.
4 Right-click the partition and choose Properties.
5 Select the Partition Settings tab.
6 Check the Enable JPDA Remote Debugging option.
7 Set the transport address field to 3999.
8 Uncheck the Suspend Partition Until Debugger Attaches option.
9 Click OK.
Preparing to remote debug partitions that are managed in JBuilder
To prepare to remote debug partitions that are managed in JBuilder, you have two
options:
Starting the server/configuration/partition outside of JBuilder
1 Shut down the server.
2 Open the file <APPSERVER_HOME>/var/domains/base/configurations/configuration.xml.
3 Look for the JPDA element and edit attribute values as follows:
enable-jpda-debug="true"
jpda-transport-address="3999"
jpda-suspend="false"
4 Start the server/configuration/partition outside of JBuilder.
Starting the management agent/partition in JBuilder
1 Shut down the server.
2 Open the file <APPSERVER_HOME>/var/domains/base/configurations/configuration.xml.