Bug 1000043 - add EPP product slot to EAP 5 plug-in
add EPP product slot to EAP 5 plug-in
Status: CLOSED NEXTRELEASE
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 5 (Show other bugs)
JON 3.1.2
Unspecified Unspecified
high Severity high
: ER01
: JON 3.1.3
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-22 10:43 EDT by Larry O'Leary
Modified: 2013-09-04 17:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 998968
: 1000046 (view as bug list)
Environment:
Last Closed: 2013-09-04 17:59:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 458583 None None None Never

  None (edit)
Description Larry O'Leary 2013-08-22 10:43:34 EDT
This needs to be fixed in the 3.1.x line.

+++ This bug was initially created as a clone of Bug #998968 +++

Description of problem:

Customer want to differentiate alerts for different types of JBoss server: EAP & EPP.
An easy way would be to use the name of inventoried JBoss server (starts with the string returned by JBossProductType.java) possible for EAP, EWP, SOA & BRMS.
Unfortunately the EPP case does not exist in JBossProductType.java and they would like to obtain a patch for the class :
rhq/modules/plugins/jboss-as-5/src/main/java/org/rhq/plugins/jbossas5/helper/JBossProductType.java

This should be easily feasable, as the jboss-epp-5.2/jboss-as/bin/run.jar (META-INF/MANIFEST.MF) contains the line :
Implementation-Title: JBoss [EPP]




Version-Release number of selected component (if applicable):
JON 3.1.2

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Larry O'Leary 2013-09-04 17:59:39 EDT
Closing as there will not be a 3.1.3 release. This is being tracked for 3.2 in 998968.

Note You need to log in before you can comment on or make changes to this bug.