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 10: Using JBuilder with Tomcat 95
Selecting Tomcat as your project’s web server
If you’d like more information about Tomcat or would like to run it standalone, refer to
the documentation WAR file in the following folder:
■
Tomcat 4.1 — <jbuilder>/thirdparty/jakarta-tomcat-4.1.30/webapps
■
Tomcat 5.0 — <jbuilder>/thirdparty/jakarta-tomcat-5.0.27/webapps
Tomcat 4.1 does not support JSP debugging. You can remedy this problem with the
following steps:
1 Download the Tomcat 4.0 binary from http://jakarta.apache.org/.
2 Browse to the Tomcat 4.0 installation directory. Open the lib folder.
3 Copy jasper-compiler.jar and jasper-runtime.jar to the <jbuilder>/thirdparty/
jakarta-tomcat-4.1.30/common/lib
directory. You will overwrite the two existing files.
Note The Borland Enterprise Server AppServer uses Tomcat internally for the production
web server. If you’re using the Borland Enterprise Server, you do not need to configure
Tomcat separately.
Selecting Tomcat as your project’s web server
Before you begin web development, you should select Tomcat as the web server for
your project.
To select the Tomcat web server for your project,
1 Choose Project|Project Properties.
2 Click the Server page. The Server page is displayed.
3 Select the Single Server For All Services In Project option and select the version of
Tomcat you want from the drop-down list.
4 If you want to avoid having libraries added to your project that you won’t use,
uncheck the check box in front of the service(s) you don’t need in the Services list. If
you disable services, the corresponding JBuilder features will be disabled.
Important Tomcat 4.1 and 5.0 support the JSP/Servlet and Naming/Directory services.
5 If you want to make changes to the configuration settings for the selected version of
Tomcat, click the ellipsis (…) button to the right of the server name and edit the
settings you want on the General page. Click OK when you’re finished.