UFT Mobile- Linux Installation (on-premises)

This section describes how to install the server on a Linux machine. This section is relevant only for on-premises deployments of UFT Mobile. For information about installing the server on a Windows machine, see UFT Mobile - Windows Installation (on-premises).

Before you start

Before installing UFT Mobile, make sure that:

  • Your server machine meets the system requirements.
  • You have root permissions.
  • The host name of the server machine is accessible. Check this by running the following command:
    ping -c 1 "hostname"
  • If Nginx is already installed on the server machine, remove it before installing UFT Mobile.

Use an external database with UFT Mobile

UFT Mobile includes an embedded PostgreSQL database that is installed as part of the installation of UFT Mobile. However, you can choose to connect UFT Mobile to an existing external PostgreSQL database. This option lets your organization manage and utilize existing database resources. Note that when using an external database, UFT Mobile 3.4 supports PostgreSQL version 9.6 and version 11.

Before installing or upgrading UFT Mobile using an external database:

  1. Create a backup of the original database in the form of a hp4m.bin file. For details, see Export the embedded database.
  2. If you uninstalled the server but did not uninstall the PostgreSQL database, and are now using the database as an external database with a clean installation of UFT Mobile, add the postgres user to the pg_hba.conf file. The file is located in <Postgres installation folder>\<postgres version>\data.

  3. You will also need the original UFT Mobile database encryption key. The external database needs the key to decrypt the data originally created by UFT Mobile.

  1. In a distributed environment where the external database is on a different machine from the UFT Mobile machine, make sure that the database server accepts connections from the UFT Mobile server, and that UFT Mobile is configured to connect to the correct database server machine:
    • In the postgresql.conf file stored under <Postgres installation folder>/<postgres version>/data search for listen_addresses = . This specifies the addresses on which the server is to listen for connections. Update the value with the UFT Mobile server IP or FQDN. Setting the value as a wildcard “*” means the database server accepts connections from all addresses.
    • Locate the conf/hp4mExt-****.properties file in <UFT Mobile installation folder>/server/conf. Check that the IP address/ FQDN is the correct address for the database server. If the FQDN is not accessible to the UFT Mobile server machine due to DNS issues, replace the FQDN with the IP address of the database machine.
  2. Restore the database. For details, see Migrate the exported data to an external database.
  3. If your PostgreSQL database exceeds 4 GB, we recommend that you run the VACUUM FULL command to clean the database from deleted content and reduce its size. For details, see the PostgreSQL Wiki.

Install UFT Mobile as a new installation

Follow these steps to install UFT Mobile as a full installation where no previous version is installed:

  1. Download the Linux server zip file.

  2. Log in as root on your Linux machine.
  3. Copy the zip file to your Linux machine.
  4. Extract the server installation files:
    unzip <name of Linux server file>.zip –d <Target directory Name>
  5. Change directory to the Target directory:
    cd <Target directory Name>
  6. Run the installer:

    As root user:
    ./<install_server-x64 file name>.bin


    The installation wizard displays the Introduction page. Read the contents and press Enter.

  7. The installation wizard displays the License agreement. Press Enter to move through the pages and press Y to accept the agreement.
  8. Choose an installation folder. The default is /opt/UFTMobile/.
  9. Configure the Linux OS user:
  10. To use an existing Linux OS user, select Y and provide the user name.

    Caution: Do not use root as the name for this user.

    If you select n, UFT Mobile creates a default Linux OS user UFTM. Provide a new password for this user.

  11. Configure the UFT Mobile server according to the following guidelines:

    FQDN or IP address

    The fully qualified domain name (FQDN) consists of the host name and the domain name. For example, myhost.microfocus.com. The FQDN must begin with an English alphabetical character. FQDNs beginning with numbers are not supported.

    SSL connection

    Specify if the connection to the server should be over SSL only.

    The default is Y (secure connection only.) Note: If you choose the SSL option, all connections to the server from connectors and testing tool machines will need to be secure. When configuring the UFT Mobile settings in connectors and tools, make sure that your selection matches that of the server.

    Caution: When you specify an SSL connection, the setup installs a self-signed certificate. Self-signed certificates are not optimal because there is no outside authority to verify the identity of the server. We highly recommend that as soon as possible after putting the UFT Mobile server into production, you install an organizational CA certificate. For details, see Using SSL certificates issued by a Certification Authority (CA).

    Server port

    By default, the installation is set to SSL on port 8443. The default non-SSL uses port 8080.

    Free port to be used internally by UFT MobileDefault: 8081
    admin@default.com userThe installation creates a default administrator user, admin@default.com, for accessing the UFT Mobile Lab Management console. Specify a password for this user.
  1. At the PostgreSQL Configuration stage, the installation prompts you to indicate whether to use an external PostgreSQL database. Using an external database lets your organization utilize existing database resources and manage them with all of their other systems. If you want to use the PostgreSQL version embedded with UFT Mobile, skip to the next step. Note that when using an external database, UFT Mobile 3.4 supports PostgreSQL version 9.6 and version 11.

    Before installing UFT Mobile with an external database, make sure that you have followed the steps described in Use an external database with UFT Mobile.

    When prompted Do you want to use an external PostgreSQL database, type "y".

    Make sure that the database machine is accessible, and provide the following parameters for the connection:

    • External database server: The IP address or Fully Qualified Domain Name (FQDN) of database machine.
    • Database port: The port of the external database machine.
    • Database: The name of the external database. You can use a database name, such as “hp4m”. This database could already exist in the target database server. If not, it will be created as part of UFT Mobile server installation provided that the user has sufficient permissions.
    • Schema: You can use a schema name, such as “public”. This schema could already exist in the specified database. If not, it will be created as part of UFT Mobile server installation, provided that the user has sufficient permissions.

      Note: If the database/schema were originally created by UFT Mobile (for example, if you uninstalled the server but not the PostgreSQL database), you will be prompted to provide the encryption key when you proceed to the next screen. If the database/schema were not created by UFT Mobile, you do not need to provide an encryption key.

    • Database user name and password.
  2. When using the embedded version of the PostgreSQL database, configure PostgreSQL according to the following guidelines.
  3. Database server port Default: 5432
    PostgreSQL superuser password

    When the PostgreSQL server is first installed, a superuser account postgres is created automatically. The superuser is needed to create the UFT Mobile database schema, and to add a user for administering the database. The superuser can override all access restrictions within the database, so it is best to carry out most operations using a non-superuser role.

    You need to provide a password for the superuser:

    • The password must be between 6-20 English characters long (any alphabetical character, numbers, and the special characters "@" and "_" are permitted).
    • Contains at least one digit, one uppercase and one lowercase English character.
    PostgreSQL database administrator username

    The installation creates an additional user for administering the database. This user is not a superuser and has permissions to perform operations only on the UFT Mobile database.

    You need to provide a username for the database administrator (Default: UFTMadmin). The user name may consist of any lowercase English alphabetical characters, numbers, and the special character "_".

    Do not use postgres as the name for this user.

    PostgreSQL database administrator password

    You need to provide a password for the database administrator.
    The password must contain at least one digit, one uppercase and one lowercase English character, and must be between 6-20 English characters long. Any alphabetical character, numbers, and the special characters "@" and "_" are permitted.
  4. Choose a folder to which applications uploaded to UFT Mobile will be saved. The default is opt/UFTMobile/storage. Read and write permissions to the folder are required both for the user running this installation, and for the Linux OS user that will be defined in the next step of the installation.

    Note: Starting with Mobile Center version 3.2, applications are no longer stored in the database but are saved to the file system.

  5. Optionally, set the shared spaces (multi-tenancy) configuration:
    If required, enable the shared spaces feature.
    Important: This feature requires an Enterprise or Ultimate license. Disabling shared spaces is not supported and requires a clean installation. For details, see Shared spaces (on-premises).
  6. Review the pre-installation summary and press Enter to continue with the installation.
  7. The installation takes several minutes to complete. When the installation is complete, a message is displayed that the server was installed and provides options to:
    • Allow collection of anonymous data for the improvement of the product. You can modify your selection for this option after installation, in the Administration Settings.
    • Start the service. Unless specified otherwise during the installation process, by default, the server starts on port 8443 (HTTPS).
  1. After installation:

    To keep your files and data and safe, we strongly recommend that you incorporate the following for the application file storage folder and external database (if relevant):

    • Access monitoring

    • Limited access rights (only UFTM user)

    • Regular backup

    • Encryption

    • Storage consumption monitoring

    We also recommend that you:

    • Incorporate filesystem monitoring on the UFT Mobile installation and temporary folders.
    • Back up the encrypted.properties file located in the <path to your UFT Mobile server installation> Server >conf directory.

Back to top

Upgrade the UFT Mobile server

UFT Mobile 3.4 can be installed as an upgrade from versions 2.50 and higher. If you are using an earlier version of UFT Mobile, first upgrade to version 2.50.

To ensure a smooth upgrade see Best practices for upgrades.

Packaged apps: 
To run the app packager upgrader on iOS apps, you must have already set up your Mac machine as described in Set up automatic app packaging and signing services

If your apps were packaged manually from the command line and then uploaded to UFT Mobile, the upgrader will not be able to upgrade the apps. You will need to repackage your apps using the latest version of the Packager Service (iOS) or the Android Enabler, before uploading them to UFT Mobile.

To upgrade the UFT Mobile server:

  1. Download the UFT Mobile Linux Server zip file.

  2. Log in as root on your Linux machine.
  3. Copy the zip file to /root, your home directory.
  4. Extract the server installation files:
    unzip <name of Linux server file>.zip –d <Target directory Name>
  5. Change directory to the Target directory:
    cd <Target directory Name>
  6. Run the installer:
    As root user:
    ./<install_server-x64 file name>.bin

    The installation wizard displays the Introduction page. Read the contents and press Enter.
  7. Read the License Agreement, and select y to accept the terms and proceed with the installation.
  8. The installer detects that this is an upgrade and warns you accordingly. When you upgrade, all existing apps remain associated with their corresponding workspaces.
  9. Enter the PostgreSQL superuser password.
  10. Indicate whether you want to perform an automatic backup of the database during the upgrade, so that the installation can perform a rollback in case of failure. This step may increase the duration of the upgrade.
  11. Indicate whether you want to automatically run the app packager upgrader after the installation. Apps will be upgraded asynchronously after upgrade of the UFT Mobile server, reducing downtime of the server. Users will be able to access the upgraded server and continue using UFT Mobile while apps are being upgraded.

    If you choose not to, you can run it manually after the upgrade. For details, see Upgrade packaged apps with the app upgrader (on-premises).

  12. You can also choose to delete old uploads of applications. If you select y, specify the number of uploads to keep (Default: 30). When you choose to delete old uploads and specify the number of uploads to keep, these settings are copied over to the General section in Administation > Settings. For details, see General settings.
  13. Select a folder to which applications uploaded to UFT Mobile will be saved. Read and write permissions to the folder are required both for the user running this upgrade, and for the Linux OS user that was defined during the initial installation.

    Note: Starting with UFT Mobile version 3.2, applications are no longer stored in the database but are saved to the file system.

  14. If you choose to upgrade the apps, you are prompted to select the operating systems of the apps you want to upgrade.
  15. Review the pre-installation summary and press Enter to continue with the installation.

  16. In the package upgrade summary section, click Enter to complete the server upgrade. Applications will continue to be upgraded after the upgrade of the server.

    Note that after the installation is complete and the server is started, you will be able to check the upgrade status of apps in the APPS menu in the UFT Mobile Lab console. To see the status of an app, click the More info icon on the app card. The example below shows an app that is still in the process of being upgraded.
  17. When the installation is complete, a message is displayed that the server was installed, and provides an option to allow collection of anonymous data for the improvement of the product. You can modify your selection for this option after installation, in the Administration Settings.
  18. Exit the installer.
  19. After the upgrade:
    • Clear the browser cache before logging into the Lab Management console. Testing engineers should clear the browser cache on their testing tool machines before connecting to UFT Mobile.
    • iOS: Re-sign the Agent apps with your Developer certificate. For details, see Connect iOS mobile devices.

    To keep your files and data and safe, we strongly recommend that you incorporate the following for the application file storage folder and external database (if relevant):

    • Access monitoring

    • Limited access rights (only UFTM user)

    • Regular backup

    • Encryption

    • Storage consumption monitoring

    We also recommend that you:

    • Incorporate filesystem monitoring on the UFT Mobile installation and temporary folders.
    • Back up the encrypted.properties file located in the <path to your UFT Mobile server installation> Server >conf directory.

Back to top

Stop, start, or restart the server

You can stop and start the UFT Mobile server with the following commands:

  • To start the server: service UFTM start
  • To stop the server:  service UFTM stop
  • To restart the server: service UFTM restart

Back to top

Server logs

We do not recommend deleting server logs while the server is running. However, if you need to clear a log file while the server is running on Linux, you can run the following command:

cat /dev/null > <logFileName>

When deleting log files to increase free disk space, it is recommended to only delete log files with a numbered suffix. For example, connectorKeepAlive-1.log, connectorKeepAlive-2.log.

Best practices for upgrades

To ensure a smooth upgrade and prevent the loss of data, we highly recommend first performing an upgrade on a test machine, with the same operating system as your production machine. If the upgrade succeeds on the test machine, you can then proceed to upgrade your production server.

Prepare for the upgrade

Before you start the upgrade process:

  1. If you are using the iOS packager service, upgrade it to the new version before you run the upgrade process. For details, see Set up automatic app packaging and signing services.
  2. Decide if you would like to upgrade your applications during the upgrade process, as you will be prompted during the setup.

    • Starting with UFT Mobile 3.2, apps are upgraded asynchronously. Users can access and continue to use the upgraded server, while apps are being ugraded. You can check the upgrade status of an app in the APPS menu of the Lab console.
    • If you do not want to upgrade your apps automatically, you can upgrade the apps a later stage. For details, see Upgrade packaged apps with the app upgrader (on-premises).
  3. Back up your existing UFT Mobile database. For details, see Export the embedded database.
  4. Prepare a testing machine with the same operating system as your production environment. Other hardware parameters such as CPU and RAM can be different. This machine will serve as a test environment for the upgrade.

Perform the upgrade

We recommend that you perform an upgrade on the test machine that you prepared above. Upgrade UFT Mobile as follows:

  1. Install your current UFT Mobile server version on the test machine with the same operating system as your production environment.
  2. Import the original database to the test machine. For details, see Migrate the exported data to an external database.
  3. Verify that the import was successful by logging into UFT Mobile on the testing machine and verifying the apps, devices, settings, and so forth as indicated in the Upgrade checklist. Note that you will not be able to communicate with those connectors, because they were configured to work with the production machine—not the test machine.

  4. Locate the server installation file for the UFT Mobile version to which you want to upgrade.
  5. Extract its contents and run the file on the test machine as described in Upgrade the UFT Mobile server. If you encounter any difficulties during the upgrade, contact Support.
  6. Verify that the import was successful by logging into UFT Mobile on the test machine and verifying the apps, devices, settings, and so forth as indicated in the Upgrade checklist.
  7. Optional: Install a new connector on the upgraded test machine and attempt to run a test through one of the integrated testing tools.
  8. If all of the above information is correct on the test machine, proceed to Upgrade the UFT Mobile server on your production machine.

Upgrade checklist

After the upgrade process has completed on the test machine, check the following items to ensure that the upgrade succeeded:

  • Login. Log in to UFT Mobile as an admin user.
  • Users. Check that all the users were migrated to UFT Mobile in the ADMINISTRATION > Users page.
  • Settings. Check that all the Administration Settings were migrated from the production environment.
  • Apps. If you chose to upgrade your applications during the upgrade process, make sure that all of your apps are visible in the APPS screen.
  • Connectors. Verify that all the connectors are visible in the DEVICES > Connectors page. Note that you will not be able to communicate with those connectors, because they were configured to work with the production machine—not the test machine.
  • Devices. Make sure that you see all of the production environment's devices.

If there are any missing items or if you encounter any other issues, contact Support.

Back to top