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 4: Configuring the target server settings 21
Setting up servers within JBuilder
dialog box when not all required values are set or selecting another server while the
current one is enabled displays a message dialog box that informs you about the
missing settings and usually selects the control representing the missing setting.
4 If you want to change any of the settings, click the ellipsis (…) button next to the field
and make your changes.
You can add any necessary application dependencies to the server’s classpath by
clicking the Required Libraries tab and using the Add button to add the libraries the
server needs.
5 Click the Custom tab to view settings unique to the server. Most application servers
allow you to specify the location of the JDK the server uses; some require you to
specify the JDK location for successful configuration completion. Updates you make
on the Custom page can update settings on the General page. (Note that Tomcat
configurations do not have a Custom tab.)
Following are the JDKs and their installed locations for the application servers
supported by JBuilder:
■
Borland Enterprise Server AppServer Edition 5.2.1: <bes home>/jdk/jdk1.3.1 or
<bes home>/jdk/jdk1.4.1 (the default value)
■
Borland Enterprise Server AppServer Edition 6.0: <bes home>/jdk/jdk1.4.2
■
WebLogic Server 7.x: <bea home>/jdk131_10
■
WebLogic Platform Server 8.1: <bea home>/jdk141_04. WebLogic 8.1 also
supports JRockit (a JDK optimized for server applications), so the JDK directory
could be <bea home>/jrockit81sp3_142_04
■
WebSphere 4.x (either Advanced Edition or Single Server): <websphere home>/
java
■
WebSphere 5.x: <websphere home>/java
As you make your edits, JBuilder attempts to validate your settings. Once you’ve
made your edits, click the OK button to accept your changes and close the dialog
box. If you prefer that JBuilder not try to validate your changes, uncheck the Enable
Server dialog box. Selecting OK saves changes for all servers you’ve enabled,
disabled, or modified.
6 Click OK when you are through configuring the application server.
When you click OK and the Enable Server check box is checked, JBuilder attempts
to verify your settings. If errors are detected, a message box containing information
about the errors appears and focus is given to the control appropriate for fixing the
error. If the Enable Server option is unchecked, the dialog box simply closes and no
setting validation is performed.
Once a server is properly configured and validated, the server you configured is listed
in black type in the pane on the left. Gray type indicates the server hasn’t been
configured yet. Red type indicates an error condition; specifically it means the server’s
library containing its settings has been read, but the OpenTool representing the server
can’t be found. You can delete a server shown in red by selecting it and clicking the
Delete button.
The Reset To Defaults button sets the settings back to the values they originally had
when JBuilder was first installed and the server is disabled.
If a dialog box appears with a message that you must restart JBuilder, you must close
and then restart JBuilder for changes to become effective; otherwise, restarting
JBuilder is not necessary.