Testing and Debugging Projects : Launch Configurations Reference

Launch Configurations Reference
 
The Source, Classpath, and Common tabs are standard Eclipse dialogs. See Eclipse help for details on use of those tabs. For example if the project uses third party JARs, you must also reference them in the Classpath tab.
For Testing and Local Debugging
 
Browse to select the name of the BusinessEvents project to use for this configuration. You can select from projects in the workspace. The project currently selected in Studio Explorer appears by default.
Optional. Provide any options and parameters just as you would if you were starting the BusinessEvents engine at the command-line.
CDD File Location
Select the name of the processing unit (PU) whose values are used for this launch configuration. The drop-down list displays PUs available in the CDD specified in the CDD File Location setting.
Working Directory
The location of the working directory for the BusinessEvents engine. Used to store temporary files and logs. Browse to and select an existing directory.
Path names that do not start with the root directory are assumed by the operating system to start from the working directory.
For Remote Debugging
You can debug a running BusinessEvents engine on the current machine or another machine
Browse to select the name of the BusinessEvents project to use for this configuration. You can select from projects in the workspace. The name of the BusinessEvents project in the workspace. It must be the same as the project that is running remotely.
Remote Connection
Enter VM arguments for running the remote VM. Alternatively, add these to the java.extended.properties property in the remote application’s runtime properties (TRA) file. Default value is:
-Xdebug -Xrunjdwp:transport=dt_socket,address=25192,suspend=n,server=y
Default is localhost.