2022.2
Table Of Contents
- Table of Contents
- What is Connect Send?
- Installation
- Printer driver
- Workflow Plugins
- Connect Send database cleanup service
- Moving Workflow to another machine
- Prerequisites
- System Requirements
- Installing OL Connect Send Printer Driver
- Printer driver properties and advanced settings
- Mass deployment of the OL Connect Send Printer Driver
- Using API Keys
- OLCS Notifier
- Known Issues
- Existing OL Connect Send Upgrade Issue
- Installing OL Connect Send on Windows Server 2016
- Installing OL Connect Send on a machine with Connect installed
- OL Connect Send issues under Microsoft Edge browser
- Printing PDF files with Adobe Acrobat Reader
- Paper Size vs Printer Page Size
- Passthrough Printing not supported
- License modes
- OL Connect Send in Workflow
- Using the Printer Driver
- Log files
- Troubleshooting
- OL Connect Send 2.1.2 Printer Driver Release Notes
- Overview
- Important Notes
- OL Connect Send 2.1.2 Printer Driver
- OL Connect Send 2.1.1 Printer Driver
- OL Connect Send 1.8.0 Printer Driver
- OL Connect Send 1.7.0 Printer Driver
- OL Connect Send 1.6.6 Printer Driver
- OL Connect Send 1.4.5 Printer Driver
- OL Connect Send 1.3.5 Printer Driver
- OL Connect Send 1.2.5 Printer Driver
l
General
l
Compresses PostScript files during transmission to minimize bandwidth.
l
Allows the printer driver to include an API key in its HTTP headers to authorize itself
for printing.
l
Unlicensed mode
l
Non-interactive job submission.
l
Free to use.
l
Confirms job transmission with a message in the Notification Area.
l
Licensed mode
l
Interactive job submission possible.
l
Launches the user’s default browser to display web content produced by a Connect
server.
l
Database containing domain, workstation ID, document information and page count
information.
Main steps in OL Connect Send
The main steps in the functioning of OL Connect Send are:
1.
A user prints a document to a printer using the OL Connect Send Printer Driver.
2. The resulting print job is captured by the printer driver code, zipped up, and, if applicable,
split into multiple chunks.
3.
The chunks are transferred to the Workflow process and received by the Job Processor
plugin (see "Job Processor plugin" on page49).
4. The plugin communicates with the printer driver to ensure that all data has been received
correctly.
5. The plugin combines all the chunks into a .7z file and then unpacks it to the original print
job. This is a Postscript file.
6. The plugin stores the print job at a specified location with a specified name.
7.
The plugin creates a Workflow metadata file for the print job, containing basic job
information (See License Modes – Basic Mode, below).
8. The plugin (if licensed) stores all job related info in a database.
Page 8