Admin: Created page with "= Health Analyzer = ===Vault Link=== https://vault.vmware.com/group/vault-main-library/healthanalyzer ===Registration Link=== https://pstoolhub.vmware.com/ === Registration Code for 5.4 === Registration Key: WG88IS9LJFA1KNYWUV Registration E-mail: droessner@vmware.com ===Support Information=== services-software-support@vmware.com = Issues and Fixes = ==Fails to collect Data from vCenter== ===Issue=== Unable to get progress information. See application logs for mor..."

2023-06-02T19:10:04Z

Created page with "= Health Analyzer = ===Vault Link=== https://vault.vmware.com/group/vault-main-library/healthanalyzer ===Registration Link=== https://pstoolhub.vmware.com/ === Registration Code for 5.4 === Registration Key: WG88IS9LJFA1KNYWUV Registration E-mail: droessner@vmware.com ===Support Information=== services-software-support@vmware.com = Issues and Fixes = ==Fails to collect Data from vCenter== ===Issue=== Unable to get progress information. See application logs for mor..."

New page

= Health Analyzer =
===Vault Link===
https://vault.vmware.com/group/vault-main-library/healthanalyzer
===Registration Link===
https://pstoolhub.vmware.com/
=== Registration Code for 5.4 ===
Registration Key: WG88IS9LJFA1KNYWUV
Registration E-mail: droessner@vmware.com
===Support Information===
services-software-support@vmware.com

= Issues and Fixes =
==Fails to collect Data from vCenter==
===Issue===
Unable to get progress information. See application logs for more information. (Version 5.4)
===Fix===
In general vHA tool is very memory hungry when analyzing big projects. You will need to increase the amount of RAM for the tool (if this is possible)

Please follow this guide:

If you use java version -

For java app 64-bit JRE is recommended for large environments
To change the amount of memory using the Java application
1. Stop the VMware HealthAnalyzer Java application.
2. Go to the directory where the VMware HealthAnalyzer Java application was unzipped.
3. Open <vhalocation>/resources/applicationContext.xml using a Text Editor (Notepad++ like app)
4. App Server: Locate vha-start section and change the value of Xmx1024m to Xmx2048m, and XX:MaxPermSize=256M to XX:MaxPermSize=512M
<util:map id="vha-start" map-class="java.util.LinkedHashMap">
<entry key="java" value="" />
<entry key="-Xmx2048m" value="" />
<entry key="-XX:MaxPermSize=512M" value="" />

5. DB Server: Locate basex-start section and change the value of Xmx1280m to Xmx2048m. Notice there is a new line added as well.

<util:map id="basex-start" map-class="java.util.LinkedHashMap">
<entry key="java" value="" />
<entry key="-Xmx2048m" value="" />
<entry key="-XX:MaxPermSize=512M" value="" /> #new line

6. Start the VMware HealthAnalyzer Java application.

-----------------------------------------

To change the amount of Tomcat memory with a virtual appliance
1. Log in to the virtual appliance using the user root and password vmware.
2. Open the configuration file using vi or another text editor:
vi /usr/share/vha/tomcat/conf/vha-tomcat-memory
3. Locate the default value of 2048 and change it to your desired value. This is the amount of memory allocated to Tomcat in megabytes.
4. To change the amount of database memory with a virtual appliance You have to edit basexserver configuration file
/usr/share/vha/basex/bin/basexserver
# Options for virtual machine
VM=-Xmx2048m - change this to amount memory you have and want
5. Restart the appliance with the following command:
shutdown –r now
6. You can confirm that the memory value changed by issuing the following command and reviewing the argument –Xmx .
ps –ef | grep catalina and ps -ef | grep -i basex
Default virtual appliance memory size is 1.5GB so it must be increased as well.

If this did not work I have deployed one vHA instance in our vCenter with 8G for tomcat and 8G for database. You can access it on the following URL:

http://10.26.226.213/vha/HealthAnalyzer.html#!explore
(you must be in VMware VPN/network)
You can use it as long as needed. Please let me know when You finish. Thank You

Best regards,
Anton Sabev
Support Engineer, Field Tools
sabeva@vmware.com

VMware/VHA - Revision history