Red Hat Bugzilla – Bug 974890
windows service install wrong
Last modified: 2015-08-31 22:58:52 EDT
This was accidentally reported for EWS 2.0 docs. It should be fixed as a one-off patch for 1.x.
This is doc bug for EWS 1.0.2 and EWS 1.0.2 has different directory structure than 2.0.X
Thanks for clarifying that, libor. Mandar, please check with Jean-Frederic and see if he can provide instructions for 1.0.2 specifically before you apply any changes here.
Can you provide me the instructions for 1.0.2 version?
The EWS 1.0.2 installation guide contains the following information:
Procedure 4.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.
32-bit vs 64-bit Command Prompt
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 sbin folder in the JBoss Enterprise Web Server installation folder:
C:\> cd /D "C:\Program Files\Red Hat\Enterprise Web Server\sbin"
5. In the Command Prompt, run the following command with the required Tomcat version (5 or 6) to install Tomcat:
call service<VERSION>.bat install
You can check the service parameters by typing tomcat<VERSION>w.exe.
- call service<VERSION>.bat install OK
- You can check the service parameters by typing tomcat<VERSION>w.exe ~ OK
In fact the tomcat<VERSION>w.exe are in "C:\Program Files\Red Hat\Enterprise Web Server\bin" not in sbin. It might be a good idea to add something like
Note: tomcat<VERSION>w.exe are located in "C:\Program Files\Red Hat\Enterprise Web Server\bin".
Mandar, please escalate the priority on this so we can push out the 1.0.2 patch.
Verified comm 10
Now available on access.redhat.com.