Database application development is a feature of JBuilder Professional and Enterprise. Distributed application development is a feature of JBuilder Enterprise.
JBuilder provides a JDBC monitoring class which can monitor JDBC traffic. JBuilder provides a user interface, invoked from Tools|JDBC Monitor, to work with this class at design time. For information on using this class at run time, see "Using the JDBC Monitor in a running application".
JDBC Monitor will monitor any JDBC driver (i.e.,
any subclass of java.sql.Driver
) while it is in use by JBuilder. The JDBC Monitor monitors all output directly from the JDBC driver.
To start the JDBC Monitor, select Tools|JDBC Monitor. The JDBC Monitor displays:
How to use the JDBC Monitor:
To monitor database connections at run time, a MonitorButton
or a MonitorPanel
must be included with the application. MonitorButton
is a Java bean which allows you to run the JDBC monitor against a running application. To do so, the instance of the JDBC monitor in use must be brought up by the application. An instance of the JDBC Monitor brought up from the IDE will only monitor database activities during design time. Pressing the Monitor button displays a dialog containing the JDBC Monitor.
The MonitorPanel
can be used to place the monitor directly on a form. It has the same properties as the MonitorButton
.
MonitorButton
can be put on the component palette by following these steps:
Select Data Express from the Pages field on the Pages tab.
Select the Add Components tab.
Select JBCL in the Select Library field.
Click Install.
Browse to com.borland.jbcl.sql.monitor.MonitorButton
.
Click OK to close the dialog.
MonitorButton
is added to the palette, it can be dropped on to your application. You could also add an instance of the MonitorButton
in code, as follows:
MonitorButton monitorButton1 = new com.borland.jbcl.sql.monitor.MonitorButton(); this.add(monitorButton1);
MonitorButton
to control the default state of the monitor:
Property | Effect |
outputEnabled | Turns Driver trace on/off. |
maxLogSize
| Maximum trace log size. Default is 8K. |