[jopr-issues] [JBoss JIRA] Commented: (JOPR-103) EWS/Tomcat detection logic ambiguous (namespace collision?)

[corey welton (JIRA)]

    [ https://jira.jboss.org/jira/browse/JOPR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458568#action_12458568 ] 

corey welton commented on JOPR-103:
-----------------------------------

QA test notes:

Simply perform a standard tomcat installation on RHEL, inventory it, and assure it doesn't display as an EWS instance therein.


> EWS/Tomcat detection logic ambiguous (namespace collision?)
> -----------------------------------------------------------
>
>                 Key: JOPR-103
>                 URL: https://jira.jboss.org/jira/browse/JOPR-103
>             Project: Jopr
>          Issue Type: Bug
>          Components: Plugin - Tomcat
>    Affects Versions: 2.2
>            Reporter: corey welton
>            Assignee: Jay Shaughnessy
>            Priority: Blocker
>
> 1. Install RHN Satellite on a box
> 2. Install JON Agent on same box; begin monitoring.
> 3. View inventory, noting "JBoss EWS Tomcat" in the inventory.
> 4. Go to Inventory > Connection tab for this tomcat server
> 5. Observe "Installation Home" value 
> Current results:
> The value for "Installation home" used by RHN Satellite is "/usr/share/tomcat5".  This is the string that is used to identify EWS.  However, this is not an EWS Tomcat install.  End result:  This is detected/displayed as "JBoss EWS Tomcat" in jopr, even though it actually isn't.
> Expected results:
> a non EWS-labelled value returned

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira