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 79
Enabling remote debugging
You can also deploy a module to a remote server from JBuilder’s project pane:
1 Right-click the module you wish to deploy.
2 Select Properties.
3 Select Deployment in the tree to display the Deployment page.
4 Specify these options in the Options field:
-nameServiceHost<host name> -nameServicePort<port number>
5 Set the Primary Node and Server Name to match your server configuration.
6 Right-click the module in the project pane and choose Deploy Options|Deploy.
Deploying locally
These are the deploy options you’ll find on the Deploy Options context menu:
■
Deploy — Deploys a JAR to the currently running container of the project application
server. If the Build Target option is Make for the current runtime configuration
(Choose Run|Configurations, select the current runtime configuration, and click Edit
then click Server and select Deployment in the tree of services to see the Build
Target), this option will “make” the JAR’s contents before deploying it to the
container.
■
Redeploy — Deploys a JAR again to the currently running container. If the Build
Target option is Make for the current runtime configuration (Choose Run|
Configurations, select the current runtime configuration, and click Edit then click
Server and select Deployment in the tree of services to see the Build Target), this
option will “make” the JAR’s contents before redeploying it to the container.
■
Undeploy — Undeploys an already deployed JAR in the running container.
■
List Deployments — Lists all JARs deployed in the running container.
■
Stop Container — Stops the container. This option appears for WebSphere 4.0
Advanced Edition only. When a deployed EJB changes, the container must be
stopped and then restarted for the changes to register.
■
Start Container — Starts the container. This option appears for WebSphere 4.0
Advanced Edition only.
Enabling remote debugging
The steps to enable remote debugging of a bean running on a WebSphere server vary
depending on which version of WebSphere you are using.
Note You won’t be able to debug JSPs in a remote debug session.
WebSphere Application Server 5.x
Follow these steps to enable remote debugging for WebSphere Application Server 5.x:
1 Launch the server with the -script option:
WEBSPHERE_HOME/bin/startserver -script
This command should write a script called start_<server name> in the
WEBSPHERE_HOME/bin directory.