advertisement
Installation and Activation
Guide
Version: 2020.1
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. 19942021 . 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.
Objectif Lune Inc.
disclaims responsibility for any errors and omissions in this documentation and accepts no responsibility for damages arising from such inconsistencies or their further consequences of any kind.
Objectif Lune Inc.
reserves the right to alter the information contained in this documentation without notice.
Table of Contents
System and Hardware 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
Terminal Server/Service Support
32-bit or 64-bit Operating Systems?
Windows Search Indexing Service
Commandline switches and .ini entries
Language and Encoding Considerations
Network and internet connections
Operating system (64-bit only)
Recommended hardware requirements
Page 6
Requirements for individual Connect modules
Installing PrintShop Mail Connect on Machines without Internet Access
Updating from Connect versions predating 2019.1
Starting the PrintShop Mail Connect installer
Selecting the required components
Configuring Supplied Database Connection
Running Connect installer in Silent Mode
Updating from Connect versions predating 2019.1
Required and optional properties
Required and optional properties
Getting the exit code of a silent installation
Obtaining the PrintShop Mail Connect Magic Number
Activating PrintShop Mail Connect
Migrating to a new workstation
Before installing the software
Downloading and installing the software
Backing up files from the current workstation
Upgrading from previous Connect versions
Page 7
Parallel Processing preferences
Parallel Processing properties
Issues running Connect on Hyper-V 9.0
The Update Client OL for Connect 2019.1 does not cater for standalone Connect Print
Legal Notices and Acknowledgements
Page 8
System and Hardware
Considerations
There are a variety of considerations to be aware of. These are documented in the following pages: l
"System requirements" on page 24
l
"Database Considerations" on page 11
l
"Environment considerations" on page 16
l
l
"Language and Encoding Considerations" on page 19
l
"Antivirus Exclusions" on the facing page
l
"Performance Considerations" on page 22
Page 9
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 PrintShop Mail and their internal requirements and needs. This page describes the mode of operation and the files and folders used by PrintShop Mail 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.
IT managers and IT professionals then may decide the anti-virus strategy to follow for their internal requirements and needs depending on the statements outlined herein.
Directories and folders
All Connect applications are installed under an arbitrarily selectable main folder. If the default installation folder options were used, this installation folder would be %PROGRAMFILES%\Objectif
Lune\OL Connect .
The installation folder will hold all the executable files and other files and folders required for the operation of the whole product suite. All these files and folders remain static after installation. It depends upon the company virus protection strategy, if such files and folders will be monitored or not.
We do, however, recommend that the following file or folders be excluded from antivirus protection.
Working folders
Working folders for Connect are created and used on a per-user-basis under the respective user's profile folder, accessible on Windows with the standardized system variable
%USERPROFILE% in the subfolder "Connect". Working folders are: l
%USERPROFILE%\Connect\filestore : This folder will hold non-intermediate files for the operation of Connect. Files in this folder will be used frequently, but not with a high frequency. Supervising this folder with a virus protection system should not have too much of an impact on the speed of the whole Connect suite.
l
%USERPROFILE%\Connect\logs : As the name implies, log files are created and updated here. These log files are plain text files. Virus protection may have an impact on the speed of the whole Connect suite.
Page 10
l
%USERPROFILE%\Connect\temp : Storage folder for temporary data, usually intermittent files in multiple folders. Virus protection on this folder and its subfolders may have a serious impact on the performance of Connect.
l
%USERPROFILE%\Connect\workspace : Usually containing settings and helper files and folders. Supervising this folder with a virus protection system should not have too much of an impact on the speed of the whole Connect suite.
Database 1
Depending on the components installed, a database instance is created in a folder called
" connect.database
" under the Windows system temp folder. This folder is accessible via the standardized system variable
%TMP%
. Usually, folders holding such temporary files and folders should be excluded from a virus protection, because this influences the overall performance of 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 ".
As this database will be in extremely strong usage, virus protection on this folder and its subfolders may have a serious impact on the performance of Connect.
Database Considerations
This page describes the different considerations and pre-requisites for the database back-end used by PrintShop Mail Connect, whether using the MySQL instance provided by the installer, or pre-existing ( external ) instance.
Using the MySQL Instance from the Installer
The MySQL Instance provided in the
is already pre-configured with options to provide the most stable back-end setup.
Page 11
These are the specific options that have been changed in our version of " my.ini
": l max_connections = 200 : PrintShop Mail Connect uses a lot of database connections.
This number ensures that even in high volume environments, enough connections will be available.
l max_allowed_packet = 500M : In some implementations, especially when using Capture
OnTheGo, large packet sizes are required to allow transferring binary files. This substantial packet size maximum setting ensures that the data received by PrintShop Mail
Connect will be able to be stored within the database.
l character-set-server = utf8 , collation-server = utf8_unicode_ci , default-characterset=utf8 : These indicate database support for UTF-8/Unicode.
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
The minimum supported MySQL version is MySQL 5.6.
l
The MySQL account must have access to all permissions using the GRANT Command, including creating databases.
l
The database configuration must include the options detailed in the "Using the MySQL
Instance from the Installer" on the previous page topic above.
l
The database configuration must allow the use of mixed case table names.
This is particularly an issue on Linux MySQL installations.
l
The SQL instance must be open to access from other computers. This means the bindaddress option should not be set to 127.0.0.1 or localhost.
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. will take no responsibility for setting up database connections to any
Page 12
but the supplied MySQL database.
Options available within the installer: l
The Configuration page for the local MySQL is displayed.
l
MySQL settings are pre-filled with default values if no existing MySQL database configuration is found.
l
MySQL settings are pre-filled with existing database configuration settings, if they point to a MySQL database type.
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. will take no responsibility for setting up database connections to any but the supplied MySQL database.
Note
Since PrintShop Mail Connect version 1.6 the minimum required version of the MS SQL
Server is SQL Server 2012 .
Page 13
l
When MS SQL is selected, the default values for root user are sa and 1433 for the port.
l
If database settings from a previous OL Connect installation are found, the pre-exising settings will be displayed for the matching database type. For MS SQL settings, this will only work if they were created with Server Config Tool 1.5.0 or later, or the Installer for
OL Connect 1.6.0 or later.
If the database type is changed in the Installer configuration page, the default values for this database type will be displayed.
If the pre-existing database settings are set to Hsqldb, the default database type selection will be MySQL.
l
Selected database settings are stored in the preferences, and can be found in this file:
C:\ProgramData\Objectif Lune\OL
Connect\.settings\ConnectHostScope\com.objectiflune.repository.eclipselink.generic.pref
s
Updating With No Local MySQL Product
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.
l
On Update from 1.4.2 or earlier, the Database Configuration Page will always default to
MySQL connection settings, and if the installation was manually tweaked to connect to
MS SQL Server, the user has to switch to "Microsoft SQL Server" type and enter connection details again.
When modifying Connect
l
If local MySQL is removed from an installation, the Database Configuration page will offer additionally the Microsoft SQL Server database type with respective default values.
l
If local MySQL is added to an installation, the usual MySQL Configuration page with default values will be displayed.
If the user has installed the Installer Supplied MySQL and then switches to an external
Microsoft SQL by using the Server Configuration Tool, the supplied MySQL cannot be switched off. By design the installer adds a service dependency between Connect Server and the supplied MySQL service.
Page 14
Note
The Microsoft SQL selection capability will be available only with 1.6 version and upwards.
To remove this dependency the user needs to do the following
1. Have a foreign Microsoft SQL running, ready for use with Connect Server.
2. Use the Server Configuration Tool Database Connection preferences to switch the database to Microsoft SQL.
3. Re-start the Connect Server Service, so that the modifications become active.
4. Counter check that everything is working properly with Microsoft SQL.
5. Open a command-line prompt with full administration rights.
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 the dependency has been removed, it is possible to stop the supplied MySQL service (OLConnect_MySQL).
Warning
If a Connect 1.5
user wants to use Microsoft SQL instead of MySQL for the Connect Server, there are several points to be taken care of. These are: l
If a MySQL instance exists which could be used intermediately, then this should be selected during the setup. This ensures, that nothing gets installed. Otherwise the supplied MySQL needs to be installed and the switch to Microsoft SQL needs to be done as outlined above.
l
It is not possible to uninstall the supplied MySQL hereafter, when running the
Connect 1.5 Installer in Modify mode.
Page 15
Important
If a Server Product and a MySQL Product were selected to be installed on Connect 1.5.0, and then the Server Configuration Tool is used to switch the database used by the Server to an external Microsoft SQL, then the Update to 1.6 requires an extra step. The procedure is as follows:
1. Run the Update to Connect 1.6
. This will assume the local MySQL database needs to be updated and configured, so the user has to enter a root password on the MySQL
Configuration Page (can be any password matching Connect security rules).
2. After the update, the Connect 1.6 Setup needs to be run once more to modify Connect.
3. On the Product Selection page, now the MySQL product can be unselected.
4. When stepping forward in the Wizard, the Database Configuration page will be displayed which allows to configure the Microsoft SQL Server with appropriate settings.
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.
Environment considerations
Terminal Server/Service Support
PrintShop Mail Connect does not support Terminal Server (or Terminal Service) environment as possible under Windows 2000, 2003 and 2008. This is to say, if Terminal Service is installed on the server where PrintShop Mail Connect is located, unexpected behaviours may occur and will not be supported by Objectif Lune Inc.. Furthermore, using PrintShop Mail
Connect in a Terminal Service environment is an infringement of our End-User License
Agreement.
Page 16
Virtual Machine Support
PrintShop Mail Connect supports the following virtual environments: l
VMWare Environments. This includes VMWare Player, VMWare Workstation as well as
VMWare ESX Server.
l
VMWare VMotion. This means the virtual machine hosting PrintShop Mail Connect can be automatically moved from one ESX server to another in a clustered installation.
Note that if all servers in a VMotion cluster are not strictly identical, you will have to provide the Objectif Lune Activations team with all possible magic numbers so they can generate a license that works on all servers. Obtaining the magic numbers is simply a question of manually moving the VM on which Connect is installed to each server, and recording the magic number for each of them.
l
Microsoft Hyper-V/Azure infrastructure environments.
PrintShop Mail 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.
Remote Desktop Support
Tests have demonstrated that PrintShop Mail Connect can be used through Remote Desktop. It is however possible that certain combination of OS could cause issues. If problems are encountered, please contact OL Support and we will investigate.
PrintShop Mail Connect 1.3 and later have been certified under Remote Desktop.
Page 17
32-bit or 64-bit Operating Systems?
PrintShop Mail Connect is a 64-bit software and can only be installed on 64-bit operating systems.
Antivirus Considerations
l
Antivirus software may slow down processing or cause issues if they are scanning in
temporary folders or those used by PrintShop Mail Connect. Please see "Antivirus
Exclusions" on page 10 for more information.
l
Antivirus software might interfere with installation scripts, notably a VBS script to install fonts. McAfee, in particular, should be disabled temporarily during installation in order for
MICR fonts to install and the installation to complete successfully.
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
Change the Startup Type to Disable , and click Stop to stop the service.
l
Try the installation again.
l
Once complete, you may re-enable the service and start it.
Commandline switches and .ini entries
PrintShop Mail Connect is intended to work stably and reliably, based on Java and the Eclipse framework. To ensure this reliability and robustness, many Java and Eclipse parameters have been tested and tuned, which is reflected in the respective .ini entries and the used command line switches. A collection of valuable settings has been elaborated and found its entry in
PrintShop Mail Connect “good switches list” (called the “whitelist”).
The protection of the end user’s system is one of our main goals and therefore we have implemented a very strict verification mechanism, which ensures, that only these whitelisted ini
Page 18
entries and command-line switches are accepted, when one of Connect components is started and run. Please be therefore advised, that any non-whitelisted ini entry or command-line switch will be accepted and will - if tried to be used - lead to the respective application’s “sudden death”. If you should encounter such a behaviour then please double-check your Connect log file/s for respective entries.
Language and Encoding Considerations
Please note the following considerations: l
Language : l
PrintShop Mail 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 PrintShop Mail Connect help system (this document) is currently only available in English.
l
Encoding : l
Issues can sometimes be encountered in menus and templates when running
PrintShop Mail Connect on a non-English operating system. These are due to encoding issues and will be addressed in a later release.
Page 19
Network Considerations
The following should be taken into consideration in regards to network settings and communications l
If a local proxy is configured (in the Internet Explorer Options dialog), the option
Bypass proxy server for local addresses must be checked, or some features depending on local communication will not work.
Firewall/Port considerations
The following describes all of the ports that can be used by an OL Connect solution. IT staff may decide the firewall strategy to follow for their internal requirements and needs depending on the statements outlined herein.
Messenger
Listens on port
#
Destination port #
5863/5864
Type Comment
5863/5864 TCP+UDP
Used for inter-module communication
Connect
Server
9340 TCP Used for Connect REST API
Connect
Server
9350 TCP
Dedicated internal connection for inter-process communication (i.e. between engines)
HTTP
Server
HTTPS
Server
NodeJS
Server
8080
443
9090
NodeJS
HTTPS
Server
8443
SMTP Input plugin
25 , or 587 when encryption is enabled
TCP
TCP
TCP
TCP
TCP
Page 20
Listens on port
#
Destination port #
Email Input plugin
Secure
Email Input plugin
Send Email plugin
Secure
Output plugin
LPR
LPD
Telnet
FTP
Input/Output
515
9100
MySQL
Microsoft
SQL Server
3306
1433
HyperSQL 9001
110
993
25
587
515
21
Type
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP
TCP+UDP
TCP+UDP
TCP
Comment
Default POP3 port
Default SMTP port 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. A few examples:
The Create Email Content plugin will use the port defined in the Mail host setting in
Workflow's OL Connect Preferences.
The ports used by the HTTP Client Input task, Legacy SOAP Client and SOAP Client plugin depend on the configured URL.
Page 21
Performance Considerations
This page is a guide to getting the most performance out of PrintShop Mail Connect as well as a rough guideline to indicate when it's best to upgrade.
Performance analysis details
In PrintShop Mail Connect, after each print job, a message dialog displays a print job summary
(see Print Job Summary dialog). This summary may help you determine how best to maximize the performance of PrintShop Mail Connect.
With no Performance Pack, PrintShop Mail Connect's Weaver engine can generate output at
250 PPM (pages, or emails per minute) for Subscription licence, or 1,000 PPM for Perpetual licence. Additional Performance Packs increase this quota.
If your print jobs are not running at the licensed speed, there may be several ways to improve the performance, as described below. Note however that it is not guaranteed that the licensed speed can be achieved with any job. Creating output for templates with very complex scripts or complex graphics resources will take a certain amount of time, even on high-end hardware.
If your print jobs are running at the licensed speed, then improving performance will require purchasing either a Performance Pack or upgrading to PlanetPress or PReS Connect (see
Performance Packs ). For advice please contact your local sales office (see Objectif Lune's
Contact page ).
Engine configuration
A Merge engine merges the template and the data to create Email 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.
Configuring these engines to match the hardware configuration is probably the fastest and most
effective way to improve Connect's performance. See "Engines preferences" on page 57 for
how to do this.
Page 22
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.
Network and internet connections
Use a fast network and internet connection or avoid loading external or internet resources.
Using images, JavaScript or CSS resources located on a slow network or on a slow internet connection will obviously lead to a loss of speed. While we do our best for caching, a document with 5,000 records which queries a page that takes 1 second to return a different image each time will, naturally, slow output generation down by up to 83 minutes.
Hardware configuration
When processing speed is important, the following is suggested before looking into
Performance Packs to enhance performance (and after addressing the other issues mentioned in this topic).
l
Antivirus exclusions . Sometimes, virus scanners, other security software or indexing services can interfere. It can help to disable those kinds of tools for the areas where
Connect stores intermediate files. You could exclude the entire
C:\Users\<connectuser>\Connect
folder. See also: "Antivirus Exclusions" on page 10.
l
Use a high-performance, low-latency hard drive . Connect benefits from fast I/O.
Preferably use a Solid State Drive (SSD) or similar for storage.
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
Designer needs 1GB each, and that each engine needs 1GB as well, you can roughly estimate how much memory is needed.
l
Consider using a physical machine instead of a virtual machine. When running on a
Virtual Machine, the machine may report that it has sufficient hardware (cores) available, but in a virtual environment you need to make sure that this hardware is not being shared with lots of other virtual machines.
l
Consider using hardware with more physical cores . PrintShop Mail Connect doesn't limit the number of Merge engines that is used for a Print job, so if the number of physical
Page 23
cores is low, it makes sense to see if that can be increased. When running on a virtual machine, this is usually easy. When running on a physical machine, it means that you may have to switch hardware.
l
For both virtual and non-virtual environments, make sure the machine is not busy with all kinds of other processes.
System requirements
These are the system requirements for PrintShop Mail Connect 2020.1
Operating system (64-bit only)
l
Microsoft Windows 2008 R2 Server l
Microsoft Windows 2012/2012 R2 Server l
Microsoft Windows 2016 Server l
Microsoft Windows 2019 Server l
Windows 7 l
Microsoft Windows 8.1
l
Microsoft Windows 10 (Pro and Enterprise versions only)
Note
Windows Vista, Windows 8.0, Windows 2003 Server and earlier versions of Windows are 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.
Page 24
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. It can be used when configuring a trial or a development system, however.
l
File system: NTFS (FAT32 is not supported) l
CPU: multi-core l
RAM: 6GB l
Disk Space: 4GB for the software modules, 5GB for work files*
* 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.
Recommended hardware requirements
Due to its versatility, OL Connect is used for a wide variety of applications. Consequently, it is difficult to determine which hardware configuration will produce the best results for any given implementation. The following specs should therefore be viewed as a general guideline that is most likely to produce expected results for most implementations. You should, however, keep in mind that it may not represent the optimal setup for your particular application.
For more information and tips about performance considerations, see "Performance
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.
Page 25
Requirements for individual Connect modules
OL Connect Products comprises multiple modules that can be operated separately on multiple
PCs. Each module has its own set of requirements that may differ from the other modules.
While the hardware requirements described above are relatively generic when installing all
Connect modules on a single server, they should not be interpreted literally for each individual module.
When installing on multiple PCs, keep the following rules of thumb in mind: l
The Connect Workflow module requires less RAM but fast hard drive access. It also benefits from fast multi-core CPUs, in order to run processes in parallel.
l
The Connect Server module requires more RAM and benefits from fast multi-core CPUs.
Disk access speed is less of a concern.
l
The Connect Designer module requires more RAM and fast disk access to provide a responsive user-experience.
l
The back-end database (MySQL by default) benefits from more RAM, speedy disk access and fast networking as it will be solicited by all modules simultaneously.
Editions of Connect Products
There are three editions of OL Connect: PrintShop Mail Connect, PlanetPress Connect and
PReS Connect.
While all three editions share common modules, they are generally not used for the same purposes. Technically speaking, their hardware requirements would therefore be the same but in practice, PReS Connect is likely to require higher-end hardware while PrintShop Mail
Connect will generally require less power to achieve expected results.
Note
As with any JAVA application, the more RAM available, the faster PrintShop Mail Connect will execute.
Page 26
Installation and Activation
This topic provides detailed information about the installation and activation of PrintShop Mail
Connect 2020.1.
Note
A PDF version of this guide is available for use in offline installations.
Click here to download it .
Where to obtain the installer
The installer for PrintShop Mail Connect 2020.1 can be obtained on DVD or downloaded as follows: l
If you are a Customer , the installer can be downloaded from the Objectif Lune Web
Activation Manager (https://www.objectiflune.com/webactivationmanager/) or through the
OL Update Client if it is activated.
l
If you are a Reseller , the installer can be downloaded from the Objectif Lune Partner
Portal site (https://extranet.objectiflune.com/) or through the OL Update Client if it is activated.
Installation - important information
For important information about the Installation, including requirements and best practices, please see the following topics: l
"Installation prerequisites" on the facing page
l
"User accounts and security" on the facing page
l
"Migrating to a new workstation" on page 47
l
"Upgrading from previous Connect versions" on page 53
Page 27
Installation - "How to" guides
For information on how to conduct the installation itself, choose from the following topics: l
"Installation Wizard" on page 31
l
"Running Connect installer in Silent Mode" on page 36
l
"Installing PrintShop Mail Connect on Machines without Internet Access" on the next page
Activation
For information on licensing, please see "Activating a License" on page 44.
Installation prerequisites
l
Make sure your system meets the
l
PrintShop Mail Connect Version 2020.1 can be installed under a regular user account
with Administrator privileges., see "User accounts and security" below.
l
PrintShop Mail Connect must be installed on an NTFS file system.
l
PrintShop Mail Connect requires Microsoft .NET Framework 4.5
already be installed on the target system.
l
Connect 2019.1 requires updated Connect License and/or Update Client.
See "Upgrading from previous Connect versions" on page 53 for details.
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.
Page 28
The following links contain the details as to when and where Windows Administrator rights are required: l
Connect Installation:
l
Activating Connect:
Permissions for PrintShop Mail Connect Designer
PrintShop Mail Connect Designer does not require any special permissions to run besides that of a regular program. It does not require administrative rights and only needs permission to read/write in any folder where templates are located.
If generating Print output, PrintShop Mail Connect Designer requires permission on the printer or printer queue to send files.
Installing PrintShop Mail Connect on
Machines without Internet Access
Installing PrintShop Mail Connect2020.1 in offline mode requires some extra steps. These are listed below.
Updating Connect
Updating to Connect 2019.1 from earlier Connect version
In order to update PrintShop Mail Connect to 2019.1 it is first necessary to update the Connect
License.
For details on how to upgrade the Connect License offline see the Upgrading Connect on machines with no internet access section in the Update Client 1.2.40 Upgrade Guide (see http://help.objectiflune.com/en/archive/Update_Client_1.2.40-Upgrade_Guide.pdf).
Initial Connect Installation
GoDaddy Root Certificate Authority needs to be installed
In order to install PrintShop Mail Connect it is necessary for the GoDaddy Root Certificate
Authority to be installed (G2 Certificate) on the host machine and for this to be verified online.
Page 29
When a machine hosting the installation does not have access to the Internet, the installation will fail because the verification cannot be performed. To solve this problem one must first ensure that all Windows updates have been installed on the host machine. Once the Windows updates are confirmed as being up to date, then complete the following steps:
1. Go to https://certs.godaddy.com/repository and download the following two certificates to copy to the offline machine: l
GoDaddy Class 2 Certification Authority Root Certificate - G2 - the file is gdrootg2.crt
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 PrintShop Mail 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. The integrity of these files is checked at various times by different, context related, methods. One of these checks, done during the installation process, uses the Windows certificate validation check. .
The Windows certificate validation process not only checks the integrity of a file against its signature, but also usually checks if the certificate itself is still valid. That check is done against the current Certificate Revocation List (CRL), which needs to be retrieved from the internet.
However, if the machine in question does not have internet access, the retrieval of the CRL must fail, which will lead to subsequent validation issues.
To circumvent such issues it is highly recommended to switch off the CRL retrieval prior to installing Connect on machines without internet access. There is no security risk associated with this, as the CRLs would never be retrievable without internet access, anyway. Advantage of the switch will not only be found during the installation and operation of Connect, but also in some speed improvements for any application which use signed binaries.
To switch off CRL retrieval on the computer, complete the following steps:
Page 30
1. Open the “Internet Options” via the Control Panel
2. Select the “Advanced” tab and scroll down to “Security” node.
3. Uncheck the entry “Check for publisher’s certificate revocation” under that node.
4. Click the OK button to close the dialog.
5. Re-start the computer.
Installation Wizard
Updating from Connect versions predating 2019.1
In order to update PrintShop Mail 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 54
Starting the
PrintShop Mail Connect
installer
The PrintShop Mail Connect installer may be supplied as an ISO image or on a DVD.
l
If an ISO image, you can choose between the following, depending upon your Operating
System and the choices available:
1. Burn the ISO image onto a DVD
2. Un-zip the contents to a folder (keeping the internal folder structure intact)
3. Mount the ISO image from within Windows Explorer l
If on a DVD, either insert the DVD and initiate the installation from there or copy the contents to a folder on the target computer (keeping the folder structure intact)
Navigate to the PrintShop Mail_Connect_Setup_x64.exe and double-click on it. After a short pause the Setup Wizard will appear as a guide through the installation steps.
Note that PrintShop Mail Connect requires prior installation of Microsoft .NET Framework 4.5.
For a full list of other prerequisites, see "Installation prerequisites" on page 28.
Running the Installation with extra logging
The installer can be run with enhanced logging options, if needed.
To do so, run the PrintShop Mail_Connect_Setup_x64.exe from the command line with one of
Page 31
the following command line options: l
PrintShop Mail _Connect_Setup_x64.exe -verbose
This adds extra debugging style logging to the installation process.
l
PrintShop Mail _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 PrintShop Mail Connect can be selected for installation. Currently, the following are available: l
PrintShop Mail Connect Designer : The Designer module (see The Designer) can be installed standalone (with no other installed modules) on as many machines as you like. It does not require a license to run as a standalone designer tool . This allows for any number of people to use the Designer for creating jobs, but without production capabilities such as automation and commingling.
l
MySQL : A supplied MySQL database used by PrintShop Mail Connect.
The database is used for referencing temporary Connect files and for sorting temporarily extracted data, and similar.
A pre-existing MySQL or Microsoft SQL server (referred to as an external database, in this documentation) could be used instead, for the same purposes.
The external database could reside on the same computer or on a separate server.
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
Page 32
any but the supplied MySQL database.
See "Database Considerations" on page 11 for more information about setting up
external databases.
l
Installation Path : This is the location where modules are to be installed.
Note
To cater for MySQL requirements, the installation path cannot contain any non
ASCII characters (such as Asian language Unicode characters). Nor can it contain characters that Windows disallows in filenames (such as '?', ''>' or trailing spaces).
If an invalid character is entered, the Installation Path entry box will turn red and a 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
Disk space required : Displays the amount of space required on the disk by the selected components.
l
Disk space available on drive : Displays the amount of space available for installation on the drive currently in the Installation Path.
l
Recalculate disk space : Click to re-check available disk space. This is useful if space has been made available for the installation while the installer was open.
l
Source repository location : Displays the path where the installation files are located.
This can be a local drive, installation media, or a network path.
End User License Agreement
The next page displays the End User License Agreement , which needs to be read and accepted before clicking Next .
Page 33
Configuring Supplied Database Connection
The Default Database Configuration page appears if the supplied MySQL module was selected for installation in the Product Selection screen. It defines the administrative password for the MySQL server as well as which port it uses for communication.
The installer will automatically configure the Connect Server to use the supplied password and port.
l
MySQL user 'root' Password : Enter the password for the 'root', or administration account, for the MySQL server. The password must be at least 8 characters long and contain at least one of each of the following: l a lower case character (a, b, c ... ) l an upper case character (A, B, C ...) 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
Confirm MySQL user 'root' Password : Re-enter to confirm the password. Both passwords must match for installation to continue.
l
TCP/IP Port Number : The port on which MySQL will expect, and respond to, requests. A check is run to confirm whether the specified TCP\IP Port Number is available on the local machine. If it is already being used by another service (generally, an existing
MySQL installation), the number is highlighted in red and a warning message is displayed at the top of the dialog.
Page 34
Note
The MySQL database controlled by the OLConnect_MySQL service communicates through port 3306 by default.
Click Next to display the Selection Confirmation page.
Selection Confirmation
This page confirms the installation selections made.
Click Next to start the installation itself. This process can take several minutes.
Completing the installation
This screen describes a summary of the components that have been installed.
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 PrintShop Mail 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.
l
Show Log...
: If an issue was encountered during the installation, click this button to obtain details. This information can then be provided to Objectif Lune for troubleshooting.
l
When ready, click the Finish button to close the installation wizard, and initialize the
Product Update Manager, if it was selected.
The Product Update Manager
If the Configure Update Check option has been selected, a message will be displayed after clicking “ Finish ” in the setup. The message details the information that needs to be sent back to
Objectif Lune Inc. in order to determine when/if the software needs updating.
Click “Yes” to install or open the Product Update Manager where the frequency with which the updates can be checked and a proxy server (if required) can be specified.
Page 35
Note
If the Product Update Manager was already installed by another Objectif Lune Inc.
application, it will be updated to the latest version and will retain the settings previously specified.
Select the desired options and then click OK to query the server and obtain a list of any updates that are available for your software.
l
Note that the Product Update Manager can also be called from the “ Objectif Lune
Update Client ” option in the Start menu.
l
It can be uninstalled via Control Panel | Programs | Programs and Features.
Product Activation
After installation, it is necessary to activate the software. See
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 PrintShop Mail 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 54
Required and optional properties
PrintShop Mail Connect can be installed in a so called "silent mode" to allow an automated setup during a company wide roll-out or comparable situations. The trigger for the Connect
Installer to run in silent mode is a text file with the fixed name install.properties
, which is
Page 36
located either in the same folder as the PrintShop Mail_Connect_Setup_x86_64.exe or in the unpacked folder of the installer.exe
.
Note
Only the installation can be run silently.
Silent Mode does not apply to uninstalling, modifying, or updating Connect. Any previous version of Connect must be uninstalled
before using the Silent Installer (see: "Uninstalling" on page 75).
The required properties file has the following attributes: l
Comment Lines, starting with # (e.g. # The options to configure an external database) l
Key = Value pairs (e.g. install.product.0 = Connect Designer)
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.verbose = true
# Product selection install.product.0 = Connect Designer install.product.1 = Connect Server
# Server settings server.runas.username = Localadmin
Page 37
server.runas.password = admin
# Database configuration database.type = mysql database.host = 192.168.116.10
database.port = 3308 database.username = root database.password = admin database.schema = my_ol
Verbose logging (optional)
By default, the Silent Installer will log the same way as the GUI installer. That means logging of error and warnings, and certain information during database configuration. A more verbose logging can be switched on by using logging.verbose = true .
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).
PrintShop Mail defaults install.product.0 = Connect Designer install.product.1 = Connect Print Manager install.product.2 = MySQL
Note
The values of install.product
properties must contain the exact product names.
Server configuration (required if Server is selected for install)
For Server, the following properties need to be provided: server.runas.username = <username> server.runas.password = <password>
Page 38
Server Extension configuration (required if Server Extension is selected for install)
For Server Extension, the following properties need to be provided: server.runas.username = <username> server.runas.password = <password> server.master.host = <IP or name> server.master.port = <port> server.master.authenticate = true or false server.master.username = <username for the Connect Server> server.master.password = <password>
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 = <password> (required and must meet the rules) database.port = <port> (3306 is the default port value) database.unlocked = true or false (the default value is false, optional)
Note
The unlocked option should only be used when the database requires an external access.
If the Silent Installer runs with the default product selection, MySQL is included, and hence the database.unlocked = true property may be optionally set if MySQL on this machine is intended to serve as the central database also for remote machines.
If the Silent Installer runs with the explicit installation of a stand-alone (install.product.0 =
Connect Server), the database.unlocked
property is irrelevant.
Page 39
Note
The port will be defined automatically for the MySQL installation. All connect products selected in the Silent Installer will automatically be configured to use the MySQL running under the port defined by the database.port
property, regardless of the default port 3306 or any other user defined port.
A different port is required if 3306 is already taken on that machine by another application.
Case 2: The Connect Server 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 = <host> (default value is localhost, otherwise required) database.port = <port> (default value is 3306, otherwise required) database.username = <username> (default value is root, otherwise required) database.password = <password> (required) database.schema = <schema name> (default value is objectiflune, optional)
2b: Configuring an external Microsoft SQL Server database
Note
Since PrintShop Mail Connect version 1.6 the minimum required version of the MS SQL
Server is SQL Server 2012 .
To configure an external Microsoft SQL Server database, the following properties should be defined:
Page 40
database.type = Microsoft SQL Server (required) database.host = <host> (default value is localhost, otherwise required) database.port = <port> (default value is 1433, otherwise required) database.username = <username> (default value is sa, otherwise required) database.password = <password> (required) database.schema = <schema name> (default value is objectiflune, optional)
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. If the property exists, and its value starts with http://, the installer will attempt to install from that location. It will fail if no repository can be found at this location.
3. If none of the conditions mentioned in the previous steps are met, the installer will look next for a local "repository" folder (located in the same folder as the running Installer
(Setup) executable file). If a repository is found, the installer will attempt to install from that repository.
4. As a last resort, the installer will attempt to install from the default Connect Update Site
URL.
Examples product.repository = http://192.168.79.73/Connect/Version_
01/repository product.repository = C:\\iso\\2.0.0.39695_unpacked\\repository
Locale definition
It is possible to define the Locale which affects the installation language and installed locale for
Connect products by using the following properties in the install.properties
file: user.language
user.country
Page 41
Locales supported by Connect
The Connect Setup supports a dedicated list of Locales, which is saved in the preinstall.ini file.
Each entry consists of a language tag and a country tag, formatted by the pattern:
<language>-<country>
The current list of supported Locales is found below, but it may be enhanced in future releases: 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.properties
file, the combination must match exactly one of the supported locales, otherwise the Installer will exit with an error.
For example, user.language = fr and user.country = CA will cause an error since fr-CA is not in the list of supported Locales.
Locale selection by defining only user.language
If only user.language
is defined in the install.properties
file, the Installer will attempt to find a
Locale in the list which starts with the given language code. The first match is selected for installation. If no match is found, the Installer will exit with an error.
For example: user.language = zh, will result in an installation with the Locale zh-CN
Page 42
user.language = no, will result in an error
Default Locale selection
If neither user.language nor user.country is defined in the install.properties file, the Installer will select a default Locale:
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 en-
US).
Getting the exit code of a silent installation
If getting the exit code of a silent installation is desirable, use the following procedure.
1. Create a new local folder on the machine (or VM) on which Connect shall be installed and copy/extract the contents of the Connect ISO into this folder.
2. Open a command prompt with Administrator privileges and use the "cd" command to access this local folder.
3. Run this command to unpack the contents of the Connect Setup executable (as a sample, we use the PReS Connect brand):
PReS_Connect_Setup_x86_64.exe -nr -gm2 -InstallPath=".\\"
4. In the local folder, the repository subfolder should now be located next to the preinstall.exe, installer.exe and other Installer files.
5. Create the install.properties file for silent installation in the local folder.
6. With a batch file calling preinstall.exe and then querying the %errorlevel%, silent installation can be started and the exit code can be evaluated. See the sample batch file below.
Exit codes
0 = Success
1 = General Error in preinstall (e.g. not supported settings for user.language / user.country, for reason see preinstall_err.log)
2 = Unknown Error in preinstall
Page 43
10 = General Error in Installer application (for reason see OL_Install_<timestamp>.log)
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_<timestamp>.log" goto:eof
:err_unknown echo "Unknown preinstall error - see preinstall_err.log" goto:eof
:err_preinstall echo "Preinstall error - see preinstall_err.log" goto:eof
Activating a License
PrintShop Mail Connect comes with a30 day trial license period during which time it is not necessary to have a commercial license to run the application. This allows time for reviewing the applications and for organizing a commercial license. If a modification to the trail license is required, such as to allow an extension to the trial period, or for extra functionality, then a new activation code will need to be requested.
Obtaining the
PrintShop Mail Connect
Magic Number
To obtain an activation file the OL™ Magic Number must first be retrieved. The Magic Number is a machine-specific code that is generated based on the computer's hardware and software using a top-secret Objectif Lune family recipe. Each physical computer or virtual computer has a different Magic Number, and each requires a separate license file to be functional.
Page 44
To get the PrintShop Mail Connect Magic Number open the Connect Software Activation application.
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 PrintShop Mail Connect Software Activation application consists of the following: l
License Information subsection: l
Magic Number : Displays the PrintShop Mail Connect Magic Number.
l
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.
l
Licensed Products subsection: l
Name : Displays the name of the application or module relevant to this activation.
The Information button provides detailed information about the application or module license.
l
Serial Number : Displays the trial license serial number or the activation serial number if the product has been activated in the past.
l
Expiration Date : Displays the date when the activation will expire, or the current date if the product is not activated.
l
End-User License Agreement - Appears only when loading a license file : l
License : This box displays the EULA. Please note that this agreement is legally binding.
l
I agree : Select to accept the EULA. This option must be selected to install the license.
l
I don't agree : Select if you do not accept the EULA. You cannot install the license if this option is selected.
l
Load License File : Click to browse to the Connect license file ( .olconnectlicense
), once it has been received.
l
Install License - Active only when a license file is Loaded : Click to install the license and activate the software.
l
Close : Click to cancel this dialog.
Page 45
Even if a license file has been Loaded, it will not be installed if this dialog is
Cancelled before the Install License button was clicked.
Requesting a license
After getting the Magic Number, a license request must be done for PrintShop Mail Connect: 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 PrintShop Mail Connect license file via email.
l
Resellers can create an evaluation license via the Objectif Lune Partner Portal by following the instructions there: http://extranet.objectiflune.com/
Note that if you do not have a serial number, one will be issued to you by the OL Activations team.
Accepting the license will activate it, after which the PrintShop Mail Connect services will need to be restarted. Note that in some case the service may not restart on its own. To resolve this issue, restart the computer, or start the service manually from the computer's Control Panel.
Activating
PrintShop Mail Connect
To activate PrintShop Mail Connect, simply save the license file somewhere on your computer where you can easily find it, such as on your desktop. You can then load the license by doubleclicking on it, or through the PrintShop Mail Connect Software Activation tool.
Activating the PrintShop Mail 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
Click the Load License File button, and browse for the .olconnectlicense file you received from Objectif Lune Inc..
l
Read the EULA and click the I agree option to accept it.
Page 46
l
Click Install License to activate the license. The license will then be registered on the computer and you will be able to start using the software.
Warning
After installation message will appear warning that the Server services will need to be restarted. Just click OK to proceed.
Migrating to a new workstation
The purpose of this document is to provide a strategy for transferring a Connect installation to a new workstation. The following guide applies to OLConnect v1.x/201x.x .
Before installing the software
Before upgrading to a new version, even on a new workstation, consult the product's release note to find out about new features, bug fixes, system requirements, known issues and much more. Simply go to the product page and look for "Release notes" in the Downloads area.
You should also consult the following pages for some technical considerations before installing: l
"Network Considerations" on page 20
l
"Database Considerations" on page 11
l
"Environment considerations" on page 16
l
"Installation prerequisites" on page 28
l
"Antivirus Exclusions" on page 10
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 PrintShop Mail Connect on the new workstation.
Page 47
Backing up files from the current workstation
The first step in migrating to a new workstation would be to make sure all necessary production files and resources are backed up and copied over to the new system.
Note
Although it is not necessary to convert all of your documents when upgrading to the latest version, we strongly recommended doing so. It is considered "Best Practice" to convert the documents to the version installed.
Backing up Connect Resources
The following resources are used by Connect and can be backed up from their respective folders: l
Job Presets (.OL-jobpreset):
C:\Users\
[UserName]\Connect\workspace\configurations\JobCreationConfig l
Output Presets (.OL-outputpreset):
C:\Users\
[UserName]\Connect\workspace\configurations\PrinterDefinitionCo nfig l
OL Connect Print Manager Configuration files (.OL-ipdsprinter):
C:\Users\
[UserName]\Connect\workspace\configurations\PrinterConfig l
OL Printer Definition Files (.OL-printerdef):
C:\Users\
[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.
Page 48
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.
Other Resources l
OL Connect Designer Templates or Package files, copied from the folder where they reside.
l
All PostScript, TrueType, Open Type and other host based fonts used in templates must be reinstalled on the new workstation.
l
Import all dynamic images and make sure their paths match those in the old server.
l
Make sure the new workstation can also access network or remote images, JavaScript,
CSS, JSON, and HTML resources referenced in the Connect templates.
Secondary software and licenses
The following only applies to specific secondary products and licenses that interact or are integrated into the main product.
Image, Fax and Search Modules l
Reconfigure the Image and Fax outputs with the new host information.
l
Import the Search Profile and rebuild the database in order to generate the database structure required by the Workflow.
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 .
Page 49
4. Import the following files and folders from the old server into their equivalent location on the new server:
C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress
Watch\capture\PPCaptureDefault.mdb
C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress
Watch\DocumentManager
C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress
Watch\PGC
5. If Capture was previously using an external MySQL or Microsoft SQL Server, reconfigure the ODBC connection details as previously from the Workflow Preferences by clicking on the Workflow button at the top left corner and clicking on Preferences, then reconfigure the PlanetPress Capture options under Behavior >PlanetPress Capture > Use ODBC
Database .
6. Start the Messenger 8 service on new server from the Workflow menu bar: Tools >
Service Console > Messenger > right-click and select Start .
OL Connect Send l
As of version 8.6 the Connect Send plugins are installed automatically with Workflow. If you are using an older version, run the OL Connect Send Plug-in Installer on the new
Workstation to re-install the Connect Send plugins.
l
Reconfigure the Server URL and port during the OL Connect Send Printer Driver setup.
l
Re-run the OL Connect Send printer driver setup on client system and select the Repair option to point the clients to the new Server URL.
Configuring the Connect Engines
Any changes made to the Server preferences require the OLConnect_Server service to be restarted to take effect.
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
Open the Server Configuration from:
C:\Program Files\Objectif Lune\OL Connect\Connect Server
Configuration\ServerConfig.exe
Page 50
l
Configure the DataMapper, Merge and Weaver engines preferences (see "Parallel
Processing preferences" on page 62). As of version 2018.1 these preferences
include the minimum (Xms) and maximum (Xmx) memory utilization for the Merge and Weaver engines .
l
Configure any other options for the Clean-up Service.
3. If the version used on the new machine is 1.8/8.8 or older, you may have to manually configure the minimum (Xms) and maximum (Xmx) memory utilization for the Merge and
Weaver engines as previously or better.
l
Edit the Xms (minimum RAM size) and Xmx (maximum RAM size) fields in the following configuration files: l
C:\Program Files\Objectif Lune\OL Connect\Connect Merge
Engine\MergeEngine.ini
l
C:\Program Files\Objectif Lune\OL Connect\Connect
Weaver Engine\WeaverEngine.ini
4. Now start the OLConnect_Server service
Configuring the Server Extensions
In the case where the OLConnect MySQL is installed on the new Master Server, it is important to reconnect all Server Extension systems to the new Master Server.
Perform the following action on each Server Extension:
1. Stop the OLConnect_ServerExtension service from Control Panel > Administrative
Tools > Services > OLConnect_ServerExtension > Stop .
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.
Transferring software licenses
Once all the above resources have been transferred over to the new server, it is recommended to thoroughly test the new system - in demo mode - with sample files under normal production
Page 51
load to identify points of improvement and make sure the output matches the user’s expectation.
Output generated at this point will normally bear a watermark which can be removed by transferring licenses from the old server to the new one.
l
To transfer Connect and Workflow licenses, the user is usually required to complete a
License Transfer Agreement which can be obtained from their local Customer Care department .
l
If you want to transfer your licenses to the new machine right away, you may ask your local Customer Care department for a 30day Transition activation code for your old machine.
l
Upgrades cannot be activated using the automated Activation Manager. Contact your local Customer Care department.
To apply the license file received from the Activation Team:
1. Ensure that all services are stopped on your old machine before activating and starting the services on the new machine. Attempting to run the software with the same license simultaneously will not only run into errors but it is a breach of our EULA.
2. Start the PReS Connect, PlanetPress Connect or PrintShopMail Connect Software
Activation module:
C:\Program Files\Objectif Lune\OL Connect\Connect Software
Activation\SoftwareActivation.exe
3. Click on Load License File to import the license.OLConnectLicense.
4. Start the Software Activation module on the Extension servers, where applicable.
5. Click on Load License File to import the above same license.OLConnectLicense.
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
)
Page 52
To apply the PlanetPress Capture License:
1. Open the Workflow Configuration.
2. Click on Help on the Menu Bar and click on PlanetPress Capture License manager to import your license.
Uninstalling PrintShop Mail Connect from the previous workstation
It is recommended to keep the previous install for a few days until everything is completed.
However, once your transition is successful and complete, the OL Connect software must be
uninstalled from the original server. See "Uninstalling" on page 75.
Upgrading
This page provides information about Upgrading to PrintShop Mail Connect version 2020.1.
Upgrade information is detailed in the following pages: l
"Upgrading from previous Connect versions" below
l
Upgrading from PReS Classic l
Upgrading from PlanetPress Suite 6/7 l
How to perform a Workflow migration l
How to perform a Capture migration
Upgrading from previous Connect versions
Always backup before upgrading
It is recommended that you always backup your existing Connect preferences before upgrading to a new version. This will enable you to revert back to the previous version, in a worst case 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.
Page 53
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.
Users of Connect prior to 2019.1
Users of all Connect versions prior to 2019.1 should note that Update Client 1.2.40
is a prerequisite for both OL Connect 2019.1 and Connect Workflow 2019.1 installations. Only
Update Client 1.2.40 has the capacity to upgrade the OL Connect license to the newer format that is required by the installers of those products.
If you do not have Update Client version 1.2.40 installed already, then the next time you run your Update Client it will show that there is an update available of itself to Version 1.2.40 (or later).
Simply click on the “Install” icon to initiate the upgrade.
For further details on how to upgrade the Update Client and update your Connect License see the Update Client 1.2.40 Upgrade Guide .
Note that an erroneous or incomplete uninstall before a reinstall or upgrade to a newer version of OL Connect may cause issues (see Product or engine exits within a second of starting in
Connect's Knowledge Base).
Note
If an error occurs during uninstallation or after/when re-installing Connect after uninstalling it, please see: Problems during a Connect installation or version upgrade in Connect's
Knowledge Base (https://help.objectiflune.com/en/kbconnect/#KB/FAQ/OL%20Connect/KB2002.htm).
Backup existing Connect version
It is recommended that you always backup your existing Connect preferences before upgrading to a new version. This will enable you to revert back to the previous version, in a worst case scenario in which the new version introduces issues with your existing production processes.
Page 54
Whilst the probability of such a worst case scenario is remote, it cannot hurt to take some simple precautions, just in case.
Backing up a virtual machine
Backing up a virtual machine installation is relatively straight forward. Simply take a snapshot of the virtual machine instance, prior to upgrading. This would save all the localized preferences and configurations.
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\workspace\Designer\.metadata\.plugins\org.ec
lipse.core.runtime\.settings
l
C:\Users\
[UserName]\Connect\workspace\Server\.metadata\.plugins\org.ecli
pse.core.runtime\.settings
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
Page 55
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.
Backup your database
If you want to be completely thorough and be able to exactly replicate your existing system, you should also backup your existing Connect database.
If the default MySQL database is being used as the Connect back-end database, we would 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).
Page 56
Engines preferences
Background
A Merge engine merges the template and the data to create Email 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.
This page appears in the Designer Window > Preferences dialog. It allows control over Merge and Weaver (output) engines.
Settings
Configure engine options
l
Tasks handled by :
Select how Connect jobs are to be processed. The choices are between: l
Engines (separate processes): Select to have a number of separate engines (for
Merging and Weaver, as appropriate) to process jobs.
Note
This is the best choice for production environments.
l
Connect Designer (uses less memory): Select to have a single Connect Designer handle processing.
Note
This option should only really ever be used for low memory, non-production
(testing) environments.
Page 57
Number of engines
This group is only available if Engines were selected as the processing architecture .
l
Merge Engines selection: Select the desired amount of Merge Engines.
A Merge engine merges the template and the data to create Email 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.
Generally, launching a relatively high number of Merge engines results in better performance, as Merge engines are involved in the creation of output of all kinds (Print,
Email and Web) and because content creation is relatively time-consuming.
Note
The Connect installer automatically sets the number of Merge Engines based upon the machine CPUs/Processors (the number of cores) and available Memory (RAM).
The default setting will likely be enough for most users.
However, virtual machines can provide an exception to this. In some virtual environments the Connect installer cannot accurately determine the number of logical cores actually available to the virtual machine, and will thus use a lesser number than that which could actually be supported.
You can confirm how many Merge engines are running on your machine by running Task
Manager and locating the mergeengine.exe entries in your process list.
Note that there will be an extra Merge and Weaver engine in your task manager if you are running Designer.
The Merge engine is responsible for the plugins Create Print Content, Create Email
Content and Create Web Content.
License restrictions only apply to the Merge engine when creating Email or Web content.
They do not apply for Create Print Content. This means you are allowed to start an infinite amount of Merge engines on any given Connect Sever to run print jobs, but you will be restricted to a set number of Merge engines for your Email and HTML jobs.
Page 58
l
Weaver Engines selection: This option is read-only in PrintShop Mail Connect Designer
Preferences.
Select the desired amount of Weaver (Output) Engines.
A Merge engine merges the template and the data to create Email 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.
Adding extra Weaver (Output) engine(s) might be useful when large Print jobs are to be run simultaneously with smaller Print jobs. However, too many running engines will waste precious RAM and CPU cycles to idle processes, whilst too few could create a bottleneck.
Memory
This group is only available if Engines were selected as the processing architecture.
Specify the maximum amount of random access memory (RAM) in megabytes that will be used per engine in order to make optimal use of the machine's memory.
The selections made here will apply to all Engines of that type.
Note
These settings only control the maximum size of the Java heap memory that an engine can use; the total amount of memory that will used by an engine is actually a bit higher.
Also keep in mind that the Connect Server and the operating system itself will need memory to keep running.
By default, each engine is set to use up to a predetermined amount of RAM. To make optimum use of a machine's capabilities it might be useful to increase the amount of memory that the various engines can use.
Here are some simple scenarios where you might want to increase an Engine's memory usage:
Page 59
l
DataMapper engines may perform better with greater memory when running jobs containing a lot of data.
l
For complex templates with a lot of pages per document, there is a chance that Merge engines will run better with more memory.
l
The maximum memory usage of a Weaver engine can be relevant for jobs with heavy graphics; or for jobs that use Cut & Stack impositioning; or for jobs using particular variables that entail page buffering (see Content variables).
The options available in the Memory group are: l
Merge Engines (MB) selection: Select the desired amount of Merge Engine memory.
For complex templates with a lot of pages per document, there is a chance that Merge engines will run better with more memory.
l
Weaver Engine (MB) selection:
Select the desired amount of Weaver (Output) Engine memory.
When running really large jobs, it often pays to increase Weaver memory allocation, even if only for the duration of the production job(s).
The maximum memory usage of a Weaver engine can be relevant for jobs with heavy graphics; or for jobs that use Cut & Stack impositioning; or for jobs using particular variables that entail page buffering (see Content variables).
Multi-threading settings
This group allows you to set Multi-threading rasterization options for form ripping when generating AFPDS or IPDS output.
l
Enable multi-threaded reading check box: This setting controls how the engine reads its input, with multi-threading reading being the default.
Note
This setting is primarily for trouble shooting. We recommended always leaving multi-threading on, unless otherwise advised by Support.
Page 60
l
Number of multi-threaded form rips selection: Set the amount of individual threads to assign to form ripping.
This setting is useful for when graphics content triggers rasterization when writing AFP or
IPDS output. Typical examples of content triggering rasterization are: transparency; fill patterns; gradient fills; or text rotated at a non-right angle.
Increasing the number of threads should speed up Output Creation under such circumstances.
Note
How effective this setting is at speeding up the output will depend upon the number of cores available on the processing machine and how many other tasks the machine is running simultaneously.
If only one Output Creation task is running, setting this value as equal to the number of (logical) cores will likely give the best performance.
Buttons
The Engines preferences also provides you with buttons to : l
Restore Defaults . This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.
l
Apply : This option applies the settings made within the current Preferences page, but does not close the Preferences dialog.
Page 61
Parallel Processing preferences
The parallel processing preferences (previously referred to as Scheduling preferences, prior to
2019.2) page provides the means to control precisely how the PrintShop Mail Connect
Designer handles jobs that operate in parallel.
For additional information on how these preferences can enhance performance, see Engine
configuration and "Performance Considerations" on page 22.
Parallel Processing properties
Preset selection
Only the Custom setting is applicableto the PrintShop Mail Connect Preferences, so this option is always selected and the field made read-only.
Content Creation Tab
The options are: l
Total Merge engines configured read only display: This is a read only entry that shows the total number of Merge engines available. To change this value, you must update the
Merge Engines in the "Engines preferences" on page 57 page.
l
Multi tasking group:
When starting a new Content Creation task, the task will immediately commence if there 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
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.
The default of 100 records was chosen purely because it is an easily multiplied
Page 62
number, not because it has been proven to have any significant value. It means that on an average system (i.e., less than 10 Merge engines) any decently sized task is 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.
Buttons
The Parallel Processing preferences also provides you with buttons to : l
Restore Defaults . This option restores the preferences to Defaults. This applies to the current Preferences page only, but not other Preferences.
l
Apply : This option applies the settings made within the current Preferences page, but does not close the Preferences dialog.
Page 63
Known Issues
This page lists important information about issues that apply to PrintShop Mail 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.
No multi-select in Outline pane in Designer
In version 2020.1 it is no longer possible to select multiple elements in the Outline pane in the
Designer. This will be fixed in version 2020.2.
Connect Updates failing due to Microsoft
Visual C++ 2017 Redistributable product
Certain updates to Connect 2019.2 from earlier Connect versions are failing due to an issue with two specific Microsoft Visual C++ Redistributable packages.
These two versions of the Visual C++ Redistributables remove a registry entry which the
Connect installer uses to determine whether or not it needs to install the Microsoft Visual C++
2015 Redistributable.
These two versions are: l
MSVC++ 2017 v14.14.26405.0
l
MSVC++ 2017 v14.14.26429.4
Page 64
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.
Whilst this issue has been fixed in the Connect 2019.2 installer, if a user had previously experienced the issue and temporarily worked around it to complete the installation, then the
Connect installer will fail on upgrade or uninstallation.
To get around this, a manual uninstall is required, or a modification to registry entries.
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.aspx) after the initial license update is complete and have them add the AFP input option back into your license.
Page 65
The Update Client OL for Connect 2019.1
does not cater for standalone Connect
Print Manager installations
The Connect Print Manager is a standalone Connect tool that is used in production sites to manage print jobs. It can be installed and run on standalone machines without a Connect license.
The Update Client for Connect 2019.1 looks for a Connect license as part of the update process, but it will not find one on standalone Connect Print Manager installations. As a result the Update Client will not recognize that there is a Connect update available to the Print
Manager machine.
In order to update Connect Print Manager to version 2019.1 you will need to download the
Connect 2019.1 installer outside of the Update Client. The Connect 2019.1 installer can be downloaded from the Web Activation Manager site: https://www.objectiflune.com/webactivationmanager/, or you could ask your local
Administration for the installer, as it would likely already have been downloaded for installation by the document designers.
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.1) on older printer models that do not support " Scale to Fit ".
Page 66
Issue with image placement in 2019.1 when using some customized AFP and IPDS
Printer Definitions
An issue with image placement in Connect 2019.1 AFP and IPDS output was discovered just prior to the release. The issue is specific to AFP and IPDS 600 DPI Printer Definitions that are not set to " Scale to Fit ".
As " Scale to Fit " is now switched on by default in all standard Connect 2019.1 AFP and IPDS
Printer Definitions, none of those should encounter the issue.
This issue will be fixed in a subsequent patch release.
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.com/en/kb-connect/#KB/FAQ/OL
Connect/KB2019.htm.)
This may be solved by deleting the %UserProfile%\Connect\.eclipse
directory.
For guidance on a full manual uninstallation please see the Solution in: Problems during a
Connect installation or version upgrade in Connect's Knowledge Base: http://help.objectiflune.com/en/kb-connect/#KB/FAQ/OL Connect/KB2002.htm.
Page 67
Backend database might require periodic maintenance
Databases maintain a variety of statistics in order to optimize performance. When high levels of inserts and/or deletions occur, the statistical data keeping can struggle to keep up. Over a period of prolonged and intensive processing this can result in a degradation in performance, with the whole database slowing down as it struggles to clean itself up.
In Connect terms the effect can be felt as the Data Mapper and/or Job Creation progressively slowing down.
To cure this issue, it is recommended that you periodically run manual maintenance on the backend database.
If using MySQL , the following script should be run in a query window: set @a=null,@c=null,@b=concat("show tables where",ifnull(concat("
`Tables_in_",database(),"` like '",@c,"' and"),'')," (@a:=concat_ws
(',',@a,`Tables_in_",database(),"`))");
Prepare `bd` from @b;
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
Page 68
Windows 10 Search service impacting
Connect
The Windows 10 Search service runs as a background task, indexing files and folders. It has been noted that this background task is sometimes preventing files being added to the Connect temporary files folder when large amounts of files are being output and copied.
If this is an issue for you, we suggest disabling Search Indexing on the
C:\Users\<username>\Connect folder.
This issue will be fixed in a later release.
Job Creation Presets: External Sorting change introduced in 2018.2
Versions prior to 2018.2 did not correctly save the line end characters for external sort configurations in Job Creation Presets, which meant the job could not be externally sorted. This issue has been fixed in version 2018.2. However, Job Creation Presets created with an earlier version may still have the wrong line end character for external sorting. To fix this, open the Job
Creation Preset in the new version, reset the line end setting in the sorting options and then save the preset.
Business Graphics: Backward
Compatibility Issues introduced in 2018.1
As a consequence of changes in both the user interface and the underlying technology,
Business Graphics made with a version prior to PrintShop Mail Connect 2018.1 may not display correctly when opened in version 2020.1.
The currently known backward compatibility issues are listed here:
Page 69
All charts
l
Legend position : The position of the legend is not converted. It defaults to 'left' in a converted chart.
l
NOTE: Expanded custom chart scripts cannot be converted.
Pie charts
l
Default colors : The default colors (used when no pie chart colors are specified) have changed.
Known Font issues
The following font(s) are known to have issues in PrintShop Mail Connect 2020.1: l
Benton Sans CFF font
Minor differences in PCL, AFP and
IPDS output introduced in 2018.1
The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer was updated for Connect 2018.1. This allows use of new CSS properties, such as flexbox.
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 PrintShop Mail Connect 2018.1 Connect is officially supported under Windows Server
2016.
Page 70
Please note, however, that the Objectif Lune Inc.
Update Client application might be blocked by the enhanced security settings in Windows Server 2016.
To fix this, add http://updates.ca.objectiflune.com
to the list of trusted web sites on that machine, or lower the internet access rules.
Limit of 100MB of image files within a single job
The browser component (Mozilla Gecko) used in the WYSIWYG editor of the Designer was updated for Connect 2018.1. This allows use of new CSS properties, such as flexbox.
However this update also introduced a limit of 100MBs for image files included within a single job. The limit is set at 100MB deliberately, as this allows most jobs to run faster. However, if a job requires more than 100MBs of image files, then the Connect image cache size can be increased to cater for such.
Please contact OL Support for instructions on how to modify the image memory cache value, if needed.
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.
With some exceptions. Booklet Impositionings that require a multiple of 4 pages ( Saddle binding and Perfect binding ) will still get empty pages added, when needed.
Page 71
Installation paths with multi-byte characters
When installing the Traditional Chinese 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.
Switching languages
Changing the language using the Window > Preferences > Language Setting menu option does not currently change all of the strings in the application to the selected language. This is a known issue and will be fixed in a later release.
In the meantime we offer the following workaround for anyone who needs to change the language:
1. Go to the .ini files for the Designer and Server Config: l
C:\Program Files\Objectif Lune\OL Connect\Connect
Designer\Designer.ini
l
C:\Program Files\Objectif Lune\OL Connect\Connect Server
Configuration\ServerConfig.ini
2. Change the language parameter to the required one under Duser.language=en | es | de | fr | it | ja | ko | pt | tw | zh
Only one of the above language tags should be selected. Once saved, Connect will appear in the selected language at next start-up.
GoDaddy certificates
When installing Connect offline, dialogs allow installing the GoDaddy certificates. Most users should use the default settings and click Next . In some cases, however, this may not work
Page 72
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
The minimum supported MySQL version is MySQL 5.6.
Available Printer Models
Note that only the single Printer Model (Generic PDF) will appear on the Advanced page of the
Print Wizard by default.
To add additional printer models click on the settings button next to the Model selection entry box.
Color Model in Style Sheets
The color model of colors defined in a style sheet can sometimes change after editing the style sheet. This is a known issue and will be addressed in a subsequent release.
Image preview in Designer
If in the Windows Internet settings ( Connection Settings > LAN configuration ) a proxy is enabled, but "Bypass proxy settings for local addresses" is not checked, the image preview service, conversion service and live preview tab in the Designer will not work and exhibit the following issues: l
Images will be shown as 0 size boxes (no red 'X' is displayed).
l
Live preview does not progress, and when re-activated reports "browsers is busy".
To fix the issue you must check the "Bypass proxy settings for local addresses" option.
Page 73
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.
Note
Installing Connect after Docker has already been installed will not cause issues.
Page 74
Uninstalling
This topic provides some important information about uninstalling (removing) PrintShop Mail
Connect2020.1.
To uninstall PrintShop Mail Connect select the application from within the Add/Remove programs option under the Control Panel. This will start the PrintShop Mail Connect Setup
Wizard in uninstall mode.
Note
The PrintShop Mail Connect Setup Wizard might take some seconds to appear.
Important: Stop any active Anti-Virus software before uninstalling Connect.
Some anti-virus systems are known to block the uninstallation of MySQL datafiles, as well as blocking the uninstallation of the MySQL database application itself. Therefore it is highly recommended that any anti-virus application be stopped prior to uninstalling PrintShop Mail
Connect, as otherwise the Connect uninstallation might not work correctly.
Impacts upon other applications and services
l
The Uninstall will terminate the installed Server / MySQL service(s).
l
The following applications / services should be stopped in a controlled fashion, before running the PrintShop Mail Connect Uninstall:
1. PrintShop Mail Connect
2. Connect products on remote systems which refer to this MySQL database.
Page 75
Uninstallation Wizard
The uninstallation is done by running the PrintShop Mail Connect Setup Wizard in uninstall mode. The Wizard consists of the following pages:
1. PrintShop Mail 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. Selections are as follows: l
Delete Connect Workspace Data : Check this box to delete the Workspace data for the current user, or for selected users (as determined by the "Select Users" button) l
Backup Connect Workspace Data for all specified Users : Check this box to backup the Workspace data for the specified users (as previously determined) into a compressed ZIP file (whose location can be customized), before deletion of the full Workspace data.
l
Delete MySQL objectlune Data : Check this box to delete the MySQL database installed with PrintShop Mail Connect.
l
Backup MySQL Date : If the deletion checkbox is selected, this option appears to allow backing up the MySQL database to a customizable location, prior to uninstallation.
Note
If an error occurs during uninstallation or after/when re-installing Connect after uninstalling it, please see: Problems during a Connect installation or version upgrade in Connect's
Knowledge Base (https://help.objectiflune.com/en/kbconnect/#KB/FAQ/OL%20Connect/KB2002.htm).
Page 76
Legal Notices and
Acknowledgements
Warning: PrintShop Mail 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
Adobe PDF Library which is either a registered trademark or trademark of Adobe
Systems Incorporated in the United States and\or other countries.
l
Adobe XMP Core Copyright © 1999 - 2010, Adobe Systems Incorporated. All rights reserved.
l c3p0 which is licensed under the terms of the Lesser General Public License
(LGPL) Version 2.1. The source code can be obtained from the following location: https://github.com/swaldman/c3p0 l
Eclipse Gemini Blueprint 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
Eclipse Persistence Services Project (EclipseLink) , Copyright © 2007, Eclipse
Foundation, Inc. and its licensors. All rights reserved. This is distributed under the terms of the Eclipse Public License Version 1.0 and Eclipse Distribution License Version 1.0.
l
Fugue Icons by Yusuke Kamiyamane which are distributed under the terms of the
Creative Commons Attribution 3.0 License .
l
Gecko which is distributed under the terms of the Mozilla Public License (MPL) Version
2.0. Information on obtaining Gecko can be found on the following page: https://wiki.mozilla.org/Gecko:Getting_Started
NOTE: This library has been modified for Connect. To obtain copies of the modified library please contact your local Objective Lune Support team.
l
Glassfish Java Mail which is licensed under the terms of the Common Development and
Distribution License (CDDL) Version 1.0. Information on how to download the Glassfish
Page 77
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
IcoMoon . Connect uses unmodified icons from IcoMoon ( https://icomoon.io/#iconsicomoon ) which have been made available under the Creative Commons By 4.0 license
( https://creativecommons.org/licenses/by/4.0
).
l
ICU4J 4.4.2
Copyright © 1995-2013 International Business Machines Corporation and others. All rights reserved.
l
J2V8 which is distributed under the terms of the Eclipse Public License (EPL) Version
1.0. The source code for J2V8 can be obtained from the following location: https://github.com/eclipsesource/j2v8 l
Jacob Java Com Bridge which is licensed under the terms of the GNU Lesser General
Public License (LGPL) Version 2. The source code for this can be obtained from the following location: http://sourceforge.net/projects/jacob-project/files/jacob-project/ l
JavaSysMon Copyright © 2009 ThoughtWorks, Inc. All rights reserved.
l
JavaX Mail which is distributed under the terms of the Common Development and
Distribution License (CDDL) Version 1.1. The source code for this can be obtained from the following location: https://java.net/projects/javamail/downloads/directory/source l
Java XmlHttpRequest which is licensed 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/objectifluneCA/java-XmlHttpRequest l
Jersey which is distributed under the terms of the Common Development and Distribution
License (CDDL) Version 1.1. Information on how to obtain the source code can be found at the following location: http://repo1.maven.org/maven2/org/glassfish/jersey/jersey-bom l jersey-json-1.13
which is licensed under the terms of the Common Development and
Distribution License (CDDL) Version 1.1. Information on how to obtain the source code can be found at the following location: http://mvnrepository.com/artifact/com.sun.jersey/jersey-json/1.13-b01 l
Jersey Multipart which is distributed under the terms of the Common Development and
Distribution License (CDDL) Version 1.1. Information on how to obtain the source code
Page 78
can be found at the following location: http://repo1.maven.org/maven2/org/glassfish/jersey/jersey-bom 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 l
Logback which is distributed under the terms of the Eclipse Public License
(EPL) Version 1.0. The source code for Logback can be obtained from the following location: https://logback.qos.ch/download.html
l
Mchange Commons Java which is licensed under the terms of the Lesser General
Public License (LGPL) Version 2.1. The source code can be obtained from the following location: https://mvnrepository.com/artifact/com.mchange/mchange-commons-java l
Objectweb ASM , Copyright © 2000-2011 INRIA, France Telecom. All rights reserved.
l
Oracle JDBC Driver which is licensed by the Oracle Free Use Terms and Conditions
(FUTC) licence.
l
Polyfills which is licensed under the Unlicense license. The source code can be obtained from the following location: https://github.com/inexorabletash/polyfill .
l
Relique CSV Driver which is licensed under the terms of the Lesser General Public
License (LGPL) Version 2.1. The source code can be obtained from the following location: https://sourceforge.net/p/csvjdbc/code/ci/csvjdbc-1.0.31/tree/ l
Rhino 1.7R4 and 1.7.7.1
which are licensed under the terms of the Mozilla Public
License (MPL) Version 2.0. The source code for these can be obtained from the following location: https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino/Download_
Rhino l
Saxon which is distributed under the terms of the Mozilla Public License (MPL) Version
2.0. The source code for this can be obtained from the following location: http://sourceforge.net/projects/saxon/files/Saxon-HE/9.6/ l
Servlet API developed by Sun as part of the Glassfish project and licensed under the terms of the Common Development and Distribution License (CDDL) Version 1.0.
Information on how to download the Glassfish source (as part of Java EE platform) can be obtained from here: https://wikis.oracle.com/display/GlassFish/Java+EE+7+Maven+Coordinates l
Simple Logging Facade for Java (SLF4J) Copyright © 2004-2017 QOS.ch. All rights reserved.
Page 79
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
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.com/angelozerr/tern.java
l
Web Services Description Language for Java which is distributed under the terms of the Common Public License v 1.0. The source code for this can be obtained from the following location: http://wsdl4j.cvs.sourceforge.net/viewvc/wsdl4j/ l
XULRunner which is distributed under the terms of the Mozilla Public License Version
2.0. The source code for this can be obtained from the following location: http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/latest/source/ l zziplib which is licensed under the terms of the Mozilla Public License (MPL) Version 1.1.
The source code for this can be obtained from the following location: http://sourceforge.net/projects/zziplib/files/zziplib13/ l
7-Zip SFX which is licensed under the terms of the GNU Lesser General Public License
(LGPL) Version 2.1. The source code for this can be obtained from the following location: https://github.com/chrislake/7zsfxmm
Portions of certain libraries included in this application which are distributed under the terms of the Mozilla Public License have been modified. To obtain copies of the modified libraries please contact your local Objective Lune Support team.
Apache Software License Components
This application also uses the following components which are distributed under the terms of the Apache Software License Version 2.0
: l
Apache ActiveMQ l
Apache Batik l
Apache Commons Beanutils l
Apache Commons CLI l
Apache Commons Codec l
Apache Commons Collections
Page 80
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
Google Collections l
Google GSON l
Hibernate Validator l
Jackson JSON processor l
Jetty l
Liquibase l
LMAX Disruptor l
Objenesis l
OpenCSV l
OPS4J Pax Web
Page 81
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
.
Java SE framework and platform:
This application uses the Java SE framework and platform which is distributed under the terms of the Oracle Binary Code License Agreement for the Java SE Platform Products and Java FX.
Copyright 2013, Oracle America ,Inc. All rights reserved.
Use is subject to license terms. ORACLE and JAVA trademarks and all ORACLE- and JAVArelated trademarks, service marks, logos and other brand designations are trademarks or registered trademarks of Oracle in the U.S. and other countries.
Use of the Commercial Features for any commercial or production purpose requires a separate license from Oracle. “Commercial Features” means those features identified Table 1-1
(Commercial Features In Java SE Product Editions) of the Java SE documentation accessible at http://www.oracle.com/technetwork/java/javase/documentation/index.html
.
Further Components: l
Portions of this software are copyright © 2018 The FreeType Project (www.freetype.org).
All rights reserved.
l
This product includes software developed by JSON.org
(http://www.json.org/java/index.html).
Page 82
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. ("OL") and describes your rights to use the OL software, including any stand-alone application sold as part of the software and all companion products, components, patches, updates and upgrades, and also including any computer software, PostScript ® programs, media and all accompanying on-line or printed documentation (collectively the
"Software"). The term Software also includes licensed components of other third parties bundled with OL’s proprietary Software.
BY SELECTING "I AGREE" OR INSTALLING, COPYING OR OTHERWISE USING THE SOFTWARE, YOU ACCEPT TO BE BOUND BY ALL OF THE TERMS
AND CONDITIONS OF THIS LICENSE AGREEMENT. IF SELECTING "I DECLINE", YOU MAY NOT USE THE SOFTWARE FOR ANY PURPOSE
WHATSOEVER. IF YOU ARE AN EMPLOYEE, RESELLER, SERVICE PROVIDER, CONSULTANT, CONTRACTOR OR OTHER PARTY THAT INSTALLS THE
SOFTWARE OR OBTAINS THE SERVICE ON BEHALF OF ANOTHER PERSON OR ENTITY, YOU WILL BE DEEMED TO HAVE ACCEPTED THE TERMS OF
THIS CONTRACT ON BEHALF OF THAT PERSON OR ENTITY.
COPYRIGHTS. The Software is owned by OL, its affiliates companies or its suppliers and is protected by the Copyright Act (Canada), any copyright law and international copyright treaties. Therefore, you must treat the Software like any other copyrighted material except that you may make one copy of the Software solely for security backup or archival purposes or if it is essential for the compatibility of the computer program. You may also transfer the Software to a single hard disk provided you keep the original solely for backup or archival purposes and that such copy is not installed or used on any other computer. Any copies that you are permitted to make under this agreement must contain the same copyright and other proprietary notices that appear in the Software.
PROPERTY AND INTELLECTUAL PROPERTY RIGHTS. You acknowledge that the Software in source code, its structure and organization form remain confidential valuable trade secrets of OL or its suppliers and that all OL libraries, source code, byte code executables and any other files (collectively the “files”) remain OL's exclusive property or that of licensed third parties suppliers which are usually more fully identified in the “About” section of the Software Help menu. Therefore, you agree not to modify the Software or attempt to reverse engineer, decompile or disassemble or otherwise attempt to discover the source code of the Software. You also agree that you may not distribute any files (particularly but not limited to OL source code and other non-executable files) except those that OL has expressly designated. Nothing in this License Agreement permits you to derive the source code of files provided to you in executable form only, or to reproduce, modify, adapt, translate, use or distribute the source code of such files. This License Agreement does not grant you any intellectual property rights in the Software nor in any third parties’ components licensed to OL and bundled in the Software.
INFRINGEMENT. OL will, at its own expense, defend or settle any claim or suit against you alleging that the Software, when used in accordance with this License Agreement, infringes a patent, copyright, trademark, trade secret or other proprietary right of a third party. OL will also pay all damages and costs that may be assessed against you by final judgment as a result of such an infringement under the following conditions: i) OL shall be notified promptly in writing of any claim or suit; ii) OL shall have sole control of the defense or settlement of any claim or suit; iii) you shall cooperate with OL in a reasonable way to facilitate the settlement or defense of any claim or suit; and iv) the claim or suit does not arise from modifications by you, or from combinations of products provided by OL with products provided by a third party, except as a combination occurring by use of the Software for which they were designed.
For more clarity, this indemnity undertaking by OL applies only to the Software content and excludes any infringement of third party’s intellectual property rights resulting from your use or operation of the Software, or from development you made with the Software, including any workflow process developed by you with the Software functionalities.
If the Software becomes, or in OL’s opinion is likely to become, the subject of a claim of infringement, OL will, at its option: i) procure you the right to continue using the Software; ii) replace the Software with a non-infringing product substantially complying with the Software specifications; iii) modify the Software so it becomes non-infringing and performs in a substantially similar manner to the original Software. If OL fails to provide any of the preceding options, you will discontinue any infringing use and OL will refund any fees theretofore received by OL hereunder with respect thereto less a reasonable allowance for use.
You hereby agree to keep harmless OL, its officers, directors and employees, representatives and agents of any claim or action from any third party, as well as any damages, fees, expenses including reasonable attorney’s fees, relating to the violation of this section by you, including any third party’s intellectual property infringement resulting from your use, operation or any development made with the Software.
Page 1
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. THE SOFTWARE IS NOT FAULT-TOLERANT AND IS NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE OR
RESALE AS ON-LINE CONTROL EQUIPMENT IN HAZARDOUS ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS, WITHOUT
LIMITATION, IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC CONTROL, DIRECT
LIFE SUPPORT MACHINES OR WEAPONS SYSTEMS, IN WHICH THE FAILURE OF THE SOFTWARE COULD LEAD DIRECTLY TO DEATH, PERSONAL
INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE ("HIGH RISK ACTIVITIES"). OL AND ITS SUPPLIERS SPECIFICALLY DISCLAIM ANY
EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES.
SCOPE OF USE. The license granted to you under this agreement is a single device license only and not a multi-device license. Consequently, you agree to use the Software for your own customary business or personal purposes on a single instance of any physical or virtual computer system for which the Software was licensed. If you need to use the Software on more than one device, you must purchase additional licenses. Contact OL for applicable royalties and licensing terms.
EXCEPTIONS TO THE SCOPE OF USE. a) The following products can be used on any number of devices: Designer , OL Connect Send and PlanetPress Search . b) A Capture OnTheGo (COTG) user license can be used simultaneously on multiple devices if and only if the operator of these devices is the same physical person. c) If the Software can or will generate, create or modify PostScript programs called Variable Content Documents ("VCD"), any VCD generated by the Software is licensed on a per "licensed output device" basis (including, without limitation, printers, Adobe Acrobat Distiller, Aladdin
Ghostscript, etc.). This means that any VCD generated by the Software can be used by any number of users as long as they use the VCD on only that single licensed output device. If you need to use the VCD on more than one output device, you must purchase additional licenses.
In case of cluster printing systems (multiple print engines attached to a single Raster Image Processor (RIP)), each print engine needs to be licensed individually. Contact OL for the applicable royalties and licensing terms for distribution of any VCD. Note that this paragraph does not apply for PlanetPress Office’s “Windows Printing”, PlanetPress Production’s “Optimized PostScript Stream” and “Windows Printing”,
PlanetPress Connect or PReS Connect.
SOFTWARE ACTIVATION. Technological protection measures are included in the Software to prevent its unauthorized or illegal use. You agree to such technical measures and you undertake to follow their requirements.
The Software requires activation within thirty (30) days after the initial installation. If you are using a time-based license, you may need to reactivate the Software prior to its expiry. You may also need to reactivate the Software if you modify your computer hardware or install the
Software on another computer.
SINGLE/MULTI-TENANCY SOFTWARE AS A SERVICE (SAAS) AND PAY-PER-CLICK. This license cannot be used to offer SaaS or PAY-PER-CLICK services without first contacting OL for execution of a specific agreement to that purpose.
ANTI-SPAM AND PROTECTION OF PERSONAL INFORMATION. As the Software may allow you to generate and output emails, you undertake to use the Software and any email functionality in strict compliance with any anti-spam laws and regulations applicable to you in your jurisdiction. You also undertake to protect transactional information and personal information that you may collect using the Software in strict compliance with any protection of personal information laws and regulations applicable to you in your jurisdiction.
OL, ITS AFFILIATED COMPANIES, DIRECTORS, OFFICERS AND EMPLOYEES ASSUME NO LIABILITY WHATSOEVER REGARDING ANY VIOLATION FROM
YOU OF ANY ANTI-SPAM OR PROTECTION OF PERSONAL INFORMATION LAWS OR REGULATIONS.
TRANSFER. If the Software was provided to you through a leasing or a subscription agreement, it cannot and shall not be transferred and/or used by any third party at the end of the agreement. However, if you extend the agreement or buy-out your lease without change of ownership, this
License Agreement shall remain in effect accordingly.
Page 2
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.
Except as provided herein, you may not transfer, rent, lease, lend, copy, modify, adapt, sublicense or time-share in any manner the Software or any part hereof.
TERM. This License Agreement is effective until the end of the period defined by the type of license used (as described on OL’S website) or until terminated. This License Agreement shall be automatically terminated upon i) if you fail to comply with any of the terms of this License Agreement and that you have not remedied any such breach within ten (10) days from receipt of a written notice from OL, without prejudice to OL‘s legal recourses, including injunctive reliefs or ii) default of payment not remedied within ten (10) days from receipt of a written notice from OL. Upon termination, you must destroy the original and any copy of the Software and cease all use of all the trademarks mentioned herein.
LIMITED WARRANTY - SOFTWARE PURCHASE ON A PHYSICAL MEDIA. OL warrants that the Software media will be free from defects in materials and workmanship, for a period of ninety (90) days from the date of its purchase. In case of defect, you must return the Software media to OL with a copy of your receipt and within the warranty period for replacement.
DO NOT RETURN ANY PRODUCT UNTIL YOU HAVE CALLED THE OL CUSTOMER CARE DEPARTMENT AND PREVIOUSLY OBTAINED A RETURN
AUTHORIZATION NUMBER.
This Limited Warranty is void if failure of the Software media results from accident, abuse or misapplication. Any replacement of the Software media will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer.
WARRANTY DISCLAIMER.
EXCEPT AS EXPRESSLY SET FORTH IN THE "LIMITED WARRANTY - SOFTWARE PURCHASE ON A PHYSICAL MEDIA"
SECTION, OL MAKES NO OTHER REPRESENTATION NOR PROVIDES ANY ADDITIONAL WARRANTY REGARDING THE SOFTWARE WHICH IS BEING
DELIVERED « AS IS ». YOU ACKNOWLEDGE AND AGREE TO RELY AND OPERATE THE SOFTWARE AT YOUR OWN RISKS. OL MAKES NO
REPRESENTATION NOR WARRANTY i) THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS, ii) THAT THE RESULTS WHICH MAY BE OBTAINED
FROM THE SOFTWARE WILL BE ADEQUATE, RELIABLE OR ERROR FREE, NOR iii) THAT ANY SOFTWARE DEFECT WILL BE CORRECTED.
MORE SPECIFICALLY, OL GIVES NO CONVENTIONAL OR LEGAL WARRANTY OF ANY NATURE, EXPRESS OR IMPLIED, ON THE SOFTWARE CONTENT,
ITS RESULTS OR ITS DOCUMENTATION.
OL EXPRESSLY DISCLAIMS ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE OR QUIET ENJOYMENT.
No opinion, advice or representation whether verbal or in writing that you may receive from OL’s employees or its affiliated companies will constitute an additional warranty to the terms and conditions of this License Agreement.
LIMITATION OF LIABILITY. TO THE FULLEST EXTENT PERMITTED BY LAW, OL, ITS AFFILIATED COMPANIES, DIRECTORS, OFFICERS AND EMPLOYEES
SHALL NOT BE HELD LIABLE, WHETHER BY CONTRACT OR IN TORT, TOWARDS YOU OR ANY OTHER THIRD PARTY FOR ANY SPECIAL, INCIDENTAL,
INDIRECT OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS
OR SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS) ARISING FROM ANY SOFTWARE
DEFECT, ITS DOCUMENTATION OR FOR ERRONEOUS RESULTS OR FROM THE USE OF OR INABILITY TO USE THE SOFTWARE OR THE PROVISION OF
OR THE FAILURE TO PROVIDE SUPPORT SERVICES, EVEN IF OL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. OL ASSUMES NO
LIABILITY FOR ANY DAMAGE RESULTING FROM YOUR MISHANDLING OF THE SOFTWARE.
IF A COMPETENT COURT SHOULD CONCLUDE TO OL’S LIABILITY DESPITE THE FOREGOING PROVISION, YOU EXPRESSLY AGREE THAT OL SHALL NOT
BE LIABLE TO YOU FOR ANY DAMAGES REGARDLESS OF THE CAUSE OF ACTION, WHETHER IN CONTRACT OR IN TORT, IN EXCESS OF THE AMOUNT
PAID FOR THE PURCHASE OF THE SOFTWARE.
ASSIGNMENT OF OL RIGHTS. OL is entitled to sell, transfer or assign in any way and at its sole discretion any rights under the present License
Agreement to any third party and the assignee will be entitled to any of OL’s rights, privileges or recourses resulting from the present agreement.
OL will notify you of such sale, transfer or assignment through a specific notice on its website.
GENERAL PROVISIONS. This License Agreement may only be modified in writing by a duly authorized officer of OL. OL shall announce any modifications to this License Agreement whether on its website or by email to you, at its own discretion, within thirty (30) days before its effective
Page 3
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. Any declaration of a court to the effect that any provision hereof is invalid or unenforceable shall not affect the validity or enforceability of any remaining provisions hereof.
If OL fails to avail itself of any of its rights under the present agreement, this does not constitute a waiver or a modification of the rights available to it hereunder and OL may within the time prescribed by law, institute procedures to invoke its rights. A delay in doing so does not constitute a defense which is enforceable.
None of the parties hereto shall be deemed in default in the performance of its obligations hereunder if such performance is delayed, detained or prevented because of force majeure. Force majeure is any cause beyond the control of the parties hereto and against which they could not protect themselves. Force majeure includes, without limitation, any fortuitous and natural disasters, strikes, work stoppages, lockouts, fire, riot, failure of communication networks including Internet, power failure, embargo, order, war, terrorism, inability to obtain raw materials, regulation or government controls or other similar event.
U.S. GOVERNMENT RESTRICTED RIGHTS. If a Software is acquired under the terms of a proposal or agreement with the United States
Government or any contractor thereof, the Software is subject to the following restricted rights notice: "This Software is commercial computer software provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, FAR 52.227-17 Alternate III (g)(3), or subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48 CFR 52.227-19, as applicable, and their successor provisions. Contractor/Manufacturer is Objectif Lune Inc., Montréal, Québec, Canada, H1V 2C8.
U.S. EXPORT RULES. You agree that the Software will not be shipped, transferred or exported into any country or used in any manner prohibited by the United States Export Administration Act or any other export laws, restrictions or regulations (collectively the “Export Laws”). In addition, if the Software is identified as export controlled items under the Export Laws, you represent and warrant that you are not a citizen of or otherwise located within an embargoed nation and that you are not otherwise prohibited under the Export Laws from receiving the Software. All rights to use the Software are granted on condition that such rights are forfeited if you fail to comply with the terms of this paragraph.
ONLINE VERSION. You acknowledge that when provided in its online format, this License Agreement has the same effect and same value as if it was signed on a paper version. A printed version of this online License Agreement or any notice sent by electronic mail shall be admissible in litigation as any other business document of the enterprise or register generally kept in paper format.
GOVERNING LAW. This License Agreement shall be governed and construed by the laws of the Province of Quebec or in default by the applicable
Laws of Canada, excluding those provisions relating to conflicts of laws and excluding the United Nations Convention on contracts for the
International Sale of Goods if applicable. The parties hereby irrevocably submit to the jurisdiction of the Courts of the Province of Quebec in the judicial district of Montreal, Canada for any litigation resulting from the present License Agreement, excluding any other jurisdiction.
LICENSED THIRD PARTY COMPONENTS AND SPECIFIC RIGHTS AND LIMITATIONS. As part of this License Agreement, you agree to the specific rights and limitations regarding third parties licensed components bundled in the Software in addition to the rights and limitations already mentioned herein which benefit such third parties, including:
ADOBE® TECHNOLOGY
The term Software includes Adobe Technology and related documentation, and any upgrades, modified versions, updates, additions, and copies thereof.
LICENSE GRANT AND RESTRICTIONS. OL grants you a non-exclusive right to use the Software under the terms of this Agreement. You may make one backup copy of the Software, provided the backup copy is not installed or used on any computer.
Page 4
INTELLECTUAL PROPERTY RIGHTS. The Software is owned by OL and its suppliers, and its structure, organization and code are the valuable trade secrets of OL and its suppliers'; The Software is also protected by United States Copyright law and International Treaty provisions. You may not copy the Software, except as provided in this Agreement. Any copies that you are permitted to make pursuant to this Agreement must contain the same copyright and other proprietary notices that appear on or in the Software. You agree not to
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. If the Software includes font software you may embed the font software, or outlines of the font software, into your electronic documents to the extent that the font vendor copyright owner allows for such embedding. The fonts contained in this package may contain both Adobe and non-Adobe owned fonts. You may fully embed any font owned by Adobe.
DISCLAIMER OF WARRANTY. THE "LIMITED WARRANTY. SOFTWARE PURCHASED ON A PHYSICAL MEDIA" SECTION OF THIS AGREEMENT
STATES THE SOLE AND EXCLUSIVE REMEDIES FOR OL’S BREACH OF WARRANTY. EXCEPT FOR THE FOREGOING LIMITED WARRANTY,
ADOBE AND ITS SUPPLIERS MAKE NO WARRANTY, EXPRESS AND IMPLIED, AS TO THE MERCHANTABILITY, FITNESS FOR ANY PARTICULAR
PURPOSE OR NON-INFRINGEMENT.
LIMITATION OF LIABILITY. IN NO EVENT WILL ADOBE OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY DAMAGES, CLAIMS OR COSTS
WHATSOEVER OR ANY CONSEQUENTIAL, INDIRECT, INCIDENTAL DAMAGES, OR ANY LOST PROFITS OR LOST SAVINGS, EVEN IF AN ADOBE
REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY THIRD PARTY.
Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, or limitations on how long an implied warranty may last, so the above limitations may not apply to you. To the extent permissible, any implied warranties are limited to thirty (30) days. This warranty gives you specific legal rights. You may have other rights which vary from state to state or jurisdiction to jurisdiction.
EXPORT RULES. You agree that the Software will not be shipped, transferred or exported into any country or used in any manner prohibited by the United States Export Administration Act or any other export laws, restrictions or regulations (collectively the "Export
Laws"). ln addition, if the Software is identified as export controlled items under the Export Laws, you represent and warrant that you are not a citizen, or otherwise located within, an embargoed nation (including without limitation Iran, Iraq, Syria, Sudan, Libya, Cuba, North
Korea, and Serbia) and that you are not otherwise prohibited under the Export Laws from receiving the Software. All rights to use the
Software are granted on condition that such rights are forfeited if you fail to comply with the terms of this Agreement.
GENERAL PROVISIONS. If any part of this Agreement is found void and unenforceable, it will not affect the validity of the balance of the
Agreement, which shall remain valid and enforceable according to its terms. This Agreement shall not prejudice the statutory rights of any party dealing as a consumer.
TRADEMARKS. Adobe and Adobe PDF Library are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
ORACLE® TECHNOLOGY
EXPORT. You agree that U.S. export control laws and other applicable export and import laws govern your use of the programs, including technical data; additional information can be found on Oracle's Global Trade Compliance web site located at http://www.oracle.com/us/products/export/index.html
. You agree that neither the programs nor any direct product thereof will be exported, directly, or indirectly, in violation of these laws, or will be used for any purpose prohibited by these laws including, without limitation, nuclear, chemical, or biological weapons proliferation.
DISCLAIMER OF WARRANTY AND EXCLUSIVE REMEDIES. THE PROGRAMS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
WE FURTHER DISCLAIM ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT SHALL WE BE LIABLE FOR ANY
INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR
DATA USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, EVEN IF WE HAVE BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. OUR ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN NO EVENT EXCEED ONE THOUSAND
DOLLARS (U.S. $1,000).
NO TECHNICAL SUPPORT. Oracle technical support organization will not provide technical support, phone support, or updates to you for the programs licensed under this agreement.
Page 5
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. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in
FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle America, Inc., 500 Oracle Parkway, Redwood City,
CA 94065."
END OF AGREEMENT. You may terminate this agreement by destroying all copies of the programs. We have the right to terminate your right to use the programs if you fail to comply with any of the terms of this agreement, in which case you shall destroy all copies of the programs.
RELATIONSHIP BETWEEN THE PARTIES. The relationship between you and us is that of licensee/licensor. Neither party will represent that it has any authority to assume or create any obligation, express or implied, on behalf of the other party, nor to represent the other party as agent, employee, franchisee, or in any other capacity. Nothing in this agreement shall be construed to limit either party's right to independently develop or distribute software that is functionally similar to the other party's products, so long as proprietary information of the other party is not included in such software.
OPEN SOURCE. - "Open Source" software - software available without charge for use, modification and distribution - is often licensed under terms that require the user to make the user's modifications to the Open Source software or any software that the user 'combines' with the Open Source software freely available in source code form. If you use Open Source software in conjunction with the programs, you must ensure that your use does not: (i) create, or purport to create, obligations for us with respect to the Oracle programs; or (ii) grant, or purport to grant, to any third party any rights to or immunities under our intellectual property or proprietary rights in the Oracle programs. For example, you may not develop a software program using an Oracle program and an Open Source program where such use results in a program file(s) that contains code from both the Oracle program and the Open Source program (including without limitation libraries) if the Open Source program is licensed under a license that requires any "modifications" be made freely available. You also may not combine the Oracle program with programs licensed under the GNU General Public License ("GPL") in any manner that could cause, or could be interpreted or asserted to cause, the Oracle program or any modifications thereto to become subject to the terms of the GPL.
ECLIPSE TECHNOLOGY
The Software may include unmodified Eclipse redistributables available at www.eclipse.org
. The Eclipse redistributables are submitted to the
WARRANTY DISCLAIMER and LIMITATION OF LIABILITY provisions of this Agreement, and to the Eclipse Public License - v 1.0 that can be found at https://www.eclipse.org/legal/epl-v10.html
.
ENTIRE AGREEMENT. This License Agreement contains the entire understanding of the parties. There are no representations, warranties, promises, covenants of understandings, oral or otherwise, other than those herein contained.
Page 6
OL is a registered trademark of Objectif Lune Inc.
All registered trademarks displayed are the property of their respective owners.
© 2019 Objectif Lune Incorporated. All rights reserved.
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement