5.2
Table Of Contents
- vFabric Web Server Installation and Configuration
- Table of Contents
- 1. About vFabric Web Server Installation and Configuration
- 2. Overview of vFabric Web Server
- 3. Installing vFabric Web Server
- Installation Note for vFabric Suite Customers
- Available Distribution Packages
- RHEL: Install vFabric Web Server from an RPM
- Unix: Install vFabric Web Server from a Self-Extracting ZIP
- Windows: Install vFabric Web Server from a ZIP File
- Activate a vFabric Web Server Local License
- Description of the vFabric Web Server Installation
- 4. Upgrading vFabric Web Server
- 5. Creating and Using vFabric Web Server Instances
- 6. Configuring vFabric Web Server Instances
- Using Sample Configuration Files to Enable Features and Modify Configuration
- Configure Load Balancing Between Two or More tc Runtime Instances
- Configure SSL Between vFabric Web Server and vFabric tc Server
- Configure tc Runtime Instances to Use SSL
- Configure the vFabric Web Server Instance to Use SSL
- Restrict Communication With tc Runtime Instances to Known Clients
- Update the Web Server Configuration for HTTPS Connections to tc Runtime Instances
- Configure vFabric Web Server to Authenticate Itself Using a Specific Client Certificate
- Configure BMX for Monitoring vFabric Web Server Instances
- 7. Security Information
- 8. Managing Planned and Unplanned Outages
- 9. Additional Documentation
Overview of vFabric Web Server 5
VMware vFabric Suite 5.2 5
vFabric Web Server vFabric ERS Customer Action
Windows, Solaris, and AIX. See Supported
Configurations and System Requirements for
the exact versions.
HPUX. See ERS Supported Platforms for the
exact versions.
instances, and apply all patch releases (such
as service packs) issued by that vendor
no later than 12 months from their vendor
release.
Includes the current enterprise-ready release
of Apache HTTPD Server 2.2.
Includes the current release of Apache
HTTPD Server 2.2, as well as the now-
deprecated 2.0 and 1.3 versions.
Migrate all Apache HTTPD 2.0 and 1.3
instances to vFabric Web Server 2.2
instances. The migration requires updates to
the *.conf file.
During installation or upgrade, the Apache
HTTPD binaries are written to a path
in the format vfabric-web-server/
httpd-2.2.xx.x-32. This preserves any
existing Apache HTTPD binaries without
overwriting them.
During installation or upgrade, the Apache
HTTPD binaries are always written to the
same directory (ers-install-path/
apache2.2-64), which means on upgrade
any existing binaries are overwritten.
Point all server instances to the common
symlink vfabric-web-server/
httpd-2.2, modify it to revert/roll back/
change 32-64 bit modes.
Includes the most commonly-used modules.
See Complete Packages and Modules in
vFabric Web Server 5.2.
Included additional modules, such as
mod_perl, mod_php, and mod_snmp.
Migrate PHP and Perl applications to the
supported, and more optimal, mod_fcgid
environment.
Closely tracks Apache Software Foundation
(ASF) naming and directory layout
conventions. In particular:
• install-dir/httpd-2.2/modules/
directory contains the loadable modules
• Binaries and configuration file names use
httpd prefix
• install-dir/newserver creates new
instances
• instance-dir/bin/httpdctl controls
each deployed instance
• instance-dir/conf/extras/ offers
feature-based small config templates
Has a number of now-stale, legacy file and
path conventions. In particular:
• install-dir/apache2.2/modules/
standard directory contains the loadable
modules
• Binaries and configuration file names use
httpsd prefix
• install-dir/ers-server.pl creates
new instances
• install-dir/servers/instance-
dir/bin/apache_startup.sh|bat
controls each deployed instance
• install-dir/servers/instance-
dir/conf/httpsd.conf is one large,
monolithic configuration template.
Create a new vFabric Web Server instance,
then migrate customizations from your
existing vFabric ERS instance. Alternatively,
modify a copy of the deployed vFabric
ERS instance tree to use vFabric Web
Server path and file name conventions.
Use smaller functional .conf snippets to
make the configuration more organized and
maintainable.