Morfik Trace Options
From Morfik Wiki
The Trace options allows the user to specify the level of trace desired during debugging sessions. Morfik can trace general HTTP Requests, XML Web Service calls and a series of different database operations. By default database operations are not enabled for tracing.
|
| Morfik Trace Options |
Trace Options
The Trace options in the Trace section of the Options dialog allow the user to precisely specify what are the items that should be traced. The options in this area are the following:
Monitor HTTP Request/Response
This options allows the user to specify if the HTTP requests and responses of the XApp should be traced while debugging.
HTTP Headers Only
- This option allows the user to choose to trace only the the HTTP headers instead of the the entire requests and responses.
Monitor SOAP XML Messages
If selected, this option will instruct Morfik to trace the SOAP XML Messages that are received and sent by the XApp server component.
Monitor SQL
This option enables tracing of SQL operations. This option is off by default. Using this option the user can monitor all commands which are sent by the application's server side component to the actual database server. This option is useful for application optimization as it can help the user to follow commands issued by both the application's own code and the Morfik framework.
Monitor Designer SQL
This option, which is off by default, enables tracing of the SQL commands generated by the Table and Query designers. This option allows the user to see what commands the Morfik development environment is sending to the database server to effect changes the user requests through visual designers.
SQL Monitor Options
This is a list of different database operations that can be traced from within Morfik. Only the operations selected in this list will be traced.
The following operations can be monitored: Connection, Transaction, Statement, Row, Blob, Array, ClientTrace, Profile, Allocate, Prepare, Describe, StatementInfo, Execute, ExecuteImmediate, ServerCursor.
Some operations happen with great frequency during normal application execution and turning on many options at the same time might make it harder to follow the sequence of operations. It is important to note that the monitoring happens at a lower level the application commands and one command in the application might trigger several operations to be sent from the application/database driver to the database server and back.