Home
Test Execution Specialist guide
This guide, which is intended for a tester or a test execution specialist, describes tasks that you must complete before you can configure and run tests on Rational® Test Automation Server. You can find information about other tasks that you can perform on the Resource Monitoring Service, Virtualization, and Integrations with third-party applications.
Managing Docker hosts
You can set up dedicated external Docker hosts to run large tests or run tests remotely to free up the dependency of running tests on the internal Docker host of IBM® Rational® Test Automation Server.
Setting up a remote Docker
You must set up a system to host the remote Docker host. You can set up the remote host with a non-secure mode of connection with IBM® Rational® Test Automation Server.

Test Execution Specialist guide
This guide, which is intended for a tester or a test execution specialist, describes tasks that you must complete before you can configure and run tests on Rational® Test Automation Server. You can find information about other tasks that you can perform on the Resource Monitoring Service, Virtualization, and Integrations with third-party applications.
- Prerequisites to running tests
  Before you can configure and run a test in a project on Rational® Test Automation Server, you must read the information about the different tests. You might want to add a remote static agent or a remote Docker host to the project as an alternate location to run the tests.
- Managing Docker hosts
  You can set up dedicated external Docker hosts to run large tests or run tests remotely to free up the dependency of running tests on the internal Docker host of IBM® Rational® Test Automation Server.
  - Test run considerations for running tests on remote Docker hosts
    Before you can configure a test to run on a remote Docker host, you must read the considerations you must take into account.
  - Setting up a remote Docker
    You must set up a system to host the remote Docker host. You can set up the remote host with a non-secure mode of connection with IBM® Rational® Test Automation Server.
  - Setting up a secure remote Docker
    You must set up a system to host the remote Docker host. You can set up the remote host with a secure mode of connection with IBM® Rational® Test Automation Server by using certificates issued by the remote host system that authenticate the connection.
  - Copying third-party application Jars to a remote Docker host
    You can run API Suites in a project on Rational® Test Automation Server on a remote Docker host. If the API Suites use a transport and the transport requires third-party Jar files for a successful run, you must ensure that the third-party application Jar files are available at the test run time. To achieve this, you must copy the third-party application Jar files to the computer where you have set up the remote Docker host.
  - Registering a remote Docker
    You must register the remote Docker host with Rational® Test Automation Server before you add the remote Docker host to your project, which contains the test assets that you want to run on the remote Docker host.
  - Adding a remote Docker host
    You can choose to run tests on Docker hosts that you have set up on remote host systems. You must register the Docker host with IBM® Rational® Test Automation Server and then add them to your project before you run tests on the remote Docker hosts.
  - Editing configurations
    You can edit the host name or the port of the registered Docker host system instead of registering it as a new remote host if any of the parameters are changed on the remote host system. You can also change the mode of authentication of a registered remote Docker host.
  - Deleting a remote Docker
    You can delete a remote Docker host that you added to your project in IBM® Rational® Test Automation Server when you no longer need it to run tests.
  - Unregistering a remote Docker
    You can unregister a remote Docker host that is registered with Rational® Test Automation Server when you no longer require it.
- Test run configurations
  You can configure and run tests in IBM® Rational® Test Automation Server after you add the test resources to your project.
- Management of running tests
  Find information about the tasks that you can perform on a test that you configured for a run either while it runs or after it completes the run.
- Management of virtualized services
  You can find information about the tasks that you can perform and manage on the virtualized services that run on Rational® Test Automation Server. You can start or stop the stubs connected to Rational Test Automation Server. You can view the stub usage statistics and the routing rules configured for the stubs, agents, or proxies that are connected to Rational Test Automation Server.
- Test results
  After the tests or schedules are run and completed, you can view the results and reports in IBM® Rational® Test Automation Server to analyze the verdict, the performance, and statistics. You can also re-execute tests and schedules from the Result page with the same commit id.
- Resource Monitoring service
  When you apply load to a system under test, the amount of resources consumed by your system is increasing. If the capacity of the resources does not match the load, you can see performance issues in the results. The Resource Monitoring service in Rational® Test Automation Server helps you monitoring the resources of a system and establish the performance metrics of the system. Thus, you can observe the health of these resources while a schedule is running.
- Integrating with other applications
  You can integrate certain applications with IBM® Rational® Test Automation Server to run tests and view the test results.
- Managing access to the server
  Desktop clients and third-party integrations use offline user tokens to connect to Rational® Test Automation Server.

Setting up a remote Docker host system

You must set up a system to host the remote Docker host. You can set up the remote host with a non-secure mode of connection with IBM® Rational® Test Automation Server.

Procedure

Locate a remote computer or Virtual Machine (VM) that acts as the remote Docker host system. The remote systems must be running on Ubuntu V18.04 or later, and has a minimum of 16 GB RAM.
Install Docker Enterprise Edition for a non-secure mode of connection with IBM® Rational® Test Automation Server.
For more information, refer to the related links.
As a system administrator of the remote system, specify a port to access the Docker daemon in the docker.service file located in the directory /lib/systemd/system. You must add the configured port at the line in the file:

ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:PORT

For example, if the port configured is 4342, then the line must read as:

ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:4342
Restart the Docker service by using the following commands:

$ sudo systemctl daemon-reload

$ sudo systemctl restart docker
Run the following command on the remote Docker host system to get access to the Docker repository:

$ sudo docker login <host_name> -u <username> -p <password>

Where, <host_name> is the host name of the remote Docker host system, <username> and <password> are your credentials to log in.
Pull the following images from Rational® Test Automation Server to the remote host system:

Docker images of: hcl-onetest-studio, hcl-onetest-virtualization

You can use the following command to pull the image:

$ sudo docker pull <host_name>/ot/hcl-onetest/studio:10.1.0

$ sudo docker pull <host_name>/ot/hcl-onetest/virtualization:10.1.0

Results

You have set up the remote Docker host system that can be accessed in a non-secure mode.

What to do next

You can set up a secure remote Docker host system optionally, that enables a secure connection with Rational® Test Automation Server.

You must configure the remote Docker host on Rational® Test Automation Server.