Setting Tomcat Installation Properties
See Also
The Installation property sheet enables you to edit the attributes of a Tomcat
web server installation.
To display the property sheet for a Tomcat installation:
- On the Runtime tab of the Explorer, expand the Installed Servers node in
the Server Registry.
- Expand the Tomcat node, then right-click on the appropriate installation
node. Note that the Internal Tomcat node represents the Tomcat installation
that is added when you install the IDE.
- Choose Properties from the contextual menu.
On the Properties pane of the property sheet for an installation, you can set
the following properties:
- Base Directory. This property specifies the base directory for the
Tomcat server. You can set this property when you add a new Tomcat installation
to the Server Registry. If you set a base directory, then that is where the
Tomcat configuration files will reside. One reason for specifying a separate
base directory is to allow several instances of the server, which run different
web modules, to share the same libraries. If no base directory is specified,
then the configuration files reside in the home directory. In the internal
Tomcat installation, the home directory is under the IDE installation directory
and is called tomcat406. The base directory is under IDE user directory,
and is called tomcat406_base. This setup differs from a typical Tomcat
installation, where the base directory and the home directory coincide. See
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/RUNNING.txt for more
information.
- Enable Assertions. If set to True,
adds the -enableassertions argument to the java command. The default
value is False.
- External Execution Process. Use the External Execution Process property
to specify execution details for Tomcat, such as adding directories,
ZIP files, or jar files to the classpath that Tomcat uses when executing.
To add or edit an execution process, click the External Execution Process
value field, then click on the ellipses (...) to display the External Execution
Process property editor. To add a ZIP file to the Tomcat execution
classpath, add the path and name of the ZIP file to the -classpath
argument in the Arguments field. Use {:} to separate individual
members in the -classpath option. When you are finished, click
OK to close the property editor. Note that the default settings match the
behavior of the standard Tomcat startup wrappers. You should not modify
default settings unless you are very experienced with Tomcat customization.
- Home Directory. This property specifies the home directory for the
Tomcat server on your local system. This property is set when you add
a new Tomcat 4.0 installation to the Server Registry. This location is where
Tomcat expects to find its own binaries and any libraries that are used by
web modules but which are not part of Tomcat itself.
- IDE Integration Mode. Use this property to choose an IDE integration
mode. The default value is Full. In Minimum mode, the IDE will not modify
the configuration file in any way except those changes required to deploy
your web module. In this mode, some features of the IDE will be unavailable,
including HTTP monitoring and JSP debugging. In Full mode, all web module
development features are available, including HTTP monitoring, JSP compilation,
and JSP debugging. The web.xml file in your server will be modified
to support these features. To set IDE Integration mode, click on the ellipses
(...) in the right-hand column of the IDE Integration Mode row and choose
the appropriate button in the property editor.
- Server Port. This property specifies the TCP/IP port number on which
this server waits for a shutdown command. This connection must be initiated
from the same server computer that is running this instance of Tomcat. In
most situations, you do not need to modify this value.
On the Debugger pane of the property sheet for an installation, you can set
the following properties:
- Classic. This property refers to the "classic" JDK 1.1
JVM. Select True or False from the list to set this
property. If the selected value is True, then the JDK 1.1 JVM
will be used for debugging. If False, the default HotSpot JVM
will be used.
- Debugger Port. Use the Debugger Port property to specify the Debugger
port number that Tomcat will use for debugging. To edit the port, type the
desired port number in the value field.
- Debugging Type. Use the Debugging Type property to specify the type
of debugging you prefer. Select socket or shared memory from the list. If
the selected value is socket, then the IDE connects to the server being debugged
using sockets. If shared memory, then the IDE connects to the server being
debugged using shared memory.
- External Debugger Process. Use the External Debugger Process property
to specify external debugging information for Tomcat. To add or edit a debugging
process, click the External Debugger Process value field, then click the ellipses
(...) to display the External Debugger Process property editor. In the property
editor, use the Process field to enter (or browse for) a process, then provide
an argument for that process in the Arguments field. When you are finished,
click OK to dismiss the property editor.
- Name. Use this property to specify the identification string for
shared memory access. To specify a name, click the External Debugger Process
value field, then click the ellipses (...) to display the Name property editor.
In the property editor, type a name, then click OK to dismiss the property
editor.
Legal Notices