HP Web Jetadmin - Performance and Threadpools in HP Web Jetadmin

Sample design proposal

After all options have been considered and the customer environment is understood, it is time to

design a proposal. Let’s consider a case study of an HP Web Jetadmin implementation. The following

key functionality is required:

Deploy

 Discover, configure, update firmware on a fleet of 3,000 devices

 Use auto-groups and templates to apply security settings

 Export various device list fields to CSV on a schedule

 15 user potential

Resolve issues

 Investigate device issues remotely

 Apply resets remotely

 Send PJL and config templates to devices

 Monitor (proactive) 3,000 devices

 50 user potential

Reporting

 Establish data collection on all but Peak Usage and By User on 3,000 devices

 Retain data for up to 5 years

 15 user potential

Design recommendation – distribute functionality across three servers

Here is an actual proposal from a customer implementation in 2009:

 Server 1

 Proactive Management - Distributed Alerts

 2 or 4 core SQL Express

 ~3,000 devices

 Subscriptions 1-3

 Server 2

 Fleet Deployment and Trend Reporting - Consolidated Reports and Admin support

 4 core and off-box SQL

 3,000 devices

 ~15 admins

THREADPOOL SETTINGS

HP Web Jetadmin provides an optional technique for improving the performance of many tasks by

manipulating the number of threads used for each task. Threadpool settings can be configured in an

XML file named PerformanceTuning.config.xml in the following directory for Windows 7 and Server

2008 (R2):

C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Hewlett-

Packard\HPWebJetadmin\WJAService\Config