Doc2Print |
||||||||
![]() |
OverviewRSD™ content management systems optimize the electronic flow of enterprise information and support the migration toward a paperless environment. Nevertheless, many business issues still rely heavily on printing. Doc2Print™ has been developed to efficiently manage both printers and print requests issued from RSD solution servers and their clients. Verifying that each print job is output on a printer physically close to the recipient, that its format conforms to the printer requirements and that a job is not sitting in a long queue when another printer is available, can be a full-time responsibility. Doc2Print, designed for high-volume, cross-platform delivery, automates the management of these tasks on a departmental basis or across the enterprise. ![]() Benefits
Extended ViewA unique architectureDoc2Print was developed to respond to customer requirements for print management in a distributed environment. Its design takes full advantage of the print-related features built into the RSD solution set. The definition of delivery requirements, such as print separators and destination printer, can be specified at the logical document level, when the data flow is captured. Any package of documents can be bundled and sorted. The result is streamlined print processing. The time needed to actually assemble the required data for a request and the size of the data parcel are drastically reduced because the printer spool is sent only the required portion(s) of physically stored data, pre-packaged. Intelligent deliveryPrinter queue gridlock and unrecognized data formats are two situations hindering productivity in large-scale printing environments. Doc2Print bypasses these problems by applying two simple concepts: workload balancing and dynamic rules-based rerouting. It also facilitates the temporary rerouting of requests to another device when a printer is offline. Workload balancingThe grouping of printers into printer pools automates workload balancing and ensures the optimal use of print resources. When a request is sent to a printer pool, it is automatically dispatched to the first available device in the pool that can process the job. A printer pool is not limited to a specific location or platform, as requests can be sent to any TCP/IP printer. Dynamic rules-based reroutingThe printer is available, but can it process the request? Rule-based rerouting prevents situations such as cluttering a high-volume printer, intended to process large text documents, with small requests to print images. Before actually sending data to an available printer, Doc2Print verifies whether the request conforms to the printer-specific rules concerning document size limits and format. If it finds that the printer will not recognize the request format, it tries to convert the data, on-the-fly, to the required format. If the printer cannot process the job, an attempt is made to forward it to another device in the printer pool or to an alternate printer. Simply managedPrint management operational tasks can be performed from Doc2Print, EOS and RSD Folders administration interfaces. All definitions for converters, formats, printers and requests are stored centrally. Print requests for EOS™ or RSD Folders™ output can be issued manually by end-users and product administrators or automatically when data is inserted in an RSD database. Doc2Print also supports the issuing of requests to print data flows not archived by RSD products. Each request is recorded in the Doc2Print queue as a unique job with detailed attributes including: job ID, target, priority, issuer, date of request, number of copies, process status, final delivery target and date. An option for delayed purging permits requests to reside in the queue until a specified retention date. A listing of jobs in the request queue can be filtered, for example to view only those sent to a specific printer. From Doc2Print, the administrator has a global view of the entire print environment. From EOS or RSD Folders, the administrator sees only the requests related to the particular database. Job control permits the resending of interrupted processes. Open solution The on-the-fly conversion feature reflects RSD’s determination to develop solutions that fit the corporate computing environment. The enterprise has total control over how data is converted as any built-in or external converter can be applied, for example to change a viewing format to a print format. As for the Doc2Print component, one server can operate as the central tool for all enterprise print management or individual servers can be flexibly installed for departmental use. Doc2Print can be installed on any of the following platforms: Unix ( AIX, HP-UX, Sun Solaris ), Linux for zSeries and Windows server. Print requests from all RSD solutions, running on the aforementioned platforms and z/OS can be managed and processed. |
|
| Copyright & Privacy | Contact | Webmaster | Site map |