Bug 756098

Summary: Basic Admin Guide: Update/add section about configuring EWS
Product: [Other] RHQ Project Reporter: Libor Zoubek <lzoubek>
Component: DocumentationAssignee: Deon Ballard <dlackey>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2CC: hrupp, theute
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-29 15:13:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Libor Zoubek 2011-11-22 17:10:52 UTC
Description of problem:
I was trying to setup EWS (tomcat 5/6) on windows 7. I've successfully installed tomcats to run as windows services. I was following http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html-single/Basic_Admin_Guide/index.html#configuring-tomcat-for-discovery

Especially Chapter 8.7.1. I tried to do similar steps in windows startup.bat and setenv.bat but without access. Tomcat was not affected by any change in these  files. After few hours spend I found a solution:

I had to run regedit, navigate to 
HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\Tomcat<VERSION>\Parameters\Java 
and edit Options attribute and add:

-Dcom.sun.management.jmxremote.port=9876
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false

Since that, I've restarted Tomcat service and it started to listen on desired JMX port without requiring authorization.

I am not aware of any other/better way to configure startup tomcat aguments when it runs as a service.

Please add this in to Chapter 8.7.1 it can save few hours of madness for some people.