When you are building a PowerBuilder NVO as an application server component, you can use the PowerBuilder debugger to debug the application server component. You can debug the component whether you use the live editing feature in the User Object painter or deploy the component to the server from the Project painter.
Before you begin debugging a remote component, check that your configuration meets these requirements:
You are using the same version of the application and PBLs as were used to develop the deployed component. To debug several deployed components in the same session, they must all have been built using the same versions of the PBLs, the same application name, and the same library list.
The Supports Remote Debugging check box on the Components page in the Project painter is selected. You can also set the debugging option by checking the Supports Remote Debugging check box in the Project wizard.
You have a client application that exercises the methods and properties in the deployed components. This can be a compiled executable built with any compatible development tool, or a PowerBuilder application running in another PowerBuilder session.
Open the target that contains the deployed components. Click Start Remote Debugging in the PainterBar, and complete the wizard. You can select only components that were generated in PowerBuilder with remote debugging support turned on. Remote debugging support is a security setting that does not add any debugging information to the component. To prevent users from stepping into and examining your code, turn remote debugging support on when you are testing a component, then, turn it off when you deploy the component to a user’s site.
Set breakpoints as you would when debugging a local application, then start the client application that invokes the remote components (if it is not already running).
The Instances view shows the state of each component instance:
When a component instance is destroyed, it is removed from the Instances view.
Multiple component instances can be stopped at the same time, but actions you take in the debugger act only on the first instance that hits a breakpoint. This instance is indicated by a yellow arrow in the Instances view. The current instance changes to the next instance in the queue when the method completes or when you click Continue.
You can also change context from one instance to another by double-clicking the new instance in the Instances view. You might want to do this if you step over a call to another component instance and the Instances view shows that the called instance stopped.
