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
74 Developing Applications for J2EE Servers
Configuring JBuilder for WebSphere servers
4 If you want to change any of the settings, click the ellipsis (…) button next to the field
and make your changes. If you installed WebSphere into
[drive]:/Program Files/
WebSphere
, the default Home Directory is [drive]:/Program Files/WebSphere/
AppServer
. Otherwise, the Home Directory becomes whichever directory you specify.
5 Click the Custom tab to view fields unique to the server. Change or fill in these
fields:
For WebSphere Application Server 4.0.7:
■
IBM JDK Installation Directory: Where the IBM installation of the JDK is installed.
JBuilder uses this field to locate the proper version of the JDK the server
requires. This field is set when you specify the Home Directory, so it should be
the
java directory of the Home Directory; for example, the directory would be
[drive]:/Program Files/WebSphere/AppServer/java if [drive]:/Program Files/
WebSphere/AppServer
is your Home Directory.
■
DB2 Installation Directory: The directory in which DB2 is installed on your
system. Usually this is in
[drive]:/SQLLIB.
■
Add An Administrator’s Console Item to The Enterprise Menu: Checking this
check box adds the WebSphere Admin Console item to JBuilder’s Enterprise
menu so you have quick access to it from the JBuilder IDE.
■
Add an Application Assembly Tool Item to The Enterprise Menu: Checking this
check box adds the WebSphere Application Assembly item to JBuilder’s
Enterprise menu so you have quick access to this tool from the JBuilder IDE.
For WebSphere Application 5.0.2.4, 5.1.0.4:
■
JDK Installation Directory: Where the IBM installation of the JDK is installed. This
field is set when you specify the Home Directory, so it should be the
java
directory of the Home Directory; for example,
[drive]:/Program Files/WebSphere/
AppServer/java
.
■
Embedded Message Path: The directory where WebSphere’s messaging
software is located. This field is set by default and is usually in the
Ibm/WebSphere
MQ
directory. So, if you installed WebSphere into [drive]:/Program Files/
WebSphere
, the Embedded Messaging Path would be [drive]:/Program Files/Ibm/
WebSphere MQ
. You can, however, specify any path directly that contains the
messaging software.
■
Cell Name: The cell name is set by default. It is read in from your local server
configuration. You can edit this field, but you will seldom need to do so. For more
information about cells, see your WebSphere documentation.
■
Node Name: The node name is set be default. It is read in from your local server
configuration. You can edit this field, but you will seldom need to do so. For more
information about nodes, see your WebSphere documentation.
■
Server Name: The server name which you are configuring. It is read in from your
local server configuration. JBuilder suggests a default name, which you can
change to meet your needs.
■
Add An Administrative Console Item To The Enterprise Menu: Checking this
check box adds the WebSphere Admin Console item to JBuilder’s Enterprise
menu so you have quick access to it from the JBuilder IDE. You must also fill in
the next field, Web Browser Path, to have the menu item added.
■
Web Browser Path: Specify the path and file name of the web browser of your
choice. For example, you might specify
c:/Program Files/Internet Explorer/
iexplore.exe
if you want to use Microsoft’s Internet Explorer.
■
Add An Application Assembly Item To The Enterprise Menu: Checking this check
box adds the WebSphere Application Assembly item to JBuilder’s Enterprise
menu so you have quick access to this tool from the JBuilder IDE.