You can debug your application logic interpretively using Debugger in Agile Business Suite System Modeler. Debugger performs JIT (Just-In-Time) compilation of the components being debugged (and other required components), and thus does not require a full generate of the application. JIT compilation is only for Winforms Containers, that is the UI generation or compilation. This does not apply to any other UI clients. The reason a full generate is not required is because most things are never generated – they are interpreted. The only things that are generated are interfaces to mimic the Windows runtime interface for the system so that the Windows infrastructure can provide services to the Debugger. Debugger also allows the components being debugged to be run against a test database, rather than your production database. In this way, Debugger helps you to rapidly develop robust applications that can be tested in a controlled manner.
AB Suite Debugger
AB Suite Debugger has been enhanced with auto configure feature, wherein the minimum configuration properties are populated with default values when you initiate a debug session. However, these default configuration properties can be modified on the Configuration Properties dialog box of the model.
Note: Building of wrapper is taken care of when the debug session is initiated.
Following are the types of debug session cycle:
Debugger cycle is initiated depending on the element that has been selected in the class view of the AB Suite application. If you select a Segment, a Folder, or an Ispec, an Online Cycle is initiated. Similarly, when you select a Report, Report cycle is initiated. When you select a Segment Method, Method cycle is initiated. When you select a Messenger class, Messenger Cycle is initiated.
Online Cycle
An Online System debug session runs a segment through Online UI Client. This can be the standard Windows Forms Client, standard Wpf Client, or a custom Client.
Report Cycle
A Report Cycle runs report and will use the standard Report Console Client to display report output.
Method Cycle
A Method call executes public segment method.
Messenger Cycle
A Messenger Cycle runs the Messenger and will use the standard Messenger UI Client which allows you to submit xml data to be processed by Messenger classes.
Notes:
On the Configuration Properties dialog box, when you specify a client , the details filled in Client section is used for debugging. However, when Client details is not specified, it will use the winform container for debugging.
The Debugger configuration properties are stored in the Visual Studio Solution files and not the database. Hence, these properties cannot be exported.
If a model contains huge number of reports, it is recommended to set the Deployable Report to False in Folder level configuration properties and then start debugging. If you want to debug a particular report, it is recommended to select the report you want to debug and then set the Deployable Report to True in the Report configuration properties and then start debugging the report.
The Debugger builds wrapper for the segment level elements. The Debugger build allows you to build the Ispec screens just-in-time.