Install the connector on a Linux machine
The Device Connector is a standalone component for connecting devices to UFT Mobile.
For details on how to see all of your connectors, see View and manage connectors (Admin only).
Before you start
- You will need the IP address or FQDN of the UFT Mobile server machine. Your administrator can help with these details. The FQDN must begin with an English alphabetical character. FQDNs beginning with numbers are not supported.
- You also need to be connected to the UFT Mobile server when installing and starting the connector.
- Make sure that a UFT Mobile server is not already installed on the machine.
- Check that your machine complies with the recommended system requirements. For details, see system requirements.
- If Nginx is already installed on the connector machine, remove it before installing the UFT Mobile connector.
an access keyfor the connector.
- For admins, in the UFT Mobile Lab management console, click Generate New Key in the CONNECTORS page of the DEVICE LAB tab. Provide a name and description, and click GENERATE.
- For a non-admin user, request one from your admin. Select Contact Your Admin from the Help menu (upper right).
Tip: Ping the server to check that it is up.
Download the connector
Download the connector in one of the following ways:
- For admins, Select Download Connector in the CONNECTORS page. Download the appropriate connector from UFT Mobile on ADM Marketplace.
- For a non-admin user, select Download Connector from the Help menu in the upper right corner of the UFT Mobile console.
Install the connector
The standalone connector for UFT Mobile 3.4 can be installed as a full installation, or as an upgrade on top of an existing installation of the connector for UFT Mobile 3.0. The installer checks what files are already present, and installs or updates the relevant files.
- On your Linux machine, log in as root .
- Copy the file to your Linux machine and extract the installation files:
unzip <name of Linux connector installation file>.zip –d <Target directory Name>
- Change directory to the CONNECTOR directory in the Target directory:
cd <Target directory name>/CONNECTOR
- Run the connector installer:
./<install_connector-x64 file name>.bin
- Read the License Agreement, and select Y to accept the terms and proceed with the installation. Fill in the information or answer the questions in each of the Installation sections following these guidelines:
|Enter your credentials. For UFT Mobile, enter the access key provided by your admin.
UFTM SaaS: The SSL Enabled option should be selected.
|If connecting over a proxy, select Server address in the proxy section, and specify the server, port, and credentials if required.|
|Provide a meaningful name for the connector, as this will allow you to effectively filter devices based on connector names. Enter the Connector's IP address or FQDN, or accept the defaults.|
For details on how to change the configuration after the installation, see Change the configuration of the connector.
Review the pre-installation summary and press Enter to continue with the installation of the connector.
Caution: To insure integrity and confidentiality of the information stored with UFT Mobile, we strongly recommend that you incorporate filesystem monitoring on the installation and temporary folders.
Connect and verify devices
If you have not already done so, make sure to follow the steps for initial device configuration when connecting Android and iOS devices .
- Connect the device to the connector machine using a USB cable. On some devices, when you connect the device, there may be notification, trust, or location pop-ups. Accept these pop-ups.
- Wait until the Agent is running on the device.
If the Agent does not start up on the device, verify that the devices are recognized:Android devices
Run the following command on the Linux connector machine (If you are a root user, change directory to
All your connected devices should be listed. The status of the device should be "device" and not any other state, for example "unauthorized".
Tip: If you are connecting with a C-Type USB device, such as One Plus, Nexus 5, etc, the idVendor value may not have been recognized.
dmesgto obtain the idVendor value, beginning with 0x. Run
sudoto switch to the user specified during installation. Run the
~/add_android_vendor.sh <idVendor>script.iOS devices
- Navigate to:
The result of this command should be a list of devices IDs (UDID). If the command returns an empty result or ERROR message, try the following:
- On the
UFT Mobile server orconnector machine, log in as root .
- Locate the process ID of “usbmuxd”"
ps aux | grep '[u]sbmuxd'
- Kill the process:
kill –9 <processID>
- Start usbmuxd again:
idevice_id –lagain to see if the device is recognized.
If the devices are connected correctly, try to manually launch the UFTM Launcher app. If you see an Untrusted App Developer notification:
- Click Trust.
- Disconnect the device.
- Wait 5 seconds and then reconnect the device.
- Navigate to:
Additional considerations for iOS devices
If you have not already done so, enable UI Automation on the device in Settings >Developer> Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it.
Users who install apps signed with an Enterprise certificate (that do not use a Mobile Device Management (MDM) solution) will be prompted to trust the Enterprise developer the first time the app is installed. To trust the profile, go to Settings > General > Device Management, select the Enterprise developer profile, and trust it. These actions can be performed remotely on the device.
All users who install your enterprise-signed app for the first time will also need an internet connection. Once an Enterprise developer profile has been trusted on a device, additional apps with the same profile do not need to be trusted again, provided that the devices on which they are opened are connected to the internet. If the Enterprise developer profile of the application under test is not trusted, the Agent will not be able to open the app and a 1009 Error: "Cannot communicate with AUT " will result.
You can stop and start the connector with the following commands:
- To start the connector:
service UFTM start
- To stop the connector:
service UFTM stop
- To restart the connector:
service UFTM restart
To display system apps (apps that are used to run the device itself) in a supported language other than English, after installing the connector, navigate to
/opt/UFTMobile/connector/conf/connector.properties and uncomment the following line in the file:
Uninstall the connector
You can uninstall the connector for Linux as follows:
Log into the Linux connector machine as root user.
- Change directory to the connector installation directory:
cd <path to installation folder>(Default
- Run the uninstall script by entering the following command:
- Press enter to proceed with uninstalling the UFT Mobile connector.
Note: If you installed or upgraded the connector using an existing Linux user, you will be asked during the uninstall whether or not to remove this user. If you used the default new user created by UFT Mobile during the installation ("UFTM"), this user will be deleted automatically.
If you need to modify your connector details, for example to switch between an on-premises UFT Mobile server or the UFT Mobile hosted device lab, of if you need to change the
UFT Mobile server details:
IP address or FQDN
Secure or non secure connection (SSL)
UFT Mobile Connector details:
Connector IP address
To change the configuration of the connector:
- On the connector machine, log in as root or as a user in the Linux sudoers file.
- Navigate to your connector installation directory.
- Run the following command:
- When prompted, specify the new details.
- Restart the connector at the end of the process to allow the change to take effect.
- SSL access only: When you modify the connector details following a change to the server details, a new certificate is generated for the connector. Testing tool users will also need to reconfigure their SSL access UFT Mobile.