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 8: Using JBuilder with IBM WebSphere servers 81
Container-managed persistence (CMP) 1.1 and 2.0 in WebSphere 5.x
5 In the dialog box that appears, enter the following VM options:
-Xdebug
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,address=3999,suspend=n
6 If you start the server outside of JBuilder, choose Run|Configurations and click the
New button in the dialog box that appears. In the Configuration Name field, specify a
name for the new run configuration server for debugging on your application server.
7 Select Debug|Remote and make these changes on the Debug page:
a Check the Enable Remote Debugging check box.
b Select the Attach option.
c In the Port Number field, enter the port number you noted during the server
startup process.
d Click OK twice to close all dialog boxes.
8 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 be attaching to the application server process. Now you can deploy your
web applications and you’ll be able to stop at breakpoints you set in the bean, JSPs,
or servlets.
To start the server in debug mode within JBuilder, follow these steps:
■
Choose Run|Configurations.
■
Select the Command node and enter the remote debug port number in the Debug
Transport Address field.
Now clicking the debug toolbar button launches the server in debug mode and attaches
to it, all in one session.
Container-managed persistence (CMP) 1.1 and 2.0 in WebSphere 5.x
You can set the schema name and database vendor type as properties on EJB module
nodes:
1 Right-click the EJB module and choose Properties.
2 Select Build|WebSphere 5.x in the tree.
3 Enter your schema and database vendor information in this dialog box:
4 Click OK.