Questo contenuto non è disponibile nella lingua selezionata.

3.3. Configuring the Environment


Before running JBoss Enterprise Web Server, set the environment variables and run the post-installation scripts.

Procedure 3.4. Setting Environment Variables

  1. Log in to an account with local administrator permissions.
  2. Go to Control Panel System.
  3. Click on the Advanced tab.
  4. Click the Environment Variables button.
  5. Click the New for System Variables.
  6. Enter the required JAVA_HOME, TMP and TEMP name-value pairs.
  7. You will also need to add C:\Program Files\jboss-ews-2.0\bin to 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 3.5. Running the Post-Installation Script

  1. Run the Command Prompt as administrator even if you are logged in as the administrator:
    1. Click the Start button.
    2. Go to All Programs Accessories.
    3. Right-click the Command Prompt and select Run as administrator.
  2. In the Command Prompt, type the following to change to the etc folder of your Enterprise Web Server installation:
    C:\> cd /D "C:\Program Files\jboss-ews-2.0\etc"
    Copy to Clipboard Toggle word wrap
  3. Issue the command call postinstall.httpd.bat and then the command call postinstall.tomcat.bat to run the post-installation script.
    The script creates the required symbolic links (Junction Points) for temporary logging and configuration directories.

Procedure 3.6. Installing Tomcat

Follow this procedure to install Tomcat as a service:
  • Run the Command Prompt as administrator:
    1. Click the Start button.
    2. Go to All Programs Accessories.
    3. 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 the cmd command 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.
    4. Change to the bin folder in the JBoss Enterprise Web Server installation folder.
      1. For Tomcat 6

        For Tomcat 6, the command is:
         C:\> cd /D "C:\Program Files\jboss-ews-2.0\share\tomcat6\bin"
        Copy to Clipboard Toggle word wrap
      2. For Tomcat 7

        For Tomcat 7, the command is:
        C:\> cd /D "C:\Program Files\jboss-ews-2.0\share\tomcat7\bin"
        Copy to Clipboard Toggle word wrap
    5. In the Command Prompt, run the following command :
      call service.bat install
      Copy to Clipboard Toggle word wrap

Procedure 3.7. Installing HTTP

Follow this procedure to install Tomcat as a service:
  1. Run the Command Prompt as administrator:
    1. Click the Start button.
    2. Go to All Programs Accessories.
    3. Right-click the Command Prompt and select Run as administrator.
  2. Change to the bin folder of your new installation:
    C:\> cd /D "C:\Program Files\jboss-ews-2.0\bin"
    Copy to Clipboard Toggle word wrap
  3. In the Command Prompt, run the install command:
    httpd -k install
    Copy to Clipboard Toggle word wrap
    A Firewall security dialog prompt demanding networking access for the Apache HTTP Server service appears. Click Allow if you wish to access this service from the network.

    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 to Manual
    • World Wide Web... service is configured to listen on a different port
    Alternatively, you can edit the httpd.conf file before installing the service and change the Listen directive to a port that does not collide with the Internet Information Service listening ports.

Procedure 3.8. Configuring log4j

Follow this procedure to use log4j logging in Tomcat:
  1. Change to C:\Program Files\jboss-ews-2.0\share\extras\
  2. 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 to Clipboard Toggle word wrap
    • If using Tomcat 7, run the following commands:
      copy log4j.jar log4j.properties ..\tomcat7\lib
      Copy to Clipboard Toggle word wrap

Procedure 3.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:
  1. Go to C:\Program Files\jboss-ews-2.0\etc\httpd\conf.d
  2. Rename the SSL configuration file:
    • To remove SSL, rename ssl.conf to ssl.conf.disabled.
    • To re-add SSL rename ssl.conf.disabled to ssl.conf.

Procedure 3.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.properties file
  • the mod_jk configuration file mod_jk.conf
Follow this procedure to configure the HTTP Server to use mod_jk as its load balancer:
  1. In C:\Program Files\jboss-ews-2.0\etc\httpd\conf\ create workers.properties (refer to http://tomcat.apache.org/connectors-doc/reference/apache.html).
  2. In C:\Program Files\jboss-ews-2.0\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 files mod_jk.conf.sample and workers.properties.sample available in C:\Program Files\jboss-ews-2.0\etc\httpd\conf: modify their content as needed and rename them to mod_jk.conf and workers.properties.

Procedure 3.11. Configuring mod_cluster

Follow this procedure to configure the HTTP Server to use mod_cluster as its load balancer:
  1. In the C:\Program Files\jboss-ews-2.0\etc\httpd\conf\httpd.conf file, add the hash (#) sign at the beginning of the following line to disable mod_proxy_balancer.so:
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    Copy to Clipboard Toggle word wrap
    This module is incompatible with the JBoss HTTP Connector.
  2. Configure the server to load the JBoss HTTP Connector modules:
    1. Create the file C:\Program Files\jboss-ews-2.0\etc\httpd\conf.d\mod_cluster-native.conf.
    2. Add the following lines to the mod_cluster-native.conf file:
      LoadModule proxy_cluster_module modules/mod_proxy_cluster.so
      LoadModule slotmem_module modules/mod_slotmem.so
      LoadModule manager_module modules/mod_manager.so
      LoadModule advertise_module modules/mod_advertise.so
      Copy to Clipboard Toggle word wrap

Procedure 3.12. Setting Security

Follow this procedure to ensure that the account used to run the services has full control over the C:\Program Files\jboss-ews-2.0 folder and all of its subfolders:
  1. Right-click the C:\Program Files\jboss-ews-2.0 folder and click Properties.
  2. Select the Security tab.
  3. Click the Edit button.
  4. Click the Add button.
  5. In the text box, enter LOCAL SERVICE.
  6. Select the Full Control check box for the new LOCAL SERVICE account.
  7. Click OK.
  8. Click the Advanced button.
  9. Inside the Advanced Security Settings dialog, select LOCAL SERVICE and click Edit.
  10. Select the check box next to the Replace all existing inheritable permissions on all descendants with inheritable permissions from this object option.
  11. Click OK.
  12. Click OK again.
  13. Click OK a third time to apply the settings.
This procedure is intended for Windows 2008. The equivalent procedure in Windows Server 2008R2 can differ slightly.
Torna in cima
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

© 2025 Red Hat