Starting a debug session

You can begin a debug session from the Administrative Script debug launch shortcut or from the WebSphere Administrative Script launch configuration. When you use a launch shortcut to start a debug session, the Debug action that you use creates a launch configuration for you.
Note: WebSphere Application Server v6.1 must be started before using the Jython debugger.

Before you can start a debug session for Jython script, the script should be in a project in your workspace and it must contain a set breakpoint. To learn more about preparing for a debug session, see the related topic.

To launch a debug session from the Administrative Script debug launch shortcut:

  1. Open a workbench perspective that offers the launch/debug/run action set (such as the Java perspective).
  2. In a project file Navigator view, select the file that you want to debug.
  3. Perform one of the following tasks:
    1. Select the workbench toolbar Debug push button.
    2. Select the down-arrow beside the workbench toolbar Debug push button and choose Debug As >Administrative Script from the menu.
    3. Choose Run > Debug As > Administrative Script from the workbench menu bar.
    4. Right-click the file and select Debug As >Administrative Script from the pop-up menu.
  4. This will either launch a debug session for the file or open the Debug launch configurations dialog box, pre-filled with information about the script. If you need to change any of this information, refer to the information topics that cover launch configuration usage. To launch the debug session with the existing information, click Debug.

The Jython debugger may take some time to start up as it connects to Websphere Application Server. Watch for the message Starting the jython debugger on the status line (bottom right-hand corner of the workbench). When this message no longer displays, the script is suspended at the first breakpoint and the stack frames are displayed in the Debug view.

When you use the Jython debugger for the first time, the debugger builds an index of run time jars and caches the index in a predefined directory. You will see messages beginning with sys-package-mgr*: processing new jar in the Console view. This caching operation is performed only once per WebSphere Application Server run time.

You can also create a launch configuration manually. For information about this, see the related topic.

Related tasks
Preparing to debug
Using the Jython debugger launch configuration

Feedback