T-Plan Ltd Home
T-Plan Robot Enterprise 4.4.5 Doc Collection
06/12/18

T-Plan Robot Enterprise 4.4.5 Release Notes

Build No.  4.4.5-20181206.1


Contents

1. Client System Requirements
1.1 Java Requirements
1.2 JDK Installation & Configuration
2. Server System Requirements
3. Installation
4. License
5. Upgrade And Migration
6. Uninstallation
7. Startup
8. Integration With T-Plan Professional
9. Optimizing Performance
10. Troubleshooting

1. Client System Requirements

T-Plan Robot Enterprise runs in a client-server scenario where the client system executes T-Plan Robot Enterprise and automates the server system (System Under Test, SUT) through one of the supported remote desktop technologies (such as RFB/VNC). As the client and server systems may be two fundamentally different platforms, we list the client system (discussed in this chapter) and server system requirements (the following chapter) separately. These are the requirements for the client system running T-Plan Robot Enterprise:

Item
Minimum
Recommended
Processor (CPU)
Not set1
2GHz+
Memory (RAM)
128MB (required by Java)2
512MB+
Free Disk Space
50MB for Robot alone. Add approx. 50/100MB for the Java JRE/JDK installation.
200MB+
Operating System
Any system supported by Oracle's Java 8+ or compatible.
64-bit OS preferred for memory intensive2 deployments.
Web Browser
Internet Explorer 6 and higher
Mozilla Firefox 3 and higher
Google Chrome 1 and higher
Opera 9 and higher
Apple Safari 3 and higher (limited support due to missing XPath support)
Any other web browser supporting XML, XSLT and XPath

Installed Software
1. Windows Installer 3.1 (WindowsInstaller-KB893803-v2-x86.exe) - only for users installing the Robot's .exe distribution (see Installation)
2. Java (JRE or JDK) version 6 or higher (see the Java Requirements and JDK Installation & Configuration chapters below)
3. Tesseract OCR (optional) if text recognition on the SUT screen is required (details).
Latest Java SE (JDK) from Oracle Inc. supported by Robot (see table)
1 Slower processors will result in slow performance of graphical operations, such as image comparison or OCR.
2 The overall memory requirements depend on the SUT desktop size, the nature of graphical operations performed by the script and the number of parallel automated processes where the test suite is designed as a multithreaded one. If you experience errors with java.lang.OutOfMemoryError visible in the stack trace, raise the heap size allocated to the Java Virtual Machine (JVM) through the -Xmx option. The instructions are available in the Memory Adjustments chapter.


1.1 Java Requirements


T-Plan Robot Enterprise is a Java application and it will run on any system with Java 8 or higher installed. Though there are more Java producers T-Plan Robot Enterprise is being developed on Java from Oracle Inc. and we recommend you to use it as long as your platform (OS) is supported (see the list of supported systems). Support of particular Java releases is listed in the table below.

Robot Version
Supported Java Versions
Note
5.x
Java 8, 9, 10, 11, 12 Dynamic loading of plugins is not possible with Java 9+. The plugin JAR files must be put onto the class path or copied to the install folder. See the Startup chapter.
4.4.4+ Java 8, 9, 10, 11
Dynamic loading of plugins is not possible with Java 9+. The plugin JAR files must be put onto the class path or copied to the install folder. See the Startup chapter.
4.4 - 4.4.3 Java 6, 7, 8, 9
Dynamic loading of plugins is not possible with Java 9+. The plugin JAR files must be put onto the class path or copied to the install folder. See the Startup chapter.
Some features such as for example the iOS Mirror connection require Java 7+.
3.x-4.4.2 Java 6, 7, 8 Some features such as for example the iOS Mirror connection require Java 7+.

To verify whether Java is installed on your machine open a terminal window (Unix/Linux) or a command line prompt (Windows) and run the following command:

java -version

