Install the connector on a Windows machine
The Device Connector is a standalone component for connecting devices to your mobile lab.
For example, the connector can be installed on a testing engineer's PC, and configured to connect to the UFT Mobile server machine. In this way, devices connected to distributed connector machines become part of the UFT Mobile device pool.
For details on how to see all of your connectors, see View and manage connectors (Admin only).
Before you start
The standalone connector for UFT Mobile can be installed as a full installation, or as an upgrade on top of an existing installation of the connector for UFT Mobile as follows
Version 3.3 can be installed as an upgrade to a UFT Mobile 3.0 Connector.
- You will need the IP address or FQDN (fully qualified domain name) of the UFT Mobile server machine. The FQDN must begin with an English alphabetical character. FQDNs beginning with numbers are not supported.
- Make sure that a UFT Mobile server is not already installed on the machine.
- You need to be connected to a UFT Mobile server when installing and starting the connector.
- Check that your devices are supported.
Tip: Ping the server to check that it is up.
Before installing the connector, make sure your machine meets the connector requirements.
To install the connector:
Obtain an access key for 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 (optional), and click GENERATE.
- For a non-admin user, request a connector key from your admin. Select Contact Your Admin from the Help menu (upper right).
Download the connector (32-bit or 64-bit) from UFT Mobile on ADM Marketplace.
- For admins, Select Download Connector in the CONNECTORS page. Download the appropriate connector (32-bit or 64-bit) 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.
Extract the contents of the connector installation file to a folder on your computer. Locate the .exe file.
Double-click on the .exe file to open the Installation wizard. Read the contents and click Next.
Fill in the information or answer the questions in each of the Installation wizard pages following these guidelines:
Authentication Enter your credentials. For UFT Mobile, enter the access key provided by your admin. If connecting over a proxy, select Server address in the proxy section, and specify the server, port, and credentials if required. Connector configuration 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 Modify a 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.
Set up your Windows machine to detect the devices you want to connect to UFT Mobile by performing the following steps:
Download the USB driver for your devices. See http://developer.android.com/tools/extras/oem-usb.html for a list of links to Original Equipment Manufacturers (OEM) USB Drivers. Alternatively, search the Web for a USB driver for Windows, for your device.
For Google Nexus devices, you must download the Google USB driver.
- Extract the contents of the downloaded driver's archive file.
Connect the device(s) to your machine and install the driver per Windows version as described on the Install OEM USB Drivers page.
Note: When you connect the device through a USB port, a security message may ask you to allow USB debugging or trust the connected computer. Accept the warning.
- If you haven't already done so, follow the steps for the initial configuration of Android devices.
- Connect your devices to your computer via USB cable. Accept all notification, trust, or location pop-ups that may be displayed when you connect a device.
- When the connector is running, the following items are automatically installed on the devices plugged into the connector machine:
- Remote viewer services
- The Agent application
Wait until the Agent is running before interacting with the device. If the Agent crashes, try to unplug the device and then plug it in again. For additional troubleshooting information, see Troubleshoot the Windows connector.
Tip: If you unplug a device, wait 5 seconds before reconnecting it to allow the system to stabilize.
- If the Agent app does not start up after you connect the devices, check if the devices are recognized: Verify Android devices
Navigate to the
<Windows Connector folder>\android-sdk-windows\platform-toolsfolder and run adb at a command prompt.
All your connected devices should be listed.
Verify iOS devices
- If your device is listed as unauthorized, check the device and accept any security pop-ups.
If your device is not listed, or if there are no devices listed, check for the following:
A hardware problem. The USB port may not be working.
- Improper Installation of Windows driver. Select the driver inf file in the File Explorer and select Install from the right-click menu.
- Incorrect drivers for Android devices. Check the vendor website to see that you have the most recent version of the driver.
To verify iOS devices:
- Open a command prompt window
- Navigate to the <Windows Connector folder>\libimobiledevice\windows-amd64 folder
- Run the idevice_id command:
The result of this command should be a list of devices IDs (UDID).
If there are no devices listed when a device is connected to the USB port, check for the following:
A hardware problem. The USB port may not be working.
- Incorrect version of iTunes. Check that you are using the most up-to-date version of iTunes.
- UI Automation is not enabled. For iOS 8.x and above with a Developer signed Agent app, enable UI Automation in Settings > Developer > Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it.
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 will issue a 1009 Error: "Cannot communicate with AUT ".
When the installation is complete, the setup program prompts you to start the connector service.
If you chose not to start the connector service after installing it, you can perform a manual Start, Stop, and Restart from the Services console, or directly from the machine's Start menu:
- Start > UFT Mobile Connector > Start
- Start > UFT Mobile Connector > Stop
- Start > UFT Mobile Connector > Restart
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, or to change the
To access the tool, select Start > UFT Mobile Connector > Modify configuration. The configuration wizard opens.
When running, the wizard stops the Connector service. The wizard's final page prompts you to start the service again.
When working with servers that use SSL, and you change the server details, you do not need to reinstall the connector. First run the generateSelfSignCertificate script on the server and then run the Modify configuration tool. Testing tool users will also need to reconfigure their SSL access to UFT Mobile. For details, see Working with SSL and certificates.
Note: The Modify configuration utility is not supported for connectors using a CA certificate, connecting to a UFT Mobile server with SSL. If you want to modify the connection to the server after importing the CA certificate to the connector, you must remove the existing connector and then reinstall it.
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
<path to your Windows connector folder>\conf\connector.properties and uncomment the following line in the file:
This section provides some tips and guidelines for getting your connector to work.
If the Windows connector started successfully, but you don't see devices in the UFT Mobile lab:
- Verify that your machine can detect your device.
- Check the connector.log file located in <
Windows connector folder>\connector\logfolder and make sure that there are no "connection refused" messages or other errors.
- If the connector.log does not show any errors, check the service.log file on the UFT Mobile server machine. The file is located here:
<Path to UFT Mobile server installation folder>\server\log
<Path to the UFT Mobile server installation folder>/server/log
If, during installation, Windows issues the warning “Windows Firewall has blocked some features of this app”, click Allow access or contact your system administrator. When this message is issued, the current Connector installation is aborted.
If you cannot view a remote device in UFT Mobile, this may be a result of the antivirus software installed on the machine. For example, McAfee Host Intrusion Prevention blocks access. Workaround: Disable the antivirus while running the test.
The Windows connector started successfully and the device is displayed in the UFT Mobile lab, but either remote access or recording are not working. In some cases, UFT Mobile will issue a message with the problematic IP address and port. In other instances, you may receive a "connection refused" message, indicating an IP address problem:
- Check the service.log file on the UFT Mobile server machine and look for possible "connection refused" errors:
<UFT Mobile installation folder>\server\log
Check that the IP address (shown in the error message) that UFT Mobile is trying to reach, is the correct one for your connector machine. To show the IP address of your machine, open a command line window and type
If, for example, you were connected to a different network or IP when you installed the connector, you will need to run the Modify configuration utility under Start > UFT Mobile Connector and enter the new IP of the connector machine.
- Check that the port shown in the error message, is open for incoming traffic on the connector machine.
If you indicate SSL during connector setup, proxy machines that require credentials are not supported.
- If you have a device connected when you install the connector
for an SSL environmentusing a proxy server, the devices will not appear in the Mobile Lab. Workaround: Connect the devices after you install the connector software.
When trying to run the installation, if the setup program issues a "connection refused" or "connection timed out" warning
- The server is down. Check that you can ping the server.
- The IP address of the UFT Mobile server is wrong.
- The port for the UFT Mobile connector is wrong.
- The version of the connector that you are using is not compatible with the version of the UFT Mobile server. Check UFT Mobile on ADM Marketplace to see that you are using the most up-to-date version of the connector.
If the server details (IP address or port) have changed since you last installed the connector, Modify a connector and specify the new information.
If an existing service running on your machine is claiming the port on which the connector runs, there will be a conflict, and the connector will not start up.
To change the port, run the Modify configuration utility under the Start > UFT Mobile Connector menu.
If you installed the Android SDK for a specific user (not the SYSTEM user), the Windows connector setup program may be unable to install the Agent, since the manually installed SDK is not accessible from the SYSTEM user.
Workaround: Reinstall the Android SDK as a SYSTEM user, and delete the ANDROID_HOME environment variable.
You can uninstall the connector via the Start menu or through the standard Windows Programs and Features > Uninstall or change a program interface.
If certain applications were open during the uninstall process, some old connector files will remain. This may affect a future installation. It is therefore recommended that you check that all connector files were removed. Otherwise, remove all files and folders manually, located by default at C:\Program Files\UFT Mobile Connector\connector.
- Install the connector on a Linux machine
- Install the connector on a Mac machine
- View and manage devices
- Troubleshooting and tips