HP DSS 5 User Manual

							Figure 2-2  Configuration Utility
Remote Configuration Utility
The Remote Configuration Utility is a version of the Configuration Utility that is designed to install and
operate on a remote computer.
Using the Remote Configuration Utility allows DSS configuration across the network.
1.Launch the Configuration Utility.
2.Click Another Computer.
Figure 2-3  Remote Configuration Utility
3.Type in the network name of the DSS server.
4.Click OK.
DSS Service
The core component of the HP Digital Sending Software system of the HP Digital Sending Software is
the service named "HP Digital Sending Software", typically called the "DSS service". This is the key
component of the software that ties together all other components and enables the DSS system to
function. The DSS service is implemented as a Windows System Service.
ENWWComponents 13 
						

							Internally, the DSS service is divided into several subcomponents and has dependencies. The below
figure shows this at a high level:
Figure 2-4  DSS Service Architecture
DSS-enabled device
DSS-enabled devices are the HP MFPs, Digital Senders, or ScanJet products that support DSS.
These devices allow end-users to make use of DSS functionality by scanning to the various
destination types, using the address book etc. For a complete list of supported devices, see
Supported devices on page 5.
The firmware in these devices has a component built-in which enables use of DSS functionality. In
Pre-FutureSmart products this is enabled through DSMP (Digital Sending Management Protocol). In
HP's FutureSmart products this component has been replaced by a WS-* (Web Services Star) based
interface.
Since all DSS features must be supported by the device firmware, DSS 5.0 has a minimum firmware
version requirement, which can be found here 
Table 3-4 Device firmware requirements on page 28.
Over time, as new features become available in DSS, it might be necessary to update the device
firmware for compatibility. These changes will be documented in detail in the DSS release notes.
I.R.I.S. OCR engine
DSS uses I.R.I.S. OCR engine version 12 to provide Optical Character Recognition (OCR) and High
Compression PDF functionality. The engine features Intelligent High Quality Compression (iHQC)
technology™. The engine features Intelligent High Quality Compression (iHQC) technology™, and
the ability to create searchable PDF/A documents.
14 Chapter 2   Theory of operations ENWW 
						

							Figure 2-5  OCR engine
The figure above shows the process flow for OCR processing in DSS. When DSS receives a job that
requires OCR processing, it invokes the I.R.I.S. OCR engine using COM (Component Object Model).
The image data/document is transferred together with control parameters, such as the required
output file type. Once OCR processing is completed, the searchable document is passed back to
DSS which delivers the document to the destination.
DSS is a multi-threaded application and will launch multiple instances of the OCR engine when there
are multiple jobs in the queue that require OCR processing. We refer to this as ‘parallel processing of
OCR jobs’. This makes the OCR feature scalable, which means that average job processing times
will be improved if the server's resources are improved. For instance, adding additional CPUs and
more memory to the server will improve the average processing time of each OCR job when the
server is processing multiple jobs simultaneously. This is a significant improvement over previous
versions of DSS, where OCR processing was serial.
Database
DSS uses Microsoft SQL Server 2008 SP3 Express Edition to host the DSS database. The database
is used to hold job logs, address books, event logs, and some configuration data.
Microsoft SQL Server 2008 is a database management system (DBMS). Within the DBMS, DSS
creates two databases for specific use by DSS, named as follows:
●DSS_Customer
●DSS_Machine
The SQL Server 2008 database instance name is “HPDSS2008.”
It is possible to configure DSS to use a DBMS other than Microsoft SQL Server 2008 SP3 Express
Edition. If a different DBMS is specified during installation, DSS will not install SQL server on the local
server. Even if the local database that DSS installs is used at first, the system can be configured later
to use a different DBMS, but some data will be lost during the switch.
ENWWComponents 15 
						

							Local Data Store
