UFT Mobile High Availability - how to guide

UFT Mobile High Availability - how to guide

 

The challenge

UFT Mobile platform becomes critical vehicle for supporting ongoing testing and development efforts for Enterprise organizations and omni-channel applications. As a such, there is an expectation that the platform itself will be enterprise-grade. One of the aspects is support of high-availability configuration. UFT mobile version 3.30 does support that deployment scenario.

Solution

For deploying UFT Mobile in high availability manner, the following components should be involved:

  1. LoadBalancer: the entry-point for the end-users that can automatically fail-over to the active node of UFT Mobile. Any LB can be supported. The LB probe (health-check) configuration will be explained.
  2. UFT Mobile Active/Passive nodes: two nodes are required for active/passive configuration. Installation and configuration steps will be explained.
  3. External database: external DB PostreSQL 9.6 should be used. Database high availability and backup operations are outside of this guide.
  4. Shared disk space: for assets stored outside of UFTM database (applications, etc.). The high availability and backup procedures for shared disk space are outside of this guide.

Configuration steps:

  1. Establish LoadBalancer solution of your choice. Note the FQDN for the LB. Use the LB FQDN as the UFTM Server Address when installing the UFTM nodes.
  2. Install UFTM Active node: on first node of UFTM deployment launch the installation as usual and configure it to work with external DB. Note the DB schema name and ENCRYPTED_KEY from server/conf/encrypted.properties file after completing the installation. Start the server as usual.
  3. Instal UFTM Passive node: on the second node of UFTM deployment, launch the installation and configure external DB with the same DB schemas as in 2. The installer will automatically recognize that the schema is already exists and will ask to provide ENCRYPTED_KEY. This way we'll be able to point second node to the same DB schema. Start the server after completing the installation. It will be started immediately, but go to Passive mode (Active state of the first node will force Passive mode on the second).
  4. Configure the LB probe (monitoring point): configure the health-check on LB to /rest/v2/status/active. For instance, if using HAProxy as LB, add to haproxy.cfg:
option httpchk GET /rest/v2/status/active HTTP/1.0

Congratulation!

UFT Mobile solution is deployed using Active/Passive configuration for high availability. In case of Active node will fail for whatever reason, the Passive node will be automatically promote himself to become and Active. The health-check of LB will indicate the change and route the traffic to Active node.

P.S.: don't forget to enrich your HA deployment with PostgreSQL HA as well as Shared Files storage.

Labels (1)

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2019-12-12 16:44
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.