Next: EDG Java Security Reconfiguration
Up: Configuration and Running
Previous: LCFG Configuration
The EDG Java Security Tomcat RPM provides an init.d script
to easily start and stop the Tomcat service and to manage the service
proxy.
By the end of the manual or the LCFG configuration the init script
is linked into /etc/init.d/edg-tomcat4. In order to prevent
accidental startup of the original tomcat4 script you need
to reconfigure the system:
chkconfig --del tomca4
chkconfig --add edg-tomcat4
From this point you may use either
${EDG_LOCATION}/etc/init.d/edg-tomcat4 <command>
or
service edg-tomcat4 <command>
commands to manipulate
the Tomcat server.
To start the service (as root):
${EDG_LOCATION}/etc/init.d/edg-tomcat4 start
will create the service proxy from the hostkey, create the
/etc/tomcat4/server.xml file from the contents of the
$EDG_LOCATION_VAR/etc/server.xml.d/ directory,
and then start the Tomcat server. Note that:
- The server will be run as tomcat4:tomcat4.
- The contents of the $EDG_LOCATION_VAR/etc/server.xml.d/ directory
are used to build the server.xml file. Each file in that directory should contain
one <Service> block, describing the port, security parameters and the webapps base.
In the current deployment model, there is only one secure webapps, defined on a specific port
(8443 by default), and one non-secure webapps (on 8080), therefore only two files are used in the
$EDG_LOCATION_VAR/etc/server.xml.d/ directory.
- If a previous server.xml exists, it will be backed up to
/etc/tomcat4/server.xml.bak. You should not edit the new server.xml
file. Instead you should use the reconfiguration method as described below, or edit the
contents of the $EDG_LOCATION_VAR/etc/server.xml.d/ directory.
The server.xml file is rebuilt every time Tomcat is started (although the
backup of the old file only happens once).
- The service's logs (both Tomcat itself, EDG Java Security, and any particular servlet logs) are
written into /var/tomcat4/logs/.
To stop the service:
${EDG_LOCATION}/etc/init.d/edg-tomcat4 stop
Note that the proxy is not deleted upon stop.
To explicitly delete the proxy:
${EDG_LOCATION}/etc/init.d/edg-tomcat4 proxy-destroy
To renew the proxy manually:
${EDG_LOCATION}/etc/init.d/edg-tomcat4 proxy
To restart the service:
${EDG_LOCATION}/etc/init.d/edg-tomcat4 restart
Next: EDG Java Security Reconfiguration
Up: Configuration and Running
Previous: LCFG Configuration
2004-07-02