JDBC Source dialog box

The JDBC Monitor window can only display output from a single class. The JDBC Source dialog changes the Monitor window display from one source to another. See the Database Application Developer's Guide topic, Monitoring database connections for more information on using the JDBC Monitor.

To display this dialog, select Tools|JDBC Monitor, then select Source in the main Monitor window.

Choose the appropriate checkbox for the source you want to monitor. Notice that the three check boxes are mutually exclusive.

JDBC Driver Manager (JDBC Trace)

Displays all output from all drivers currently loaded by the Driver Manager.

Borland Local Driver (Local, or Bridge)

Displays a list of URLs for every BDE alias on your client machine. If you choose the Borland Bridge Monitor, you can monitor the output from a single alias or from all listed aliases.

Borland Remote Driver for a Single Server (Remote, or Broker)

The Broker option requires you to type a server name in the edit field. This machine name can be any machine running DataGateway which is visible to your client machine. After defining a server, selecting Broker displays a list of URLs for every alias defined on that machine, including an option to monitor all aliases on that machine. This gives instant connectivity to all BDE drivers running on another machine (i.e., the "middle tier"). Selecting a single alias will restrict monitoring to that alias.

To monitor more than one source, you must bring up another instance of the Monitor window.

The JDBC Monitor will monitor any JDBC driver (i.e. any subclass of java.sql.Driver). However, the monitor is most informative with Borland's DataGateway JDBC drivers.

Server

When the Remote option is selected, the Server edit box becomes available. The Remote option requires you to type a server name. This machine name can be any machine running DataGateway which is visible to your client machine. You can type in a server name or select the button for a list of available aliases.

After you define a server, JDBC Monitor displays a list of URLs for every alias defined on that machine, including an option to monitor all aliases on that machine. This gives instant connectivity to all BDE drivers running on another machine (i.e., the "middle tier"). Selection of a single alias will restrict monitoring to that alias.

To monitor more than one source, you must bring up another instance of the Monitor window.

The following table describes the output you will see in the JDBC Monitor depending on which source is selected. In this table and in this document, Local and Bridge are synonymous and Remote and Broker are synonymous. The log output from DataGateway is quite different from the output from JDBC.

Driver Class Output InterceptedDescription
java.sql.DriverDriverManager.getLogStream() Standard JDBC driver class. The logStream is supported by the single driver Manager, so there is just one log stream for all of the JDBC drivers running under a VM.
borland.jdbc.Bridge.LocalDriver borland.jdbc.Bridge.Monitor A monitor is a streamable output which can be attached at one of two levels:
  • At the driver level, the monitor displays all output for all instances of the LocalDriver running under the VM.

  • At the URL level, the monitor displays output for all connections to a given URL (the equivalent of a Borland Database Engine alias) running under the VM.
borland.jdbc.Broker.RemoteDriver borland.jdbc.Broker.Monitor The Broker monitor works similarly to the Bridge monitor, but for remote connections. To use the remote monitor, you must first specify a server name where the Borland Broker is running. You may then attach the monitor at one of two levels:
  • For a given server, the monitor displays all output for connections to the RemoteDriver running under the VM.

  • At the individual URL level, the monitor displays the output for a given server/alias combination running under the VM.

For more information on JDBC Monitor, consult Borland's DataGateway Online User's Guide, available from the DataGateway group when DataGateway is installed.