If Java is present on your machine and its binaries are on the system path it displays its version. If Java is not present you may download it for free from the following location:
Java is being shipped in two distributions, the Java Runtime Environment (JRE) and Java Development Kit (JDK). JRE is a subset of JDK and doesn't contain the Java source code compiler and libraries needed for development. T-Plan Robot Enterprise runs with both but certain functionality requires JDK, such as development and on-the-fly execution of Java test scripts and Java code blocks. If you plan on using this functionality, get a JDK. If you are used to Java development with NetBeans IDE, you may consider getting it from Oracle Inc. together with the JDK in one software bundle. Both components are open source and free. Installation of a JDK requires an update of the system path as is described in the following chapter.


1.2 JDK Installation & Configuration


If you plan on developing Java test scripts or using the Java code blocks you will need to install JDK and configure T-Plan Robot Enterprise in one of the following two ways:

Alternative 1: Configure the JDK path through T-Plan Robot Enterprise preferences (v2.3.3 and newer):
  1. Create a new Java test script through the File->New Test Script->Java Test Script in the T-Plan Robot Enterprise GUI.
  2. Right click the editor and select Compile.
  3. T-Plan Robot Enterprise will search known paths for the installed JDK packages. If it finds a JDK the compilation succeeds and no error is reported. Otherwise it will display a message leading to the Preferences window where you may set the JDK installation path or location of the javac compiler manually.
  4. Should you need to cancel the auto setting or to switch to another JDK you may reconfigure the path in Edit->Preferences->Java Test Script Interpret panel.
Alternative 2: Make T-Plan Robot Enterprise start using the java or javaw binary (all product versions). This method overrides the first alternative if both are set up.
  1. Option 1: Put the <JDK_dir>\bin path to the system path. This will make your OS use the JDK as a default interpret for all Java applications.
MS Windows instructions:
    1. Start Windows Explorer, right click the Computer node and select Properties in the context menu.
    2. Navigate to the Advanced tab or item (depends on Windows version) and select Environment Variables.
    3. Edit the Path system variable and put path to your JDK's bin/ directory followed by a semicolon to the beginning of the path (typically "C:\Program Files\Java\jdk1.8.0_<version>\bin;").
    4. Save the variable and close all windows with OK. 
    5. Open a command prompt and type javac. The command must be found and print out the supported parameters.
Other systems: Installation of JDK on other systems may or may not configure the system to use the JDK binaries by default. Refer to your OS documentation for information on how to adjust the system path list and/or associate Java applications with a particular Java distribution.
  1. Option 2: Replace "java" in the T-Plan Robot Enterprise start command with absolute path to the JDK's "java" binary. For example, on MS Windows edit the robot.bat file, replace "java" with "C:\Program Files\Java\jdk1.8.0_<version>\bin\java" and use the batch file to start T-Plan Robot Enterprise. For information on how to modify the other start up methods (Windows menu, starting from T-Plan Professional) see the Startup and Integration with T-Plan Professional chapters. 
To verify that Robot runs on top of the JDK restart Robot's GUI, select Help->About in the menu, switch to the System Information tab and make sure that the java.home property value points to the JDK install folder.


2. Server System Requirements


Server system requirements depend on the connection type (protocol) selected for the System Under Test (SUT) control. T-Plan Robot Enterprise 4.4.5 by default supports these connections:

Connection Type
Description
VNC Server
Testing over the RFB (VNC) 3.3, 3.7 or 3.8 protocol.
Static Image
Testing of image files or systems with image file output.
Android Over ADB
Testing of Android devices connected through the USB cable over the Android Debug Bridge (ADB) tool.
Local Desktop
Testing of applications and system components displayed on the local desktop.
iOS Mirror
Testing of iOS devices using a combination of AirPlay screen mirroring and the T-Plan or VNC server.
iOS Over Xcode
Testing of iOS 9 devices from Mac OS X with Xcode installed.
RDP Server
Testing over the RDP protocol.



3. Installation

