Lotus® Expeditor's remote debugging function automatically builds, packages, deploys, and launches your project on a target device. In order to debug a Lotus Expeditor application, you must launch it using specific debug options. You can launch Web applications or Client Service applications using a Debug Launch Configuration from the Expeditor on Device launcher in the toolkit.
In the Eclipse based IDE, select Debug...
, then create a new Expeditor on Device launch configuration. Select the name of project you want to debug, and select a device type. For Connection Properties, supply the IP address or host name of the remote system if required, and leave the default values for other settings.
When attempting to remotely debug or run an application on a device, ensure that Lotus Expeditor is not already running on the device. Do not use the autostart option and always double check that no other Lotus Expeditor applications are running before initiating a debugging session.
If a problem occurs while launching a bundle on a device, check the error description in the console output view or from the log file. The problems may be caused by unexpected errors from the bundle.
Normally, in order to perform remote debugging on a device you only need to install the debugging CAB on a device. However, if the device has a Platform Builder created runtime, the debugging CAB will not be able to determine the Lotus Expeditor install location. Therefore, you must manually set up the debugging functionality (as in previous releases of Lotus Expeditor). This means copying a debugging version of J9 to the WECE plugin folder on the device, and editing the config.ini
file (located in the eclipse\\configuration
folder) to add the key osgi.console=
. The debug version of J9 may be found under \\utils\\debug
on the Lotus Expeditor Client DVD. Select the one appropriate for your device operating system.
The J9 console is not navigable on Windows® Mobile Standard edition. Therefore, you will not be able to enter OSGi commands on the device or scroll the output pane. The work-around for this is to remotely connect to the device from the IDE. This will provide the console within the IDE.
Parent topic: Debugging and testing applications: XPD622