Installation and Activation Guide 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 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. by any means whatsoever without the express written permission of Objectif Lune Inc.
Table of Contents Table of Contents 4 System and Hardware Considerations 7 Antivirus Exclusions Directories and folders Database Considerations Using the MySQL Instance from the Installer Installing / Updating Connect using an existing MySQL instance Installing Connect using an existing Microsoft SQL Server instance Updating With No Local MySQL Product When modifying Connect Important Environment considerations Terminal Server/Service Support Virtual Machine Support Remote Desktop Support 32-bit or 64-b
Requirements for individual Connect modules Editions of Connect Products Installation and Activation Where to obtain the installers Installation prerequisites User accounts and security Installing PReS Connect on Machines without Internet Access Updating Connect Initial Connect Installation Installation Wizard Updating from Connect versions predating 2019.
Upgrading from PReS Classic Upgrading from PlanetPress Suite 6/7 Information about PReS Workflow Server Configuration Settings 66 66 84 86 Connection preferences Background Connection settings (standalone/Master) Connection settings (Slave) Engine configuration Speed quota: Pages Per Minute Launching multiple engines Allocating processing power to jobs Automatic Restart Settings Parallel Processing preferences Parallel Processing properties (Designer Preferences) Parallel Processing properties (Server Con
System and Hardware Considerations There are a variety of considerations to be aware of.
Antivirus Exclusions The information on this page is designed to assist IT managers and IT professionals decide what anti-virus strategy to follow with consideration to PReS and their internal requirements and needs. This page describes the mode of operation and the files and folders used by PReS as well as the files, folders and executables that are recommended to be ignored for best possible performance and to avoid issues caused by antivirus file locks.
AFP Input Performance issues have been reported with the AFP Input option under Windows Server versions from Windows Server 2012 onwards. The issues have been specifically associated with Windows Servers running Windows Defender, but the performance degradation might also be encountered when using other Antivirus applications. Consequently, we recommend that an exclusion be made for the afp2pdf.exe executable file in your Antivirus application. The afp2pdf.
the whole system at all. However the responsible person for the computer protection has to decide about the monitoring of such temporary folders following the company guidelines. Database 2 Another database instance for Connect will be hold and used under the folder, which is intended to hold data, accessible by and for all users. The path to this folder is stored in the standardized system variable %PROGRAMDATA%. The Connect database instance is located in the subfolder "Connect\MySQL".
Installing / Updating Connect using an existing MySQL instance If MySQL Server is already present and you wish to use it, the following should be taken into consideration: l l l l l The minimum supported MySQL version is MySQL 5.6. The MySQL account must have access to all permissions using the GRANT Command, including creating databases. The database configuration must include the options detailed in the "Using the MySQL Instance from the Installer" on the previous page topic above.
Installing Connect using an existing Microsoft SQL Server instance If Microsoft SQL Server is already present and you wish to use it, the following should be taken into consideration: Warning If you chose not to install the supplied MySQL database, and instead opt for using a preexisting (External) database then you yourself must ensure that the External database is accessible to Connect. Objectif Lune Inc.
Updating With No Local MySQL Product l l When updating a Connect installation from 1.5.0 which contains a Server Product but no local MySQL Product, the Database Configuration Page will detect which database type was set before (especially if the database configuration was switched from MySQL to MS SQL using the Server Configuration Tool), and default to those settings. On Update from 1.4.
6. Enter the command sc config OLConnect_Server depend= /. This removes the dependency. Please be aware: The key word depend must be followed immediately by the equal sign, but between the equal sign and the forward slash there must be a space. Additional information can be found here: http://serverfault.com/questions/24821/howto-add-dependency-on-a-windows-service-after-the-service-is-installed#228326. 7.
After this modification, the local MySQL is removed, and also the service dependency from Server to MySQL is removed. Note If Connect was initially installed not containing the local MySQL product (i.e. on 1.5 installation an external MySQL was configured as database), then the Update to 1.6 will allow to select either external MySQL or external Microsoft SQL on the Database Configuration Page.
PReS Connect is not officially supported on any other virtual machines such as Virtual PC, Parallels, Bochs, Xen, etc. Warning Copying (duplicating) a Virtual Machine with Connect installed and using both images simultaneously constitutes an infringement of our End-User License Agreement. Note While some virtual machine environments (from VMWare and Microsoft) are supported, other virtual environments (such as Parallels, Xen and others) are not supported at this time.
Windows Search Indexing Service Tests have concluded that the Windows Search service, used to provide indexing for Windows Search, can interfere with Connect when installing on a virtual machine. If the installation hangs during the last steps, it is necessary to completely disable this service during installation. l Click on Start, Run. l Type in services.msc and click OK. l Locate the Windows Search service and double-click on it.
l Language: l PReS Connect is currently offered in several languages. These languages can be switch between via the Preferences dialog. The current languages include: l English l French l German l Spanish l Italian l Korean l Portuguese l Chinese (Simplified) l Chinese (Traditional) l Japanese. The default language is English. The PReS Connect help system (this document) is currently only available in English.
on the statements outlined herein. Listens on port Destination # port # Messenger 5863/5864 Connect Server Connect Server HTTP Server HTTPS Server NodeJS Server NodeJS HTTPS Server Type 5863/5864 TCP+UDP 9340 Comment Used for inter-module communication TCP Used for Connect REST API 9350 TCP Dedicated internal connection for inter-process communication (i.e.
Listens on port Destination Type # port # 9100 TCP Telnet FTP Input/Output MySQL 3306 Microsoft 1433 SQL Server HyperSQL 9001 21 Comment TCP TCP+UDP TCP+UDP TCP l Port numbers in bold type are user configurable. l Port numbers in bold underlined type are based on the type of database used. l Some of the ports listed above may also be used by other modules. l User-configurable modules may use other ports entirely, depending on the settings defined by the end user.
Processing preferences" on page 99). Next, open the log file of the Weaver engine. By default, the log files are located in this folder: C:\Users\[username]\Connect\logs\WeaverEngine, where [username] is your own Windows user name. Search the log file for "PPM" (pages per minute). Repeat this a few times to determine the average output speed. Likewise, the output speed for an Email or Web template can be found by running it with one Merge engine and the maximum target speed per job.
Note Connect Server and Connect Designer each have their own distinct scheduling preferences. Use the Connect Server Configuration tool to change the Connect Server settings and Designer > Windows >Preferences for changing Designer settings. Template optimization When you find that the speed per Merge engine - the Content Creation speed - is low, optimizing a template can make a huge difference. For advice on how to optimize a template see: Optimizing a template.
l l l l Use at least 8+ GB High-Quality RAM. Check memory usage while the Print command is being executed to see if you need more than the minimum of 8GB. Assuming that the Connect Server and the Connect database need 1GB each, and that each engine needs 1GB as well, you can roughly estimate how much memory is needed. Consider using a physical machine instead of a virtual machine.
not supported by OL Connect products. Virtual Environments l VMWare/VSphere l Hyper-V l Azure l Amazon Web Services (AWS). Note that only EC2 M4 was certified, other instances may not work as expected. Minimum hardware requirements As with any software application, minimum hardware requirements represent the most basic hardware on which the software will run. Note however that settling for the minimum specification is unlikely to produce the performance you expect from the system.
l File system: NTFS (FAT32 is not supported) l CPU: Intel Core i7-4770 Haswell or equivalent l RAM: 16GB l Disk Space: 4GB for the software modules, 20GB for work files* l Storage Type: Solid State Drive (SSD) l Networking: 10Gb Ethernet * This depends on the amount of data you process through OL Connect. For instance, a PostScript file containing several thousands of documents could easily take up several GBs.
Note As with any JAVA application, the more RAM available, the faster PReS Connect will execute.
Installation and Activation This topic provides detailed information about the installation and activation of PReS Connect 2020.1. Note A PDF version of this guide is available for use in offline installations. Click here to download it. PReS Connect 2020.1 is comprised of 2 different installers: one for the PReS Connect software and one for PReS Workflow 2020.1. Where to obtain the installers The installers for PReS Connect 2020.1 and PReS Workflow 2020.
l "Migrating to a new workstation" on page 54 l "Upgrading from previous Connect versions" on page 62 Installation - "How to" guides For information on how to conduct the installation itself, choose from the following topics: l "Installation Wizard" on page 32 l "Running Connect installer in Silent Mode" on page 43 l "Installing PReS Connect on Machines without Internet Access" on page 30 Activation For information on licensing, please see "Activating a License" on page 51.
.NET 3.5 must also be installed. This will need to be installed manually, as .NET 3.5 is not included in the Workflow setup. User accounts and security Connect requires local Windows Administrator rights when installing the software and activating the software license. This is to allow read/write access to protected Windows folders and registry entries. Once installed Connect requires only standard Windows user credentials to run.
l In the Connection tab, define the account name and password that the service should use. This can be a local account on the computer or an account on a Windows Domain. The account must have administrative access on the machine. It should also correspond to the user account set up in PReS Worfklow. Installing PReS Connect on Machines without Internet Access Installing PReS Connect2020.1 in offline mode requires some extra steps. These are listed below. Updating Connect Updating to Connect 2019.
l GoDaddy Secure Server Certificate (Intermediate Certificate) - G2 - the file is gdig2.crt 2. Install the certificates: Right mouse click -> Install Certificate, and follow the steps through the subsequent wizard. 3. Now copy the PReS Connect installer to the offline machine and start the installation as normal Windows certificate validation - Certificate Revocation List retrieval should be switched off For your security Objectif Lune digitally signs all relevant files with our own name and certificate.
Installation Wizard Updating from Connect versions predating 2019.1 In order to update PReS Connect to 2020.1 from Connect versions prior to 2019.1 it is first necessary to update the Connect License. For details on how to upgrade the Connect License see "Users of Connect prior to 2019.1" on page 63 Starting the PReS Connect installer The PReS Connect installer may be supplied as an ISO image or on a DVD.
l PReS_Connect_Setup_x64.exe --trace This adds full trace style logging to the installation process. The log file this produces will be very large, as this option logs everything. Selecting the required components After clicking the Next button, the component selection page appears, where the different components of PReS Connect can be selected for installation.
If you wish to make use of an external database, please make sure the MySQL option is not selected. Warning .If you chose not to install the supplied MySQL database, and instead opt for using a pre-existing (External) database then you yourself must ensure that the External database is accessible to Connect. Objectif Lune Inc. will take no responsibility for setting up database connections to any but the supplied MySQL database.
description of the error will be displayed in the information area. The installer can also calculate how much disk space is required for installing the selected components as well as how much space is available: l l l l Disk space required: Displays the amount of space required on the disk by the selected components. Disk space available on drive: Displays the amount of space available for installation on the drive currently in the Installation Path.
l a numeric digit (1, 2, 3 ...) l a punctuation character (@, $, ~ ...) For example: "This1s@K" Note When updating from an earlier Connect version, the appropriate MySQL password must be entered or the update will fail. If the password is subsequently forgotten, then MySQL must be uninstalled and its database deleted from disk before attempting to reinstall. l l Confirm MySQL user 'root' Password: Re-enter to confirm the password. Both passwords must match for installation to continue.
PReS Connect installation. Tip This option may represent a security risk if the machine is open to the internet. We heavily recommended that your firewall is set to block access to port 3306 from external requests. Configuring External Database Connection The Database Connection page appears if the supplied MySQL module was not selected for installation. This page is for setting up the connection to the existing External database.
non-local TCP connections, and the user account must also be configured to accept remote connection. For example, the "root" MySQL user entered as root@localhost is not allowed to connect from any other machine than the one where MySQL is installed. l l Administrator Password: Enter the password for the above user account. For MySQL the appropriate password must be entered or the Connect installation will fail. Use Encrypted SSL Connection checkbox: Check to enable encrypted connections to MySQL (v5.6.
Server Extension (Slave) component is configured, depending upon which option was selected as part of the installation: Connect Server or Connect Server Extension. Connect Server (Master) settings The Connect Server (Master) settings are as follows:. l Run Server as: Defines the machine username and password that the Connect Server module's service uses.
Such an installation assumes that the Connect Server (the Connect Master Server) has previously been setup on another machine, and that the option "Allow MySQL Server to accept non-local TCP connections” option were selected during that installation. Before installing the software, make sure that both TCP/IP ports 3306 and 9340 are open on the Connect Master Server and Connect Extension Server, in both the Inbound and Outbound Firewall Rules. Access within the Private and Domain profiles is sufficient.
Note This button must be clicked and the user validated before the Next button becomes available. l Master Server Connection (Default Settings): l Hostname: Enter the machine name or IP Address where the Connect Master Server resides. There is no requirement for the Master and Extension servers to belong to the same IP subnet. IP subnetting is beyond the scope of this documentation, but more information can be found here: https://en.wikipedia.org/wiki/Subnetwork.
Completing the installation This screen describes a summary of the components that have been installed. l l l Configure Update Check checkbox: This option is enabled by default. It causes the Product Update Manager to run after the installation is complete. This allows configuring PReS Connect to regularly check for entitled updates. Note: this checkbox may not be available in the event that an issue was encountered during the installation. Show Log...
Product Activation After installation, it is necessary to activate the software. See Activating your license for more information. Before activating the software, please wait 5 minutes for the database to initialize. If the software is activated and the services rebooted too quickly, the database can become corrupted and require a re-installation. Running Connect installer in Silent Mode Updating from Connect versions predating 2019.1 In order to update PReS Connect to 2020.
For supported keys, please refer to the next paragraph. Note The install.properties file notation must follow commons configuration rules. Please refer to Properties files for more details. Required and optional properties Required properties depend on the specified product. Only fields related to that specified product must be entered. If no product is mentioned, properties must be specified for all valid Connect products. Here is an example of an install.properties file. # Verbose logging logging.
Product selection (optional) By default, if nothing is entered for the products to be installed (install.product.X), Silent Installer will install all products which are visible to the user for the respective brand (except for the Server Extension, because only Server or Server Extension can be installed at the same time). PReS defaults install.product.0 install.product.1 install.product.2 install.product.3 = = = = Connect Designer Connect Server Connect Print Manager MySQL Note The values of install.
Database configuration Case 1: MySQL is among the selected Connect products to be installed (new MySQL installation) If MySQL is selected and there is no previous MySQL configuration on the machine, the following properties should be defined: database.password = (required and must meet the rules) database.port = (3306 is the default port value) database.
Case 2: The Connect Server or the Connect Server Extension is selected and MySQL is not selected In this case, an external database must be configured for the Server (and other Connect products included in the Silent installation) to be used. 2a: Configuring an external MySQL database To configure an external MySQL database, the following properties should be defined: database.type = mysql (required) database.host = (default value is localhost, otherwise required) database.
Repository selection The Connect installation process requires a repository from which the installer copies (locally) or downloads (online installation) all selected Connect products. In Silent Installer mode, the installation process looks for the property product.repository in the install.properties file and then proceeds with the following steps: 1. If the property exists, and its value contains an existing file location with a repository, the installer will attempt to install from that repository. 2.
l en-US (English, US) l de-DE (German, Germany) l fr-FR (French, France) l ja-JP (Japanese, Japan) l zh-CN (Chinese, China) l zh-HK (Chinese, Hongkong) l zh-MO (Chinese, Macau) l zh-TW (Chinese, Taiwan) l it-IT (Italian, Italy) l pt-BR (Portuguese, Brazil) l es-419 (Spanish, Latin America) Locale selection by defining user.language and user.country If both user.language and user.country are defined in the install.
1. If the System Locale is in the list of supported Locales, it will be selected. 2. Otherwise, if there is an entry in the list of supported Locales, which matches the System language, it will be selected (e.g. on a fr-CA system, fr-FR is selected). 3. As last resort, the first Locale in the preinstall.ini is selected (usually that should be enUS). Getting the exit code of a silent installation If getting the exit code of a silent installation is desirable, use the following procedure. 1.
Sample batch file @echo off preinstall.exe if errorlevel 10 goto err_installer if errorlevel 2 goto err_unknown if errorlevel 1 goto err_preinstall echo Success goto:eof :err_installer echo "Installer error - see OL_Install_.log" goto:eof :err_unknown echo "Unknown preinstall error - see preinstall_err.log" goto:eof :err_preinstall echo "Preinstall error - see preinstall_err.
l Open the Start Menu l Click on All Programs and browse to the Objectif Lune folder. l Open the Connect Software Activation shortcut. l The PReS Connect Software Activation application consists of the following: l License Information subsection: l l l Magic Number: Displays the PReS Connect Magic Number. Copy the magic number to the clipboard: Click to copy the Magic Number to the clipboard. It can then be pasted in the activation request email using the Windows CTRL+V keyboard shortcut.
Requesting a license After getting the Magic Number, a license request must be done for both PReS Connect (for both Master and Extension Servers, if using a Clustered environment) and Workflow 8: l l Customers must submit their Magic Number and serial number to Objectif Lune via the Web Activations page: http://www.objectiflune.com/activations. The OL Customer Care team will then send the PReS Connect license file via email.
Activating the PReS Connect license requires the user to have local Windows Administration rights. l Using a user profile that has local Windows Administration rights, open the Start Menu l Click on All Programs, then browse to the Objectif Lune folder. l Run the “Connect Software Activation” tool. l l l Click the Load License File button, and browse for the .olconnectlicense file you received from Objectif Lune Inc.. Read the EULA and click the I agree option to accept it.
l "Environment considerations" on page 15 l "Installation prerequisites" on page 28 l "Antivirus Exclusions" on page 8 Downloading and installing the software In order to migrate to a new workstation, the software must already be installed on the new workstation. Follow the "Installation and Activation" on page 27 guide to download and install the newest version of PReS Connect on the new workstation.
l l l If you still use PlanetPress 7 legacy documents, PTK files can be imported by clicking on the Workflow tool button at the top left corner of the Workflow tool interface. If copying the PlanetPress Workflow 8 folder directly, it's important to delete any file with the .ps7 extension so as to refresh the PostScript file for the new workstation. Deleting the .ps7 files will make Workflow recreate them. The Workflow configuration file itself is named ppwatch.cfg, and is backed up with the folders.
1. Click on Tools in the Workflow Configuration menu bar. 2. Click Configure Services. 3. Select the user account. l l If required, grant permissions to other machines (Designer clients and other servers) to send documents and jobs to the new server. l Click on Tools in the Workflow Configuration menu bar. l Click on Access Manager l Grant necessary permissions to remote machines. l Restart the Workflow Messenger service.
[UserName]\Connect\workspace\configurations\PrinterDefinitionCo nfig l OMR Marks Configuration Files (.hcf): C:\Users\[UserName]\Connect\workspace\configurations\HCFFiles Where [username] is replaced by the appropriate Windows user name. Tip Actually, the path may not begin with 'C:\Users', as this is language-dependent. On a French system, for example, it would be 'C:\Utilisateurs'. Type %userprofile% in a Windows File Explorer and press Enter to open the actual current user's home directory.
Capture 1. Download the latest version of the Anoto PenDirector. 2. Before installing the PenDirector, make sure the pen’s docking station isn’t plugged into the server. Then install the PenDirector. 3. Stop the Messenger 8 service on the old and new server from the Workflow menu bar: Tools > Service Console > Messenger > right-click and select Stop. 4. Import the following files and folders from the old server into their equivalent location on the new server: C:\ProgramData\Objectif Lune\PlanetPress Workfl
1. Stop the OLConnect_Server service from Control Panel > Administrative Tools > Services > OLConnect_Server > Stop. 2. Configure the Merge and Weaver Engines scheduling preferences as in the previous installation l l l Open the Server Configuration from: C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.exe Configure the DataMapper, Merge and Weaver engines preferences (see "Parallel Processing preferences" on page 99). As of version 2018.
2. Open the Server Extension Configuration from: C:\Program Files\Objectif Lune\OL Connect\Connect Server Extension\ServerExtension.exe 3. Click on Database Connection and configure the JDBC Database connection settings so that the hostname points to the new Master Server. 4. Click on Scheduling and type in the location of the new Master Server. 5. Start the OLConnect_ServerExtension service.
6. Restart the OLConnect_Server service and restart the OLConnectServer_Extension service on the Extension servers, where applicable. 7. The number of Expected Remote Merge and Weaver engines should now be configurable in the Connect Server Configuration module (C:\Program Files\Objectif Lune\OL Connect\Connect Server Configuration\ServerConfig.exe) To apply the PlanetPress Capture License: 1. Open the Workflow Configuration. 2.
scenario in which the new version introduces issues with your existing production processes. Whilst the probability of such a worst case scenario is remote, it cannot hurt to take some simple precautions, just in case. For instructions on how to do so, please see "Backup existing Connect version" on the facing page. Note The scheduling settings in version 2019.2 have changed. Please make sure to record your current scheduling settings for reference before proceeding with an upgrade.
Knowledge Base (https://help.objectiflune.com/en/kbconnect/#KB/FAQ/OL%20Connect/KB2002.htm). Users of Connect 1.1 In order for users of PReS Connect 1.1 to upgrade to any later version through the Update Manager it is necessary to install a later version (1.1.8 or later) of the Objectif Lune Update Client. If you do not have such a version installed already, the next time you run your Update Client it will show that there is an update available of itself to Version 1.1.8 (or later).
Backing up a real machine Note The scheduling settings in version 2019.2 have totally changed, making it impossible to revert these settings back to the previous version. Please make sure to record your current Scheduling settings for reference before proceeding with an upgrade. Backup these folders l C:\ProgramData\Objectif Lune\OL Connect\.settings\ConnectHostScope l C:\Users\[UserName]\Connect\filestore l C:\Users\[UserName]\Connect\workspace\configurations l C:\Users\ [UserName]\Connect\workspa
recommend the MySQLDump tool be used for this. See for details on this utility program: mysqldump (https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html). Upgrading from PReS Classic PReS Classic and PReS Connect are very different products. Whilst PReS Connect provides considerably more options for email and web output, one need not abandon existing PReS Classic print jobs. They can still be run through Connect Workflow, via the PReS Print Controls task in the Online Help of Workflow (see http://help.
l Imaging for PReS Connect is available as an option. It contains: l PReS Fax l PReS Image l PReS Search IMPORTANT: If you owned them, you must also upgrade your Imaging modules to use the new version. l l l PlanetPress Capture is still supported in PReS Workflow 2020.1 but only with documents created with the PlanetPress Suite Design 7. PReS Connect Designer. This is a design tool based on completely new technology.
PReS Connect installation considerations The PlanetPress Suite could run on a computer with a minimum of only 1GB of RAM available. The PReS Connect Server with PReS Workflow 2020.1, by default, requires 8GB of RAM, but if you intend on using the new PReS Connect Designer on the same computer, you should consider having at least 16GB of RAM available. See "System requirements" on page 23.
Note If you were a PlanetPress Production user, you retain all functionalities within PReS Workflow 2020.1. These are automatically imported during the activation (see below). Create new documents and integrate them into your workflow at your own pace You can start benefiting from the innovative technology of the new PReS Connect Designer right away by designing new documents, or re-doing existing ones at your own pace.
in the Workflow setup. 4. If you installed PReS Workflow 2020.
7.
8. Then select the product from which you wish to upgrade: 9.
10.
11. After that you will need to get the activation file for your product. To obtain your activation, download the PReS Connect installer from the Web Activation Manager (http://www.objectiflune.com/webactivationmanager/), follow the instructions for the installation using the serial number provided to you. You can activate your license through the Web Activation Manager. 12.
How to perform a Workflow migration What do you need to consider when upgrading from PlanetPress Suite 7 to PReS Connect Workflow 2020.1 on a new computer? Installing and Activating Workflow 2020.1 on a new computer Points to consider: l l l l Before installing, be sure to read "Installation and Activation" on page 27. There you will find detailed Connect Workflow installation steps as well as system requirements, notes on license activation and much more.
then activate all of your printers on the new computer. l l Login to our Web Activation Manager (www.objectiflune.com/activations) using your customer number and password to get your Printer Activation Codes. If you do not have access to the computer in which PlanetPress Suite was previously installed, print a Status Page for each printer from your Connect Workflow 8 Configuration. Do this via the Tools > Printer Utilities menu option.
2. Copy all the PlanetPress Suite 7 Documents and Compiled forms (*.ptk and *.ptz) from the Documents folder on the PlanetPress Suite computer and paste them into the equivalent folder on the Connect Workflow Computer. The PlanetPress Suite 7 folder would be "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\Documents". The PReS Connect Workflow 8 folder will be "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\Documents" 3.
Alternatively, you can download custom plug-ins from http://planetpress.objectiflune.com/en/suite/resources/support onto the new computer. Once you've copied your PlanetPress Suite Workflow configurations to Connect Workflow, you can confirm their availability through the Plug-in Bar Uncategorized category. There you will find all the Custom plug-ins that have been installed. Missing plug-ins will be represented in Workflow steps through the use of a "?" icon.
l l l l If the Windows "TCP/IP Print Server" service is running on the new computer, it is recommended that you disable the Server so that it does not interfere with the PlanetPress LPD/LPR services. If you are using images from a virtual drive, copy the entire contents of "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PSRIP" and paste them onto the new computer here: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PSRIP". Make sure to set the user who will run the PlanetPress Services.
page 75. Failure to do so will result in unexpected problems. Note It is recommended that you first update your PlanetPress Suite to version 7.6 before cross-grading to PReS Connect. Using PReS Connect Workflow 2020.1 on the same computer as PlanetPress Suite 7.6 Steps to migrate: 1. Update existing installation to PlanetPress Suite version 7.6 if not already done. 2. Install PReS Connect Workflow 2020.1 on the same computer. 3. Do the following for both PlanetPress Suite version 7.
Note Prior to PlanetPress Suite 7.6, all Capture patterns, documents and several other details were contained within the one single database. As of PlanetPress Suite 7.6 a separate database has been used for the patterns alone (PPCaptureDefault.mdb). 5. Copy the contents of this folder: "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\DocumentManager" to this folder: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\DocumentManager". 6.
rending the parallel mode very hard to produce. It is not impossible, but describing how it can be done is beyond the scope of this migration article. Steps to migrate: 1. Update existing installation to PlanetPress Suite version 7.6 if not already done. 2. Install PReS Connect Workflow 2020.1 on new computer. 3. The Anoto PenDirector must be installed. It if is not, you can download it from http://www.objectiflune.com/OL/lib/Common/Downloads/PlanetPressCaptureResources/ AnotoPenDirector.
Note These steps must be done for both PlanetPress Suite Workflow 7 and PReS Connect Workflow 8. 5. Copy the file PPCaptureDefault.mdb from this folder on the PlanetPress Suite 7.6 computer: "C:\ProgramData\Objectif Lune\PlanetPress Suite 7\PlanetPress Watch\capture" to this folder on the new PReS Connect Workflow 2020.1 computer: "C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\capture" and overwrite the existing database. Note Prior to PlanetPress Suite 7.
2. Select Messenger in the tree list, right click and select Start from the context menu options. 9. Contact your local Objectif Lune activation team and transfer any Pen(s) licenses across. Information about PReS Workflow If you wish to use PReS Workflow (automation) in conjunction with PReS Connect, you will need to install PReS Workflow 2020.1 as well. Workflow 2020.
versions (as far back as Version 4) to run on PReS Workflow 2020.1, removing the need to run both versions. For more information on the licensing of Workflow 2020.1, please see "Activating a License" on page 51.
Server Configuration Settings This chapter describes configuring the PReS Connect Server. In PReS Connect you can install Servers on multiple machines, in a Master/Slave relationship. To see an overview of these Master/Slave setups, please see the "Server Clustering" on page 107 topic. The Connect Server settings are maintained by the Connect Server Configuration utility tool which is installed alongside PReS Connect.
l Engines preferences l "Automatic Restart Settings" on page 98 (not available in Server Extension (Slave) installations) Note Automatic Restarts are controlled by the main server. Slaves are treated the same as local engines in regards to restart timing.
Connection settings (standalone/Master) l Primary Connection group. Use this to adjust the HTTP communication settings for Connect. l l l l Port: Set the primary HTTP Server connection port number for Connect. Maximum threads: Sets the maximum number of HTTP threads for processing requests. This entry should only be changed in consultation with OL. Maximum queues: Sets the maximum number of requests can remain in the queue. This entry should only be changed in consultation with OL.
Connection settings (Slave) l Master Server group. Use this to set connection to PReS Connect Master server. l Hostname: Set the device name for the PReS Connect Master server. l Port: Set the port number for the PReS Connect Master server. l l l l l Username: The account that the services use to login to the PReS Connect Master server. If the machine is on a domain, use the format domain\username. Password: Enter the password associated with selected username.
Engine configuration The Connect Server cooperates with different engines to handle specific tasks. A DataMapper engine extracts data from a data file. A Merge engine merges the template and the data to create Email and Web output, or to create an intermediary file for Printed output. The intermediary file is in turn used by a Weaver engine to prepare the Print output. (For more information see: Connect: a peek under the hood).
This topic explains all of these settings and the principles behind them, and it provides guidelines for letting the Server manage the workload in such a way as to achieve the highest possible output speeds. Factors to take into account are: l l l Your licence, which imposes a speed quota (see "Speed quota: Pages Per Minute" below). The processing power of your machine(s). How many cores it has determines how many engines can be launched (see "Launching multiple engines" on the facing page).
l l l Weaver engines always require a Licensed task to run. Merge engines only require a Licensed task when creating Email or Web output. Merge engines involved in a Print process don't need a Licensed task in order to run. DataMapper engines don't need Licensed tasks. In situations where Print and Email and/or Web output are created at the same time, only the Merge engines that create Email/Web output count towards the maximum number of Licensed tasks for that type of output.
cores, Windows Task Manager will show 4 cores and 8 logical processors on its performance tab. On a CPU like this, 5 or 6 engines can be configured to run in parallel. To configure the number of engines: 1. Open the Connect Server Configuration utility tool (see "Server Configuration Settings" on page 86). 2. Under Parallel Processing, go to the Content Creation tab and set the number of Merge engines for the various tasks. 3. Go to the Output Creation tab and set the Reserved Weaver (Output) engines.
The Connect MySQL database needs a fast storage system (SSD or other fast devices) to be able to keep up with two or more DataMapper engines. When the database is installed on a system with a slow hard drive, adding a DataMapper engine may not increase the overall performance. Weaver engine Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run simultaneously with smaller Print jobs.
Depending on the answers to these questions, you can allocate processing power to jobs in order to run them as fast as possible, and/or in the order of your preference. The first step in this process is to define the size of small, medium and large jobs. Job size Connect lets you define job sizes by setting the maximum number of pages a job can have and still be considered a small job, and what the minimum number of pages a job can have in order to be considered large.
handled at the same time by that kind of engine, because there are only so many engines (and speed units) available. Note When each individual record in a job is composed of a very large number of pages, the Memory per engine setting and the machine's hard drive speed are probably more important than the number of Merge engines, since one record cannot be split over multiple machines or even cores (see "Memory per engine" on page 94).
may have to wait (or wait longer). However, if the server receives many web requests then having engines reserved for HTML output can help performance. l l By reserving a number of parallel engines for Print jobs of a certain size (see "Number of parallel engines per Print job" on page 95). More parallel engines will make them run faster, but they will have to wait (longer) if the required number of engines isn't available when they come in.
Batch processing. In a batch processing situation, jobs don't have to be handled simultaneously. All jobs - whether they are big and small - are processed one after another. Every job should be handled as quickly as possible. It is therefor recommended to assign the maximum number of engines and target speeds to all jobs. Do not reserve engines for certain jobs. Web requests. In online communication, response times are critical.
l l Daily restart period begin: Only available if Daily restart in period selected. Enter the daily start time for the time window in which automatic restarts will be scheduled to occur. Daily restart period end: Only available if Daily restart in period selected. The end of the daily time window in which the automatic restarts are scheduled to occur. Memory limit Enter the memory limit for individual Engines.
Parallel Processing properties (Designer Preferences) Preset selection (Designer Preferences) Only the Custom setting is applicable to the Designer Preferences, so this option is always selected and the field made read-only. Content Creation Tab (Designer Preferences) A Tab with data that relates solely to Content Creation. The options are: l l Total Merge engines configured read only display: This is a read only entry that shows the total number of Merge engines available.
l Additional engine every (records) entry: This controls how many Merge engines are used for a Content Creation task. It means that for every additional 'x' records in the task, an additional Merge engine will be used. For example, with the default 100 record threshold, tasks with 1-100 records will be assigned 1 Merge engine, tasks with 101-200 get assigned 2 merge engines, tasks with 201-300 get assigned 3 merge engines, and so on. Note These entries aren't applied instantaneously. There is often a lag.
l l l l l l l Default - Basic settings that are good for running most things. Single jobs have preference over multi-tasking, however. Batch Print - Best settings for processing jobs, one by one, in a sequential, first in first out (FIFO) order. On demand Print - Best settings for processing many small print jobs simultaneously. On demand - Use when serving web pages, sending emails, and printing many on demand jobs simultaneously. Connect Send - Settings optimized for use with Connect Send.
is a Merge engine available. How many Merge engines to use is based on the number of records in the input data. Select from the following options: l Optimize per task: This runs each task with as many Merge engines as needed (until engines are exhausted). Using this option means that Merge engines will not be reassigned when new tasks come in. This option is better suited for batch processing.
allowed to use all Merge engines. It also assumes that using more than one Merge engine for less than 100 records will probably not make a big enough difference to throughput speed. Obviously, there are situations where these assumptions will not apply. Note Currently, it’s only the print and PDF content creation tasks that use multiple Merge engines. l Reserve engines for on demand tasks group checkbox: Reassigning engines is not instantaneous when a new task arrives.
If only the single Weaver Engine is configured in the Engines preferences page, then this whole tab will be disabled. l l Licensed speed limit (pages per minute): This read only entry shows the current license speed limitations, in pages per minute. The speed limitations are determined by your Connect license. This information is to help you choose what settings would make sense when assigning the “Target speed” values later in the Tab.
Output Creation tasks. This it to prevent large jobs from using all available engines and blocking small or medium jobs from running. Since Weaver engines cannot switch tasks, such behaviour can only be achieved through reserving engines for small and/or medium jobs. Engines may be reserved both for small, and for medium sized jobs. Engine reservations are not required for either though. l l l Small job (engines): Optionally enter the number of Weaver engines you wish to reserve for Small jobs.
l Small job (PPM): Enter the target speed for Small jobs, in Pages Per Minute (PPM). l Medium job (PPM): Enter the target speed for Medium jobs, in Pages Per Minute (PPM). l Large job (PPM): Enter the target speed for Large jobs, in Pages Per Minute (PPM) The entire licensed speed limit will always be distributed among jobs when running jobs simultaneously. After assigning a target speed, any remaining licensed speed will be distributed throughout any simultaneous jobs by a ration of the target speed.
Setting up Server Clustering requires two or more installations of PReS Connect on separate machines. The Master server is setup by installing the PReS Connect Server module during the Installation Wizard, while any Slave Servers are setup by installing the PReS Connect Server Extension module instead. Quick Howto 1. Install the Master server (PReS Connect Server module), making sure to select the MySQL module. 2. Grant access to the MySQL root user for the appropriate IP range on the Master server. 3.
Connect\MySQL\my.ini in a text editor and change the line bind-address= 127.0.0.1 to bind-address=0.0.0.0. Once the changes have been made and saved you need to restart the MySQL services. l Access must be granted to the root user on the IPs from which the Slave server will connect.> l Open a Command Prompt in the following folder: C:\Program Files\Objectif Lune\OL Connect\MySQL\bin Note Navigate to the folder, SHIFT+Right-click and select "Open a command prompt here" l Type in the following command to
Clustering Preferences and Setup When Server extensions are installed and connected to a Master, the following options and settings change in availability or behaviour: l The Clean-up Service requires special configuration on Clustering setups: l l Clean-up service should not run simultaneously on all machines (staggered cleanup). Doing so may cause jobs not to be processed since all servers are busy. Only the machine where the MySQL Server product is installed should attempt to clean-up database items.
l l l Administrator's password: Enter a password for the server security. The default password is secret. Confirm password: Re-enter the password for the server security. Default session length (min): Enter a session time (in minutes) that the authentication stays valid for the requested process. This can reduce the number of requests to the server since an authentication request is not necessary during the session.
Known Issues This page lists important information about issues that apply to PReS Connect 2020.1. Issues running Connect on Hyper-V 9.0 Some customers have reported difficulties running OL Connect on Hyper-V version 9.0. In some instances Connect cannot install and in others the Connect Server service sometime stops with a signature error. To resolve these issue we recommend downgrading to Hyper-V version 8.0 where these issues are not reported.
To workaround this issue, we recommend downloading and manually installing the latest Visual C++ Redistributable from https://support.microsoft.com/en-ca/help/2977003/the-latestsupported-visual-c-downloads then re-running the Connect 2019.2 installation. Issues associating PDF files with Connect Under certain circumstances, Connect Setups prior to 2019.2 would fail when attempting to add the "Enhance with Connect" association with PDF files. This would then cause the setup to appear to fail.
The OL Connect 2019.1 license update does not cater for existing AFP input licenses AFP Input is an add on option for OL Connect licenses. Unfortunately, the update to the 2019.1 version of the OL Connect license does not cater for existing AFP input licenses. If you have an existing AFP input license we ask that you contact your local Customer Care team (https://www.objectiflune.com/WebActivationManager/CareInfo.
Page break changes in 2019.1 Improved page breaking in Connect 2019.1 might impact upon some existing templates. It is recommended that you check page breaking in existing jobs, where page breaks at a specific location are a known criteria. Minor differences in AFP and IPDS output introduced in 2019.1 Connect 2019.1 now defaults to "Scale to Fit" for both IPDS and AFP output. Please note that this may have an impact when printing pre-existing Connect jobs (made in Connect versions predating 2019.
Issue after erroneous or incomplete update or re-installation If one or more products (the Connect Designer, Connect Server, Software Activation, Print Manager, or Server Configuration Tool) or engines exit within a second of starting, this may be caused by a recent erroneous or incomplete uninstall before a reinstall or upgrade to a newer version of OL Connect. (See Product or engine exits within a second of starting in Connect's Knowledge Base: http://help.objectiflune.
EXECUTE `bd`; DEALLOCATE PREPARE `bd`; set @a:=concat('optimize table ',@a); PREPARE `sql` FROM @a; EXECUTE `sql`; DEALLOCATE PREPARE `sql`; set @a=null,@b=null,@c=null; If using Microsoft SQL Server run the following command in a query window: sp_updatestats Windows 10 Search service impacting Connect The Windows 10 Search service runs as a background task, indexing files and folders.
Engine Preferences: Backward Compatibility Issues introduced in 2018.2 l Prior to version 2018.2 Connect allowed a mixture of internal and external engines. As of PReS Connect 2018.2 this is no longer allowed. When upgrading to PReS Connect 2018.2 from such installations, the pre-existing settings will not only no longer apply, but can cause scheduling preference conflicts for the Merge and Weaver engines.
conversion to 2018.1, charts that used the Rows are series setting will be displayed as if the Columns are series setting were used. Pie charts will thus only show data from the first record in the detail table. If the number of records in the detail table remains consistent, then the charts can be corrected by modifying the data mapping configuration (see Preparing a data table in the Online Help: https://help.objectiflune.com/en/PReSconnect-user-guide/2020.1.).
However this update could lead to increased output file sizes for some PCL, AFP and IPDS jobs. This is generally not a cause for concern, however there might be some associated increase in processing times, as well as some minor differences in the output. For example, table line widths and font spacings might differ slightly (particularly for SMALL CAPS text), which could lead to slightly different word-wrapping in some circumstances. Windows Server 2016 issue As of PReS Connect 2018.
Print Output: Booklet Impositioning changes introduced in 2018.1 When Booklet Impositioning is enabled, all pages within a document need to be changed to duplex prior to Impositioning . The method for duplexing jobs has been changed to now always combine existing pages into the front and backsides of sheets, rather than adding empty backsides to any simplex pages. The result is that now every document in the job becomes a booklet without any empty pages between the first page and the last page.
Installation paths with multi-byte characters When installing the Chinese (Traditional or Simplified) or Japanese versions of Connect, if the user specifies an alternative installation path containing multi-byte/wide-char characters it can break some of the links to the Connect-related shortcuts in the Start Menu and cause an error to appear at the end of the installer. The workaround for the moment is to use the default installation path. The problem will be addressed in a later release.
correctly. For this reason those users should activate Place all certificates in the following store and then select the Trusted Root Certification Authorities as the target certificate store. MySQL Compatibility After installing Connect 2020.1 a downgrade to a Connect version earlier than Connect 1.3 or to a MySQL version earlier than 5.6.25 is not seamlessly possible. This is because the database model used in Connect 1.3 and later (MySQL 5.6) is different to that used in earlier versions.
External resources in Connect There are certain limitations on how external resources can be used in Connect. For example if you want to link a file (e.g., CSS, image, JavaScript etc.) from a location on the network but you do not want to have a copy of the file saved with the template you need to do the following: 1. The resource must be located where it can be accessed by all Servers/Slaves run as users.
Capturing spool files after installing Workflow 8 If PReS Connect Workflow 8 is installed alongside PlanetPress Suite Workflow 7, the PlanetPress Suite 7 option to capture spool files from printer queues will no longer function. The solution is to use PReS Connect Workflow 8 to capture spool files from printer queues. Color Model in Style Sheets The color model of colors defined in a style sheet can sometimes change after editing the style sheet.
REST Calls for Remote Services The Server will accept REST calls for all remote services and will make commands wait indefinitely until the required engines become available. The Server will log when it is waiting for an engine and when it becomes available. Note that there is no way to cancel any commands other than stopping the Server.
VIPP Output Some templates set up with landscape orientation are being produced as portrait in VIPP. It can also sometimes be the case that text and images can be slightly displaced. These are known issues and will be addressed in a later release of Connect. Magic Number changes when installing Docker Installing Docker on a system where Connect has already been installed may impact Connect's licensing mechanism and require reactivation.
Uninstalling This topic provides some important information about uninstalling (removing) PReS Connect2020.1. To uninstall PReS Connect select the application from within the Add/Remove programs option under the Control Panel. This will start the PReS Connect Setup Wizard in uninstall mode. Note The PReS Connect Setup Wizard might take some seconds to appear. Important: Stop any active Anti-Virus software before uninstalling Connect.
4. PReS Connect Server Extensions on remote systems which connect to this machine as the Master Server. Uninstallation Wizard The uninstallation is done by running the PReS Connect Setup Wizard in uninstall mode. The Wizard consists of the following pages: 1. PReS Connect Setup: An information page, listing what will be uninstalled, and also warning about impacts upon running Applications and Services. 2. Data Management: A page that provides options for backing up or deleting Connect data.
Legal Notices and Acknowledgements Warning: PReS Connect is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this program, via any means, in part or in whole, may be prosecuted to the full extent of the law. The license agreements for the associated open source third party components can be found in the following installation folder: C:\Program Files\Objectif Lune\OL Connect\Legal Notices This application uses the following third party components: l l l
source can be obtained from here: https://wikis.oracle.com/display/GlassFish/Java+EE+7+Maven+Coordinates l Google Core Protocol Buffers library which is distributed under a BSD 3-clause License l Hamcrest Matchers Copyright © 2000-2006, www.hamcrest.org. All rights reserved. l HyperSQL, Copyright © 2001-2010, The HSQL Development Group. All rights reserved. l l l l l l l l l l IcoMoon. Connect uses unmodified icons from IcoMoon (https://icomoon.
can be found at the following location: http://repo1.maven.org/maven2/org/glassfish/jersey/jersey-bom l l l l l l l l l l l JNA Version 3.5.1 which is distributed under the terms of the GNU Lesser General Public License Version (LGPL) 2.1. The source code for this can be obtained from the following location: https://github.com/twall/jna/releases Logback which is distributed under the terms of the Eclipse Public License (EPL) Version 1.0.
l Spring Framework which is distributed under the terms of the Apache Software License Version 2.0. This product includes sub-components with separate copyright notices and license terms. l StAX Utilities Copyright © 2007, StAX Utilities Project. All rights reserved. l Stax2 API Copyright 2010-2018 FasterXML.com. l l l l l Tern which is distributed under the terms of the Eclipse Public License (EPL) Version 1.0. The source code for tern can be obtained from the following location: https://github.
l Apache Commons DBCP l Apache Commons Digester l Apache Commons Imaging l Apache Commons IO l Apache Commons JCS Core l Apache Commons Lang l Apache Commons Logging l Apache Commons Math l Apache Commons Pool l Apache Commons Text l Apache Commons Validator l Apache Derby l Apache Felix and dependencies l Apache Geronimo l Apache HttpClient Mime l Apache POI l Apache ServiceMix l Apache Xerces2 Java Parser l Apache XML Graphics l Apache XML Beans l Barcode4j l Go
l org.json.simple l Quartz Scheduler l Snakeyaml l SNMP4J l Spring Dynamic Modules l UCanAccess l Woodstox Eclipse Technology: This Software includes unmodified Eclipse redistributables, which are available at www.eclipse.org. The Eclipse redistributables are distributed under the terms of the Eclipse Public License - v 1.0 that can be found at https://www.eclipse.org/legal/epl-v10.html.
END USER LICENSE AGREEMENT AND LIMITED WARRANTY END USER LICENSE AGREEMENT AND LIMITED WARRANTY IMPORTANT – PLEASE READ CAREFULLY Thank you for choosing Objectif Lune’s software. This End User License Agreement and Limited Warranty (hereinafter collectively the "License Agreement") constitute a legal agreement between the End User, either as a physical person or as a legal entity ("you"), and Objectif Lune Inc.
END USER LICENSE AGREEMENT AND LIMITED WARRANTY THIS SECTION STATES THE ENTIRE LIABILITY OF OL REGARDING INFRINGEMENT BY THE SOFTWARE OR ANY OTHER PRODUCT OR SERVICE PROVIDED BY OL. PRE-TESTING OF THE SOFTWARE. - You acknowledge that the Software must be thoroughly tested by you with noncritical data before you rely on it and you hereby assume the entire risk of using the Software. WARNING - HIGH RISK ACTIVITIES.
END USER LICENSE AGREEMENT AND LIMITED WARRANTY If the Software was not provided to you through a leasing or a subscription agreement, you may transfer it to a third party on a permanent basis, after prior written authorization of OL. In case of permanent transfer, you shall not retain any copy of the Software and the transferee shall be bound by the terms of this License Agreement.
END USER LICENSE AGREEMENT AND LIMITED WARRANTY date. Acceptance of the modifications by selecting "I AGREE" and your subsequent use of the Software will be deemed your acceptance of these modifications. This License Agreement shall be binding upon the parties hereto and their respective successors and permitted assignees. If any or part of any provision of this License Agreement is, by final judgment, found void or unenforceable, the remainder shall remain valid and enforceable according to its terms.
END USER LICENSE AGREEMENT AND LIMITED WARRANTY modify, adapt, translate, reverse engineer, decompile, disassemble or otherwise attempt to discover the source code of the Software. Except as stated above, this Agreement does not grant you any intellectual property rights in the Software. FONT LICENSE.
END USER LICENSE AGREEMENT AND LIMITED WARRANTY NOTICE OF RESTRICTED RIGHTS. - "Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement.
