Votes - 0, Average rating: 0
(
)
)
|
Other manuals for this model:
manual abstract
WHAT IS HP WEB JETADMIN POLLING?
HP Web Jetadmin uses a registration mechanism to add both device identities and device data into a
background process called polling. HP Web Jetadmin is able to then query the details from devices
on the network by using an efficient centralized polling mechanism. Devices and their associated data
move in and out of polling registers for a variety of reasons. Here is an example:
HP Web Jetadmin has been set up with Automatic Groups. These groups populate (and depopulate)
with devices based on device attributes such as model and capability. As devices are added to the
network or as devices change, groups are automatically kept up to date throughout the day and night
by background polling. Devices are polled for the details contained within Automatic Group filtering.
The returned data either matches or mismatches and the group membership is dynamically updated
appropriately. The filter criteria and all devices managed by HP Web Jetadmin are maintained in
background polling.
DATABASE INFO VS. DEVICE INFO
HP Web Jetadmin stores device and other data within a Microsoft® SQL database. All data has a
date and time attribute so that a given feature can choose to use stored device data or request fresh
data directly from the device, depending on data aging. Some details are considered quite volatile
and are requested frequently (Page Count, for example). Some details are considered very stable and
requests are generated infrequently (Color Capability, for example). HP Web Jetadmin documentation
at this time does not include details on these factors. HP Web Jetadmin does not poll the device
directly if the detail is not considered “aged.”
Some information is considered static and will never change unless there is a registration action that
causes the information to change. Device Model Name and Device IP Address are both considered
static. However, Device IP Address is part of the device connection attribute and will change if the
device is discovered on a new IP address. A discovery or Refresh Selection (Full) action must take
place before HP Web Jetadmin data will reflect a Device IP Address change.
IP Hostname is considered static as well, but has a special 12 hour “time to live” attribute. While it
isn’t expected that IP Hostnames will change often, HP Web Jetadmin checks occasionally and adjusts
the IP Hostname attribute if necessary.
NOTE Hostname caching takes place within the Microsoft Windows® operating system. The DNS
Client is a service that caches IP hostnames and proxies them for applications like HP Web
Jetadmin. Microsoft has a knowledgebase document that covers adjusting the default cache
settings and can be found at support.microsoft.com/kb/318803. More information about IP
hostnames, HP Web Jetadmin, and Jetdirect print servers can be found in the Best Practices
For Managing Your Assets whitepaper at the Self Help and Documentation tab at
www.hp.com/go/wja.
PROTOCOL—HOW THE QUERY TAKES PLACE
When HP Web Jetadmin queries devices or infrastructure, it uses a variety of protocols depending on
the information being gathered. The most important are:
• SNMP—The primary communication method for gathering device information
• HTTPS—Used to gather security, digital sending, and other device information
• DNS and WINS—HP Web Jetadmin asks the local host to perform a name resolution
Sometimes HP Web Jetadmin requires credentials in order to complete a query. HP Embedded Web
Server passwords, SNMP Get names and other device credentials may be needed. “
2
...