Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 40 Testing and Debugging Projects : Adding and Working with Launch (Debug or Run) Configurations

Adding and Working with Launch (Debug or Run) Configurations
Launch configurations are of two types: run configurations and debug configurations. All launch configurations have the same basic fields, but debug configurations have extra settings for remote debugging.
Before you begin  Ensure that you know the EAR file location, the CDD file location, and the name of the processing unit (configured in the CDD file) that you want to use. (The processing unit runs as an engine.)
To Add and Work with Launch Configurations
A reference to the settings is provided in Launch Configurations Reference.
1.
You see the Debug Configurations or Run Configurations dialog.
2.
For testing or local debugging, select TIBCO BusinessEvents Application
For remote debugging, select Remote TIBCO BusinessEvents Application.
3.
To add a new configuration, click the New Configuration () button.
To duplicate a configuration, select the configuration and then click the Duplicate () button. Modify, then save as a new configuration.
When you add, edit or duplicate a configuration, Configuration fields appear in the right panel.
4.
Select the Main tab and configure values as explained in Launch Configurations Reference.
Select the Classpath tab and configure the classpath for external libraries or custom functions as needed, for example if the project uses Rendezvous or JMS channels. See Working with External Library and Custom Function Paths for details.
Select the Environment tab and configure environment variables as needed, to run or debug the project in TIBCO BusinessEvents Studio. You can add new variables. You can select and then edit existing variables. You can append your edited variable to the existing environment variable, or you can replace the existing environment variable with it. For example if a custom function depends on a native library, you can add the path to that library using the PATH, LD_LIBRARY_PATH, SHLIB_PATH, or LIBPATH variable, as appropriate for your operating system.
On Linux platforms when TIBCO BusinessEvents DataGrid is used, you must set LD_LIBRARY_PATH to AS_HOME/lib in the Environment tab.
Select the Common tab and set the Encoding to Other. Then select UTF-8 from the drop-down menu.
This procedure is documented in Plug-in Development Environment Guide > Reference > Launchers > JUnit Plug-in Test Launcher > Common Tab.
5.
If you selected Remote TIBCO BusinessEvents Application in step 2, you must connect to the remote engine. Click the Remote tab and specify the host name or IP address and port the engine is running on. Use the same JDI port number in the TRA file and in the debug configuration (see For Remote Debugging Only, Configure Java Debug Interface (JDI)).
6.
Click Apply to save configuration settings.
7.
Click Close and save the configuration you worked on.
If you have done the setup as explained in this chapter and are ready to run or debug, click Debug to save the configuration and launch the debugger, or click Run to save the configuration and run the engine.
You can then assert test data as desired in order to observe the effect of the data on the engine. See Asserting Rule Input Data.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved