pdfdocs Desktop 3.2 Open Text Content Server 10 Integration Installation & configuration Copyright DocsCorp International Unit Trust

Transcription

1 pdfdocs Desktop 3.2 Open Text Content Server 10 Integration Installation & configuration Copyright DocsCorp International Unit Trust Level 5, 66 Clarence St Sydney NSW 2000 AUSTRALIA Ph: Fax: Web: Oct 11 th 2012

2 2

3 Table of contents TABLE OF CONTENTS... 3 PDFDOCS DESKTOP 3 CONTENT SERVER INTEGRATIONS... 4 OPEN TEXT CONTENT SERVER INTEGRATION... 4 PRE-REQUISITES... 6 MICROSOFT.NET FRAMEWORK 3.5 SP MICROSOFT VISUAL J# VERSION 2.0 REDISTRIBUTABLE PACKAGE... 6 SYSTEM REQUIREMENTS... 7 pdfdocs Desktop 3 - System Requirements... 7 INSTALLING PDFDOCS DESKTOP MODULE WITH CONTENT SERVER 10.2 UPDATE HOW TO ADD AND CONFIGURE CS10 INTEGRATION... 8 INSTALLING PDFDOCS DESKTOP MODULE WITH CONTENT SERVER 10.2 UPDATE HOW TO ADD AND CONFIGURE CS10 INTEGRATION... 9 OPEN TEXT ENTERPRISE CONNECT CONFIGURATION ENABLING CS10 INTEGRATION IN PDFDOCS DESKTOP HOW TO ADD AND CONFIGURE CONTENT SERVER INTEGRATION SERVER.INI SETTINGS SERVER.INI VALUES Integration specific settings Handling of Reserved documents Binder import all versions check box visibility Save into Content Server as Generation or Shortcut default naming behavior Content Server Integrator window in Content Server and Save Into options from pdfdocs Desktop TROUBLE SHOOTING COM.OPENTEXT.API.LLIOEXCEPTION: COULD NOT ACCESS SERVER PDFDOCS DESKTOP SUPPORT HOW TO LOG A SUPPORT CALL

4 pdfdocs Desktop 3 Content Server Integrations This document provides information on how to install and configure integration between pdfdocs Desktop and Open Text Content Server, and Open Text Enterprise Connect. Please note that there are different module installations for releases of Open Text Content Server 10.2 update 4 (or earlier, refer to page 8), and Open Text Content Server 10.2 update 5; 6 & 7 (refer to page 9). For sites running Open Text Enterprise Connect 10 with Open Text Livelink 9.7.1, please refer to separate installation guide, which can be referenced by clicking here Livelink For details on how to use functionality within pdfdocs Desktop, please refer to the user guide accessible through the Help menu within pdfdocs Desktop. For detailed information on available integration workflows, please refer to the Open Text Content Server 10 Integration User Guide. Open Text Content Server Integration Save into Open Text Content Server from pdfdocs; o A new document; o A new version; o A new rendition; o A new generation; o A new shortcut; Import from Open Text Content Server; Send to pdfdocs from Open Text Content Server (Individual & Multiple documents) o Load into Project; o as PDF; o Create as new document; o Create as new version; o Create as new rendition; o Create as new generation; o Create as new shortcut; 4

5 o Apply digital signature; o OCR PDF to Word; Drag n Drop a single document from Open Text Content Server to pdfdocs Desktop; Send to pdfdocs from Open Text Enterprise Connect (Individual documents only); o Load into Project; o as PDF; o Create as new document; o Create as new version; o Create as new rendition; o Create as new generation; o Create as new shortcut; o Apply digital signature; o OCR PDF to Word; Check Open Text Content Server version in Binder Project. 5

6 Pre-requisites Microsoft.NET Framework 3.5 SP1 Before installing pdfdocs Desktop 3, please check Microsoft.NET Framework 3.5 SP1 or higher Service Pack has been installed on each workstation or server. Install Microsoft.NET Framework 3.5 SP1 on your workstation by referring to our Knowledge Base article KB 55 - pdfdocs Desktop 3 requires Microsoft.NET Framework 3.5 at time of installation. Microsoft Visual J# Version 2.0 Redistributable Package Enables LAPI functionality, and requires version 2.0 in order for support of pdfdocs Desktop. 6

