Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

The WebSphere help information to export HQ_JAVA_HOME needs to be related to Windows

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ-server 4.3.0-EE-1382 running on CentOS 5.2
    HQ-agent 4.3.0-EE-1382 running on Windows 2003
     - WebSphere 7.0 running with HQ-agent
  • Case Links:
    none
  • Regression:
    No

Description

The WebSphere help information to export HQ_JAVA_HOME needs to be related to Windows.

Existing (as seen on Windows):

The HQ Agent must be run using the IBM JDK to monitor WebSphere:
% export HQ_JAVA_HOME=/opt/IBM/WebSphere/AppServer/java
% hq-agent.sh start

Update to:
% export HQ_JAVA_HOME=C:\sw\/IBM\WebSphere\AppServer\java
% hq-agent.bat start

Steps to reproduce:
1. Log into the HQ Server Dashboard
2. Browse and select the WebSphere Admin 7.0 Server running on Windows
3. Go to the Inventory tab
4. Go to the Configuration Properties
5. Examine the Help Information at the bottom
6. Note the information

  • is not correct on Windows
  • is not specifc to WebSphere 7.0 and needs updating

Work around:
N\A - does not affect product functionality

Issue Links

Activity

Hide
Todd Rader added a comment -

That should be

set HQ_JAVA_HOME="C:\sw\IBM\WebSphere\AppServer\java"

Double quotes would likely be necessary, for example, if WAS was installed in the more standard "C:\Program Files" directory. It's best to try before doing the update.

Show
Todd Rader added a comment - That should be set HQ_JAVA_HOME="C:\sw\IBM\WebSphere\AppServer\java" Double quotes would likely be necessary, for example, if WAS was installed in the more standard "C:\Program Files" directory. It's best to try before doing the update.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 3 days ago