Overview
The Performance Health Checker (PHC) tool acts as a checklist (configuration collector) to verify whether all the performance-related properties are in place before running the performance tests.
It helps to identify the current configuration against the recommended configuration (based on previous performance tests and benchmarks).
This tool can be run from the build virtual machine (in case of SaaS) or from any On-Premise (On-Prem) virtual machine (VM) and can fetch the configuration information from the App, Web, API, Queueing (ActiveMQ), Batch and CamelLayers (test environment layers).
The following layers and their respective configurations are covered as part of the Performance Health Check as shown below:
-
TAFJ General Information (Version, Session Monitor information)
-
TAFJ Properties (tafj.properties)
-
TAFJ Trace Properties (TAFJTrace.properties)
-
JBOSS Release Information
-
JBOSS Memory Configuration (standalone.conf)
-
JBOSS Message Driven Bean Queue or Pool or Timeout Configuration (TAFJEE_EAR.ear> TAFJEE_MDB.jar > jboss-ejb3.xml and JBOSS config file)
-
JBOSS DataSource Pool Configuration (JBOSS configuration XML)
-
JBOSS DataSource Driver Configuration (JBOSS configuration XML)
-
JBOSS EJB OFS Source Timeout Configuration (TAFJEE_EAR.ear> TAFJEE_EJB.JAR> ejb-jar.xml)
-
TRANSACT DB Views Configuration includes Transact Version Used and TAFJ_VOC Lookup used to fetch TRANSACT View Names
-
App Logger information
(JBOSS_HOME > standalone > configuration > logging.properties)
-
JBOSS Release Information
-
Connection Timeout info (BrowserWeb.war > BrowserParameters.xml)
-
Web Logger information
(JBOSS_HOME > standalone > configuration > logging.properties)
-
JBOSS Release Information
-
IRIS WAR Flusher Configuration
( irf-provider-container.war > WEB-INF > lib > irf-core-22.0.0.jar > META-INF > irf-core-applicationContext.xml )
-
API Logger Information
(JBOSS_HOME > standalone > configuration > logging.properties)
-
IRIS Logger Information
(JBOSS_HOME > standalone > deployments > irf-provider-container.war > WEB-INF > classes > log4j2.properties)
-
Message Persistence Configuration
-
Policy Entry Configuration
-
env – Arguments
-
Logger Information
-
JBOSS Release Information
-
Agents Configuration
-
Batch Logger information
(JBOSS_HOME > standalone > configuration > logging.properties)
-
JBOSS Release Information
-
CamelIn Consumer Configuration
-
CamelOut Consumer Configuration
-
Camel Logger information
(JBOSS_HOME > standalone > configuration > logging.properties)
-
General Info – URL, Version, #dbcores, dbMemory, and collation details
-
Disk Volume Info – Drive Details and Size info
-
DB Object Level Information – Size, #rowsCount, Indexing info, and Partitioning Info
-
DB Log Space Information – Log File name and Size info
All test environment layers except DB.
In this topic