mobilelifecycle/uft-mobile repository overview

⁠Micro Focus UFT Mobile Server Docker image

Latest documentation can be found here: https://admhelp.microfocus.com/uftmobile/en/2022/Content/Docker_install.htm⁠

⁠Obtain the UFT Mobile server image

You can obtain the latest UFT Mobile Docker image from the Docker hub. Type the following in your Linux environment:

docker pull mobilelifecycle/uft-mobile:2022.0

The image contains the Dockerfile of the UFT Mobile server that connects to a remote Postgres database (the database installation is not included in the package). Note that when installing UFT Mobile with a Docker image:

• Integration with LDAP is not supported
• SSL is not supported
• Extended services: only Production Usage (AppPulse Mobile) is supported.

⁠Run PostgreSQL

The PostgreSQL database used by UFT Mobile is not included in the UFT Mobile server image. Make sure that you have the PostgreSQL database up and running on a machine that can be accessed by the server. We recommend PostgreSQL version 11.7. If you don't have PostgreSQL, you can obtain it from the Docker hub by typing docker pull postgres:11.7.

⁠To run the PostgreSQL container in the background:

Enter the following command when using the default PostgreSQL port (5432):

docker run --name postgres -p 5432:5432 -e POSTGRES_PASSWORD=[postgres_password] -d postgres:[PostgreSQL version number]

If you need to use a custom port, run the following:

docker run --name postgres -p [custom_port]:5432 -e POSTGRES_PASSWORD=[postgres_password] -d postgres:[PostgreSQL version number]

Make sure to use this custom port for POSTGRES_PORT= in the command for running the UFT Mobile server in section Start a container and launch the UFT Mobile server.

⁠Start a container and launch the UFT Mobile server

After you have the PostgreSQL database up and running, you can start the UFT Mobile server container.

⁠To start the UFT Mobile container:

1. Check that the default port, 8080, is available and not being used by another process.
2. Run the following command to run the UFT Mobile server in the background in detached mode:

docker run -d --name uftm -p 8080:8080 -e POSTGRES_HOST=[postgres_ip] -e POSTGRES_PORT=5432 -e POSTGRES_USER=[postgres_user] -e POSTGRES_PASSWORD=[postgres_password] -e FQDN=[host_ip] mobilelifecycle/uft-mobile

If you need to use a custom port, specify the custom port as follows:

docker run -d --name uftm -p [custom_port]:8080 -e POSTGRES_HOST=[postgres_ip] -e POSTGRES_PORT=5432 -e POSTGRES_USER=[postgres_user] -e POSTGRES_PASSWORD=[postgres_password] -e FQDN=[host_ip] mobilelifecycle/uft-mobile

docker volume create uftm_data
docker run -d --name uftm [options] -v uftm_data:/opt/uftm/mcStorage mobilelifecycle/uft-mobile

⁠Begin your UFT Mobile test

To use UFT Mobile for testing your mobile app:

1. Open the UFT Mobile home page http://<host>:<port> and log in with the default credentials:
   Email: [email protected]⁠
   Password: password
   It may take a minute for the server to start up, and for the page to open.
2. Install the appropriate UFT Mobile connector on the machine/s to which you will be connecting devices with a USB cable. The connector can be installed on the same machine on which Docker is installed. For details, see Install the connector on a Windows machine⁠, Install the connector on a Linux machine⁠ or Install the connector on a Mac machine⁠.
3. Prepare your UFT Mobile test with the relevant testing tool, such as UFT, Sprinter, or TruClient.

⁠Tips and guidelines

The following list includes useful Docker commands:

• docker ps : Lists the containers that are running
• docker stop uftm : Stops the UFT Mobile service
• docker start uftm : Starts the UFT Mobile service
• docker images : Lists the images
• docker inspect uftm | grep '"Source": "/var/lib/docker/volumes" : Check the logs of the running UFT Mobile container.
  The output will have the following form:

  "Source": "/var/lib/docker/volumes/07ec0041ecf5f86934d2957648a24248fefeffdbb0da3a5b353d1d1fe480b656/_data"  
  

  Copy
  Append server/log to the above path shown in the output. This folder contains the log files.