Red Hat Summit Red Hat SummitSupportoConsoleSviluppatoriInizia una provaContatti

Questo contenuto non è disponibile nella lingua selezionata.

Release Notes

Red Hat JBoss Web Server 1.0

for Use with Red Hat JBoss Web Server 1.0.0

Isaac Rooskov

Copyright © 2009 Red Hat, Inc

Abstract

These release notes contain important information related to Red Hat JBoss Web Server 1.0.0. You should read these Release Notes in their entirety before installing Red Hat JBoss Web Server 1.0.0.

1.  Introduction
Copia collegamento

These release notes contain important information related to JBoss Enterprise Web Server 1.0.0. New features, known problems, resources, and other current issues are addressed here.

1.1. Overview
Copia collegamento

JBoss Enterprise Web Server is a fully integrated and certified set of components for hosting Java web applications. It is comprised of the industry's leading Web Server (Apache HTTP Server), the popular Apache Tomcat Servlet container as well as the mod_jk connector and the Tomcat Native library. This release of the JBoss Enterprise Web Server consists of the following components :
  • Apache Tomcat 5.5.23: Apache Tomcat is an implementation of the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. Apache Tomcat version 5.5 implements the Servlet 2.4 and JavaServer Pages 2.0 specifications.

    Note

    Apache Tomcat 5.5.23 is available within the default Red Hat Enterprise Linux 5 installation.
  • Apache Tomcat 6.0.18: Apache Tomcat is an implementation of the Java Servlet and JavaServer Pages technologies. The Java Servlet and JavaServer Pages specifications are developed by Sun under the Java Community Process. Apache Tomcat version 6.0 implements the Servlet 2.5 and JavaServer Pages 2.1 specifications.
  • Apache Tomcat Native 1.1.16: Tomcat can use the Apache Portable Runtime to provide superior scalability, performance, and better integration with native server technologies. The Apache Portable Runtime is a highly portable library that is at the heart of Apache HTTP Server 2.x. APR has many uses, including access to advanced IO functionality (such as sendfile, epoll and OpenSSL), OS level functionality (random number generation, system status, etc), and native process handling (shared memory, NT pipes and Unix sockets). This package contains the Tomcat native library which provides support for using APR in Tomcat.
  • Apache Tomcat Connector (mod_jk) 1.2.27: Apache Tomcat Connector (mod_jk) is bridge between Apache Httpd and Apache Tomcat using binary AJP protocol. It also contains load balancer providing clustering and fault tolerance.
  • Apache HTTP Server 2.2.10: The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards.

    Note

    The Apache HTTP Server 2.2.10 is available within the default Red Hat Enterprise Linux 5 installation.
This release of JBoss Enterprise Web Server is certified for the following Operating Systems :
  • Red Hat Enterprise Linux 4 (32-bit systems, 64-bit systems)
  • Red Hat Enterprise Linux 5 (32-bit systems, 64-bit systems)
  • Solaris 9 (32-bit systems)
  • Solaris 10 (32-bit systems, 64-bit systems)

2. Installation Notes
Copia collegamento

This section contains information related to installing JBoss Enterprise Web Server version 1.0.0, including hardware and platform requirements and prerequisites.

2.1. Installation Notes for Red Hat Enterprise Linux
Copia collegamento

The preferred method for installing the Red Hat Enterprise Web Server on Red Hat Enterprise Linux is by using the Red Hat Enterprise Linux rpm file; however we will also discuss installation via the zip package.
You must have adequate disk space to install JBoss Enterprise Web Server while also allowing enough space for your applications.
A working, supported installation of Java 1.5 or 1.6 on your system will also be necessary. On Red Hat Enterprise Linux 4 systems subscribed to the Extras channel, this can be achieved by executing: 
up2date java-<version>-<vendor>
Copy to Clipboard Toggle word wrap
Where <version> can be 1.5.0 or 1.6.0 and <vendor> can be sun or ibm.
On Red Hat Enterprise Linux 5 systems, this can be achieved by executing: 
yum install java-<version>-<vendor>
Copy to Clipboard Toggle word wrap
Where <version> can be 1.5.0 or 1.6.0 and <vendor> can be sun, ibm or openjdk. Please note that OpenJDK is only available for version 1.6.0.
Once the Java SDK has been installed, please check to make sure the desired JDK is chosen by executing the following: 
alternatives --config java
alternatives --config javac
Copy to Clipboard Toggle word wrap
If the JDK in use is not the desired option, the above commands can be used to switch to another JDK.

Important

By switching alternatives for the Java JDK for Tomcat, other software that makes use of the java and javac commands will now be using the same JDK as well.
JBoss Enterprise Web Server can either be installed via the Red Hat Network (RHN) or the JBoss Customer Support Portal (CSP).
Installing via RHN

  1. If you are subscribed to the Stacks channel, you will need to disable that channel before installing the JBoss Enterprise Web Server.
  2. Subscribe to the JBoss Enterprise Web Server channel: Red Hat Enterprise Linux 4 ews or Red Hat Enterprise Linux 5 ews
    The avaliable channels for Red Hat Enterprise Linux 4 are:
    • jb-ews-1-i386-as-4-rpm
    • jb-ews-1-64-bit systems-as-4-rpm
    • jb-ews-1-i386-es-4-rpm
    • jb-ews-x86_64-es-4-rpm
    The avaliable channels for Red Hat Enterprise Linux 5 are:
    • jb-ews-1-i386-server-5-rpm
    • jb-ews-1-x86_64-server-5-rpm
  3. Install the packages: tomcat5, tomcat6, tomcat-native, httpd22 and mod_jk
    On Red Hat Enterprise Linux 4 to install the packages, execute: 
    up2date tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5 tomcat5-webapps tomcat5-admin-webapps ecj tomcat-native httpd22 mod_jk-ap20
    Copy to Clipboard Toggle word wrap
  4. On Red Hat Enterprise Linux 5 check that the Tomcat 5 packages are not already installed, if not then install the packages by executing: 
    yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5 tomcat5-webapps tomcat5-admin-webapps tomcat-native httpd mod_jk-ap20
    Copy to Clipboard Toggle word wrap
    Otherwise, in order to install the Tomcat 5 packages, you need to make the following modification to the /etc/yum.conf file. Comment out the option: 
    exactarch=1
    Copy to Clipboard Toggle word wrap
    Then install the packages: 
    yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps tomcat5.noarch tomcat5-webapps.noarch tomcat5-admin-webapps.noarch tomcat-native httpd mod_jk-ap20
    Copy to Clipboard Toggle word wrap

    Note

    Revert the change in /etc/yum.conf once installation is complete, this returns yum configuration to default settings.

Warning

Following RPM installation on Red Hat Enterprise Linux 4, the /var/log/httpd22 directory must be manually created, otherwise the httpd startup script will fail.
Installing via CSP

  1. Download the JBoss Enterprise Web Server zip file from the CSP site that is correct for your operating system and architecture.
  2. Unzip the file.

Important

You can install both Tomcat 5 and Tomcat 6 in parallel on your system, however port addresses would need to be modified in order to avoid conflict.

2.2. Red Hat Enterprise Linux directory structure
Copia collegamento

The following is the default directory layout after a successful installation: 
.
|-- jboss-ews-1.0
    |-- httpd (includes mod_jk)
    |-- tomcat5 (includes tomcat-native)
    |-- tomcat6 (includes tomcat-native)
    |-- doc
|-- jboss-ews-1.0-src
    |-- httpd
    |-- mod_jk
    |-- tomcat5
    |-- tomcat6
    |-- tomcat-native
Copy to Clipboard Toggle word wrap

2.3. Running the Installation
Copia collegamento

To run the downloaded packages differs depending on the download method. This section will now detail how to run the installation for a RHN download and CSP download.

2.3.1. Running a RPM Installation
Copia collegamento

Running Tomcat version 5 or 6

Tomcat can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool.

