A profile specifies the EAR file whose rules you want to debug, and other supporting information. You can configure and save multiple profiles to point to different EAR files, or to the same EAR file but with a different configuration.
Remote Debugging This setting is not used for remote debugging.
Remote Debugging This setting is not used for remote debugging.
Identify the path and name of the property file (be-engine.tra) used when starting the engine, for example:
Remote Debugging Specify the location of the property file used to start the remote engine if it is available to the debugger session using the file system. If it is not available on the file system, specify the location of a copy of the original file that you save to an accessible location. Do not change the copy in any way.
The location of the working directory for the BusinessEvents engine. The default default value is a dot (
.), which means that the working directory is the directory where the BusinessEvents engine is started. The
be-tools and
be-engine executables are normally started in the
TIBCO_HOME\be\3.0\bin directory.
Remote Debugging This setting is not used for remote debugging.
Remote Debugging Specify the location of the EAR file of the project you want to debug if it is available to the debugger session using the file system. If it is not available on the file system, specify the location of a copy of the original file that you save to an accessible location. Do not change the copy in any way.
Remote Debugging Check this checkbox if you are configuring a profile for remote debugging.
Remote Debugging Provide the name of the machine on which the remote BusinessEvents engine runs.
Remote Debugging Provide the JDI port number, as specified in the remote engine’s property file. See
Configuring a BusinessEvents Engine for Remote Debugging.
Complete the values you want to use as default properties when you click the New Profile button

in the Edit Debug Configurations dialog. See above for details on the meaning of each setting.
Profile settings are saved in XML format in the be-tools.debugger.config file, stored in the user’s
.TIBCO directory. For example, for a Windows user called jsmith, the location would be
C:\Documents and Settings\jsmith\.TIBCO.