User Guide Version: 1.6.6 Connect Version: 2020.1 Last Revision: 2021-06-03 Objectif Lune, Inc. 2030 Pie-IX, Suite 500 Montréal, QC, Canada, H1V 2C8 +1 (514) 875-5863 sales@ca.objectiflune.com www.objectiflune.com All trademarks displayed are the property of their respective owners. © Objectif Lune, Inc. 1994-2021. All rights reserved. No part of this documentation may be reproduced, transmitted or distributed outside of Objectif Lune Inc.
Table of Contents What is Connect Send? 6 Features List Main steps in OL Connect Send Installation 6 7 9 Printer driver Workflow Plugins Connect Send database cleanup service Moving Workflow to another machine Prerequisites System Requirements Plugin Printer Driver HTTP Browser Installing OL Connect Send Printer Driver Setup process – new installation Adding, modifying or deleting a printer Shared Printers Managing multiple OLCS printers Printer driver properties and advanced settings Mass deployment of
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 License modes 34 34 34 35 36 Basic mode User mode Click Charge mode Incoming print jobs and the license Scenario 1 Scenario 2 OL Connect Send in Workflow 36 37 37 38 39 39 40 Configuring the OL Connect Send Workflow processes Job transfer process Interactive process Production report process Plugins Job Processor p
What is Connect Send? Connect Send is an application with two components. The first is a Windows printer driver and the second includes a set of Workflow plugins. These two components work together – they cannot be used on their own. Connect Send allows for PostScript files to be received over the internet from any Windows Desktop application. It can be used in unlicensed mode and licensed mode. The Unlicensed mode (default) allows users to push documents to Connect Send.
l General l l l l Compresses PostScript files during transmission to minimize bandwidth. Allows the printer driver to include an API key in its HTTP headers to authorize itself for printing. Unlicensed mode l Non-interactive job submission. l Free to use. l Confirms job transmission with a message in the Notification Area. Licensed mode l l l Interactive job submission possible. Launches the user’s default browser to display web content produced by a Connect server.
9. The plugin returns a status message to the client, indicating a successful or failed job transfer. 10. The plugin sends the license status to the Printer Driver. 11. The Printer Driver (if licensed and interactive) will launch a browser window and send an HTTP request to Workflow. The result of the receiving interactive process (see "Get Job Data plugin" on page 47) will be displayed in the browser.
Installation Printer driver The OL Connect Send Printer Driver must be installed on a dedicated machine and a Windows printer must be set up using this driver. Additionally several settings regarding the host for sending print jobs have to be set. All this is done with the Printer Driver installer; see "Installing OL Connect Send Printer Driver" on page 12. Any OL Connect Send Printer Driver with a version number less than 1.0.5 should be uninstalled before installing the newest Printer Driver. 1.
Connect Send database cleanup service A cleanup mechanism in the OLCSService service and in the Job Processor plugin prevent excessive growth of the Connect Send database. There are no settings to make for these mechanisms, except that you could change the default number of days to keep history of transactions. This influences the output of the Get Data plugin (see "Get Data plugin" on page 52). By default, the minimal number of days to keep history of transactions is 60. To change this: 1. Create a olcs.
l l OL Connect Send: l OL Connect Send Printer Driver l OL Connect Remote Print plugins. These are built in Workflow as of version 8.6.1. An OL Connect Send license (required for interaction to take place) System Requirements Plugin The Job Processor plugin is designed to work with the Workflow module (Workflow) of PlanetPress Connect and PReS Connect (Connect) which means it will run on any operating system by those products.
The OLCS Printer Driver is not supported for Windows Terminal Services (also known as Remote Desktop Services), Citrix and other thin client solutions. An individual installation of it is required on each individual machine on which the solution is intended to be used. Remote Desktop (RDP) for non-Terminal Services environments, however, is supported. HTTP Communications between the Printer Driver and the plugin is achieved using HTTP.
1. Open the Windows Control Panel and click Programs and Features. 2. Select OL Connect Send Printer Driver and click Uninstall. Setup process – new installation The following section describes the installation process for the OL Connect Send (OLCS) Printer Driver. Starting the installation Click the OLCS_Printer_Driver_Setup_1.6.6.msi file to start the OL Connect Send Printer Driver Setup. If an OLCSClient.
Please read the legal notices and acknowledgements. Click Next to proceed. EULA The next screen shows the EULA. Please read and accept it to proceed further by clicking Next. Communication URL settings The URL for the print job submission is required for the HTTP connection with the receiving OL Connect Workflow server (e.g. http://192.168.159.100:9090/olcs_transfer). This would be the Workflow process which accepts the relevant data. If the Workflow server is active, it is useful to test the connection.
If a license is valid for the local system and the interactive mode is activated, the action name has to be given for this (default: “olcs_interaction”). This would be the Workflow process that starts/executes the interaction. URL for print job submission The URL for print job submission allows the URL for Workflow to be entered. This is the server that will capture and process print jobs. It needs to be entered as a full URL, for example: http://demo.objectiflune.
l : Sets the communication protocol and has to be either HTTP or HTTPS. Any other setting is invalid. As soon as HTTPS is set as protocol, the communication will automatically run in protected mode (SSL). Tip For additional information about secure file transfer, HTTPS certificates and how to request a countersigned certificate, please see this page: SSL HowTo. l l l l : The host name or IP address of the target machine.
Certificate Authorities. In that case, the root validation of the certificate can be switched off by checking this option. URL for interaction Enter the URL for interaction, following the same pattern as the URL for job submission. The last part of this URL is the action as defined in the related Workflow HTTP Input plugin, including any path components. For example: http://demo.myhost.com:80/path/to/target/olcs_ interaction. This URL may be entirely different from the URL for job submission.
Printer name By default the printer name is OL Connect Send Printer. If a printer with the same name already exists, a number is added and increased until no matching printer name is detected. This then becomes the proposed printer name in this dialog. The printer name must consist of valid characters. Invalid, forbidden characters are: l / = forward slash, 0x2F l " = quote, 0x22 l \ = backslash, 0x5C l * = asterisk, 0x2A l : = colon, 0x3A l ? = question mark, 0x3F l < = less than sign, 0x3C l
l | = pipe symbol, 0x7C l , = comma, 0x2C Note As opposed to the other settings, the printer name can’t be changed after installation. Logging The OL Connect Send Printer Driver creates one log file per printer per day. (For information about all log files, see "Log files" on page 64.) The number of log messages can be set by choosing the log level. Available log levels are: l l l l DEBUG: Logs all messages and is intended to be used only for bug research.
Finishing the installation At this point Setup has collected the required information to install the printer driver and create it. The next screen will ask you to continue by clicking the Install button. A progress bar is shown, while the installation process is running. After a successful installation, the Finish dialog is shown. Click Finish.
Adding, modifying or deleting a printer To install an additional printer, modify a printer or delete a printer, run the installer again. The installer will detect that it’s not being used for the first time and will present a different screen. Clicking the Next button will bring you to the selection page where you can decide to: l Add a printer. l Modify the settings of an existing printer. l Delete one or all existing printers.
Adding a printer The wizard pages that follow when clicking the Add printer button are the same as for a new installation. Each printer can have its own settings. Modifying the printer settings Depending on the number of printers already installed, you will either see the Wizard window or a dialog box from which you must select the printer you wish to modify.
The wizard pages are the same again, so you can modify any of the values (e.g. if the host name has changed), except for the printer name which is grayed out and locked. Removing a printer Depending on the number of OLCS printers installed, you will either get a selection box to identify which printer to remove, or you can just delete the only one.
Note Printers installed and running with the pre-release of Connect Send have to be removed before updating the Printer Driver (see also: "Workflow Plugins" on page 9). Shared Printers The OL Connect Send Printer Driver is not a shareable driver. This is because the browser interaction cannot be routed through the print server to the end user's desktop. Also a shared printer would transfer the print server's machine name, user name, domain etc., thus invalidating the intended behavior.
Printer driver properties and advanced settings It is not normally necessary to change the OL Connect Send printer driver's properties or advanced settings. Most of these settings (e.g. Output Destination, Stapling, Jogging) will not have an effect, unless the print service supports them. Ask your print service provider which features can be used when printing a document. Nevertheless, a few settings are important to the proper functioning of OL Connect Send.
Mass deployment of the OL Connect Send Printer Driver The OL Connect Send Printer Driver is intended to be installed on computers from which print jobs shall be sent to the respective Workflow server. Often such computers are part of specific domains on which end users are not allowed to install software on their own. Such users may not have the knowledge to install printers, and often dedicated restrictions and policies have to be taken into account.
installation will fail silently, but the respective log entries will be created (see "Installation errors" on page 30). Configuration file content The silent installation mode will only work with a valid configuration file. The name of the file must be OLCSClient.ini and it must be located in the same folder as the Silent Setup tool. The content of the file must follow the rules for standard Windows .ini files (see: https://en.wikipedia.org/wiki/INI_file). If the .
Section Description Default Workflow can be changed in the Workflow preferences under Plugin > HTTP Server Input 1 > Protocol options > Port. PrinterName Name for the printer to create and configure. If a printer with that name already exists, the installer will modify the settings for that printer, following the configuration file. The installer will fail if the mentioned printer is not an OL Connect Send printer. There is NO DEFAULT printer name! LogLevel Log level.
Section Description Default HostName PortInteraction The port number for browser interaction. value of Port SecureInteraction Defines if the communication shall use secure HTTPS (1) or not (0). value of Secure JobInteraction Name of the HTTP action in Workflow for the browser interaction process. olcs_ interaction StartTBN Defines if the taskbar notifier (OLCS Notifier) is started during the setup process (1) or not (0).
Reboot requirement Depending on what applications and Visual C++ runtimes already installed, a reboot may be required after the successful installation of the OL Connect Send Printer Driver. In this case the silent installer will: Return the exit value 3010 (= "Reboot required". See e.g. Windows installer error codes). Log a respective message in the log file. The administrator needs to make sure, that the respective machine is rebooted so that OL Connect Send can work as expected.
tool,documented by Microsoft: https://go.microsoft.com/fwlink/?LinkId=94329. Using API Keys OL Connect Send allows to use API keys to enhance security. Using API keys is optional, but strongly recommended. This is how it works. l l l l l The print service provider provides an API key to the OL Connect Send user (see "Providing an API key to a user" below).
OLCS Notifier Once an OL Connect Send Printer Driver is installed, an application called OLCS Notifier is also installed. It displays information concerning the preparation and transfer of each print job. The OLCS Notifier resides in the Windows taskbar, in the notification area (also called "system tray" or "status area"). It shows up with the OL Connect Send icon. The OLCS Notifier will show each OL Connect Send printer message with a standard Windows balloon speech bubble.
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: [][][] l []: The timestamp in 24 h format embedded in brackets. l []: The Job ID of the print job in question. l l []: The full name of the respective printer as defined by the user and seen in the list of printers.
l l HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Objectif Lune\ConnectSend\TaskbarNotify on 64bit Windows HKEY_LOCAL_MACHINE\SOFTWARE\Objectif Lune\ConnectSend\TaskbarNotify on 32bit Windows The key must be named UDPPort and must be of type REG_SZ. The OLCS Notifier will check this entry when it is (re)started and keeps it as long as it is running. The OL Connect Send Printer Driver is checking this entry on each job transfer.
Printing PDF files with Adobe Acrobat Reader It is recommended not to use Adobe Acrobat reader to print PDF files with OL Connect Send. Print the source file (e.g. the Word file) whenever available. If PDF files are to be printed with OL Connect Send, use a different PDF viewer instead. Adobe Acrobat Reader produces its own PostScript file, rather than passing the PDF to the OLCS Printer Driver to generate a PostScript file.
License modes OLCS can operate in three different modes but they cannot be mixed on a single Connect system. The three modes are: Basic, User and Click Charge. The Basic, unlicensed mode: l allows non-interactive job submission. l is free to use. l confirms job transmission with a message in the Notification Area (also called the "system tray"). The User and Click Charge modes are licensed modes in which: l l l interactive job submission is possible.
possible. Workflow will not save any information in the database (see "Job Processor plugin" on page 43). User mode User mode requires a license for each domain or subdomain submitting jobs. A (sub)domain license can be obtained to allow 10, 25, 50, 100, 200 or unlimited (Enterprise) users to print. Each (sub)domain needs its own domain/user license, but multiple domains/users licenses can be added to a single Connect system to allow job submissions from multiple domains.
documents -, the Click Charge license can be used. It allows any number of domains and users to submit jobs into the Connect system, providing credits are available. 1. This mode enables the Printer Driver to request a web page (which could include a preview of the document) from Connect. For each job that is received, the Job Processor plugin records key data in the database. 2. One click equals one page (any size) of the submitted print job.
Scenario 1 OLCS is licensed in Click Charge mode with 10,000 pages. They have already used 9,870 credits, so 130 are left. l l Case 1: A job comes in with 40 pages. This job can be handled in LICENSED mode, so this is a "licensed job". Case 2: A job comes in with 243 pages. This is more than 130. This job is handled in UNLICENSED mode (reduced metadata and no database entries). This is an "unlicensed job". Scenario 2 Perpetual license with domain = "some.phantasy.com" and number of licensed users = 100.
OL Connect Send in Workflow Just as the Printer Driver is an indispensable part of OL Connect Send, OL Connect Send cannot function without its Workflow plugins, embedded in special Workflow processes. These processes take care of the communication with the OL Connect Send and they handle the interaction with the user who sends a print job using the OL Connect Send. The following topics explain how to configure these processes.
Sample project The Ad Hoc Mail Consolidation sample project may help you understand the Workflow processes for OL Connect Send and configure your own. l l Watch the sample in action on demo.objectiflune.com. Under Ad Hoc Mail Consolidation, click Demo and follow the instructions. (If you have already installed the printer driver, you don't have to do that again.) Add a Connect Send printer with the given settings and print the provided Word file to that printer.
l l l l Just as the job transfer process, the interactive process start with an HTTP Server Input plugin. The action name of this HTTP Input task must match the HTTP action for interaction given in the printer driver installer (by default: olcs_interaction). (For information about this plugin, see the Workflow Help: HTTP Server Input.
Plugins Job Processor plugin The Job Processor plugin is an output plugin that appears in the Plug-in Bar of Workflow under OL Connect Send. The Job Processor plugin must be added to a Workflow job transfer process that starts with an HTTP Server Input. The Job Processor plugin can be the only other task in that process (except when API keys are used; see "Verifying an API Key" on page 58).
Configuring the plugin To configure the Job Processor plugin, right-click it after adding it to the Workflow process, and click Properties. The color of the property names in the Job Processor Properties dialog indicates that these fields can contain variables. Workflow variables To facilitate using job related information for the creation of the target folder and file name/s, the Job Processor plugin maps job relevant information to the standard Workflow variables (%1 to %8).
Information Workflow Variable When licensed When unlicensed IP Address 1 %4 The IP address The IP address No. of Pages 1 %5 Number of pages of the job Number of pages of the job No. of Copies 1 %6 Number of copies set by the user Number of copies set by the user Domain Name 1 %7 The Domain Name "na" Machine Name 1 %8 The Machine Name "na" 1) These values originate from the Printer Driver machine.
HTTPS Communication The Printer Driver can be set to use HTTPS for any job transfer. To do this Workflow must also be set to use HTTPS. This topic is covered briefly in the “Server URL Setting” section in this document (new Printer Driver installation), but full details can be found in the Workflow documentation. Job Origin OL Connect Send allows to use API keys to enhance security (see "Using API Keys" on page 31). Each print job will include unique information about the machine it has been sent from.
Timeout During a job transfer from the Printer Driver to Workflow, a timeout could occur (indicated by a log entry like “ERROR: sendBinaryContents: Could not open request. Reason: 12002”). In this case, the timeout for the HTTP service in Workflow needs to be increased. It is recommended to use a value of more than 10 minutes (>600 seconds). Additionally, the timeout in the browser on the client side should be enhanced. Please see the help pages for your browser about how to do this.
Typically, it is used in the interaction process just after the initial HTTP Server Input plugin. The Get Job Data plugin gets all relevant information for the dedicated print job using the Unique Job ID. Whenever an OLCS Printer Driver is sending a print job to the Job Processor plugin, it creates a unique ID string composed of 10 upper- and lowercase letters and digits e.g. “ri0zZdluLp”.
General Tab Three different settings affect the general behavior of the plugin: l Where to get the Print Job ID. l When to continue with the next step. l Where to store the job information details. Select Job ID Source The plugin can be used in a generic way. Whenever information about a specific print job is required, it can be retrieved as long as the related job ID is known. However, the plugin has been implemented in a way that it can also be used very easily in the OLCS interaction process.
l Read from Variable. When selecting this option, any existing Workflow variable can be chosen via the drop-down field. In this case the plugin reads the Job ID from that variable. Select Returning Type Depending on this setting the plugin gets status information about the job before it has arrived or it gets information after the job has been completely received. l l Immediately.
l l l Job UID: This is the 10 (ten) character long Unique Job Identifier string. Status ID: The status ID shows in which stage the job currently is: 0 = undefined; 1 = idle; 2 = transfer; 3 = chunk; 4 = concatenate; 5 = unzip; 6 = done. A value of 6 indicates a fully processed job. Any value between 2 and 5 (inclusive) means that the job is still in progress. For a small job, some statuses may be skipped. Date/Time stamp: This is the time when the matching job was initially created in the database.
l l l l Domain (workgroup) name: The name of the domain or workgroup the printing user belongs to. This is not necessarily the name of the domain the machine itself belongs to. Domain / Workgroup Indicator: This domain name is the real domain name or only a workgroup name. For explanations about domains, domain names, users, user names, user domains, logged on users vs. application running users, machine names etc. please refer to the respective Windows help pages or ask your system administrator.
A cleanup mechanism in the OLCSService service and in the Job Processor plugin prevent excessive growth of the Connect Send database. There are no settings to make for these mechanisms, except that you could change the default number of days to keep history of transactions. This influences the output of the Get Data plugin (see "Get Data plugin" on the previous page). By default, the Connect Send database keeps history of transactions for 60 days.
l User(s) l Machine name(s). Except for start and end dates, it is possible to pass a list of multiple search criteria, separated with semicolons, containing: l Workflow variables l Job variables l Names. Note No spaces are allowed around the listed names, respectively before or after a semicolon. Operators l Searches are case-insensitive. l Multiple entries in one filter field are combined with: OR. l Entries in different filter fields are combined with: AND.
Example 2 The domain name entered in the Filter Domains field is objmtl.objectiflune.com and the user name entered in the Filter Users field is rentel. If search criteria are entered in multiple input fields, all of them are combined with AND. Therefore the result will only contain all the print job information for objmtl.objectiflune.com where the user name is rentel. Date and Time Definitions Both date and time entries must be notated in UTC format.
l Original file name l Original file size l Domain (workgroup) name l Domain / Workgroup Indicator l Machine name l Machine GUID. Results File Format The following result file formats are selectable: l XML l JSON l CSV (Separator = semicolon (0x3B), string indicator = quote (0x22)). Note This file is not automatically saved to disk. The retrieved job info is written to a temporary results file that will be passed on as the new Workflow job file.
Note The Printer Driver machine time stamp in the Printer Driver log may significantly differ from this value. l l l l l l l l Number of Copies: This is the value set by the Printer Driver for the number of copies (intended number of copies required for the print job). Some applications do not use the general print job information to define the number of copies. In such (rare) cases, the Number of Copies sent in the job can differ from what the user entered in the print dialog.
l Machine GUID: The unique machine ID (see "Job Origin" on page 46) of the machine on which the job was produced. It can be used as an additional identification mark to validate the origin of the job. On Error Tab Please refer to the Using the On Error tab paragraph from the Workflow documentation. Miscellaneous Tab Please refer to the Miscellaneous tab paragraph from the Workflow documentation.
Retrieving the API key from the HTTP headers can be done with a Run Script task. For example: // Get Bearer Key from raw header var rawHeaders = Watch.ExpandString("xmlget('/request[1]/header [1]/rawheaders[1]',Value,KeepCase,NoTrim)"); var authHeaderPattern = /^Authorization=Bearer (\S+)$/m; var matchResult = rawHeaders.match(authHeaderPattern); if (matchResult != null && matchResult.length == 2) { Watch.SetVariable ('bearer_key', matchResult[1]); Watch.SetVariable ('key_found', 'yes'); } else { Watch.
Another Text Condition task checks if the API key is actually valid (here: comparing the value found in the %{bearer_key} variable to a string value). If it is valid, the job may be processed by the Job Processor task. If the API key wasn't valid, use the Set Job Infos and Variables task to assign the value of the respective response code, 401, to the variable that was selected in the Input task. If the API key is missing, the code should be 400 (bad request).
Using the Printer Driver The OL Connect Printer Driver can be used like any physical printer. Just go through the usual steps: 1. Click the Print button (or use the menu from the software used). The Print dialog appears. 2. In the Print dialog, select a printer that works with the OL Connect Send printer driver and click OK.
The OL Connect Send Printer generates a local PostScript file. This data is zipped and sent in one or multiple chunks to the Workflow server. Depending how the environment has been setup, information is sent using the HTTP or HTTPS protocol.
customer’s machine is launched showing the interactive web page defined in the installation process. Warning It is recommended not to use Adobe Acrobat Reader to print PDF files with OL Connect Send. Print the source file (e.g. the Word file) whenever available. If PDF files are to be printed with OL Connect Send, use a different PDF viewer instead. Adobe Acrobat Reader produces its own PostScript file, rather than passing the PDF to the OLCS Printer Driver to generate the PostScript file.
Log files Workflow log files The OL Connect Send Workflow plugins write to the Workflow log file. Its location can be found in the Workflow Help (see help.objectiflune.com). Printer log files Each OL Connect Send printer logs its messages in a daily log file. The log files are located under %ProgramData%\Objectif Lune\CPD\Log\ on the machine/s on which the Printer Driver has been installed.
On the first line of this CSV file are its column headers: {{Date;Time;Printer;Job ID;Document Path;Document Name;Pages;Chunks;Chunk No;Status;Mode;User;Target}} The separator character is the semicolon (0x3B). Each following line is one log entry. The file can be loaded with e.g. Excel and filtered, ordered, sorted and modified as desired.
l Printer name l Job ID l l Document path as can be retrieved from the spooler information. Please be aware that some applications suppress this information. Document name as can be retrieved from the spooler information. Please be aware that some applications modify, mix up, enhance or truncate this information. l Number of pages l Number of chunks l Chunk number = number of the currently transferred chunk l Job transfer status.
Troubleshooting There are some known issues that can be encountered when using Connect Send, depending on the way OL Connect Send is installed, configured or used; see "Known Issues" on page 34. If another issue occurs and you find that you cannot solve the issue, there are a few things to check. 1. Switch the OL Connect Send Printer Driver logging to DEBUG. This can be done by modifying the OL Connect Send Printer Driver; see "Installing OL Connect Send Printer Driver" on page 12.
c. Remove the existing OLConnect1.OLConnectLicense from %ProgramData%\Objectif Lune\OL Connect\licenses. d. Put the new license at that location. e. Restart any Connect services you stopped. You may notice that removing the existing license may be forbidden and you need to allow it explicitly. It may even be that you need to log on as an administrator to delete the file. Note This is not an issue with OLCS, but with the Connect and/or Workflow version and under which user it has been installed.
