HPDPS can operate within either of two environments. In
the first, it optionally uses Distributed Computing Environment
(DCE) services to interact with a heterogeneous mix of hardware
and software products as if they were a single print environment.
When HPDPS interacts with DCE, the environment is called the
DCE Extended Environment. This environment
requires separately purchased DCE Security software. In the second
environment, called the Basic Environment,
when HPDPS is not part of DCE, it uses only the limited DCE services
bundled with the HP-UX operating system.
The DCE Extended Environment |
 |
In the DCE Extended Environment, HPDPS objects (such as physical printers
and spoolers) created by any member of a DCE cell are instantly available
to the entire cell. For example, if a new physical printer is created
within a DCE Extended Environment server, the name of the new physical
printer is visible to every client in the DCE cell, and each client can immediately
issue HPDPS operations for that physical printer. This is possible
because the entire cell shares the same
namespace
called the DCE Cell Directory Service.
This allows for single-point administration as a result of the distributed
namespace. See Chapter 8 “Managing DCE Security for HPDPS ” for more information
on the DCE Extended Environment.
The Basic Environment |
|
In the Basic Environment, only a local namespace
is visible to HPDPS.
Objects created on one host are not instantly accessible to
the other hosts in the network. You can create special logical printers,
called HPDPS Gateway Printers, to access printers on another host.
See “HPDPS Gateway Printer Considerations ” in Chapter 3 for more information.
Administration is possible only for those resources that reside
within the boundaries of the Basic Environment namespace. Accordingly, single-point
administration across hosts is not a feature of Basic Environment.
Printable version
