Home TOC Index

Running admintool

The admintool Web application can be used to manipulate Tomcat while it is running. For example, you can add a context or set up users and roles for container-managed security.

To start admintool, follow these steps.

1. Start Tomcat by calling its startup script from the command line, as follows:

     <JWSDP_HOME>/bin/startup.sh        (Unix platform)
    
     <JWSDP_HOME>\bin\startup           (Microsoft Windows)
    
   

2. Start a Web browser.
3. In the Web browser, point to the following URL:

     http://localhost:8080/admin
    
   

   This command invokes the Web application with the context of admin.

4. Log in to admintool using the user name and password combination defined when you installed the Java WSDP.

   This user name and password combination is assigned the roles of admin, manager, and provider by default. To use admintool, you must log in with a user name and password combination that has been assigned the role of admin. This user name and password must match the user name and password in the build.properties file (read Creating the Build Properties File for more information on the build.properties file).

   If you've forgotten the user name and password, you can find them in the file <JWSDP_HOME>/conf/tomcat-users.xml, which is viewable with any text editor. This file contains an element <user> for each individual user, which might look something like this:

     <user name="your_name" password="your_password" 
     roles="admin, manager,provider" />
    
   

The admintool Web application displays in the Web browser window:

Figure A-1   The Tomcat Server Administration Tool

5. Perform Tomcat Web Server Administration tasks.

   After you have made changes to Tomcat, select the Save button on that page to save the attributes for the current Tomcat process. Select the Commit Changes button to write the changes to the <JWSDP_HOME>/conf/server.xml file so that the changes to the Tomcat server are persistent and will be retrieved when Tomcat is restarted.

   The previous version of server.xml is backed up in the same directory, with an extension indicating when the file was backed up, for example, server.xml.2002-06-15.12-11-54. To restore a previous configuration, shut down Tomcat, rename the file to server.xml, and restart Tomcat.

6. Log out of admintool by selecting Log Out when you are finished.
7. Shut down Tomcat by calling its shutdown script from the command line, as follows:

     <JWSDP_HOME>/bin/shutdown.sh        (Unix platform)
    
     <JWSDP_HOME>\bin\shutdown           (Microsoft Windows)
    
   

This document contains information about using admintool to configure the behavior of Tomcat. For more information on these configuration elements, read the Tomcat Configuration Reference, which can be found at <JWSDP_HOME>/docs/tomcat/config/index.html.

This document does not attempt to describe which configurations should be used to perform specific tasks. For information of this type, refer to one of the following documents:

• Class Loader How-To. This document discusses decisions that application developers and deployers must make about where to place class and resource files to make them available to Web applications. This document can be found at <JWSDP_HOME>/docs/tomcat/class-loader-howto.html.
• JNDI Resources How-To. This document discusses configuring JNDI Resources, Tomcat Standard Resource Factories, JDBC Data Sources, and Custom Resource Factories. This document can be found at <JWSDP_HOME>/docs/tomcat/jndi-resources-howto.html.
• Manager Application How-To. This document describes using the Manager Application to deploy a new Web application, undeploy an existing application, or reload an existing application without having to shut down and restart Tomcat. This document can be found at <JWSDP_HOME>/docs/tomcat/manager-howto.html.
• Proxy Support How-To. This document discusses running behind a proxy server (or a web server that is configured to behave like a proxy server). In particular, this document discusses how to manage the values returned by the calls from Web applications that ask for the server name and port number to which the request was directed for processing. This document can be found at <JWSDP_HOME>/docs/tomcat/proxy-howto.html.
• Realm Configuration How-To. This document discusses how to configure Tomcat to support container-managed security by connecting to an existing database of user names, passwords, and user roles. This document can be found at <JWSDP_HOME>/docs/tomcat/realm-howto.html.
• Security Manager How-To. This document discusses the use of a SecurityManager while running Tomcat to protect your server from unauthorized servlets, JSPs, JSP beans, and tag libraries. This document can be found at <JWSDP_HOME>/docs/tomcat/security-manager-howto.html.
• SSL Configuration How-To. This document discusses how to install and configure SSL support on Tomcat. Configuring SSL support on Tomcat using Java WSDP is discussed in Installing and Configuring SSL Support on Tomcat. The Tomcat documentation at <JWSDP_HOME>/docs/tomcat/ssl-howto.html also discusses this topic, however, the information in this tutorial is more up-to-date for the version of Tomcat shipped with the Java WSDP.

Home TOC Index

This tutorial contains information on the 1.0 version of the Java Web Services Developer Pack.

All of the material in The Java Web Services Tutorial is copyright-protected and may not be published in other works without express written permission from Sun Microsystems.