Show Table of Contents
4.5. Running Enterprise Web Server
After the installation is complete, you can run the required Enterprise Web Server components.
4.5.1. Running Tomcat
Tomcat can be run either in the foreground as a program or in the background as a service.
Important
We strongly recomend to run tomcat as a service (see Section 4.5.1.2, “Running Tomcat as a Service”). Note that this is the only supported running method.
4.5.1.1. Running Tomcat as a Program
If you want to run Tomcat as a program, use either the
tomcat[6,7] script in the sbin directory or the catalina script in the lib directory:
- To start Tomcat with the tomcat script, run the following command as the root user with the respective Tomcat version (
6or7):/opt/jboss-ews-2.1/sbin/tomcat<VERSION> start
The system reads the configuration file and changes to the user and group of the tomcat user account (that is, Tomcat is always run under the tomcat user). By default,tomcat-nativeis automatically added to theLD_LIBRARY_PATHand-Djava.library.pathduring Tomcat startup. - To start Tomcat with the
catalina.shscript, run the following command with the respective Tomcat version (6or7) :/opt/jboss-ews-2.1/share/tomcat<VERSION>/bin/catalina.sh
Thecatalina.shscript detects the running JVM version and adds the/opt/jboss-ews-2.1/lib/path (/opt/jboss-ews-2.1/lib64for 64 bit JVM) to the library path.
4.5.1.2. Running Tomcat as a Service
To run Tomcat as a service with
jsvc:
- In Tomcat 6, use the script
daemon.shlocated in/opt/jboss-ews-2.1/share/apache-tomcat-6.x/bin/. - In Tomcat 7, use the script
daemon.shlocated in/opt/jboss-ews-2.1/share/apache-tomcat-7.x/bin/.
To run Tomcat as a service, use
scm as follows:
Procedure 4.9. Use SCM to Run Tomcat as a Service
- At the shell prompt, become the
rootuser. - Create a new file named
tomcat.xmlat the location/var/svc/manifest/application/web/. - Copy and paste the following contents into the newly created
tomcat.xmlfile.<?xml version='1.0'?> <!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'> <!-- Service manifest for Apache Tomcat --> <service_bundle type='manifest' name='tomcat6:tomcat6'> <service name='network/tomcat6' type='service' version='1'> <create_default_instance enabled='false' /> <single_instance /> <dependency name='fs' grouping='require_all' restart_on='none' type='service'> <service_fmri value='svc:/system/filesystem/local' /> </dependency> <dependency name='net' grouping='require_all' restart_on='none' type='service'> <service_fmri value='svc:/network/loopback' /> </dependency> <exec_method type='method' name='start' exec='/opt/jboss-ews-2.0/sbin/tomcat6 start' timeout_seconds='-1'> </exec_method> <exec_method type='method' name='stop' exec='/opt/jboss-ews-2.0/sbin/tomcat6 stop' timeout_seconds='-1'> </exec_method> <exec_method type='method' name='restart' exec='/opt/jboss-ews-2.0/sbin/tomcat6 restart' timeout_seconds='-1'> </exec_method> </service> </service_bundle> - Run the following command to import the new file:
# /usr/sbin/svccfg import /var/svc/manifest/application/web/tomcat.xml
- Use the following command to start tomcat:
# /usr/sbin/svcadm enable tomcat6
For further information about Jsvc, see the About Jsvc chapter of the HTTP Connectors and Load Balancing Guide .

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.