Ricoh InfoPrint Pro C900AFP Planning Guide - Page 18

Understanding the InfoPrint Manager server, Basic print flow, Job B, Notes

Get Ricoh InfoPrint Pro C900AFP PDF manuals and user guides View all Ricoh InfoPrint Pro C900AFP manuals
Add to My Manuals
Save this manual to your list of manuals

Page 18 highlights

InfoPrint Manager, you select the types of notification you want to make sure that the appropriate people are alerted when significant events occur. The most common form of notification is that a job has completed successfully. For example, when a set of payroll checks has finished printing, someone in the Payroll department can be notified that they are ready. Continue with the "Understanding the InfoPrint Manager server" section that describes the different InfoPrint Manager objects and basic configuration considerations for each. Understanding the InfoPrint Manager server The InfoPrint Manager server runs as a service on Windows. The server manages jobs submitted to it from client applications (including InfoPrint Select and Windows applications that support a print function). The InfoPrint Manager server contains a number of "objects" that are used to control the processing of submitted jobs. Objects include queues, logical destinations, actual destinations, and any defaults for job and document characteristics. The server administrator creates, deletes, and modifies these software objects to optimize the management and performance of the InfoPrint Manager environment. The InfoPrint Manager server can also contain auxiliary sheets, media, resource-context objects, and transform objects. You can use auxiliary sheets to separate jobs and to print job identification information. Resource-context objects point to the directory locations of Advanced Function Presentation™ (AFP) resources, such as fonts and overlays, that some jobs require. Basic print flow You can submit print jobs to the InfoPrint Manager server in a variety of ways. Various print submission methods are described in Chapter 3, "Planning to print with host systems," on page 19 and Chapter 5, "Planning to share printers," on page 27. No matter which method you use, your jobs will travel similar paths once they get to the server. In the most common configuration, you submit jobs to an InfoPrint Logical Destination (LD). The LD forwards the job to a print queue, and the print queue forwards the job to an InfoPrint Actual Destination (AD). The AD then sends the job to the printer. See Job B in Figure 1 on page 3 for an illustration. This configuration is especially useful if you have multiple printers and want to balance the workload between them. Another common configuration is to submit jobs directly to the AD. The AD then forwards the job to the LD that is associated with it. The LD sends the job to a print queue, and the print queue sends the job back to the AD where it started. Then, the AD sends the job to the printer. See Job A in Figure 1 on page 3 for an illustration. This configuration is particularly useful when you need to make sure jobs are sent to a specific printer. Notes: 1. If you submit jobs directly to an AD, the AD and LD that you associate with it must reside on the same server. 2. If you use the Distributed Print Facility (DPF) to print from a host system, you must submit directly to an AD. 2 InfoPrint Manager for Windows: Introduction and Planning Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
InfoPrint Manager, you select the types of notification you want to make sure
that the appropriate people are alerted when significant events occur. The most
common form of notification is that a job has completed successfully. For
example, when a set of payroll checks has finished printing, someone in the
Payroll department can be notified that they are ready.
Continue with the “Understanding the InfoPrint Manager server” section that
describes the different InfoPrint Manager objects and basic configuration
considerations for each.
Understanding the InfoPrint Manager server
The InfoPrint Manager server runs as a service on Windows. The server manages
jobs submitted to it from client applications (including InfoPrint Select and
Windows applications that support a print function). The InfoPrint Manager server
contains a number of “objects” that are used to control the processing of submitted
jobs. Objects include queues, logical destinations, actual destinations, and any
defaults for job and document characteristics. The server administrator creates,
deletes, and modifies these software objects to optimize the management and
performance of the InfoPrint Manager environment.
The InfoPrint Manager server can also contain auxiliary sheets, media,
resource-context objects, and transform objects. You can use auxiliary sheets to
separate jobs and to print job identification information. Resource-context objects
point to the directory locations of Advanced Function Presentation
™
(AFP)
resources, such as fonts and overlays, that some jobs require.
Basic print flow
You can submit print jobs to the InfoPrint Manager server in a variety of ways.
Various print submission methods are described in Chapter 3, “Planning to print
with host systems,” on page 19 and Chapter 5, “Planning to share printers,” on
page 27. No matter which method you use, your jobs will travel similar paths once
they get to the server.
In the most common configuration, you submit jobs to an InfoPrint Logical
Destination (LD). The LD forwards the job to a print queue, and the print queue
forwards the job to an InfoPrint Actual Destination (AD). The AD then sends the
job to the printer. See
Job B
in Figure 1 on page 3 for an illustration. This
configuration is especially useful if you have multiple printers and want to balance
the workload between them.
Another common configuration is to submit jobs directly to the AD. The AD then
forwards the job to the LD that is associated with it. The LD sends the job to a
print queue, and the print queue sends the job back to the AD where it started.
Then, the AD sends the job to the printer. See
Job A
in Figure 1 on page 3 for an
illustration. This configuration is particularly useful when you need to make sure
jobs are sent to a specific printer.
Notes:
1.
If you submit jobs directly to an AD, the AD and LD that you associate with it
must reside on the same server.
2.
If you use the Distributed Print Facility (DPF) to print from a host system, you
must submit directly to an AD.
2
InfoPrint Manager for Windows: Introduction and Planning Guide