T-Plan Robot Enterprise 4.4.5 is delivered in three forms:
  1. T-Plan Robot Enterprise with Windows installer (an .exe or a ZIP file containing an .exe file). This package can be installed just on MS Windows and it will allow you to manage the software as a standard Windows program. It also associates Robot with the .tpr test script file extension. The installer installs the tool into the C:\Program Files\T-Plan\Robot directory by default.
  2. T-Plan Robot Enterprise packaged as Mac OS X application (a .dmg or a ZIP file containing a .dmg file). This package can be installed on Apple Mac OS X only. To install the product on Mac OS drag the TPlanRobot application to Applications after the system opens the downloaded file.
  3. T-Plan Robot Enterprise ZIP file which is a self contained platform independent ZIP archive containing all necessary files. There's no installer. It can be used for all platforms including Windows and Mac OS. All you have to do is to unzip the file into a folder on your hard drive. The archive should contain at least the following files:
File Name
Description
robot.jar Java archive with compiled T-Plan Robot Enterprise classes.
jh.jar JavaHelp(TM) v1.1.3 library, distributed by Sun Microsystems Inc. under Binary Code License (BCL). Used to display Online Help (OLH) window in the GUI. When omitted the OLH functionality falls back to the web browser.
activation.jar
JavaBeans(TM) Activation Framework (JAF) v1.1.1 library, distributed by Sun Microsystems Inc. under BCL. Required by the JavaMail library. Not used directly by the product.
mail.jar
JavaMail(TM) v1.4.1 library, distributed by Sun Microsystems Inc. under BCL. It provides E-mail infrastructure for the SendMail command/Java API method call.
poi-3.6-20091214.jar Repackaged Apache POI 3.7 libraries distributed under Apache License v2.0. The archive contains contents of the poi-ooxml, poi-ooxml-schemas, xmlbeans and dom4j libraries. The old library name of poi-3.6-20091214.jar is preserved for compatibility with v2.1 and 2.2. For information on the POI and its subcomponent licenses see the LICENSE file. The library provides connectivity to MS Excel files through the Excel command.
javaparser.jar
Java Parser 1.0.8 library distributed under GNU Lesser GPL (LGPL). To upgrade the library simply replace the file and either put it on the class path or keep the same name to allow T-Plan Robot Enterprise to load it dynamically. The source code of the library packaged with the product is available here. The source code is equivalent to release 1.0.8 and it was not modified.
jna-3.5.1.jar
platform-3.5.1.jar
Java Native Access (JNA) 3.5.1 libraries distributed under GNU Lesser GPL (LGPL). To upgrade the library simply replace the file and put it on the class path. If the files are not put onto the class path Robot will search for any "jna- " and "platform-" prefixed JAR files and load them dynamically. The source code of the library packaged with the product is available here. The source code is equivalent to JNA release 3.5.1 and it was not modified.
JTattoo.jar
JTattoo Look And Feel (JTattoo binary license).
JNativeHook.jar
JNativeHook 2.0.3 library distributed under GNU Lesser GPL (LGPL) v3. To upgrade the library simply replace the file and either put it on the class path or keep the same name to allow T-Plan Robot Enterprise to load it dynamically. The source code of the library packaged with the product is available here. The source code is equivalent to release 2.0.3 and it was not modified.
cron4j-2.2.5.jar
Cron4J 2.2.5 library distributed under GNU Lesser GPL (LGPL). To upgrade the library simply replace the file and either put it on the class path or keep the same name to allow T-Plan Robot Enterprise to load it dynamically. The source code of the library packaged with the product is available here. The source code is equivalent to release 2.2.5 and it was not modified.
gson-2.5.jar
GSON 2.5 (Google JSON parser) distributed under Apache License v2.0.
robot.sh T-Plan Robot Enterprise start script for Unix/Linux. See the 6. Startup chapter for more information.
robot.bat T-Plan Robot Enterprise start script for Windows. See the 6. Startup chapter for more information.
imgcompare.sh
Script for offline CLI image comparisons for Unix/Linux. See the 6. Startup chapter for more information.
imgcompare.bat Script for offline CLI image comparisons for Windows. See the 6. Startup chapter for more information.
install.html A copy of this T-Plan Robot Enterprise 4.4.5 Release Notes document.
LICENSE.txt License text. Please read carefully before you start using T-Plan Robot Enterprise.
crc32.properties
CRC32 check sums of all installed files for the Update & Upgrade feature.
help/
Directory with help topics and Java API documentation.
plugins/
Default drop-in folder for plugins. It may or may not exist.

T-Plan Robot Enterprise also relies on unmodified FFmpeg libraries version 3.0.1 which are distributed under GNU Lesser GPL (LGPL) v3. These are packaged inside the robot.jar file where they can be replaced with a newer version provided that the file names are preserved. The FFmpeg 3.0.1 source code is available at Zeranoe or at our site.

One machine can host multiple T-Plan Robot Enterprise installations. If you however execute more than one program instance at the same time under the same user account, they will overwrite the user specific configuration files because there's no synchronization or locking mechanism in place.


4. License

T-Plan Robot Enterprise requires a valid license to run. There are two supported mechanisms:

License Server

License server is the default option starting with release 4.3. You must install and run a licensing server. If you are about to switch from a file based license key to the license server please read the instructions below.
    1. Through the Tools->License Key Manager window in the GUI. This will store the server address under the ls.address key to the user configuration file.
    2. Specify the address through the --licenseserver CLI option.
    3. Solutions integrating Robot into 3rd party Java frameworks and/or applications may specify the license key path or  a list of semicolon separated paths through the robot.licenseServer system property (since v4.4). It must be done before the ApplicationSupport class gets instantiated. This option is available since v4.4. Example:
      System.setProperty("robot.licenseServer", "mymachine:8880");
      ...
      ApplicationSupport robot = new ApplicationSupport();

IMPORTANT:


For compatibility reasons Robot prefers file based key settings to the server ones. If there's a file based key setting (even an invalid one) Robot will not check for the server. If you are switching from a file based key to the server please ensure that:


File Based License Keys
File based keys are maintained for backward compatibility with Robot v4.2 and older. They are provided for new contracts only where the server is not suitable. The key is an encrypted file with the .tlic extension which contains details of your license, such as: When you purchase a T-Plan Robot Enterprise license, you should also receive one or more license keys. For security purposes the file may be delivered to you separately from the product, for example by an E-mail from a T-Plan Ltd sales representative. There are several options to install it:
  1. Save the key file to the T-Plan Robot Enterprise installation directory (where the robot.jar file is located). As the tool checks the folder for any license key files on startup, it will be picked up right away. There might be any number of license files in the installation directory.
  2. Alternatively save the key file to a custom location on your hard drive and take advantage of the License Key Manager to register it. To open the Manager start T-Plan Robot Enterprise in the GUI mode (with no custom CLI arguments). If you have no valid license installed, the tool will display a "No license" error message and it allows you to start the License Key Manager. If you already have a valid license installed, you may start the window through the Tools->License Key Manager menu item. Then add the file to the list of registered license keys. Be aware that the list of such files (meaning keys outside of the installation directory) is saved to a list in the user preferences and it may get lost during migration unless you copy the user configuration file as well. Any change in license key configuration requires product restart.
  3. Specify the key path(s) through the --licensekey CLI option.
  4. Solutions integrating Robot into 3rd party Java frameworks and/or applications may specify the license key path or  a list of semicolon separated paths through the robot.licenseKey system property. It must be done before the ApplicationSupport class gets instantiated. This option is available from v4.0.3. Example:
    System.setProperty("robot.licenseKey", "C:\\MyData\\robot.tlic");
    ...
    ApplicationSupport robot = new ApplicationSupport();
File based keys keys may be freely combined. It means that you may have any number of license keys installed at a moment regardless of whether the files are in the installation folder or outside of it. The number of connections will be then equal to the sum of licensed connections of all installed valid licenses. This system allows you to purchase additional licenses and plug them into the product easily when you need to scale up.


5. Upgrade And Migration

To upgrade T-Plan Robot Enterprise v2.0 or higher with a new release follow these steps:

