UFT Mobile - Windows Installation (on-premises)

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

Before you start

Before installing UFT Mobile, make sure that:

  • Your server machine meets the system requirements.
  • You have administrator privileges.
  • The host name of the server machine is accessible. Check this by running the following from a Windows command line:
    ping -n 1 "hostname"
  • You have installed the USB drivers for your Android devices, or iTunes for iOS devices.

Note that a server installation on a USB stick or flash drive is not supported.

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 address:
    • In the postgresql.conf file stored under <Postgres installation folder>\<postgres version>\data search for listen_addresses = . This specifies the addresses on which the database 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 machine. 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.
  1. Restore the database. For details, see Migrate the exported data to an external database.
  2. 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 on a Windows machine

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

  1. Make sure that a connector is not installed on your machine. If it is, you need to remove it before installing the Windows server. For details, see Troubleshooting the Windows server installation.
  2. Obtain the installation zip file. Use an extraction tool to extract the contents of the archive file install-server-windows-x64-x.xx-x.zip to your computer.
  3. Log in to your machine as administrator.
  4. Locate the extracted .exe file. Make sure it is on a local drive and not a network shared drive.
  5. Click the setup file and choose Run as administrator from the right-click menu. The installation wizard opens to the Introduction page.
  6. Select a folder for the installation.
  7. Fill in the information in each of the Installation wizard screens following these guidelines:

    Server & Database Configuration
    Use the automatically detected values or modify them as needed. When using the Fully Qualified Domain Name (FQDN), the FQDN must begin with a character from the English alphabet. FQDNs beginning with numbers are not supported.

    Clear the SSL only check box to work with a non-secure HTTP connection (non-SSL). The default is a secure SSL connection using port 8443. The SSL setting affects all connectors and testing tools that integrate with the server. 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).


    Accept or edit the default internal port, 8081, that will not be included in the machine's firewall. Make sure that this port is available and that it is not externally accessible.

    External PostgreSQL Database Configuration

    You can choose to connect UFT Mobile to an existing external PostgreSQL database by selecting the Use external PostgreSQL database checkbox. 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 UFT Mobile with an external database, make sure that you have followed the steps described in Use an external database with UFT Mobile.

    When you select this option, the Next button opens the External PostgreSQL database configuration screen. 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.
    File storage configuration

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

    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 installation and the Local System account.

    When using a shared folder, the local system account on the UFT Mobile machine must have read and write permissions to the folder. Note that machines that are not in a domain have separate user management. Each machine keeps track of its own user accounts. To use a folder on another machine, make sure that a Windows account with the same name and password is defined on both machines. After installation, modify the UFT Mobile server to run under this Windows acount. For details, see Run the services as a different user.

    Shared spaces (multitenancy) configuration

    Enable shared spaces. For details, see Shared spaces (on-premises).

    Note that:

    • This feature requires an Enterprise or Ultimate license.
    • Disabling shared spaces is not supported and requires a clean installation.
    Credentials

    UFT Mobile default administrator

    The installation creates a default administrator user, admin@default.com, for accessing the UFT Mobile Lab Management console. Specify a password for this user.

    Embedded PostgreSQL database only

    When the PostgreSQL server is first installed, a superuser account postgres is automatically created. 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.

    The installation creates an additional user for administering the database. This user is not a superuser and only has permissions to perform operations on the UFT Mobile database. The default name is UFTMadmin, do not use postgres as a user name.

    Note: Follow the password rules displayed on the screen—at least six characters, both lower and upper case, at least one digit, and only letters or numbers except for a space or the "@" symbol.

  1. When the installation is complete, the wizard displays a message that the server was successfully installed, and provides options to:
    • Start the service automatically when you press Next.
    • Allow data collection for the improvement of the product. You can modify your selection for this option in the Administration Settings. To view the privacy policy, see the Privacy Statement.
  2. After the service has started, the UFT Mobile Lab console opens in the default browser window. Log in with the credentials you provided earlier. Follow the instructions on the screen to connect devices and begin working.

    The installation creates a new shortcut on the desktop, UFT Mobile Server, to the server's installation folder.

  3. After installation:
  4. 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:

    • Change the account running the UFT Mobile service, instead of the default LocalService account. Make sure that this account has full access to the UFT Mobile installation folder. For details, see the Windows documentation.
    • Incorporate filesystem monitoring on the UFT Mobile installation and temporary folders.
    • Back up the encrypted.properties file. The file is located in <path to your UFT Mobile Server installation> server >conf.

Back to top

Upgrade the 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 UFT Mobile:


  1. Obtain the installation zip file. Use an extraction tool to extract the contents of the archive file install-server-windows-x64-x.xx-x.zip to your computer.
  2. Run the setup file. When you begin the installation, the wizard detects that you are performing an upgrade and warns you about losing existing apps. It also prompts you for the database password. When you upgrade, all existing apps remain associated with their corresponding workspaces.
  3. 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.
  4. In the next screen, 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 run the automatic upgrader, you can run the upgrader manually at a later time. For details, see Upgrade packaged apps with the app upgrader (on-premises).
  5. You can also choose to delete old uploads of applications. If you select Yes, 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 Administration > Settings . For details, see General settings.
  6. 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 installation and the Local System account.

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

    When the file storage and the UFT Mobile server machines are not in the same domain, but are part of the same Windows workgroup, the same Windows admin username and password are required on both machines. After installation, you should run the UFT Mobile server under the Windows admin user. For details, see Run the services as a different user.

  7. If you choose to upgrade the apps, the next screen prompts you to select the operating systems of the apps you want to upgrade.
  8. Review the summary of the installation settings and click Next to proceed with the installation.
  9. To complete the server upgrade, click Next. 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.

  10. When the installation is complete, the wizard displays a message that the server was successfully installed, and provides options to:

    • start the service automatically when you press Done.
    • allow data collection for the improvement of the product. You can modify your selection for this option in Administration Settings.
  11. Click Done.

  12. After upgrade:

    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:

    • Change the account running the UFT Mobile service, instead of the default LocalService account. Make sure that this account has full access to the UFT Mobile installation folder. For details, see the Windows documentation.
    • Incorporate filesystem monitoring on the UFT Mobile installation and temporary folders.
    • Back up the encrypted.properties file located in the UFT Mobile server installation folder.

Back to top

Stop, start, or restart the server

From the Windows Start menu, navigate to UFT Mobile Server and choose the required action. In icon-based environments such as Windows 8.1, search for the required command: "Start UFT Mobile service", "Stop UFT Mobile service", or "Restart UFT Mobile service".

Run the services as a different user

For certain integrations, you may need to run the UFT Mobile service as another user. You can do this through the Services manager.

  1. Click Win +R to open the Run dialog box, and enter services.msc
  2. Locate the UFT Mobile Server and UFT Mobile Nginx services.
  3. Right-click the UFT Mobile Server service and select Properties.
  4. In the Log On tab, select This account, enter the credentials, and click Apply.

  5. Repeat the above steps for the UFT Mobile Nignix service.

Back to top

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, you can update the apps after the upgrade. 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 below. 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 UFT Mobile the newer version and extract its contents on the test machine.
  5. Run the setup file on the test machine as described in Upgrade the 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 below.
  7. Optional: 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 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 Administration > USERS .
  • 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

Troubleshooting the Windows server installation

  • For installation troubleshooting, refer to the installation log files located in the installation/Logs folder under the UFT Mobile installation. Even if an installation hangs, you can view the intermediate log, installation/UFT_Mobile_Server_install.log .
  • 503 error - Server cannot be started after installation with shared folder for application storage. When the file storage and the UFT Mobile server machines are not in the same domain, but are part of the same Windows workgroup, the same Windows admin username and password are required on both machines. After installation, you should run the UFT Mobile server under the Windows admin user. For details, see Run the services as a different user.

  • If you need to change information about the UFT Mobile server, see Reconfigure the UFT Mobile server (on-premises).
  • For troubleshooting tips regarding the connector, see Troubleshoot the Windows connector.
  • To uninstall the product, see Uninstall UFT Mobile (on-premises).
  • Before installing the Windows server, make sure that a Windows connector is not installed on the machine (C:\Program Files\UFT Mobile Connector). If there is a connector, use the Uninstall command from the Start menu.

  • If you encounter problems with the setup:

    • Navigate to C:\Program Files and delete the UFT Mobile Connector folder (after you have tried to run an uninstall) if it exists.
    • Delete the (hidden) Zero G Registry folder. If it is not visible, in the Windows Explorer, choose Organize > Folder and search options > View tab, and select Show hidden files, folders and drives.
    • If you began the server installation and it failed, delete the Windows server installation folder, C:\Program Files\UFT Mobile Server, and restart the setup.
    • If the installation was successful, but you cannot access the UFT Mobile server, check that the port is not being blocked by a firewall or your antivirus program.
    • Refer to the installation log file in the installation > Logs folder, and look for error messages.

Back to top

See also: