Appendix F Working With Rule Debugger : Rule Debugger Profiles Settings

Rule Debugger Profiles Settings
This section explains how to configure profile settings for local or remote debugging. See Running Rule Debugger and Configuring Rule Debugger Profiles for related procedures.
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  To enable debugging against a remote BusinessEvents engine, you must specify its host name and Java Debug Interface (JDI) port number. All sections below apply to both local and remote debugging, unless specific information for remote debugging is provided in the text below. Configuration is also required. See Configuring a BusinessEvents Engine for Remote Debugging.
Configuration Name
Provide a descriptive name for the profile.
BE Home
Specify the directory in which BusinessEvents is installed, for example, C:/tibco/be/3.0.
Remote Debugging  This setting is not used for remote debugging.
BE Program Arguments
Provide options and parameters as you would if you were starting the BusinessEvents engine at the command-line.
Remote Debugging  This setting is not used for remote debugging.
BE TRA File
Identify the path and name of the property file (be-engine.tra) used when starting the engine, for example:
c:/tibco/be/3.0/bin/be-engine.tra
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.
When you manage the engine for your BusinessEvents application using TIBCO Administrator, then by default the property file used to start the engine is located here:
TIBCO_HOME/tra/domain/domain-name/application/app-name/app-name.tra
BE Working Directory (and Log File Location)
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.
Working Directory and Log File Location   If you use the dot value, be aware of the following difference in the location of the working directory, and therefore engine-name.log file:
When you start BusinessEvents tools from the command line (and in its default location in the BusinessEvents bin directory), the working directory will be BE_HOME\bin\logs.
When you start BusinessEvents Tools from TIBCO Designer, the working directory will be TIBCO Designer_HOME\bin\logs.
Path names that do not start with the root directory are assumed by the operating system to start from the working directory.
Remote Debugging  This setting is not used for remote debugging.
BE EAR File
Location of the BusinessEvents EAR file of the project you want to debug.
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.
Attach
This setting is used only for remote debugging.
Remote Debugging  Check this checkbox if you are configuring a profile for remote debugging.
Host Name
This setting is used only for remote debugging.
Remote Debugging  Provide the name of the machine on which the remote BusinessEvents engine runs.
Port
This setting is used only for remote debugging.
Remote Debugging  Provide the JDI port number, as specified in the remote engine’s property file. See Configuring a BusinessEvents Engine for Remote Debugging.
Edit Defaults
Click to display the Default Configuration Properties dialog. See Edit Default Configuration Properties Dialog, next.
Edit Default Configuration Properties Dialog
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.
Profiles XML File
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.