Alternative 1: Automatic Upgrade (v2.3 and higher)

Automatic upgrade offers a comfortable and reliable way of promoting your product to a newer version through the GUI. Unlike manual upgrade the automatic process is secured against file corruption (CRC32), detects customized/modified product files and it is able to restore the original product in case of update failure. Steps:
  1. Select Tools->Update & Upgrade in the GUI. If Robot complains of insufficient write permissions, restart it with administrator privileges:
cd "C:\Program Files\T-Plan\Robot\robot"
robot
cd "C:\Program Files (x86)\T-Plan\Robot\robot"
robot
    1. Linux, Unix, Mac OS: Log in as root or run Robot with sudo ("sudo robot.sh")
  1. Select the target release in the tree, hit Download & Install, leave the window with OK and restart the application. Details of the upgrade process are available in the Update & Upgrade help topic.

Alternative 2: Manual Upgrade (all versions)

  1. Download the desired standalone cross-platform ZIP release. You may get it from any of these resources:
  2. If you have modified or customized any of the product files (such as for example the start scripts of robot.sh or robot.bat), make a back up and restore them after the update process. You don't need to back up test scripts, template images or configuration files because they will not be affected.
  3. Unzip the ZIP archive to the installation folder and say yes to overwrite the files. The install folder is the directory which contains the robot.jar file:

Migration of T-Plan Robot Enterprise is fairly straightforward. Standalone ZIP releases may be simply copied and moved across the file system or even to another machine or machines with different operating systems. If you migrate to another machine, copy also  user specific configuration files to the user's home folder to keep any preference changes.

Migration of product installed by Windows Installer is possible only through reinstallation. You may however create a standalone cross-platform Robot instance by copying the product files from the installation folder to another location. Such a product may be then started through the robot.bat script or through a direct Java command as is described in the Startup chapter.

A Mac OS X release may be simply moved and/or copied as long as you copy the whole /Applications/TPlanRobot.app folder. You may also create a standalone cross-platform Robot instance by copying the product files from the /Applications/TPlanRobot.app/Contents/Resources/Java folder to another location. Such a product may be then started through the robot.sh script or through a direct Java command as is described in the Startup chapter.


Should you expect any unexpected start up or desktop connection errors after an upgrade or downgrade (migration to a lower version), perform the following steps to restore the factory settings:

6. Uninstallation

If you installed T-Plan Robot Enterprise through the Windows installer, you may uninstall it through the Windows software manager (Control Panel->Add Or Remove Software on older Windows versions, Control Panel ->Programs And Features on Windows Vista).

To uninstall T-Plan Robot Enterprise installed from the ZIP file delete the files unzipped during installation. You may also delete the user configuration files. The tool doesn't create any other files or registry entries except automation outputs such as screenshots, template images and automated test reports.

7. Startup

To start T-Plan Robot Enterprise:
MS Windows:
Mac OS X:

Linux/Unix:

For help on CLI commands run robot.sh -h, resp. robot.bat --help. For a complete reference see the T-Plan Robot Enterprise 4.4.5 CLI Reference. If the tool fails to start, review the Troubleshooting chapter at the end of this document. The wrapper scripts actually just start Java with proper options. If you need to customize the T-Plan Robot Enterprise start command use the following syntax: It is NOT RECOMMENDED to start the tool as "java -jar robot.jar" or through double clicking onto the robot.jar file. It fails to populate class path of the Java compiler. The tool may refuse to compile or even run the Java source code (such as Java test scripts and Java code blocks embedded in regular scripts).

NOTE: As Java 9 introduced new security restrictions it is no longer possible to load 3rd party Java libraries (JARs) on the fly. All these files must be listed after the -classpath option of the above command. Pay attention to this requirement especially if you are upgrading from an older Robot release and you rely on the custom CLI start commands. This limitation does not apply to script and feature plugins delivered as JAR files by T-Plan Ltd.

