Add and Work with Launch Configurations

A reference to the settings is provided in Launch Configurations Reference.

Note: For remote debugging you first have to set properties in the remote engine TRA file. See For Remote Debugging Only Configure Java Debug Interface (JDI) .

Procedure

  1. Do one of the following:
    • To create a debug configuration, click the down-arrow to the right of the debugger button () on the toolbar. From the drop-down list, and select Debug Configurations. Or, select Run > Debug Configurations.
    • To create a run configuration, click the down-arrow to the right of the Run button () on the toolbar. From the drop-down list, select Run Configurations. Or, select Run > Run Configurations.

      You see the Debug Configurations or Run Configurations dialog.

  2. Select an option from the list on the left:
    • For testing or local debugging, select TIBCO BusinessEvents Application
    • For remote debugging, select Remote TIBCO BusinessEvents Application.
  3. Do one of the following depending on your needs:
    • To edit a configuration, expand TIBCO BusinessEvents Application or Remote TIBCO BusinessEvents and select an existing debug configuration.
    • 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.
    • To delete a configuration, select the configuration and then click the Delete () button.

      When you add, edit or duplicate a configuration, Configuration fields appear in the right panel.

  4. If you selected TIBCO BusinessEvents Application in step 2, do the following:
    • 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.
      Note: On Linux platforms when TIBCO BusinessEvents DataGrid is used, you must set LD_LIBRARY_PATH to AS_HOME/lib in the Environment tab.
    • If you need to display characters that are not present in the system’s default charset on the console, set the encoding to UTF-8.
    • 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.

    • For information on standard Eclipse features incorporated into this area, see Eclipse help.
  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. Do one of the following:
    • 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.