View the printer
friendly version of this document
|
Installing the Tomcat Java Application
Server/Servlet Container for Local Development
For: All Windows Versions
Revised: August 01, 2011
Important: The Java application server and MySQL database are not included as
part of the kinetic Service annual fee. These technologies are available on an
as-requested basis for an additional fee. Contact David Drum at
david@more.net
or (800) 509-6673 for additional information.
Contents
Overview
This document details how to install Tomcat as an application
server/servlet container for web application development. This version
of Tomcat is provided as a service to customers of MOREnet for creating
a development environment that closely matches MOREnet production servers.
Important: Individuals using MOREnet's distribution of Tomcat
must use it with the other local development environment distributions from
MOREnet to ensure a working environment. Do not mix and
match MOREnet's distributions with distributions from the official
software vendors. See
Local Development Overview for a complete list. Otherwise, please visit
the official Tomcat
web site to obtain a distribution.
Requirements
Your computer must meet the following requirements:
Download and Install Tomcat
- MOREnet has prepared a Tomcat distribution for web site development.
Download the Tomcat
installation file and temporarily save this executable file
to a location on your hard drive.
- If you have a previous version of Tomcat installed on your system,
uninstall or remove the previous installation. Before you uninstall,
make sure that you save backup copies of any files you
modified in the installation. For example, you may have modified
files in the conf directory, such as catalina.policy
and server.xml, and added web applications in the
webapps\ directory. You only need to save a backup copy if
you would like to reference your changes at a later time.
If you installed Tomcat with a Windows installer, use the uninstaller
to remove Tomcat. If you installed Tomcat without a Windows installer,
follow these steps to manually remove Tomcat:
- Stop Tomcat.
- If you are running Tomcat as an NT service, remove the service.
Open an MS-DOS Prompt window and use the
cd command
to navigate to the bin directory within your Tomcat
installation. This directory should contain a file named
JavaService.exe. Issue the following command and
replace {tomcat service name} with the name you
used for the service:
JavaService.exe -uninstall {tomcat service name}
Note that {tomcat service name} is the same name
you use when when you issue the "net start" command to start
the service. The message "The service was successfully
uninstalled." displays when the service is uninstalled.
- Delete the directory where you installed Tomcat and its
subdirectories.
- Double-click the Tomcat installation file you downloaded earlier
to begin the new installation. The steps that follow detail the prompts
that you'll encounter during installation.
- The installer reviews your system for the location of a Java2
SDK and reports its location; click OK to continue.
If an SDK is not found, the installation halts.
- The installer presents the Tomcat license (i.e. The Apache Software
License). Review the license and click I Agree to continue the
installation.
- The installer displays a list of installation types and components. The
Normal installation type is selected by default.
If you are using Windows NT, Windows 2000, or Windows XP, select the
NT Service component. Do not be alarmed that the installation
type of Custom is automatically selected when you select the
NT Service option. Running Tomcat as an NT service provides
optimum performance under these operating systems.
The other components will help you get the most out of Tomcat.
The Tomcat Start Menu Group, Tomcat Documentation, and
Example Web Applications components provide a list of shortcuts
on your Windows Start menu, the Tomcat documentation, and example web
applications.
The JSP Development Shell Extensions componenet define the
.jsp filename extension as a file that can be opened
by Windows Notepad. If you have a development tool that has already
defined this extension in your system, do not select this component.
The Configure MySQL for Tomcat component configures MySQL
with usernames and passwords for authorization of the Tomcat Manager
and access by web applications to data in the database. If you are
upgrading Tomcat and you've previously installed MySQL and Tomcat from
the MOREnet distributions, do not select this component. Your MySQL
database has already been configured to work with Tomcat.
The Create WebPublish Directory component creates a
a C:\WebPublish\localdev directory for web applications,
web site files, and log files. If this directory already exists on
your system from a previous installation, do not select this component.
Click Next when you are finished selecting components.
- The installer displays the directory where Tomcat will be installed.
To install to a different directory, click Browse and select
a different location. Click Install to begin the installation.
Note: If you selected the NT Service option, you may notice
three command prompt windows very quickly appear and disappear during the
installation. Do not be alarmed by this behavior. These appear during
the installation of the three Tomcat services that are included in this
installation.
- If you selected the Configure MySQL for Tomcat component, a
message appears that you should start MySQL before you proceed. If you
did not select this component, continue to the step below that details
the Tomcat Configuration Options window.
- Start MySQL if it isn't already started and then click OK.
- The Configure MySQL for Tomcat window displays with various
options. These settings are detailed in the steps that follow.
- Specify the directory where you installed MySQL in the
MySQL Home Directory option. The default value, C:\mysql,
should be correct. If this isn't correct, you can click the "..." button
and select the directory.
- Specify the password for the 'root' account in MySQL within the
'root' MySQL Password option. This is the password that you specified
for the 'root' account during the MySQL installation. Refer to your
records if you can't remember it.
- Specify the password for the 'localrealm' account in MySQL within the
'localrealm' MySQL Password option. This is a new account in MySQL that
will be used by Tomcat to access your MySQL database for authenticating users
that have access to the Tomcat Manager. Type a secure password in this
option and then document this password with the other MySQL passwords that
you keep in a safe place.
- Specify a Tomcat Manager User Name and Tomcat Manager
Password. This is the user name and password that you will use to
access Tomcat's Manager web application. You can specify any name
and password that you like. Beware that you should select
a secure password so that others cannot access the Tomcat Manager.
Document the name and password and keep them in a safe place.
- Click Next when you are done with the configuration options.
- The Tomcat Configuration Options window displays with various
options. These settings are detailed in the steps that follow.
- Specify a value for the SMTP Host option.
This option defines the host name of an SMTP server that can deliver
e-mail generated by your web applications. To find the value for this
option, review your e-mail client settings for the name of your SMTP
host. Note that some e-mail clients refer to this as the
"Server Name", "Outgoing Mail Server", or "Outgoing Server" option.
If you are unsure what SMTP host you can use, discuss this with your
system administrator.
- Specify a value for the User ID option.
This is another option related to the delivery of e-mail generated by
your web applications. Review your e-mail client settings for this value.
Note that some e-mail clients do not display this setting. If you are
unsure what value to specify, it is usually appropriate to use the
first part of your e-mail address setting. For example, if your e-mail
address is
johndoe1@somehost.org,
specify johndoe1 in this option.
- Specify a value for the E-mail Address option.
This is another option related to the delivery of e-mail generated by
your web applications. The value of this option is the e-mail address
that the "reply-to" header is set to in the generated e-mail messages.
Review your e-mail client settings for your e-mail address and type this
value so you will receive any replies to generated e-mail messages.
- Specify the password for the 'localweb' account in MySQL within the
'localweb' MySQL Password option. This password is used
used by the JNDI resource that is available to your web applications
for database access. You specified this password during your MySQL
installation. Refer to your records if you can't remember it.
- Specify the password for the 'localrealm' account in MySQL within the
'localrealm' MySQL Password option. This is the same password that
you specified in the previous option window. If you did not select the
the Configure MySQL for Tomcat installation component, this is the
password that you previously set for this account during a previous
installation of Tomcat. Refer to your records if you can't remember it.
- Click Next when you are done with the configuration options.
- When the installation is complete, click Close.
- You may delete the Tomcat installation file that you
saved to a temporary location to save space on your hard drive.
Starting and Stopping Tomcat
The MOREnet distribution of Tomcat includes shortcuts to start and
stop Tomcat. Click Start, Programs, Apache Tomcat 4.1 to see these
shortcuts.
Note: The first time you start Tomcat, there will be a notable
delay before Tomcat will respond to HTTP requests. This occurs the
first time that Tomcat runs as it expands and sets up all of the
web applications included with this distribution. Thereafter, startup
time will be minimal.
Starting and Stopping Tomcat in a Command Prompt Window
(Windows 95, Windows 98, and Windows ME)
The following shortcuts start and stop Tomcat in an MS-DOS command prompt
window using batch files. You may use these shortcuts on any system. However,
these are primarily for the systems indicated above that do not support
running Tomcat as an NT service. Running Tomcat in an MS-DOS command prompt
window results in slower performance compared to Tomcat running as an NT
service.
Click Start, Programs, Apache Tomcat 4.1, Control Tomcat Batch to see
the following shortcuts:
- Start Tomcat Batch No Security. This shortcut starts Tomcat
without the SecurityManager in an MS-DOS command prompt
window. MOREnet does not recommend that you run Tomcat without
the SecurityManager. This shortcut is included so that you can
temporarily run Tomcat without the SecurityManager in case you are
debugging what may be a security-related problem.
- Start Tomcat Batch Security
(Recommended).
This shortcut starts Tomcat with the SecurityManager in an MS-DOS
command prompt window. Security debug information is not included
in the logs. You should run Tomcat with this shortcut under most
conditions.
- Start Tomcat Batch Security with SecurityDebug. This
shortcut starts Tomcat with the SecurityManager in an MS-DOS
command prompt window. Security debug information is included in
the logs. You should run Tomcat with this shortcut if you are
debugging problems with your security policy.
- Stop Tomcat Batch. This shortcut stops Tomcat if it was
started with any of the shortcuts listed above.
Starting and Stopping Tomcat as an NT Service
(Windows XP, Windows 2000, Windows NT)
The following shortcuts start and stop the Tomcat NT services. If you
selected the NT Service component during installation, three Tomcat services
were installed on your system for starting Tomcat. These services start Tomcat
in specific configurations just like the batch file shortcuts. Note that
unlike the batch file shortcuts where there is one "Stop" shortcut, each
shortcut for starting an NT service has a corresponding shortcut for
stopping the service.
Click Start, Programs, Apache Tomcat 4.1, Control Tomcat Service
to see the following shortcuts:
- Start Tomcat Service No Security. This shortcut starts
Tomcat as a service without the SecurityManager. MOREnet does not
recommend that you run Tomcat without the SecurityManager. This
shortcut is included so that you can temporarily run Tomcat without
the SecurityManager in case you are debugging what may be a
security-related problem. Stop this service with the
Stop Tomcat Service No Security shortcut.
- Start Tomcat Service Security
(Recommended). This shortcut starts
Tomcat as a service with the SecurityManager. Security debug
information is not included in the logs. You should run Tomcat
with this shortcut under most conditions. Stop this service with
the Stop Tomcat Service Security shortcut.
- Start Tomcat Service Security with SecurityDebug. This
shortcut starts Tomcat as a service with the SecurityManager.
Security debug information is included in the logs. You should
run Tomcat with this shortcut if you are debugging problems with
your security policy. Stop this service with the
Stop Tomcat Service Security with SecurityDebug shortcut.
Important: Only run one of these services at a time. Running
multiple Tomcat services simultaneously will result in unpredictable
responses to HTTP requests.
The Tomcat services are configured with Startup Type settings of
manual so that you must manually start the services when you want them
to run. They will not run automatically when your system is started. You can
change these settings, as well as start and stop the services, with tools
available on your system. To see your system's services and change the
Startup Type settings, do the following:
- In Windows 2000, select Start, Settings, Control Panel and
then select Administrative Tools. Within the Administrative
Tools window, select Services. Right-click the service
name and then select Properties. Change the Startup Type
option to Automatic.
- In Windows NT, select Start, Settings, Control Panel and
then select Services. Click the service name in the list
to highlight it and then click the Startup...
button. Change the Startup Type option to Automatic.
Reviewing the Example Web Applications
If you selected to install the example web applications, you'll find
the source files in the C:\WebPublish\localhost\www
directory. This directory structure is analogous to the directory
structure on a production server. As discussed in the
Web Application Design Guidelines document, web
application archive files (.war) and web application directories coexist
with your web site content in the www directory. If you install
a web application with the Tomcat Manager, it is copied to the www
directory and Tomcat unarchives the application into a directory with
the same name as the .war file. For more information about
web applications, see the Web Applications
section on the kinetic Resources web site.
To run the examples, visit the URLs below in your web browser:
- http://localhost:8080/examples/jsp/
- http://localhost:8080/examples/servlets/
- http://localhost:8080/morenet/
- http://localhost:8080/tomcat-docs/
Configuring and Using the Tomcat Manager
Tomcat includes a Tomcat Manager web application that allows you to
administer Tomcat from your web browser. Its abilities are well documented
in the documentation installed with Tomcat. If Tomcat is running on your
system, visit http://localhost:8080/manager/html-manager-howto.html and review the documentation.
During the installation of Tomcat, you specified a user name and password
to access the Tomcat Manager. The settings you specified were added to your
MySQL local_realm database tables so that Tomcat can authenticate
your access to the Tomcat Manager.
You can add additional user names or modify your current user name
and password. To do this, you must insert or update information in the
users and user_realm tables in the local_realm database.
The two commands shown below insert database records for another user that
can access the Tomcat Manager. Note that you must change
{someusername} to the username you want to use and change
{password} to a secure password.
INSERT INTO user_roles VALUES ('{someusername}','manager','');
INSERT INTO users VALUES ('{someusername}',MD5('{password}'),'');
To access the Manager on your system, visit the following URL. When the
window prompts for a user name and password, type the values you specified
during the installation.
http://localhost:8080/manager/html/
Important: The MOREnet distribution of Tomcat includes a context in
conf/server.xml that restricts access to the Manager
to the localhost system. This added measure of security prevents users
on the Internet from using your Tomcat Manager even if they know your
user name and password. If you frequently need to access the Manager
from a different system, you can add that system's IP address to the
context configuration for the Manager. To do this, find the following
line in conf/server.xml and add that system's IP address to
the value of the Allow attribute. Each IP address that you add must be
separated with a comma. Note that the 127.0.0.1 value
is a reserved IP address that represents the local system.
<Valve className="org.apache.catalina.valves.RemoteAddrValve"
allow="127.0.0.1" />
Reviewing Your Tomcat Logs
As you run the example web applications and begin working on your
own applications, you may trigger errors that throw exceptions in Tomcat.
Tomcat's error logs are excellent resources for troubleshooting
errors.
Unlike logic errors that produce unintended results, you may encounter
translation-related problems in your JSPs or the
generated Java files, or resource-related problems that prevent
your JSPs from compiling and/or running at request-time. Information
about these types of errors is typically displayed in your web browser
window. However, the logs provide additional information from Tomcat and
the Java SDK that is not provided in the results that are returned to the
web browser window.
If you explore the C:\WebPublish\locahost\tomcat\logs directory,
you'll see these files (after adding applications, you may see more):
- catalina_log.<date>.txt
- localhost_log.<date>.txt
- stderr.log
Start troubleshooting by reviewing the stderr.log file
and the output in the MS-DOS Prompt window. If you are running Tomcat
as an NT service, an additional log file named stdout.log
will contain the information that is typically shown in an MS-DOS window.
Note: You must stop Tomcat before you can open the
log files with WordPad. If Tomcat is running, it is possible to open the
log files with NotePad since NotePad does not check to see if the opened
file is in use. Do not save the file to itself, however, as this will
overwrite any new information added to the log file since you opened
it.
If you don't find an error listed in these files, proceed to the other
logs. All of the logs are text files, so you can view them with Notepad or
Wordpad. Note that most of the log files have a name that includes the
date.
Important: The log files will be rotated daily as you use
Tomcat. You may want to occasionally delete the old logs to free up
space on your system. You may also want to delete the current
day's logs as you try to debug errors in your applications. New
errors are easier to find in a "fresh" log file.
Additional Security Permissions
If you run Tomcat with Security, your Tomcat installation
is configured to only accept requests from the localhost
(i.e., the computer where Tomcat is running). You can develop
JSP applications and test them in this configuration without
worrying about other users accessing your applications.
However, you may find that you would like to allow access for other
computers on your network, such as another computer that you use or
a colleague's computer. To do this, follow this procedure:
- Stop Tomcat.
- Double-click on My Computer or use Windows Explorer to view your
computer's file system.
- Open the conf directory in your Tomcat installation.
- Double-click on the catalina.policy file to open it.
catalina.policy is a text file, but most systems
will not be configured to open files with this extension. Windows
will prompt you to select the appropriate application and you may
select Wordpad from the list of applications.
- When Wordpad displays the file, look for the following line:
permission java.net.SocketPermission "localhost:8009", "listen";
This permission allows your local system to connect with the Apache web
server.
Note: There is more than one occurence of this line in the file;
the following steps must be performed for each occurence.
- Copy the following line:
permission java.net.SocketPermission "{xxx.xxx.xxx.xxx}:1024-", "listen";
- Paste a copy of the above line directly underneath the
"localhost:8009" line in the catalina.policy file.
- Replace the
{xxx.xxx.xxx.xxx} portion with the IP address
of the computer that needs access to your system.
- When you are done, your changes will look like the following example:
permission java.net.SocketPermission "localhost:8009", "listen";
permission java.net.SocketPermission "xxx.xxx.xxx.xxx:1024-", "listen";
- You may add as many of these sets of permissions as you need for each
computer you want to be able to connect to your Tomcat server.
Unfortunately, you cannot specify a range of IP addresses by using a
partial IP address or wildcard character. Remember that the above steps
must be followed after each occurence of the
"localhost:8080" line.
- Save the catalina.policy file.
- Restart Tomcat to use your new security permissions.
- The other systems that you've allowed access to your computer must specify
a specially formatted URL in their web browsers to access your Tomcat.
Other users must specify the following URL and replace the
{xxx.xxx.xxx.xxx} portion with your system's IP address:
http://{xxx.xxx.xxx.xxx}:8080/
Configuring Tomcat for JNDI Resources
Tomcat can use JNDI resources (Java Naming and Directory Interface
resources) for many applications. JNDI allows the web application developer
to abstract the actual details of the connection to a resource such that
the application only needs the name of the resource to use it. This greatly
increases portability of a web application and simplifies development.
Configuring a JNDI Resource for the MySQL Database Server
When you installed Tomcat, a JNDI resource for MySQL database connections
was automatically set up with information you provided. The details
for manually setting up this resource are included in case you must modify
the settings.
- Open the conf directory in your Tomcat installation.
- Use WordPad to open the server.xml file.
- Locate the following lines within this file:
<!-- JNDI JDBC DataSource Resource for using MySQL dB -->
<Resource name="jdbc/data" auth="CONTAINER"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/data">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter>
<name>username</name>
<value>localweb</value>
</parameter>
<parameter>
<name>password</name>
<value>somepassword</value>
</parameter>
- Change the value for the password to the password you
created for the localweb user name during the MySQL installation.
- For this change to be applied, you must stop and restart Tomcat.
- The Tomcat server can now connect to a local MySQL database
server (if it is installed). When it connects, Tomcat will use the
username localweb and the password you specified to access
MySQL on the localhost. The web applications you create do not
need this information since Tomcat handles the actual connection
to the database. Your web applications only need to know the name
of the defined JNDI resource. This name is
java:/comp/env/jdbc/data. This is the same resource
name used by applications you develop when they are transferred to a
MOREnet production server.
The MOREnet example web application uses this JNDI resource.
The example uses the Java Standard tag library (JSTL) to access and
display the contents of a local MySQL database. If you have Tomcat
and MySQL installed, visit
http://localhost:8080/morenet/
to see the example web application.
Configuring a JNDI Resource for Sending Mail
When you installed Tomcat, a JNDI resource for sending mail
was automatically set up for you with information you provided. The details
for manually setting up this resource are included in case you must modify
the settings.
- Open the conf directory in the location where you installed
Tomcat.
- Use WordPad to open the server.xml file.
- Locate the following lines within this file:
<!-- JNDI Resource for sending email using SMTP -->
<Resource name="mail/send" auth="CONTAINER"
type="javax.mail.internet.MimePartDataSource"/>
<ResourceParams name="mail/send">
<parameter><name>factory</name>
<value>org.apache.naming.factory.SendMailFactory</value>
</parameter>
<parameter><name>mail.smtp.host</name>
<value>smtp.host</value>
</parameter>
<parameter><name>mail.smtp.user</name>
<value>userid</value>
</parameter>
<parameter><name>mail.from</name>
<value>userid@mail.host</value>
</parameter>
</ResourceParams>
- Edit the <value>smtp.host</value> line.
Change the value to the name of your SMTP mail host. The value
must be the name of a host that sends mail for your account.
- Edit the <value>userid</value> line.
Change the value to the userid you use for sending and receiving mail.
This is the first part of the e-mail address, such as
johndoe1 for the johndoe1@somehost.org account.
- Edit the <value>userid@mail.host</value> line.
Change the value to the return e-mail address (the 'From' field)
you want to appear in e-mail messages that are sent.
- Save these changes and exit.
- Next, use WordPad to open the catalina.policy file.
- Replace all occurances of smtp.host throughout this
file with the name of your SMTP mail host. For example, if your mail
host's name is
mail.somehost.net, then the
permissions like the following:
// Permission to send email via SMTP - (permission to connect to mail server).
permission java.net.SocketPermission "smtp.host:25", "connect,resolve" ;
should be modified to this:
// Permission to send email via SMTP - (permission to connect to mail server).
permission java.net.SocketPermission "mail.somehost.net:25", "connect,resolve" ;
- Save these changes and exit.
- For these settings to be applied, stop and restart Tomcat.
- The Tomcat server can now send e-mail. When it
sends a message, it will send it as if it was the
username you entered, and will send the mail via the SMTP host you
specified. The web applications you create will not need this information
since Tomcat will handle the processing. Your web apps
only need to know the name of the defined JNDI resource. This resource is
named java:/comp/env/mail/send. This will be the same
resource name used by applications you develop when they are
transferred to the MOREnet production server.
The MOREnet example web application uses this JNDI resource.
The example uses the Java Standard tag library (JSTL) and the Mailer
tag library from the Jakarta
project to send e-mail from a web form. Visit
http://localhost:8080/morenet/
to see the example web application.
Modifying the Location of Logs and Web Applications
As discussed in the Reviewing the Example Web
Applications and Reviewing Your Tomcat Logs sections,
the MOREnet distribution of Tomcat is configured so that your web
applications are served from the C:\WebPublish\localhost\www
directory and your Tomcat log files are stored in the
C:\WebPublish\localhost\tomcat\logs directory.
In addition, Tomcat uses the C:\WebPublish\localhost\tomcat\work
directory to store its work files. This directory
structure is analogous to the directories you must navigate on a
production server. Although this structure is used by default, it is
not mandatory that you continue to use this exact directory structure
or have it located on the C: drive. You can modify the locations
of your web applications and logs in the Tomcat configuration.
Caution: If you modify the directory structure, you may
accidentally modify the behavior of Tomcat and how it works with
Apache. In addition, changing the directory structure will make
your local development environment unlike the structure on
production servers and this may cause confusion.
MOREnet advises that if you must change the locations of logs
and web applications, refrain from modifying the directory
structure and only change the drive. You can copy the
existing C:\WebPublish directory structure
to another drive to maintain it, and then follow the directions
below. By doing this, you only need to change the referenced drive
letters of C: to the new drive.
Important: Before you make any changes to a file, save
a backup copy in case you need to use it again.
Follow these steps:
- Stop Tomcat if it is currently running.
- Open your Tomcat installation's conf\sever.xml in a
text editor and search for "WebPublish". In each location
where you find "WebPublish", modify the path to point to
the location you want to use. When you are finished editing,
save the file.
- Open conf\catalina.policy in a text editor and search
for "WebPublish". In each location where you find "WebPublish",
modify the path to point to the location you want to use.
Note the special format of each line where directories
are separated by the ${/} characters.
Do not change this format. When you are finished
editing, save the file.
- If you are not running Tomcat as an NT service, you are
finished and you can restart Tomcat. If you are running
Tomcat as an NT service, continue to the next step.
- Open an MS-DOS command prompt window and navigate to the
bin directory of your Tomcat installation.
- Uninstall the existing services by typing each command line
below, one at a time, and pressing Enter.
tomcat.exe -uninstall "Apache Tomcat 4.1 Nosecurity"
tomcat.exe -uninstall "Apache Tomcat 4.1 Security"
tomcat.exe -uninstall "Apache Tomcat 4.1 Securitydebug"
- Reinstall the services by typing each command line below,
one at a time, and pressing Enter. In each line,
replace {path to jvm.dll} with the complete pathname
to the jvm.dll file in your Java SDK. This is typically
{java SDK}\jre\bin\hotspot\jvm.dll, where you replace
{java SDK} with the path to your SDK installation
directory. Also modify the paths that specify
"WebPublish" with the new paths that you want to use.
Although each of the three command lines appear as
multiple lines below, each line should be entered in the
command prompt window as a single line. You may want to edit
each line in a text editor first, and then copy and paste each
line into the command prompt window.
tomcat.exe -install "Apache Tomcat 4.1 Security" "{path to jvm.dll}" -Djava.class.path="C:\Program Files\Apache Group\Tomcat 4.1\bin\bootstrap.jar" -Dcatalina.home="C:\Program Files\Apache Group\Tomcat 4.1" -Djava.endorsed.dirs="$C:\Program Files\Apache Group\Tomcat 4.1\bin;C:\Program Files\Apache Group\Tomcat 4.1\common\endorsed" -Djava.security.debug=none -Djava.security.manager -Djava.security.policy="C:\Program Files\Apache Group\Tomcat 4.1\conf\catalina.policy" -start org.apache.catalina.startup.Bootstrap -params start -config "C:\Program Files\Apache Group\Tomcat 4.1\conf\server.xml" -stop org.apache.catalina.startup.Bootstrap -params stop -out "C:\WebPublish\localhost\tomcat\logs\stdout.log" -err "C:\WebPublish\localhost\tomcat\logs\stderr.log"
tomcat.exe -install "Apache Tomcat 4.1 Securitydebug" "{path to jvm.dll}" -Djava.class.path="C:\Program Files\Apache Group\Tomcat 4.1\bin\bootstrap.jar" -Dcatalina.home="C:\Program Files\Apache Group\Tomcat 4.1" -Djava.endorsed.dirs="C:\Program Files\Apache Group\Tomcat 4.1\bin;C:\Program Files\Apache Group\Tomcat 4.1\common\endorsed" -Djava.security.debug="access,failure" -Djava.security.manager -Djava.security.policy="C:\Program Files\Apache Group\Tomcat 4.1\conf\catalina.policy" -start org.apache.catalina.startup.Bootstrap -params start -config "C:\Program Files\Apache Group\Tomcat 4.1\conf\server.xml" -stop org.apache.catalina.startup.Bootstrap -params stop -out "C:\WebPublish\localhost\tomcat\logs\stdout.log" -err "C:\WebPublish\localhost\tomcat\logs\stderr.log"
tomcat.exe -install "Apache Tomcat 4.1 Nosecurity" "{path to jvm.dll}" -Djava.class.path="C:\Program Files\Apache Group\Tomcat 4.1\bin\bootstrap.jar" -Dcatalina.home="C:\Program Files\Apache Group\Tomcat 4.1" -Djava.endorsed.dirs="C:\Program Files\Apache Group\Tomcat 4.1\bin;C:\Program Files\Apache Group\Tomcat 4.1\common\endorsed" -start org.apache.catalina.startup.Bootstrap -params start -config "C:\Program Files\Apache Group\Tomcat 4.1\conf\server.xml" -stop org.apache.catalina.startup.Bootstrap -params stop -out "C:\WebPublish\localhost\tomcat\logs\stdout.log" -err "C:\WebPublish\localhost\tomcat\logs\stderr.log"
- Your changes are now complete. You may restart Tomcat.
|
