5
contents for displaying a custom
report.
If the data export is scheduled to
occur at a regular frequency, a
date/time column is
automatically stored in the view
to dictate when the data was
exported. However, if an
exported device list contains new
columns or deleted columns and
the server attempts to use the
same database view name,
HP Web Jetadmin recognizes
that the columns in the view no
longer match and forces a new
name to be used for the view. If
the same view name is
required—but with different
columns—the database table and
matching view can be edited by
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 (Figure 4). For a complete list, see Appendix C—Naming schema.
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 stored in SQL database views after the optional
database connection module license is installed. Either the HP Web Jetadmin background poller or
the scheduled data collections generates the data that is populated in these reports.
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. For the location of the file and the attributes that are collected,
see Appendix A—Configure the default poller.
Reports data collections can be enabled to collect the remaining data, typically the data that
represents 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 the following
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 (such as Letter legal, and A4), and job type (such as
copy, digital send, incoming fax, outgoing fax, and scan).
• Supply Utilization—Collected daily, this data contains metrics on consumable usage, such as level
value, percent remaining, supply coverage, pages remaining, and current page count. Additional
data, if supported, might include installation date, removal date, initial level, initial page count,
product information (such as serial number, part number, maximum capacity, maximum pages,
and manufacturing date) and consumable type (such as toner, fuser kit, and ink).
4—Programmatic names vs. display names
(278 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji