HP Web Jetadmin - Database Views in HP Web Jetadmin

the same view name is desired—

albeit with different columns—the

database table and matching

view could be edited using SQL

Studio Express to match the

columns that HP Web Jetadmin is

attempting to export.

Column headers in a data export

use programmatic names vs. the

friendly names that are displayed

in the HP Web Jetadmin user

interface. A matching view name

in Studio Express with _LOC

appended to the view name

contains a schema or mapping to

match the display names to the

programmatic names (see

Figure 4). See “Appendix C” for

the complete list.

REPORTS TO

DATABASE VIEWS

Data that is collected for reports in HP Web Jetadmin can be written to a database view on a

scheduled basis. There are several “canned” reports that are stored in SQL database views once the

optional database connection module license is installed. The data that is populated into these reports

is generated either by the HP Web Jetadmin background poller or by scheduled data collections.

The HP Web Jetadmin device list background poller is responsible for collecting the data that

represents device attributes. A configuration file is available to turn attributes on or off that are

collected by the background poller. See “Appendix A” for the location of the file and the attributes

that are collected.

Reports data collections can be enabled to collect the remaining data, typically those that represent

page counts and consumables usage. Reports data collections are run once per day.

HP Web Jetadmin offers several types of data collections for reports. However, only two data

collections are responsible for gathering data to be stored in database views:

 Device Utilization Data—Collected daily, this data contains page counts such as simplex, duplex,

monochrome, color, media size (letter, legal, A4, and so on), and job type (copy, digital send,

incoming fax, outgoing fax, or scan, for example).

 Supply Utilization—Collected daily, this data contains metrics on consumable utilization such as

level value, percent remaining, supply coverage, pages remaining, and current page count.

Additional data, if supported, may include install date, removal date, initial level, initial page

count, product info (serial number, part number, max capacity, max pages, manufacturing date,

and more) and consumable type (toner, fuser kit, ink, and so on).

Figure 4—Programmatic names vs. display names