The tomcat5 or tomcat6 services can be started and stopped using the service command as root on a console window (as is typical of a network service):
Starting and stopping the tomcat5 service: 
service tomcat5 start
Copy to Clipboard Toggle word wrap 
service tomcat5 stop
Copy to Clipboard Toggle word wrap
Starting and stopping the tomcat6 service: 
service tomcat6 start
Copy to Clipboard Toggle word wrap 
service tomcat6 stop
Copy to Clipboard Toggle word wrap
Once the tomcat service has been started, you can verify that it is running by pointing your web browser to http://localhost:8080.
The tomcat service runs under a new tomcat system user. Due to file system permissions it may be necessary to use the su -s /bin/bash tomcat system command to deploy the application under the webapps directory. Alternatively, a developer can be listed in the tomcat user group by the system administrator. The best approach is to use the Web Console (URL above) to deploy the application.
The behavior at boot can be controlled with the chkconfig command (see the chkconfig man page for further details).
Configuration can then be altered in the /etc/sysconfig/tomcat5 file for Tomcat version 5 and the /etc/sysconfig/tomcat6 file for Tomcat version 6.
Running the HTTP Server

The HTTP Server can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool.

The following examples of running the HTTP Server will also cover the differences of undertaking this on Red Hat Enterprise Linux 4 and 5
You can start and stop the HTTP Server service using the service command as root on a console window (as is typical of a network service):
Starting and stopping the HTTP Server service on Red Hat Enterprise Linux 4: 
service httpd22 start
Copy to Clipboard Toggle word wrap 
service httpd22 stop
Copy to Clipboard Toggle word wrap
Starting and stopping the HTTP Server service on Red Hat Enterprise Linux 5: 
service httpd start
Copy to Clipboard Toggle word wrap 
service httpd stop
Copy to Clipboard Toggle word wrap
Configuration can then be altered in the /etc/sysconfig/httpd22 file on Red Hat Enterprise Linux 4 and the /etc/sysconfig/httpd file on Red Hat Enterprise Linux 5.
Running the mod_jk

To load the mod_jk module, the file /etc/httpd22/conf/httpd.conf on Red Hat Enterprise Linux 4 or the file /etc/httpd/conf/httpd.conf on Red Hat Enterprise Linux 5 needs to be updated, and a workers.properties file needs to be added in that directory. See /usr/share/doc/mod_jk-ap20-1.2.27/mod_jk.conf.sample and /usr/share/doc/mod_jk-ap20-1.2.27/workers.properties.sample for examples of how this can be achieved.

Running log4j for logging in Tomcat 6

In order to use log4j for logging in Tomcat 6, install the tomcat6-log4j rpm file.

Running Apache Tomcat Native

Edit /etc/sysconfig/tomcat5 file for Tomcat 5 or /etc/sysconfig/tomcat6 for Tomcat 6 and add the LD_LIBRARY_PATH variable so that it points to the library correct library:

The correct value when running on 64bit architecture is: 
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64/
Copy to Clipboard Toggle word wrap
The correct value when running on 32bit architecture is: 
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/
Copy to Clipboard Toggle word wrap

2.3.2. Running a ZIP Installation
Copia collegamento

Running Tomcat version 5 or 6

After extracting the zip file, check to see if a user called tomcat exists on the system by running the following command: 

