此内容没有您所选择的语言版本。
4.3. Configuring the Environment
Before running JBoss Enterprise Web Server, set the environment variables and run the post-installation script.
Procedure 4.4. Setting Environment Variables
- Log in to an account with local administrator permissions.
- Go to
. - Click on the Advanced tab.
- Click the button.
- Click the for System Variables.
- Enter the required
JAVA_HOME,TMPandTEMPname-value pairs. - You will also need to add
<EWS_HOME>\binto the PATH environment variable of the user the service runs under. This is SYSTEM by default. Without this, the SSL Connector will fail to work.
Procedure 4.5. Running the Post-Installation Script
- Run the Command Prompt as administrator even if you are logged in as the administrator:
- Click the button.
- Go to
. - Right-click the Command Prompt and select
Run as administrator.
Note
Windows Server 2003 does not have the User Account Control concept, therefore you only need to run the Command Prompt (cmd.exe). - In the Command Prompt, type the following to change to the
etcfolder of your Enterprise Web Server installation:cd /D "C:\Program Files\Red Hat\Enterprise Web Server\etc"
C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\etc"Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Issue the command
call postinstall.batto run the post-installation script.The script creates the required symbolic links (Junction Points) for temporary logging and configuration directories.
Procedure 4.6. Installing Tomcat
Follow this procedure to install Tomcat as a service:
- Run the Command Prompt as administrator:
- Click the button.
- Go to
. - Right-click the Command Prompt and select
Run as administrator.Note
On 64-bit Windows, you need to use the 64-bit version of the Command Prompt (cmd.exe). Running thecmdcommand from a 32-bit application launches a 32-bit Command Prompt instance. This causes the service setup script to fail with a File Not Found warning. - Change to the
sbinfolder in the JBoss Enterprise Web Server installation folder:cd /D "C:\Program Files\Red Hat\Enterprise Web Server\sbin"
C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\sbin"Copy to Clipboard Copied! Toggle word wrap Toggle overflow - In the Command Prompt, run the following command with the required Tomcat version (5 or 6) to install Tomcat:
call service<VERSION>.bat install
call service<VERSION>.bat installCopy to Clipboard Copied! Toggle word wrap Toggle overflow You can check the service parameters by typingtomcat<VERSION>w.exe.Note
The tomcat<VERSION>w.exe is located inC:\Program Files\Red Hat\Enterprise Web Server\bin
Procedure 4.7. Installing HTTP
Follow this procedure to install Tomcat as a service:
- Run the Command Prompt as administrator:
- Click the button.
- Go to
. - Right-click the Command Prompt and select
Run as administrator.
- Change to the
binfolder of your new installation:cd /D "C:\Program Files\Red Hat\Enterprise Web Server\bin"
C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\bin"Copy to Clipboard Copied! Toggle word wrap Toggle overflow - In the Command Prompt, run the
installcommand:A Firewall security dialog prompt demanding networking access for the Apache HTTP Server service appears. Click if you wish to access this service from the network.httpd -k install
httpd -k installCopy to Clipboard Copied! Toggle word wrap Toggle overflow Note
By default, Apache HTTP Server is configured to listen on port 80. If you have Microsoft IIS installed, ensure the following:World Wide Web...service is stopped and the Startup Type is set toManualWorld Wide Web...service is configured to listen on a different port
Alternatively, you can edit thehttpd.conffile before installing the service and change theListendirective to a port that does not collide with the Internet Information Service listening ports.
Procedure 4.8. Configuring log4j
Follow this procedure to use
log4j logging in Tomcat:
- Change to
C:\Program Files\Red Hat\Enterprise Web Server\extras\ - Copy the respective log4j files to the Tomcat folder:
- If using Tomcat 6, run the following commands:
copy log4j.jar log4j.properties ..\tomcat6\lib
copy log4j.jar log4j.properties ..\tomcat6\libCopy to Clipboard Copied! Toggle word wrap Toggle overflow copy C:\Program Files\Red Hat\Enterprise Web Server\extras\tomcat-juli-adapters.jar C:\Program Files\Red Hat\Enterprise Web Server\tomcat6\lib
copy C:\Program Files\Red Hat\Enterprise Web Server\extras\tomcat-juli-adapters.jar C:\Program Files\Red Hat\Enterprise Web Server\tomcat6\libCopy to Clipboard Copied! Toggle word wrap Toggle overflow - If using Tomcat 5, run the following commands:
copy log4j.properties ..\tomcat5\common\classes
copy log4j.properties ..\tomcat5\common\classesCopy to Clipboard Copied! Toggle word wrap Toggle overflow copy log4j.jar ..\tomcat5\common\lib
copy log4j.jar ..\tomcat5\common\libCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure 4.9. Removing SSL
JBoss Enterprise Web Server supports SSL by default, but it may be removed.
Follow this procedure to remove or again add SSL:
- Go to
C:\Program Files\Red Hat\Enterprise Web Server\etc\httpd\conf.d - Rename the SSL configuration file:
- To remove SSL, rename
ssl.conftossl.conf.disabled. - To re-add SSL rename
ssl.conf.disabledtossl.conf.
Procedure 4.10. Configuring mod_jk
To configure the HTTP Server to use mod_jk, the following needs to be defined:
- available workers (JBoss instances) in the
workers.propertiesfile - the mod_jk configuration file
mod_jk.conf
Follow this procedure to configure the HTTP Server to use mod_jk as its load balancer:
- In
C:\Program Files\Red Hat\Enterprise Web Server\etc\httpd\conf\create workers.properties (refer to http://tomcat.apache.org/connectors-doc/reference/apache.html). - In
C:\Program Files\Red Hat\Enterprise Web Server\etc\httpd\conf.d\, create mod_jk.conf (refer to http://tomcat.apache.org/connectors-doc/reference/apache.html)Note
You can also use the sample filesmod_jk.conf.sampleandworkers.properties.sampleavailable inC:\Program Files\Red Hat\Enterprise Web Server\etc\httpd\conf: modify their content as needed and rename them tomod_jk.confandworkers.properties.
Procedure 4.11. Configuring mod_cluster
Follow this procedure to configure the HTTP Server to use mod_cluster as its load balancer:
- In the
C:\Program Files\Red Hat\Enterprise Web Server\etc\httpd\conf\httpd.conffile, add the hash (#) sign at the beginning of the following line to disable mod_proxy_balancer.so:This module is incompatible with the JBoss HTTP Connector.LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.soCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Configure the server to load the JBoss HTTP Connector modules:
- Create the file
C:\Program Files\Red Hat\Enterprise Web Server\etc\httpd\conf\JBoss_HTTP.conf. - Add the following lines to the
JBoss_HTTP.conffile:LoadModule slotmem_module modules/mod_slotmem.so LoadModule manager_module modules/mod_manager.so LoadModule proxy_cluster_module modules/mod_proxy_cluster.so LoadModule advertise_module modules/mod_advertise.so
LoadModule slotmem_module modules/mod_slotmem.so LoadModule manager_module modules/mod_manager.so LoadModule proxy_cluster_module modules/mod_proxy_cluster.so LoadModule advertise_module modules/mod_advertise.soCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Procedure 4.12. Setting Security
Follow this procedure to ensure that the account used to run the services has full control over the
C:\Program Files\Red Hat folder and all of its subfolders:
- Right-click the
C:\Program Files\Red Hatfolder and clickProperties. - Select the
Securitytab. - Click the button and type in
LOCAL SERVICE. - Select the
Full Controlcheck box for the newLOCAL SERVICEaccount. - Click the button.
- Inside the Advanced Security Settings for Red Hat dialog, select the
Replace permissions on all child objects...check box and click the button.This procedure is intended for Windows 2003. The equivalent procedure in Windows Server 2008 and Windows Server 2008R2 can slightly differ.