Files

T-Plan Robot Enterprise Text And Data File List

1. List of files bundled with the T-Plan Robot Enterprise code

File Name

Location

Description/Purpose

Messages_en.properties

com/tplan/robot

Primary resource bundle (Java .properties format). It contains English software messages used by the product UI.

EntMessages_en.properties

com/tplan/robot

Secondary resource bundle with Enterprise version specific strings (Java .properties format). It contains English software messages used by the product UI. 

MenuAndToolbar.properties

com/tplan/robot

Definition of the product GUI menu and tool bar content (Java .properties format).

DefaultConfiguration.properties

com/tplan/robot

Default values of user preferences (Java .properties format). It gets loaded by the UserConfiguration class.

PluginMap.xml

com/tplan/robot/plugin

Default map of plugins. It defines exposed functional interfaces as well as plugins bundled with the product. It gets loaded by the PluginManager class.

report_template.html

com/tplan/robot/scripting/report

Template HTML file for the default report provider DefaultReportProvider.

template.xsl

com/tplan/robot/scripting/report

Template XSL file for the Enterprise report provider XSLReportProvider.

.

com/tplan/robot/images

Product icons and images.

.

<install_path>/help

Product Online Help (OLH) files. They are delivered outside of code as part of the binary release.

2. List of files created by T-Plan Robot Enterprise on hosting machines

The product writes the following files to the hard drive:

  1. Copy of user preferences. It saves all changes to the default preference values defined by the DefaultConfiguration.properties file. The file format is Java .properties. File name and location is defined by the ApplicationSupport.APPLICATION_CONFIG_FILE variable and points currently to a file called tplanrobot.cfg in the user home folder.
  2. Copy of plugin map. It saves all changes applied to the default map defined by the PluginMap.xml file. File name and location is defined by the PluginManage.EXTERNAL_PLUGIN_XML variable and points currently to a file called PluginMap.xml in the user home folder.