Install the connector on a Windows machine

The Device Connector is a standalone component for connecting devices to OpenText Functional Testing Lab. You can install the connector as a standalone component on a Windows machine, and configure it to connect to the OpenText Functional Testing Lab server. Devices connected to distributed connector machines become part of the OpenText Functional Testing Lab device lab.

In this topic:

Before you start

The standalone connector for OpenText Functional Testing Lab can be installed as a full installation, or as an upgrade to an existing installation of the connector for OpenText Functional Testing Lab (UFT Mobile) 3.0 or later.

Before starting, make sure that the following prerequisites are met:

Connector requirements	Check that your machine complies with the recommended system requirements and that your devices are supported. For details, see Connector requirements in the Support matrix, Connect devices, and Installation and configuration best practices.
Windows 11 Build 22572 and later only	Install the WMI command-line (WMIC) utility. Open Settings by pressing the Windows + I keys together. Click Apps. Click Optional features. Click the Feature display button. Search for Wmic. Select the check box next to it and press Next. Click Install.
New installation only	The server should be accessible to the connector. Navigate to: http/s://<OpenText Functional Testing Lab server IP address>:<server port> and check that you can access OpenText Functional Testing Lab. Make sure that an OpenText Functional Testing Lab server is not already installed on the machine.

Back to top

Considerations for iOS 17 and later

If you plan to connect devices running on iOS 17 and later directly to the connector machine, take into account the following considerations.

Consideration	Details
Supported OS	Linux and macOS: iOS 17 and later is supported on the following: Mac connector. For iOS 18, macOS 14 (Sonoma) or later is required. Linux Ubuntu standalone or embedded connector. RedHat Enterprise Linux 8.9, 8.10 and 9.4 standalone or embedded connector. Windows: Only iOS version 17.4 and later is supported on the Windows connector.
Internet connection	To fetch a signature key from Apple from time to time, the connector machine must have access to the following: http://gs.apple.com OpenText recommends allowing access to all *.apple domains. If the connector machine accesses the internet via a proxy server, configure the following proxy server details in the connector.properties file located in <installation_dir>/connector or server/conf/: Note: Requires version 24.4 Patch 1 or later. APPLE_HTTP_PROXY_HOST=<proxy host name> APPLE_HTTP_PROXY_PORT=<proxy port number> APPLE_HTTP_PROXY_USERNAME= <username for connecting to the proxy server> APPLE_HTTP_PROXY_PASSWORD= <password for connecting to the proxy server>
Other requirements and considerations	IPv6 is required. Dev access is not supported. Connecting AWS Device Farm and WeTest devices is not supported. Force quit application is not supported.

Back to top

Install the connector

Before installing the connector, make sure your machine meets the connector requirements.

To install the connector:

1. Obtain an access key for the connector from the OpenText Functional Testing Lab server.

   • Admin user: select the Access Keys tab. Click Generate New and provide a name, type (Connector), expiration date, description (optional). Then, click Generate.
   • Non-admin user: request one from your admin. Select Contact Your Admin from the Help menu (upper right).

   For more details on access keys, see Access key management.

2. Download the connector.

   • For admins, Select Download Connector in the CONNECTORS page. Download the appropriate connector.
   • For a non-admin user, select Download Connector from the Help menu in the upper right corner of the OpenText Functional Testing Lab console. Download the appropriate connector.

3. Extract the contents of the connector installation file to a folder on your computer. Locate the .exe file.
   

4. Double-click on the .exe file to open the Installation wizard. Read the contents and click Next.

5. Fill in the information or answer the questions in each of the Installation wizard pages following these guidelines:

   Authentication
   Enter your credentials. Enter the access key provided by your admin. OpenText Core Functional Testing Lab: 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.
   Connector configuration
   Provide a meaningful name for the connector, as this allows you to effectively filter devices based on connector names. Enter the Connector's IP address (if the IP is static) or FQDN, or accept the defaults.

For details on how to change the configuration after the installation, see Modify a connector.

Back to top

Prepare devices

Set up your Windows machine to detect the devices you want to connect to OpenText Functional Testing Lab by performing the following steps:

iOS devices

1. Make sure you have iTunes installed on your computer so that devices will be visible on your Windows machine. For details, see the Apple documentation.

   Note: For iOS 15 and later, iTunes 12.11 and later is required.

2. If you haven't already done so, follow the steps for setting up iOS devices.

Android devices

1. Download the USB driver for your devices. See the Android developers documentation 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, download the Google USB driver. For details, see the Android Developers documentation.

2. Extract the contents of the downloaded driver's archive file.

3. Connect the device(s) to your machine and install the driver per Windows version as described on the Install OEM USB Drivers in the Android Developers documentation.

   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.

4. If you haven't already done so, follow the steps for the initial configuration of Android devices.

Back to top

Connect devices and verify the connection

1. Connect your devices to your computer using a USB cable. Accept all notification, trust, or location pop-ups that may be displayed when you connect a device.
   
2. 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 Troubleshooting.

     Tip: If you unplug a device, wait 5 seconds before reconnecting it to allow the system to stabilize.

3. 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-tools folder and run adb at a command prompt.

   adb devices

   All your connected devices should be listed.

   • 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 OEM USB drivers list in the Android Developers documentation to see that you have the most recent version of the driver.

   Verify iOS devices

   1. Open a command prompt window
   2. Navigate to the <Windows Connector folder>\libimobiledevice\win folder
   3. Run the idevice_id command:

   idevice_id –l

   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

Back to top

Start, stop, and restart the connector

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.

Back to top

Modify a connector

If you need to modify your connector details, for example to change the server or connector port, you can modify them using the Modify configuration tool.

To access the tool, select Start > OpenText Functional Testing Lab 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. Use the modify configuration tool to update the connector details. Testing tool users also need to reconfigure their SSL access to OpenText Functional Testing Lab. For details, see SSL and certificates.

Back to top

Enable localization

To display system apps (apps that are used to run the device itself) in a supported language other than English, after installing the connector, go to <path to your Windows connector folder>\conf\connector.properties and uncomment the following line in the file:
ENABLE_LOCALIZATION=true

Back to top

Troubleshooting

There may be times that your connector does not work as expected. For details on troubleshooting the connector, see Windows connector.

Back to top

Uninstall a connector

You can uninstall the connector as follows:

• Double click the shortcut on the desktop and select the Uninstall option.
• Alternatively, uninstall from the Apps page in Settings, or from the Programs and Features control pane.

If certain applications were open during the uninstall process, some old connector files 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\Functional Testing Lab for Mobile and Web Connector\connector.

Back to top

Patch installation

To benefit from the latest enhancements and fixes, install the latest patch for your current version. Server and connector patches can be downloaded from Software Licenses and Downloads. The latest patch includes the content of any previous patches. There is no need to install previous patches.

When upgrading the server to the latest patch, the following should also be upgraded:

• All connectors.

• Manual signing tools (if applicable).
  

  • iOS Enabler for manual signing of iOS apps. After installing the server patch, the iOS  enabler is available in the Agent folder. Patches are available on the ADM Marketplace.

  • Android Enabler for manual signing of Android apps. After installing the server patch, the updated Android enabler is available in the server folder.

Follow the patch installation instructions included in the patch release notes.

Back to top

See also:

• Install the connector on a Linux machine
• Install the connector on a Mac machine
• Manage devices
• Troubleshoot