There are two modes: See the CLI Options Specification document available in the T-Plan Robot Enterprise Help or online in the T-Plan Robot Enterprise 4.4.5 CLI Reference.

Once the GUI is up and running, open Help for instructions on how to use T-Plan Robot Enterprise. There should be a complete documentation set included. All the documents/document collections are also available online at http://www.t-plan.com/robot/docs.

T-Plan Robot Enterprise can be also used for offline image comparison through a simple CLI interface. To explore this feature either run one of the wrapper scripts imgcompare.sh (for Unix/Linux) or imgcompare.bat (for Windows) or invoke Java directly as follows:

8. Integration With T-Plan Professional

T-Plan Robot Enterprise may be on Windows tightly integrated with T-Plan Professional 7.0 or later. It means that T-Plan Professional offers in its GUI actions starting T-Plan Robot Enterprise. This integration is based entirely on the public CLI parameters described in the Robot's CLI reference. Integration principles are well described in the Integration Reference.

There are two ways to configure how T-Plan Professional starts T-Plan Robot Enterprise:
  1. To configure T-Plan Robot Enterprise installation path navigate to the Installed Extensions module of T-Plan Professional as is described in the T-Plan Professional 7.0 Integration Overview chapter of the Integration Reference.
  2. Should you need to modify the T-Plan Robot Enterprise base start command (for example in order to use a custom Java environment or to raise the amount of heap memory allocated by JVM), perform the following steps:
    1. Locate Robot's extension configuration file RobotExtn.ini. The file gets created when T-Plan Robot Enterprise is called for the first time from T-Plan Professional GUI. It is saved to the application data folder whose location depends on the Windows version and configuration. Typical paths are:
    2. Edit the file. It contains a bunch of command templates where each one corresponds to a specific action invoked from T-Plan Professional GUI, such as:
      Run=java -Xmx256m -cp "%1\robot.jar;%1\jh.jar;%1\activation.jar;%1\mail.jar;%1\poi-3.6-20091214.jar" com.tplan.robot.ApplicationSupport
    3. Adjust the commands to your needs. The %1 variable in the example above will be replaced with the product install path specified in the previous paragraph. Each command may contain additional variables which are populated with CLI option values by T-Plan Professional.
    4. Save the file and restart T-Plan Professional to pick up the changes.

9. Optimizing Performance

As T-Plan Robot Enterprise can be employed in various automated testing scenarios and environments, its performance may be significantly improved through fine tuning.

Memory Adjustments

As T-Plan Robot Enterprise performs memory intensive image processing, the tool may eventually run out of memory. This is usually experienced as a crash with a java.lang.OutOfMemoryError or java.lang.StackOverflowError stack trace seen in the console window (command prompt on Windows). The first aid is to raise the amount of memory assigned to the Robot process:

  1. Locate the Robot's java start command based on your start up preference:
  1. When Robot fails with a java.lang.OutOfMemoryError you need to raise the heap size. The -Xmx parameter after the java  (or javaw) command indicates how much heap memory is your Java Virtual Machine allowed to use at a maximum. Raise this number to a higher value. For example, -Xmx512m allows the JVM heap to grow up to 512MB if needed. This limit doesn't mean that the memory is allocated immediately.
  1. When Robot fails with a java.lang.StackOverflowError raise the stack size through the -Xss parameter. The syntax is the same as the -Xmx one. As the defauIt stack size is typically between 384k and 512k for x86 systems and 1MB for x64 ones it is usually sufficient to increase the stack memory to 1MB on x86 (-Xss1m) or to 2MB on x64 (-Xss2m).
Though Java is likely to accept any number up to the size of your RAM through the -Xmx switch, the behavior is further subject to the system architecture:
Tips to minimize the memory consumption:
If you experience memory problems that can't be resolved using the hints above please get us a memory dump from the failing Robot process. You may create it through clicking onto the memory monitor at the bottom right corner of the Robot  3.1.1+ GUI. Alternatively start Robot with the -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=./java_pid<pid>.hprof switches after the java (javaw) command to make the process create the dump automatically. See the Oracle documentation for details.


