Debug Configuration Reference
Debug Participants
The remote debuggers to run when the configuration is launched:
- Composite Debugger - Run a composite debugger.
- Java Component Debugger - Run a Java debugger. For information on how to use this debugger, see .
Advanced
Field | Description |
---|---|
Debug Participants | |
Composite Debugger - Port | The port of the composite debugger. |
XXX Component Debugger - Port | The port of the XXX component debugger, where XXX is Java or Spring. |
Field | Description |
---|---|
HTTP Connectors | Ports of the HTTP connectors used by the promoted services in the composite |
Node | Debug node. |
Enable Security Manager |
Indicate whether a security manager is enabled for the JVM running the debug node. Default: true. |
JVM Options |
Options passed to the Java virtual machine running the debug node. Default: -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError |
Log File |
File to which node logging messages are written. Default: Operating system-specific temporary directory /node uniqueID.log. |
Log Level |
Level of the logging messages wriĴen to the log.
Default: Info. |
Management Port | Port on which the debug node receives life cycle messages. |
OSGi Console Port | Port on which to access the node's OSGi console. Use the OSGi console to examine the runtime state of the node for debugging purposes only. For information on the features available in the OSGi console, see Explore Eclipse's OSGi console. |
Runtime | Debug node runtime artifacts and properties. |
Installation Directory | Directory containing the debug node executable. Default: TiBCO_HOME/tibcohost/3.2, which is the executable installed with TIBCO Business Studio - BPM Edition. If you change the value, the version of the executable must be the same as the executable that is installed with TIBCO Business Studio - BPM Edition. |
Instance Parent Directory |
Directory containing the debug node instance. Default: workspace/metadata/.plugins/ com.tibco.amf.tools.composite.launch. |
Provisioning Wait (ms) |
Time to wait between provisioning requests to the debug node. If set to zero, the default, the debug launcher uses notifications from the debug node to determine when the resource instances and connectors are ready for the next deployment request. If this fails, the application could fail to deploy. In that case, set a value in this field which can increase deployment time, because each provision request has a wait time. Default: 0. |
Substitution Variable Overrides | Substitution variable values defined by composite applications. You cannot override substitution variable values defined by DAAs. |
Common
See Help > Help Contents > Supplemental Eclipse Help > Plug-in Development > Environment Guide >
Tools > Launchers > JUnit Plug-in Test Launcher > Common tab .