HP Web Jetadmin - Database Views in HP Web Jetadmin

4
8. Click Add. The Enter License page is displayed.
9. Paste the license number into the License Key box and click Apply. The license is installed and
displayed in the License Manager main dialog box.
10. Restart the HP Web Jetadmin service (HPWJA Service).
The features of the database connectivity module are now activated.
DATABASE VIEWS
HP Web Jetadmin collects data from devices and stores the data in SQL database tables. Device lists
display data the user desires in columns to be sorted or filtered. Device data can be exported to .csv
or .xml files for viewing and manipulating in applications such as Microsoft Excel. Device data can be
displayed in “canned” or custom reports that HP Web Jetadmin generates to meet user needs. In
addition, this same data can be written to SQL database views to be accessed by asset and reporting
tools as long as the optional Database Connectivity license is installed. There are two areas in
HP Web Jetadmin where data can be written to database views:
 Data exports
 Reports data collections
DATA EXPORTS
Device data can be exported from any device list or device group by selecting devices, right-clicking
the selection, and choosing Export. The Export Devices wizard can also be launched from
Tools/Export devices. Data exports can be scheduled to run at any interval. No matter which
technique is used, the devices, data, and accuracy of the data can be dictated by the user and
written to a database view.
Accuracy of exported data
When the Export Devices wizard is launched, a threshold level can be set to specify the accuracy of
the data that will be exported (see Figure 1). The following threshold levels can be selected:
 Database only: Data is only gathered from the database and not from the device, no matter how
old the data may be.
 Missing items only: Data is gathered from the database if the data exists; otherwise the data is
gathered directly from the device.
 From device only: Data is gathered from the device directly regardless of whether data exists in
the database, ensuring the most accurate data.
 1 hour: Data in the database older than 1 hour is updated directly from the device.