7 System Requirements These system requirements are a guideline to the minimum requirements DocsCorp recommends for the installation of pdfdocs Desktop. pdfdocs Desktop 3 - System Requirements Minimum Client Workstation Specifications Recommended Client Workstation Specifications Processor 1GHz 1.6GHz or faster Operating System Microsoft Windows XP with SP2 or 3 (32-bit and 64-bit) Microsoft Windows Vista with or without SP1 (32- bit and 64-bit) Microsoft Windows 7 (32-bit and 64-bit) Microsoft Windows Server 2003 with SP2 (32-bit and 64-bit) running Terminal Services / Citrix Metaframe Microsoft Windows Small Business Server 2003 with SP1 (32-bit and 64-bit) Microsoft Windows Server 2008 (32-bit and 64-bit) Microsoft Windows XP with SP2 or 3 (32-bit and 64-bit) Microsoft Windows Vista with or without SP1 (32-bit and 64-bit) Microsoft Windows 7 (32-bit and 64-bit) Microsoft Windows Server 2003 with SP2 (32-bit and 64-bit) running Terminal Services / Citrix Metaframe Microsoft Windows Small Business Server 2003 with SP1 (32-bit and 64-bit) Microsoft Windows Server 2008 (32-bit and 64-bit) Memory 512MB 1GB or higher Hard Disk Approximately 250MB of available hard-disk space for installation and up to an additional 100MB of working space for files being converted, depending on the size of files being converted. Approximately 250MB of available hard-disk space for installation and up to an additional 100MB of working space for files being converted, depending on the size of files being converted. Microsoft.NET Framework Microsoft.NET Framework 3.5 SP1 Microsoft.NET Framework 3.5 SP1 Microsoft Office (Optional Integration) Microsoft Office 2010 (32 bit & 64 bit) Microsoft Office 2007 Microsoft Office 2003 with SP1 Microsoft Office XP with SP2 Microsoft Office 2010 (32 bit & 64 bit) Microsoft Office 2007 Microsoft Office 2003 with SP2 or higher Microsoft Office XP with SP3 or higher (Optional Integration) MAPI compliant system MAPI compliant system (e.g. Microsoft Outlook or Lotus Notes) Other Third Party Adobe Reader 6.01 Adobe Reader 9.1 or higher 7

8 Installing pdfdocs Desktop module with Content Server 10.2 update 4 How to add and configure CS10 Integration These instructions and download links are for installed versions of Open Text Content Server 10.2 update 4 or earlier. Refer to separate section for Open Text Content Server 10.2 update 5; 6 or 7 on page 9. For minimum specifications for pdfdocs Desktop, please refer to the Administrator guides on the DocsCorp download portal. Download pdfdocsll_2_0_1.zip file from the following link zip Extract contents of pdfdocsll_2_x_x.zip to the Open Text staging directory, for example C:\OpenText\Staging Log in to Open Text Content Server Administrator Go to Module Administration and Install Modules Go to Module Administration and select Install Modules for a new installation, or Upgrade if upgrading from an earlier server module. Content Server will prompt you for your administrators password. Enter password after which a prompt to restart Content Server, select Continue. pdfdocs Integration module will now be installed. 8

9 Installing pdfdocs Desktop module with Content Server 10.2 update 5; 6 & 7 How to add and configure CS10 Integration These instructions and download links are for installed versions of Open Text Content Server 10.2 update 5; 6 or 7 only. Refer to separate section for Open Text Content Server 10.2 update 4 (or earlier) on page 8. Please note that Open Text Content Server 10.2 SP2 is yet to be tested. For minimum specifications for pdfdocs Desktop, please refer to the Administrator guides on the DocsCorp download portal. Download pdfdocsll_2_0_2.zip file from the following link zip Extract contents of pdfdocsll_2_x_x.zip to the Open Text staging directory, for example C:\OpenText\Staging Log in to Open Text Content Server Administrator, go to Module Administration and select Install Modules for a new installation, or Upgrade if upgrading from an earlier server module. Select pdfdocs Integration, which should appear due to extracted files residing in the staging directory. Content Server will prompt you for your administrators password. Enter password after which a prompt to restart Content Server, select Continue. pdfdocs Integration module will now be installed. 9

10 Open Text Enterprise Connect configuration Enterprise Connect (EC10) connectivity will need to be configured in order for pdfdocs user interfaces to function correctly. As part of a standard deployment of EC10, Open Text Services will be deployed. pdfdocs Desktop needs to make reference to the EC10 plugin ID, if not known, then this can be referenced through: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Enterprise Connect\Solutions\ In this example, the Enterprise Connect xml plugin is located under the CS folder. Once this has been determined, this reference needs to be added to the EC PluginID field in pdfdocs Desktop accessed through Edit > Settings > Integrations > General > Content Server. Please refer to Enabling CS10 Integration in pdfdocs Desktop on page 11 for further information. 10

11 Enabling CS10 Integration in pdfdocs Desktop Install pdfdocs Desktop by following the administrator installation guides available through the download pages on the client portal Once pdfdocs Desktop is installed, please follow these steps. How to add and configure Content Server Integration From pdfdocs Desktop select Edit > Settings > Integration > General This will launch the integration settings window. Select Content Server, and enter in your Content Server name; port number; user name; user password and EC PluginID. To determine the EC PluginID value, please refer to Open Text Enterprise Connection configuration section on page 10. Clicking OK will restart pdfdocs Monitor, from which point Content Server integration will be enabled. Save into Content Server will appear as an option in the pdfdocs Desktop toolbar and right click menu options. 11

12 Server.ini settings server.ini values A number of options for pdfdocs Desktop can be managed via the server.ini and users pdfdocs.ini documents. For complete information on the full range of these ini settings, please refer to the administrator guides available through the downloads page on the DocsCorp portal. Content Server specific server.ini settings are as follows: [Content Server] Integration specific settings CS_port=2099 CS_server=localhost CS_username=admin CS_password=password EC_Pluginid=CS (refer to notes on page 10 for further information on EC_Pluginid) Handling of Reserved documents CS_ReserveDocBehaviourPrompt=True CS_ReserveDocDefaultBehaviour=YES (YES/YESTOALL/NO/NOTOALL) Binder import all versions check box visibility CS_ImportAllVersions=True Save into Content Server as Generation or Shortcut default naming behavior CS_CheckOnAutoGenerateGenerationName=True CS_CheckOnAutoGenerateShortcutName=True 12

13 Content Server Integrator window in Content Server and Save Into options from pdfdocs Desktop CS_DisableLoadIntopdfDocs=False CS_Disable AsPdf=False CS_DisableCreateAsNewDocument=False CS_DisableCreateAsNewVersion=False CS_DisableCreateAsNewRendition=False CS_DisableCreateAsNewGeneration=False CS_DisableCreateAsNewShortcut=False CS_DisableApplyDigitalSignature=False CS_DisableOCRPDFToWord=False Please note that references for hiding, are not functional, but are planned for a future release. CS_HideLoadIntopdfDocs=False CS_Hide AsPdf=False CS_HideCreateAsNewDocument=False CS_HideCreateAsNewVersion=False CS_HideCreateAsNewRendition=False CS_HideCreateAsNewGeneration=False CS_HideCreateAsNewShortcut=False CS_HideApplyDigitalSignature=False CS_HideOCRPDFToWord=False 13

14 Trouble shooting The following items may assist you in some error circumstances where documents fail to arrive in pdfdocs Desktop from Content Server. com.opentext.api.llioexception: Could not access server There may be a situation where documents sent from pdfdocs Desktop to CS10, successfully arrive in CS10, however documents sent to pdfdocs Desktop from CS10 fail to arrive. This is due to the different methods that pdfdocs Desktop has to employ to facilitate these two workflows. Sending documents to pdfdocs Desktop to CS10 employs webservices; if the port number has been configured incorrectly the document fails to arrive in pdfdocs Desktop. No error is passed. Please check that the correct port number has been entered in to the integration settings in pdfdocs Desktop, under Edit > Settings > Integration > General > Content Server. You can confirm what your port number is through this test: C:\OPENTEXT\webservices\dotnet\les-services\Web.Config <appsettings> <add key="livelink.host" value="localhost"/> <add key="livelink.port" value="2099"/> <add key="livelink.encoding" value="default"/> </appsettings> Please note: C:\OPENTEXT is the CS10 installation folder path. ERROR LOG: The below error is thrown by pdfdocs Desktop when the CS10 server name or port number is incorrect. com.opentext.api.llioexception: Could not access server You will see this message written to the users pdfdocs.log file, located under C:\program files\pdfdocs\pdfdocs.log We cannot pass a Message Box because we cannot identify a precise way for correct error detection in all scenarios. 14

15 pdfdocs Desktop Support How to log a support call We are committed to helping our customers get the most out of their investment in our software. In addition to our reliable products, you can count on our dedicated team of experienced support professionals to provide fast, dependable service for your organization. Please click here to log a support call. 15

16 Copyright DocsCorp International Unit Trust All rights reserved. pdfdocs is a trademark of DocsCorp International Unit Trust. This program is licensed to be installed on the number of workstations shown. pdfdocs cannot be installed simultaneously on any more workstations than that specified, regardless of the location of those workstations. Each user under Windows Terminal Services, or similar technology which has pdfdocs available, is deemed a 'workstation' according to this license. pdfdocs is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this program, or any portion of it, may result in severe civil and criminal penalties, and offenders will be prosecuted to the maximum extent possible under law. 16