id tomcat
Copy to Clipboard Toggle word wrap
If the user does not exist then it will need to be added, along with the appropriate usergroup. In order to achieve this, execute the following: 
groupadd -g 91 -r tomcat
useradd -c "Tomcat" -u 91 -g tomcat -s /bin/sh -r -d /home/tomcat tomcat
Copy to Clipboard Toggle word wrap
Once this is completed, if the tomcat user will be running Tomcat, then the ownership of the tomcat directories will need to be changed to reflect this:
For Tomcat 5: 
chown -R tomcat:tomcat tomcat5
Copy to Clipboard Toggle word wrap
For Tomcat 6: 
chown -R tomcat:tomcat tomcat6
Copy to Clipboard Toggle word wrap
To test that the above commands have been successful, check that the tomcat user has execution permission to the tomcat install path.
The JAVA_HOME and CATALINA_HOME variables will now need to be set and this can be achieved by either modifying your .bashrc file or by modifying the Tomcat catalina.sh file.
If you chose to modify your .bashrc file, add the following line with the correct path to suit your systems configuration (a path is provided here as an example only): 
export JAVA_HOME=/usr/lib/jvm/java
export CATALINA_HOME=<insert_install_path>/tomcat5 #(or tomcat6)
Copy to Clipboard Toggle word wrap
If you chose to modify your tomcat5/bin/catalina.sh or tomcat6/bin/catalina.sh file (depending on the version of Tomcat installed), add the following line with the correct path to suit your systems configuration (a path is provided here as an example only): 
JAVA_HOME=/usr/lib/jvm/java
CATALINA_HOME=<insert_install_path>/tomcat5 #(or tomcat6)
Copy to Clipboard Toggle word wrap
To start and stop Tomcat, execute the follwing scripts as the user tomcat:
To start Tomcat: 
sh startup.sh
Copy to Clipboard Toggle word wrap
To stop Tomcat: 
sh shutdown.sh
Copy to Clipboard Toggle word wrap
Once the tomcat service has been started, you can verify that it is running by pointing your web browser to http://localhost:8080.
Running the HTTP Server

In order to run the HTTP Server, the distcache and pcre rpm packages must be installed as they are a requirement of mod_ssl. To check if these dependencies are already installed, execute the following in a command prompt: 

rpm -q distcache pcre
Copy to Clipboard Toggle word wrap
The output will either say the rpms are not installed or it will display the package name followed by the version number. If distcache or pcre is not installed, execute:
for Red Hat Enterprise Linux 4: 
up2date distcache
up2date pcre
Copy to Clipboard Toggle word wrap
For Red Hat Enterprise Linux 5: 
yum install distcache
yum install pcre
Copy to Clipboard Toggle word wrap
While undertaking the install, you will be asked it you wish to proceed. When this occurs press the y key.
Once installation is complete run the following command in order to check that the package was installed successfully. 
rpm -q distcache
rpm -q pcre
Copy to Clipboard Toggle word wrap
If the package was successfully installed then the output of the command will be the package name and the version number.
Now, after you have extracted the Enterprise Web Server zip file, change into the httpd directory and run the post install script by executing the following: 
./.postinstall
Copy to Clipboard Toggle word wrap
Check to see if a user called apache exists on the system by running the following command: 
id apache
Copy to Clipboard Toggle word wrap
If the user does not exist then it will need to be added, along with the appropriate usergroup. In order to achieve this, execute the following: 
groupadd -g 91 -r apache 2> /dev/null || :
useradd -c "Apache" -u 91 -g apache -s /bin/sh -r -d /home/apache apache 2> /dev/null || :
Copy to Clipboard Toggle word wrap
Once this is completed, if the apache user will be running the httpd service, then the ownership of the HTTP directories will need to be changed to reflect this: 
chown -R apache:apache httpd
Copy to Clipboard Toggle word wrap
To test that the above commands have been successful, check that the apache user has execution permission to the HTTP server install path.
Start the HTTP server by changing to the sbin directory and executing: 
LD_LIBRARY_PATH=<insert_install_path>/httpd/lib ./httpd -f install_path/httpd/conf/httpd.conf -E install_path/httpd/logs/httpd.log -k start
Copy to Clipboard Toggle word wrap
Stop the HTTP server by executing: 
LD_LIBRARY_PATH=<insert_install_path>/httpd/lib ./httpd -f install_path/httpd/conf/httpd.conf -E install_path/httpd/logs/httpd.log -k stop
Copy to Clipboard Toggle word wrap
Running the mod_jk

To load the mod_jk module, the file httpd/conf/httpd.conf needs to be updated, and a workers.properties file needs to be added in that directory. See doc/mod_jk/mod_jk.conf.sample and doc/mod_jk//workers.properties.sample for examples of how this can be achieved.

Running Apache Tomcat Native

The native library for Tomcat 6 is setup to be used by default, with the LD_LIBRARY_PATH and -Djava.library.path having been set accordingly within the catalina.sh file.

