T-Plan Home
T-Plan Robot Enterprise 4.3.1 Doc Collection
GUI Reference

T-Plan Robot Enterprise 4.3.1 RAP Server

1. Overview
2. Connecting To RAP Portal
3. Data Synchronization

1. Overview

T-Plan introduced the Robot Automation Portal (RAP) product in 2016. It is a web portal allowing to monitor and manage T-Plan Robot Enterprise driven automation over the TCP/IP network (internet and/or intranet). For details see our web site.

To support communication with the RAP portal the T-Plan Robot Enterprise v4.2 delivered the RAP Server component. It is a TCP/IP server which communicates with the RAP portal. The functionality was significantly improved in the 4.3 release to address the new RAP generation.

2. Connecting To RAP Portal

To verify whether a Robot host is eligible for monitoring through RAP check that:
To start the RAP Server perform one of the following:
To connect the Robot host to the RAP portal register the Robot host in the web UI as:

Once registered the portal will establish a TCP/IP connection to the RAP Server running on the Robot machine.

Security Considerations:

As of Robot 4.3 the communication between Robot and the RAP portal is not encrypted. That is why it is recommended to use this set up only in trusted networks. To improve the security restrict the access to the Robot server through the IP or subnet mask (see the --rapmasks CLI option). Future versions of RAP/Robot will deliver SSL encryption. Should you be interested in this option please ask our support for the current status.

3. Data Synchronization

The RAP portal works on top of a relational database and stores two categories of data:
  1. Information about Robot projects, schedules and test scripts (called "work items" in the RAP terminology). The database does NOT store the script code (TPR of Java).
  2. Test results and test reports ("results")

Deletion of any records in the RAP portal removes them from the database only. It will NOT affect any data on the Robot host, such as projects, schedules, scripts or test results (test report files).

There are three ways to export work items to the RAP portal:

  1. Execution of a test script or a schedule while connected to the portal will export the item to the RAP database.
  2. Use the --rapdirs CLI option to make Robot synchronize work items at the specified file path(s) on the start up. This option is suitable where the GUI can't be used, for example on headless environments or when starting Robot remotely from a terminal (telnet, rsh).
  3. For manual synchronization in the GUI right click a project, a work item (a script or schedule tree node) or a relevant folder node in the Project View and select the "Synchronize with RAP".

Test results are being exported as follows: