Telemetry data export to 3rd party databases – Printronix PrintNet Enterprise User Manual

Page 298

298

Chapter

Telemetry Data Export To 3rd Party Databases

The AutoID Data Manager allows you to export telemetry data to 3rd party
databases using the JDBC interface. To export telemetry data, you need to
obtain either a JDBC or an ODBC driver from your database vendor.

When configured, the 3rd party database opens when the Data Validation
Printers List window opens, and closes when the window closes. Any
telemetry data collected by the AutoID Data Manager is sent to the database.

NOTE:

All external database errors are written to the file

odv_db.err

, located

in the program installation directory.

The database connection is defined by four Java system property definitions
that are placed in a global properties file called

pm.pro

. This file must be

placed in the program installation directory.

NOTE:

The

pm.pro

file is read only when the AutoID Data Manager initially

loads. Any changes made to

pm.pro

are not reflected in the AutoID

Data Manager until you relaunch the application.

Java system properties are name/value pairs, where the name and value are
separated by an equal sign. The following four properties must be defined:

OdvJdbcDriver (Driver Class Property)

This is the name of the JDBC driver classfile. This value depends on the
type of database being used, and is provided by the database or driver
manufacturer. Also, some drivers require a JAR file be placed in the
program installation classpath. This is done by renaming the driver JAR
file to

jdbcdriver.jar

and placing it in the

lib

subdirectory found in the

program installation directory. If you are using an ODBC driver, then you
need to specify the JDBC-ODBC bridge supplied by Sun Microsystems

called

sun.jdbc.odbc.JdbcOdbcDriver

OdvJdbcUrl (Database URL)

This is the Uniform Resource Locator (URL) that describes the database
being used. It depends on the database and driver being used, and its
format is defined by the database or driver vendor.

The URL is a single line of text that follows the HTTP convention. It
begins with the service identifier,

jdbc:

. Next, the service name is

appended. For a JDBC compatible database, such as MySQL, the URL is

jdbc:mysql:

. For a normal ODBC compatible database, the URL is

jdbc:odbc:

Following the service name is the URL of the database, the user ID, and
password used to log into the database.

OdvJdbcDbName (Database Name)

This is the name of the database table created to store the telemetry
values. For a standard database, it is a single word. For an Excel

spreadsheet, it must be delimited by square brackets, e.g.,

[Sheet1$]