The Local Data Store is the series of files located in the DSS installation directory, which is used to
store the DSS configuration data, device information, and debug logs. This is also where the job
queue resides.
Table 2-1  Local Data Store – Technical Detail
Technical detail
Default installation folder: C:\Program Files (x86)\Hewlett-Packard\HP Digital Sending
Software 5.0
Default temporary jobs folder: \CustomerData\DSS\Jobs
Configuration folder: \Product\DSS\Configuration
NOTE:The temporary jobs folder can be configured to reside somewhere other than the default
location. For information on changing the location of the temporary jobs folder, see 
Changing the
location of the Jobs Folder on page 25.
Third-party tools
As the name indicates, third party tools are not a part of the DSS system. However, they are
mentioned here because third party tools are required to deliver some of the DSS functionality as
listed here:
●LAN Fax. This feature requires a compatible LAN Fax product. DSS enables the functionality by
providing a Fax interface at the Digital Sending-device and then passing the fax job along with
an HPF file (metadata) to a watched folder.
●Internet Fax. This feature requires an Internet Fax server. DSS enables the functionality by
providing a Fax interface at the Digital Sending-device and then sending out an e‑mail with the
fax job attached.
●Workflow. One of the main ideas behind the Workflow feature is the ability to capture metadata
at the Digital Sending-device and pass it on to a folder that is watched by a third party
application. This application is then able to read the metadata and further process and route the
job.
●Personal Address Book. This feature requires a Microsoft Exchange Server that supports HTTP
connections.
16 Chapter 2   Theory of operations ENWW 
						

							Understand DSS data structures
The following describes the different types of data that makes up the DSS system and where they are
stored.
Table 2-2  DSS data
Component Location Description
Job logs Database Job logs for all devices are stored in the
DSS database.
Error logs Database and Windows Event Log The error logs show system events for
information, warning and error
conditions such as service stop and
security audit.
Debug logs [Install Path]\FileSystems\MachineData
\LogsDSS maintains a set of debug log files.
These files are designed to help HP
support debug issues with the DSS
service, such as crashes, hangs etc.
DSS configuration settings [Install Path]\FileSystems\Product\DSS
\ConfigurationConfiguration data used by DSS is
stored in a series of files found in the
Configuration folder. This data includes
things like SMTP gateway settings,
LDAP addressing settings, Workflow
settings etc.
Managed device Information   DSS maintains a list of all the devices it
manages in a binary configuration file.
This file also contains some basic
information about the device, such as
the hostname, device model etc.
Device configuration settings Stored on the device All the device-specific configuration
data is stored on the device itself. When
required DSS will read back the data
from the device, manipulate it and send
it back.
Configuration Utility UI ‘convenience’
dataWindows Registry For usability the DSS Configuration
Utility will remember entries made into
selected list boxes, as well as the state
of the Configuration Utility window when
closed.
Job data temporary storage \FileSystems
\CustomerData\DSSLocation for the temporary storage of
job data. This location can be
configured to a location other than the
default location. See 
Temporary jobs
folder on page 25.
Understand licensing
This section contains the following topics:
●
Licensing requirements
●
Trial license
●
Auto-generate licenses
ENWW Understand DSS data structures 17 
						

							●License activation and rehosting
Licensing requirements
DSS server software does not require a license to operate. A license seat is required for each device
which is managed by DSS. Licenses can come in bundles of 1, 5, 10, 50, and 250 seats. Licenses
can be combined in a DSS server in any combination up to 1000 seats.
Trial license
When DSS is first installed on a new server it comes with a sixty day, fifty seat trial license. If a
purchased license is installed in DSS during the trial period, the trial license becomes invalid and only
purchased licenses will work on that instance of DSS.
When the trial period ends, if no purchased licenses have been added to DSS, the software is unable
to manage or process any jobs from devices.
Auto-generate licenses
The HP 9200C Digital Sender and HP 9250C Digital Sender devices auto-generate licenses after
being added to a DSS server. These are the only two DSS-enabled devices that auto-generate
licenses.
License activation and rehosting
Purchase DSS licenses from HP or HP authorized resellers. Once purchased, the customer will
receive documentation which includes the Entitlement Order Number (EON). Activate the DSS
license in order to use it by locking the license to a server. DSS licenses are locked to servers by the
server MAC address. The output from locking a license is a license key code which users type into
the DSS user interface to enable DSS to use the license. The EON and the server MAC address are
required to activate a license.
From time to time it may be necessary for a customer to use a license on a server to which it is not
currently locked. The process of changing the server to which a license is locked is called “rehosting.”
Conduct DSS license activation and rehosting via the licensing website: 
www.hp.com/software/
licensing.
For more details on the license activation and rehosting sequence of steps, see the white paper “DSS
License Activation and Rehosting”. Access the white paper on the DSS support web site
www.hp.com/support/dss5. Once at the website home page, click the “Documentation” link on the left
hand side to find this white paper.
18 Chapter 2   Theory of operations ENWW 
						

							Understanding DSS Address Books
DSS can maintain several different address books to make available to the devices maintained by
DSS. This section will explain the different types of address books and when the addresses from
each are available to users at a device control panel.
Address Book Manager
The Address Book Manager, or ABM, is a feature within DSS that allows for the management of
several of the DSS address books. It is started from the Addressing tab of the Configuration Utility.
DSS Address Books
Public Address Book
Entries
●When a device is added to DSS, the device’s local address book entries are added.
●Entries can be made via the Address Book Manager
Modify/Delete
●The Public address book can only be modified via the ABM
Private Address Books
Private address books are kept for specific users depending on the user’s signed-in status at the
device. The “Private MFP Guest” address book is for user’s that are not signed-in, while “Private MFP
User” address books are kept for each user that is signed-in.
Entries
●When user’s at the device control panel type in new addresses and choose to save them, they
are saved in the appropriate Private address book depending on their sign-in status.
●Entries can be made via the Address Book Manager
Modify/Delete
●Entries can be made to Private address books via the ABM
Personal Address Books
Personal Address Books hold a signed-in user’s MicroSoft Outlook contacts. These are temporary
address books only available while the signed-in user is accessing addresses, and then only when
the system has been configured to collect the Outlook contacts.
Entries
●From the Outlook contacts of a signed in user.
Modify/Delete
●Personal address books are temporary and only maintained while a signed-in user is using the
address book at the device control panel.
ENWW Understanding DSS Address Books 19 
						

							Replicated LDAP Address Book
DSS is capable of replicating address information from an LDAP server into the DSS database. This
allows users to access these addresses via the DSS server instead of directly from the LDAP server
at job creation time, offloading some load from the LDAP server to DSS. A replication schedule can
be configured to collect addresses at regular intervals to keep the replicated data synchronized with
the LDAP server data.
Entries
●Only via the replication mechanism that can be configured and run from the Addressing tab in
the Configuration Utility.
Modify/Delete
●The LDAP addresses can be cleared from the DSS database using the Clear LDAP Cache
button on the Addressing tab of the Configuration Utility.
Accessing the Address Books from the device control panel
Addresses become available to a user at the device control panel when they click the address book
icon while creating e-mail or fax jobs. Which DSS address book are available to a user at the device
control panel depend on the user’s signed-in status, the device type (FutureSmart versus pre-
FutureSmart), and the address book view selection made by the user.
When using address books from the device, the user has the option of selecting an address book
view. An example of the selections is shown below:
Figure 2-6  Address book view example
The tables below show which DSS address books are available based on View, sign-in status, and
device type.
Table 2-3  Accessing Address Books form a FutureSmart MFP
View Non Signed-In user Signed-in User
All View Public + LDAP + Private MFP
GuestPublic + LDAP + Private MFP User + Personal (when configured) + Private
MFP Guest
20 Chapter 2   Theory of operations ENWW 
						

							Table 2-3  Accessing Address Books form a FutureSmart MFP (continued)
View Non Signed-In user Signed-in User
Local View Private MFP Guest Private MFP Guest
Personal View Private MFP User + Personal MFP User
Table 2-4  Accessing Address Books from a pre-FutureSmart MFP
View Non Signed-In user Signed-in User
All View Public + LDAP + Private MFP
GuestPublic + LDAP + Private MFP User + Personal (when configured) + Private
MFP Guest
Local View Private MFP Guest  
Personal View Private MFP User + Personal MFP User
ENWW Understanding DSS Address Books 21 
						

							22 Chapter 2   Theory of operations ENWW