top of page
Search

What is the Performance Health Review (PHR) Tool?

  • Writer: Josef Mayrhofer
    Josef Mayrhofer
  • 14 hours ago
  • 3 min read

The Performance Health Review (PHR) 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).


The PHR tool can be run from the build virtual machine (in case of SaaS) or from any on-premises (On-Prem) virtual machine (VM) and can fetch the configuration information from the App, Web, API, Queueing (ActiveMQ), Batch, and Camel Layers (test environment layers).


How to obtain the PHR tool:


Each bank must send a former communication mail to Temenos to utilize the PHR tool. You will be able to download it from the portal. According to the latest information available, Temenos is providing the PHR tool to certain clients free of charge for a limited number of days. Once the free license expires, the client will need to request a renewal.


How to use the PHR tool:


  • Download the PHR tool and place it in the directory mentioned in the installation guide


  • Give the read and write permissions for all the folders and files within


  • Edit the basic details in the ‘perHealthCheck.properties’ file. The configuration changes are provided by Temenos. These are different for On Prim and SAAS.


  • Go to the bin folder and execute the .sh or .bat file.


  • Reports for each layer will be generated in the reports section with Temenos recommendations.


  • Use these recommendations, review them, and adopt the changes accordingly. Scripts are available to make the changes upon review automatically.


The following layers and their respective configurations are covered as part of the Performance Health Check, as shown below:

·      App Layer

·      Web Layer

·      API Layer

·      Queueing Layer

·      Batch Layer

·      Camel Layer

·      DB Configuration Level

·      General Hardware Config of Each Layer


Directory Structure:

The PHR folders and their usage are described below:

·      bin: Contains the executable launch script for PHR tool execution.


·      log: Contains the property file for java.util.logging and log files generated during PHR tool run.


·      config: Contains the feeder files for TRANSACT DB View configurations.


·      layersinfo: Contains all the configuration files collected from all the test environment layers.


·      script: Contains the script file for parsing all the test environment layers except DB in the SaaS environment and the configuration files received from the respective layers.


·      info: Contains the deployment file of all test environment layers, including microservice, except DB


·      lib: Contains the JDBC driver libraries for the respective DB vendor and ssh library (Jsch).


·      report: Contains the generated report files post PHR run completion.


·      appLayer (sub-directory of layers info): Contains the configuration files copied from the App Layer (post script execution of podParser.sh).


·      webLayer (sub-directory of layers info): Contains the config files copied from the Web Layer (post script execution of podParser.sh).


·      apiLayer (sub-directory of layers info): Contains the configuration files copied from the API Layer.


·      activeMQLayer (sub-directory of layers info): Contains the config files copied from ActiveMQ Layer (post script execution of podParser.sh).


Preparing Test Environment:


Prerequisite

  • Java 1.8 and above is required (preferred - openjdk version "1.8.0_352")

Setting up Feeder File

  • The feeder file contains the default performance-related TRANSACT DB App Names, Property Names (Field Names), Recommended Property or Field Values, and their respective descriptions. 

  • Refer to the PHR installation guide document for more information

 

Executing the Test:

To execute the PHR test,

  • Move the executable files to the respective On-Prem server or build a virtual machine (Cloud or SaaS) and extract the ZIP file.

  • Provide read and write permission for the folders

  • Make the necessary changes in the perHealthCheck.properties file

  • Edit the .sh or .bat file with the necessary details

  • Execute the .sh or .bat file. 

  

Generating Reports:

At the top of the report, you can find the summary of results for each layer. The status has a hyperlink that takes you to the relevant layer. The outputs of the relevant layers will be shown, and the user will be able to review and make changes accordingly.

 

Automatic scripts:

We can build the scripts to apply the recommended changes from the PHR tool ourselves, or Temenos will be able to assist with this part.

 

We, Performetriks, have good experience in observability, performance monitoring, and tuning. With the help of Dynatrace- T24 Fastpack services and the PHR tool, all the clients can easily identify the performance bottlenecks and possible suggestions to resolve the issues. Some of the issues might require more analysis and tuning activities. In case you need any support in the performance area, please do contact us.

Happy Performance Engineering! #T24 #Fastpack #PerformanceEngineering


Comments

bottom of page