Appendix F Working With Rule Debugger : Rule Debugger Setup Overview

Rule Debugger Setup Overview
You can run Rule Debugger without additional setup when you invoke it from TIBCO Designer while a BusinessEvents project is displayed. However for other uses, some additional setup is required. This section summarizes the setup and points to other sections for more details.
Creating and Managing Profiles
When you run Rule Debugger at the command line, you must select a profile after the user interface displays. Each debugger profile specifies an EAR file that contains a BusinessEvents application configuration, as well as some other information about property files and startup options. See Configuring Rule Debugger Profiles for more details.
Running Rule Debugger Against a Remote Engine
You can run rule debugger against a BusinessEvents application running on a remote BusinessEvents engine. Note the following differences when you run against a remote engine:
Remote Engine Configuration  Before running debugger remotely you must ensure that the remote engine’s TRA file is configured to enable remote debugging. See Configuring a BusinessEvents Engine for Remote Debugging.
EAR File and TRA File Location  If the remote application’s EAR file and TRA file are not accessible to the debugger, copy them to the local machine (or to a shared network drive) and specify that location in the debugger profile. For accurate debugging, do not change the copied files or filenames.
Console Tab is Unavailable  When you use the debugger on a remote BusinessEvents engine, the debugger console tab (which shows the engine’s console output) is not available.
Providing Data to the Application
You may have to provide sample messages to trigger rules to fire. In TIBCO BusinessEvents Getting Started, the first tutorial explains how to using ActiveMatrix BusinessWorks activities and the ActiveMatrix BusinessWorks tester feature to provide input to a BusinessEvents application.