3.4. Running Enterprise Web Server

You can run the httpd and tomcat services from the Command Prompt or with the Computer Management tool.

Procedure 3.13. Running Enterprise Web Server from the Command Prompt

Follow this procedure to run the httpd and tomcat services from the Command Prompt:
  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. On the Command Prompt, issue the following command to run the tomcat service: 
    net start tomcat<VERSION>
  3. On the Command Prompt, run the following command to run the httpd service: 
    net start Apache2.2
    Right click to select the name of the desired service in the Services Menu. Options include Apache 2.2, Apache Tomcat 6 and Apache Tomcat 7.

Procedure 3.14. Running Enterprise Web Server from the Computer Management Tool

You can run the httpd and tomcat services from the Command Prompt or with the Computer Management tool.
  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. Go to Start → Administrative Tools → Services
  3. In the Services dialog, right-click the name of the service (httpd or tomcat) and click Start or Stop.

Note

Some thirdparty applications add libraries to the system directory in Windows. These take precedence over Tomcat when DLL libraries are looked up. This means that if they have the same name as the those used by Tomcat native libraries, they are loaded instead of the libraries distributed with JBoss Enterprise Web Server. Tomcat therefore does not start, and does not log any error messages about it in Windows Event Log, or Tomcat log files. Errors can only be seen by using catalina.bat run.
If this behaviour occurs, check the content of the C:\windows\System32\ directory and PATH directories, and check for DLLs library conflicting with those shipped with Enterprise Web Server. In particular, look for libeay32.dil, ssleay32.dll, and libssl32.dll.
Report a bug