SEH TPG60 Bedienungsanleitung PDF herunterladen (Seite 4)

Introduction

4 White Paper SEH TPG60/120

Introduction

The .print Client Gateway can greatly simplify the introduction of ThinPrint .print

because it can receive print jobs for an entire group of client machines and printers,

decompress and decrypt them, and then distribute them conventionally in a local net-

work – like a local print server. Then the .print Client is only necessary on the “local

print server” or .print Client Gateway for this remote LAN. Otherwise, the .print client

must be installed on each end device: rich clients, printers, thin clients, etc. This

could mean that with thin clients, for example, a BIOS update is necessary.

Even mixed environments pose no problem: The .print client is installed onto all

devices where simple installation is possible, and all others are served by a Client

gateway.

Any machine with .print Client installed can be used as a Client Gateway (e.g., a

Windows or a Linux workstation). Thin clients or external print servers with embed-

ded .print Clients can also be used. The following example helps you install a

ThinPrint Gateway TPG60/120 from SEH as a test scenario. Once you get a feel for

the functionality, you can install it according to your system's individual require-

ments.

An SEH TPG60/120 has an embedded .print Client. The TPG60 can address up

to six network printers (via TCP/IP) – the TPG120 twelve. See also www.seh.de

With V-Layer

, printer drivers are not needed on either the terminal servers, the

virtual desktops or the client machines, only on a central print server (see Illus. 1).

To enable this, a ThinPrint Output Gateway is installed on both the terminal serv-

ers/virtual desktops and the print server. It appears to the operating system as a

printer driver but sends the print jobs “un-print-ready“ (as RAW data).

The Output Gateway printers on the central print server are shared so that printer

connections can be established from the terminal servers (or virtual desktops) to

these shares. In this way, print data from applications on the terminal servers are

sent in EMF format to the print server. Once there, it is sent from the Output Gateway

printer to another printer for which the necessary (native) printer driver has been

installed. The print job is then completed (rendered) and the .print Engine com-

presses it, encrypts it (if specified), and sends it across controlled bandwidth to the

TPG60/120. The .print Client in the TPG60/120 then decompresses and decrypts

the print data and forwards it (conventionally) to the correct network printer.

1 Printer Virtualization Layer

1 2 3 4 5 6 7 8 9 ... 25 26

Keine Kommentare

SEH TPG60 Bedienungsanleitung Seite 4