For Tomcat 6, start the service and check that you see a message similar to: 
Feb 8, 2008 12:27:41 PM org.apache.catalina.core.?AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.x.y.
Feb 8, 2008 12:27:41 PM org.apache.catalina.core.?AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Feb 8, 2008 12:27:41 PM org.apache.coyote.http11.?Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Copy to Clipboard Toggle word wrap
For Tomcat 5, start the service and if the tomcat native library is not used, a message similar to the one below will appear: 
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path
Copy to Clipboard Toggle word wrap
Running log4j for logging in a zip installation of Tomcat 6

In order to use log4j logging in Tomcat 6, copy the content of the extras/ directory into the lib/ directory and restart Tomcat.

2.4. Installation Notes for Solaris
Copia collegamento

The preferred method for installing the Red Hat Enterprise Web Server on Solaris is by using the provided Solaris package file; however we will also discuss installation via the zip package.
Download the desired Enterprise Web Server package that you wish to use and that will match your Solaris version and CPU architecture.

Note

For Solaris version 10 you can choose between i386 (32-bit) and 64-bit systems versions. If running 64-bit JVM choose the 64-bit version of the Enterprise Web Server.
If you are building the packages from source, the Tomcat 5 and Tomcat 6 packages (regardless of the Tomcat you choose) will be built by using the srpms.

2.4.1. Installation using the Solaris package
Copia collegamento

Log into your system as root and use the gunzip and pkgadd commands. The commands will be: 
gunzip RHATews-1.0.0*-solaris10-i386.package.gz
Copy to Clipboard Toggle word wrap
and 
pkgadd -d RHATews-1.0.0*-solaris10-i386.package
Copy to Clipboard Toggle word wrap
The output will be: 
The following packages are available:
1  RHATews     Red Hat Enterprise Web Server (i386) 1.0.0,REV=2.el5
					
Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:
Copy to Clipboard Toggle word wrap
Type 1 or just press enter. The following information will now appear: 
Red Hat Enterprise Web Server(i386) 1.0.0,REV=2.GA
	
	
END USER LICENSE AGREEMENT
JBOSS(r) ENTERPRISE MIDDLEWARE(tm)
	
The end user license agreement ("EULA") governs the use of the various software modules that collectively comprise JBoss Enterprise Middleware
and any related updates, source code, appearance, structure and organization,
regardless of the delivery mechanism.
	
The JBoss Enterprise Middleware EULA can be found here:
http://www.redhat.com/licenses/jboss_eula.html
	
	
## Executing checkinstall script.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user
permission during the process of installing this package.

Do you want to continue with the installation of <RHATews> [y,n,?]
Copy to Clipboard Toggle word wrap
The package installer contains custom scripts that execute during install and are used for setting up the apache and tomcat user accounts. When package installer asks whether you wish to continue with the installation type y and press enter.
Installation will then commence and the following will be displayed: 
## Executing postinstall script.
Apache group (id=48) already exists. +++ or created if not
Apache user  (id=48) already exists.
Generating private RSA key ... OK
Generating new (+++ user hostname displayed here) certificate ... OK
Tomcat group (id=91) already exists.
Tomcat user  (id=91) already exists.
	
-----------------------------------------------------------------------
NOTICE
-----------------------------------------------------------------------
	
JAVA_HOME environment variable is not set.
Either set the  JAVA_HOME  or edit the configuration
scripts inside `/opt/redhat/ews/etc/sysconfig' directory
and set the JAVA_HOME to the installed JDK location.
	
	
Installation of <RHATews> was successful.
Copy to Clipboard Toggle word wrap
After the installation finishes the package is installed within the /opt/redhat/ews directory.
The package information can be checked by executing the following command: 
pkginfo -l RHATews
Copy to Clipboard Toggle word wrap

Note

During installation the system generated a notice that the JAVA_HOME environment variable was not set. Configuring this is discussed later in the Section 2.6, “Running on a Solaris Installation” section.

2.4.2. Installation using the zip package
Copia collegamento

Installing the zip package requires root access and the GNU version of tar.
The package should be uncompressed inside the /opt directory since the post installation script will not run if installation occurs within a different location.
The commands to achieve this are as follows: 
cd /opt
unzip -q RHATews-1.0.0*-solaris10-i386.zip
Copy to Clipboard Toggle word wrap
Once extraction of the archive has completed, the post install script must be run in order to setup the user accounts and final directories with required access privileges.
This is achieved with the following commands: 
cd /opt/redhat/ews/etc
sh .postinstall
Copy to Clipboard Toggle word wrap
Once the post install process has been completed, the users and groups apache with an ID of 48 and tomcat with an ID of 91, will have been created. The apache user will be used to run httpd, while the tomcat user will be used to run tomcat.
In addition, the post install process will also create the following additional directories that the tomcat group has write permission to:
  • /var/logs/tomcat5
  • /var/logs/tomcat6

2.5. Solaris directory structure
Copia collegamento

The following is the default directory layout after a successful installation: 
.
|-- /opt/redhat/ews
    |-- bin
    |-- doc
    |-- etc
    |-- lib
    |-- lib64 (present only for the 64-bit systems platform)
    |-- include
    |-- README
    |-- man
    |-- share
        |-- tomcat5
        |-- tomcat6
    |-- sbin
    |-- var
Copy to Clipboard Toggle word wrap
The Solaris directory structure is different to the Red Hat Enterprise Linux structure and the reasoning for this is as follows:
  • Native solaris packages require the absolute location
  • Solaris (and other non-Red Hat Enterprise Linux platforms) must ship and build all the dependent components such as openldap, openssl, db4 and cyrus-sasl to name a few.

2.6. Running on a Solaris Installation
Copia collegamento

Red Hat Enterprise Web Server consists of Apache Httpd and Apache Tomcat and the set of components needed to run them. These components can be run with the following users and groups who are created after installation:
Running Tomcat version 5 or 6

In order to run Tomcat on Solaris, some service configuration files will need manual editing.

Editing the Tomcat service entails uncommenting and setting the JAVA_HOME variable to the desired JDK in the configuration file. The configuration file can be found at:
For Tomcat 5: 
/opt/redhat/ews/etc/sysconfig/tomcat5
Copy to Clipboard Toggle word wrap
For Tomcat 6: 
/opt/redhat/ews/etc/sysconfig/tomcat6
Copy to Clipboard Toggle word wrap
To run Tomcat 5 or 6, the following command must be run as root:
For Tomcat 5: 
sbin/tomcat5 start
Copy to Clipboard Toggle word wrap
For Tomcat 6: 
sbin/tomcat6 start
Copy to Clipboard Toggle word wrap
By running one of the above commands, the configuration file is read and the user and group are changed to that of the tomcat user account before the catalina.sh script is executed.
The catalina.sh script file can be found within:
For Tomcat 5: 
/opt/redhat/ews/share/tomcat5/bin
Copy to Clipboard Toggle word wrap
For Tomcat 6: 
/opt/redhat/ews/share/tomcat6/bin
Copy to Clipboard Toggle word wrap
To stop Tomcat, one of the following commands can be executed:
For Tomcat 5: 
sbin/tomcat5 stop
Copy to Clipboard Toggle word wrap
For Tomcat 6: 
sbin/tomcat6 stop
Copy to Clipboard Toggle word wrap
By default, tomcat-native is automatically added to the LD_LIBRARY_PATH and -Djava.library.path during Tomcat startup. The catalina.sh script detects the running JVM version and adds the /opt/redhat/ews/lib path (/opt/redhat/ews/lib64 for 64 bit JVM) to the library path.
To run Tomcat as a service, use the provided scripts within the /opt/redhat/ews/etc/init.d directory. The following commands can be used to copy the necessary scripts:
For Tomcat 5: 
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rc3.d/S70tomcat5
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rcS.d/K20tomcat5
Copy to Clipboard Toggle word wrap
For Tomcat 6: 
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rc3.d/S70tomcat6
cp /opt/redhat/ews/etc/init.d/tomcat6 /etc/rcS.d/K20tomcat6
Copy to Clipboard Toggle word wrap
For information on how to choose the init level numbers, consult your Solaris documentation. The preferred method of service management is through the Solaris Service Management Facility. In order to read more about this facility, consult the smf(5) manual.
Running the HTTP Server

Apache httpd configuration files are located inside the /opt/redhat/ews/etc/httpd directory. By default all supported modules are loaded and enabled, so it is advised that you edit the httpd.conf file and disable the modules you don't need.

Starting the HTTP server is performed using the provided apachectl script located inside the /opt/redhat/ews/sbin directory. The apachectl script uses the configuration script, where you can edit and select various startup parameters, including the running of mpm. The file used is /opt/redhat/ews/etc/sysconfig/httpd
To start the HTTP Server, use the following command: 
sbin/apachectl start
Copy to Clipboard Toggle word wrap
To stop the HTTP Server, use the following command: 
sbin/apachectl stop
Copy to Clipboard Toggle word wrap
If you want your server to continue running automatically after a system reboot, a call to the apachectl script should be added to your system startup files.

Note

For complete documentation on how to start and stop the HTTP Server, refer to the files, docs/httpd/invoking.html and docs/httpd/stopping.html respectively.
Running the mod_jk

Running mod_jk on Solaris is the same as running the package on Red Hat Enterprise Linux installed via zip. For detailed instructions see Running the mod_jk

2.7. Uninstalling the package in Solaris
Copia collegamento

Uninstalling the Enterprise Web Server in Solaris is achieved by first executing: 
pkgrm RHATews
Copy to Clipboard Toggle word wrap
Following this, the run-time files have to be manually removed. The directories requiring manual removal are:
  • /opt/redhat/ews
  • /var/run/tomcat5
  • /var/run/tomcat6
  • /var/cache/tomcat5
  • /var/cache/tomcat6
  • /var/log/httpd
  • /var/cache/mod_ssl
  • /var/cache/mod_proxy

2.9. Building Tomcat from source
Copia collegamento

This section will cover what is necessary to build Tomcat from the source files.
Tomcat 5

In order to compile Tomcat 5 from source the following commands will need to be executed in sequence: 

cd servletapi/jsr154
Copy to Clipboard Toggle word wrap 
export CLASSPATH=servletapi4.jar
Copy to Clipboard Toggle word wrap 
ant -Dbuild.compiler=modern dist
Copy to Clipboard Toggle word wrap 
cd ../../servletapi/jsr152
Copy to Clipboard Toggle word wrap 
ant -Dbuild.compiler=modern dist
Copy to Clipboard Toggle word wrap 
cd ../../build
Copy to Clipboard Toggle word wrap 
sed -i -e 's:INSTALL_DIR:<install_directory>/jboss-ews-1.0-src/tomcat5:g' build.properties
Copy to Clipboard Toggle word wrap 
export CLASSPATH=../servletapi/jsr154/dist/lib/servlet-api.jar:../servletapi/jsr152/dist/lib/jsp-api.jar:../jakarta-taglibs-core.jar:../jakarta-taglibs-standard.jar:../struts.jar:../struts-taglib.jar:../ant.jar:../build/build/server/lib/tomcat-apr.jar
Copy to Clipboard Toggle word wrap 
ant -Dbuild.compiler=modern build-jasper-compiler-jdt  release
Copy to Clipboard Toggle word wrap
Tomcat 6

In order to compile Tomcat 6 from source the following command will need to be executed: 

ant -Dbase.path="." -Dbuild.compiler="modern" -Dcommons-collections.jar="commons-collections.jar"  -Dcommons-daemon.jar="commons-daemon.jar"  -Dcommons-daemon.jsvc.tar.gz="jsvc.tar.gz"  -Djasper-jdt.jar="jasper-jdt.jar"  -Djdt.jar="jasper-jdt.jar"  -Dtomcat-dbcp.jar="tomcat-dbcp.jar"  -Dtomcat-native.tar.gz=""
Copy to Clipboard Toggle word wrap

3. Excluded, Removed and Deprecated Items
Copia collegamento

This section outlines the items which are excluded from this release, deprecated or removed. In order to maintain a high level of backwards compatibility and customer service, an item will usually be deprecated before it is removed from a release.

Note

The difference between an excluded item and a removed item is that an excluded item is one that is commonly apart of a component of the JBoss Enterprise Web Server but has never featured within a JBoss Enterprise Web Framework release. However, a removed item is one that has previously been in a release of the JBoss Enterprise Web Server and is no longer included.

3.1. Excluded Items
Copia collegamento

The following items have been excluded from this release of the JBoss Enterprise Web Server:
  • Tomcat Clustering has been excluded from the Apache Tomcat 6 component. Specifically the catalina-tribes.jar file has been removed. This has occurred to eliminate any possibility of session replication and because Red Hat does not believe this feature is suitable for medium or large scale production deployments.

3.2. Deprecated Items
Copia collegamento

The following items have been deprecated for this release of the JBoss Enterprise Web Server:
  • The Tomcat Clustering feature of Apache Tomcat 5 is marked as deprecated for this release. Specifically the catalina-cluster.jar file has been deprecated.

3.3. Removed Items
Copia collegamento

As this is the first release of the JBoss Enterprise Web Server, no items have yet been removed.

5.  Known Issues with this release
Copia collegamento

Following is a list of known issues at the time of release.
  • JBPAPP-1809: A warning may occur in the log files for the tomcat user, which informs that there are no write permissions on the directory. A workaround currently exists for this issue that involves adding write permission to the tomcat group directory tomcat/conf.
  • JBPAPP-1837: Following RPM installation on Red Hat Enterprise Linux 4, the /var/log/httpd22 directory is not automatically created, forcing the httpd startup script to fail. The current workaround is to manually create this directory.
  • JBPAPP-1838: Once installation of the Enterprise Web Server has been completed via zip, a bug exists where the httpd/.postinstall script does not modify the conf/httpd.conf file to point to the correct ServerRoot directory. A workaround which exists for this involves replacing the reference to the /etc/httpd directory within the httpd/.postinstall script with the /etc/httpd22 directory.
  • JBPAPP-1788: Tomcat 6 on Solaris is stopped by the use of the command ews/etc/init.d/tomcat6 stop and though the server is successfully terminated, the output displays command usage errors. This is an issue with CATALINA_PID not being propagated for Tomcat 6 and will be fixed in a future release.

Security Known Issues

CVE-2010-2086
JBoss Enterprise Web Server 1.0.0 ships with Apache MyFaces 1.1.0. Apache MyFaces 1.1.0 does not support encrypted view state. When the application's view state is not encrypted, it is possible for an attacker to supply a new or modified view object as part of a request. This allows remote attackers to conduct cross-site scripting (XSS) attacks or execute arbitrary Expression Language (EL) statements via vectors that involve modifying the serialized view object.
JBoss Enterprise Web Server 1.0.1 and later does not ship with Apache MyFaces. Upgrading to JBoss Enterprise Web Server 1.0.1 or later is recommended to mitigate this issue.

A. Revision History
Copia collegamento

Revision History
Revision 1.0.0-1.1Wed Feb 11 2015Lucas Costi
Updated the Product Name to reflect the new name grouping for the product. No update was made to details in the guide.
Revision 1.0.0-1Thu Oct 07 2010Rebecca Newton
Retagging for Publican update

Legal Notice
Copia collegamento

Copyright © 2009 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Red Hat logoGithubredditYoutubeTwitter

Formazione

Prova, acquista e vendi

Community

Informazioni sulla documentazione di Red Hat

Aiutiamo gli utenti Red Hat a innovarsi e raggiungere i propri obiettivi con i nostri prodotti e servizi grazie a contenuti di cui possono fidarsi. Esplora i nostri ultimi aggiornamenti.

Rendiamo l’open source più inclusivo

Red Hat si impegna a sostituire il linguaggio problematico nel codice, nella documentazione e nelle proprietà web. Per maggiori dettagli, visita il Blog di Red Hat.

Informazioni su Red Hat

Forniamo soluzioni consolidate che rendono più semplice per le aziende lavorare su piattaforme e ambienti diversi, dal datacenter centrale all'edge della rete.

Theme

© 2026 Red HatTorna in cima