Client Side Configuration

T-Plan Robot Enterprise supports a large number of configurable parameters which may improve performance of both the Robot application as well as the VNC connection. The following table lists the most important ones.

Parameter Name (Location)
Description
Encodings
(GUI:Preferences->RFB (VNC) 3.x Client)
Encodings specify how the image data transferred between Robot and VNC server is encoded. They are specified as an ordered list where the first (topmost) item has the highest priority. Each encoding uses a different algorithm of encoding the image data to trade off between the volume of data transferred over the network (better compression = less data) and the local CPU resources needed to decode it.
  • If your VNC server is in a remote location or the network is slow and your local CPU is reasonably fast, move one of the encodings with high compression such as Tight, Zlib or Hextile to the first place.
  • If your local CPU is slow and the network is fast, try Hextile, RRE or CoRRE which have low compression but are cheap to decode.
  • Do not prefer (set as the first) the Raw encoding. It is the least efficient one where the pixels are transferred in raw form with no compression. Keep it however somewhere low in the list because some simple servers (such as mobile device or embedded system ones) support just this one and require it to be present.
  • Keep the Cursor encoding in the list (in any place) unless you experience problems (some servers don't like it and tend to crash when it is present). It makes the client (Robot) render the cursor locally rather then encoding it into the desktop image. This leads to significant desktop performance improvements on slow network environments. It also makes the image comparison easier and more reliable.
To observe efficiency of encodings set the "Console debug logging" parameter in the same panel to "Full" and check the console window (command prompt) for performance data.
Script editor behavior (GUI: Preferences->Execution)
The script editor in Robot's GUI is by default configured to compile any script changes after a preset amount of idle time. This may lead to slower GUI performance, especially where long scripts are being edited and/or there are multiple open editors and/or one or more scripts are Java source code or call Java source code through the technology of Java code blocks. Consider setting off the auto compilation and compile manually only when needed through the editor context menu or Script->Compile in the main application menu.
Connection pooling (Java API)
Connection pooling allows to reuse server connections which avoids the overhad of reconnection. This mechanism can be applied just from the Java API. See the RemoteDesktopClientFactory class documentation for details.


Server Side Configuration

There are several simple recommendations which may significantly improve performance of the client-server connection:

10. Troubleshooting

This chapter is intended to document the most common install and set up errors. If you meet an issue which is not described in here, report it through the Enterprise contacts at http://www.t-plan.com/support.html.

T-Plan Robot Enterprise fails to start with a message "java: command not found"

There's no Java installed on your machine or path to the Java executable is not included in your OS path. Read chapter Client System Requirements of this document.

T-Plan Robot Enterprise fails to start with a message "Exception in thread "main" java.lang.NoClassDefFoundError: com/tplan/robot/ApplicationSupport"

This indicates that the T-Plan Robot Enterprise JAR (Java ARchive) file robot.jar is not correctly included in the Java class path.

T-Plan Robot Enterprise starts but prints out a message "JavaHelp libraries not found. Please make sure that file jh.jar is included in the Java class path."

This indicates that the JavaHelp JAR file jh.jar is not correctly included in the Java class path. The tool will run but you will not have access to the online help. Some links which open in a web browser may however work fine. As all the help documents are available online at http://www.t-plan.com/robot/docs, you may switch to the online documentation and ignore this error. To resolve it:

T-Plan Robot Enterprise fails to start with a NoClassDefNotFoundError, NoSuchFieldError or any other severe Java error

Unless one of the cases listed above applies, these problems are typically experienced when you use Java of version lower than the required one. See the Client System Requirements chapter for required Java version and run java -version to find out which version you have installed.

Either the robot.sh or robot.bat script fails to pass some CLI options

The wrapper script can't handle more than 9 options. All options above this limit are ignored. You must run Java directly as is described in the Startup chapter.

T-Plan Robot Enterprise crashes with java.lang.OutOfMemoryError

Raise the memory limit as is described in the Memory Adjustments chapter.