Show TOC Start of Content Area

Procedure documentation Starting Remote Debugging  Locate the document in its SAP Library structure

Use

During the remote debugging, you cannot deploy or use applications on the server nodes in debug mode. If there are server nodes that are not in debug mode, they can handle the application or deployment requests instead. Otherwise, the whole server instance is used for debugging only.

There are two possible cases:

      You need to debug a single-server configuration

In this case, you need to deploy the application before you change to debug mode and start debugging.

·        You need to debug a multiple-server configuration

In this case, you do not need to deploy in advance, since the server processes free of debugging can receive the deployment request.

Prerequisites

·        The server has nodes that are running in non-debugging mode (so that deployment can be handled)

·        The AS Java is defined in the SAP AS Java preferences

More information: Configuring the Application Server in the Developer Studio.

·        The server has debuggable nodes

Procedure

...

       1.      In the Project Explorer, choose the Enterprise Application Project representing the application to be debugged.

       2.         (Only if this is a single-server configuration) Deploy the application:

                            a.          In the context menu, choose Publish.

                            b.          Specify server settings as necessary and choose Finish.

If this is the first time you deploy applications for this session of the Developer Studio, it will prompt you to submit Software Deployment Manager (SDM) username and password.

The Developer Studio deploys the application on AS Java.

       3.         In the context menu, choose Debug as Debug on Server.

       4.         Specify server settings as necessary and choose Finish.

Note

Always choose the SAP Launch, not the Web Browser option. The Web Browseroption does not initiate a debugging session but simply runs the application.

Note

The Developer Studio always tries to deploy the application before initiating a debugging session. Since single-server configurations cannot accept deploy requests, the deployment process fails and the Deploy View Console shows error messages. You should ignore them.

The Developer Studio launches a Web browser window inside the Developer Studio or externally, depending on the browser settings specified.

Initially, the Developer Studio generates a special debugging URL, which contains the debugging session key. That key determines the server process that will receive the application request. On that process, the application request is immediately redirected by the Web Container to a new URL hiding the debugging session key.

       5.      When the application execution reaches a breakpoint, the Developer Studio prompts you if it should switch debug mode on, or if it should continue running in the current mode.

       6.         Choose to switch on the debug mode and choose OK.

End of Content Area