2020.1
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
- License modes
- OL Connect Send in Workflow
- Using the Printer Driver
- Log files
- Troubleshooting
Regardless of the log level however, any information about success or failure of a print job
transfer will be shown.
When the log level is DEBUG, the messages will be formatted like this:
[<HH:MM:SS>][<JobID>][<Printer Name>] <Message>
l [<HH:MM:SS>]: The timestamp in 24 h format embedded in brackets.
l [<JobID>]: The Job ID of the print job in question.
l [<Printer Name>]: The full name of the respective printer as defined by the user and seen
in the list of printers.
l <Message>: The respective message.
When the log level is higher than DEBUG, the messages will be formatted like this:
[<Printer Name>] <Message>
However in any case for any ERROR log message the message will be formatted like this:
[<JobID>][<Printer Name>] <Message>
Stopping and restarting the OLCS Notifier
To stop the OLCS Notifier, right-click the icon in the notification area and select Exit.
To restart it, either click Taskbar Notifier in the Start menu (under Objectif Lune), or run it from
the folder:
%programfiles(x86)%\Objectif Lune\CPD\App
Changing the UDP communication Port
Each OL Connect Send Printer Driver sends its messages to the OLCS Notifier via UDP. By
default port 8090 is used, but it can be modified by setting a different port number in the registry
under:
Page 33