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 77
Deploying
By default in WebSphere 5.x, the stdout and stderr streams are redirected to log files at
application server startup. To view the output in JBuilder when you start the server in
JBuilder:
1 Start the server.
2 Start the Administrative Console from the JBuilder Enterprise menu.
3 Choose Servers|Application Servers|<server_name>|Process Definition|
ProcessLogs.
4 On the Configuration page, set the Stdout File Name and the Stderr File Name to
Console.
Deploying
The following sections describe deploying to both the WebSphere Application Server
5.x and the WebSphere Application Server 4.0.
Using the DD Editor
The DD Editor has several WebSphere-specific pages for information that applies only
to WebSphere servers. For information about using the DD Editor to edit J2EE
modules, see Chapter 11, “Editing J2EE deployment descriptors.” Whenever a
WebSphere-specific page is displayed in the DD Editor, you can press F1 for help on
that particular page. You’ll also find it convenient to have a copy of your server’s
documentation handy to look up the type of information your server requires in the
deployment descriptors.
To prepare to deploy a deployable module, follow the steps outlined for your version of
WebSphere:
WebSphere Application Server 5.x
This section explains how to deploy remotely and locally to the WebSphere Application
Server 5.x.
Remote deploying
WebSphere Application Server 5.x supports remote deployment using the Deployment
Manager version of the application server. The Deployment Manager must be
configured to manage the remote server instance. Please refer to your server
documentation for more information.
Once you have configured your Deployment Manager to manage the remote server
instance, you can deploy to the remote server instance in JBuilder if you follow these
steps:
1 Right-click the archive node you want to deploy in JBuilder’s project pane and
choose Properties.
2 Select Deployment in the tree to display the Deployment page and make sure the
General tab is selected.
3 Set the Cell Name to the Deployment Manager’s cell name.
4 Set the Node Name to the remote server node name.
5 Set Server Name to the remote server name.
6 Click the Connection tab.
7 Set the Connection Type field to SOAP or RMI.