Testing and Debugging Projects : Preparing to Run (Test) or Debug a Project

Preparing to Run (Test) or Debug a Project
You can do these tasks in any order. For information on setting up Tester Preferences, see Reference to Tester Preferences.
 
Build an EAR File
1.
You need to keep history value for the property in concept/event/scorecard to at least 2.
2.
If you want to build an EAR with Generate Debug Info Set, check the Generate Debug Info checkbox (checked by default).
This step is not required if you are working with test data. If you are using Rule Input data, follow the steps below.
3.
4.
Create Test Data (as Desired)
You can create test data for use across multiple sessions, or you can provide rule input data while the engine is running. See Creating and Working With Tester Data.
For Remote Debugging Only, Configure Java Debug Interface (JDI)
To configure for remote debugging you configure the BusinessEvents engine property file on the remote engine so the engine uses Java Debug Interface (JDI) for remote debugging.
You then configure a debug configuration for remote debugging, as explained in Adding and Working with Launch (Debug or Run) Configurations. You must specify the same JDI port number in the TRA file and in the debug configuration.
To Configure Java Debug Interface (JDI)
For each BusinessEvents engine you want to enable for remote debugging, do the following.
1.
Open the BE_HOME/bin/be-engine.tra file for editing.
2.
Specify the port on which you want the engine to listen, using the environment variable tibco.env.JDI_PORT, for example:
tibco.env.JDI_PORT 5192
Where 5192 is the default value. If multiple engines run on the same machine, ensure that each has a unique port.
3.
-Xrunjdwp:transport=dt_socket,address=%JDI_PORT%,suspend=na,server=y
4.