OpenText Imaging Enterprise Scan 10.2.0 - Installation Guide English (CLES100200-IGD-EN-2).pdf...
OpenText Imaging Enterprise Scan Installation Guide This guide describes the installation of OpenText Imaging Enterprise Scan and OpenText Document Pipelines.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan Installation Guide CLES100200-IGD-EN-2 Rev.: 14. Mar. 2013 This documentation has been created for software version 10.2. It is also valid for subsequent software versions as long as no new document version is shipped with the product or is published at https://knowledge.opentext.com. Open Text SA 40 Avenue Monterey , Luxembourg, Luxembourg L-2163 Tel: 35 2 264566 1 Open Text Corporation 275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1 Tel: +1-519-888-7111 Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440 Fax: +1-519-888-0677 Email:
[email protected] FTP: ftp://ftp.opentext.com For more information, visit http://www.opentext.com
Copyright © 2013 by Open Text Corporation OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text SA or other respective owners. Disclaimer No Warranties and Limitation of Liability Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.
Table of Contents
PRE
Introduction
i i.i ii ii.i ii.ii ii.iii iii iv
About This Documentation ................................................................. v Target Readership ............................................................................ v Structure of This Guide ...................................................................... v Documentation Overview .................................................................. vi How to Find Documentation .............................................................. vi Contact Information ......................................................................... vii Terms and Conventions ................................................................... vii About OpenText Imaging .................................................................. ix
1
General Information and Requirements ................................ 11
1.1 1.1.1 1.1.2 1.2 1.3 1.4
Methods of Installation ..................................................................... Local Installation ............................................................................. Mass Rollout and Distribution ........................................................... Installations at a Glance .................................................................. General Installation Requirements .................................................... Removing Enterprise Scan ..............................................................
2
Upgrading Enterprise Scan .................................................... 15
3
Installing Enterprise Scan ...................................................... 17
3.1 3.2 3.3
Requirements ................................................................................. 17 Installing Enterprise Scan ................................................................ 18 Troubleshooting the Installation ........................................................ 20
4
Using a Silent Installation and Mass Rollout ........................ 21
4.1 4.1.1 4.1.2 4.1.3 4.2
Configuring a Silent Installation ........................................................ Copying the Installation Files ........................................................... Configuring the install.ini File ........................................................... Starting the Installation .................................................................... Using Central Software Distribution ..................................................
5
Installing OpenText Document Pipelines .............................. 29
5.1 5.2 5.3 5.4 5.4.1
Overview and Background Information ............................................. Requirements ................................................................................. Installing Document Pipeline on a Stand-alone Computer .................. Installing OpenText Document Pipelines ........................................... Installing OpenText Document Pipeline for DocuLink .........................
29 30 31 32 32
OpenText Imaging Enterprise Scan
iii
CLES100200-IGD-EN-2
v
11 11 11 12 12 13
21 21 22 25 27
Table of Contents
iv
5.4.2 5.4.3 5.4.4 5.4.5
Installing OpenText Document Pipeline for SAP Solutions ................. Installing OpenText TCP Document Pipelines ................................... Installing Document Pipeline for Content Server ................................ Installing the Document Pipeline Remote Interface ............................
6
Installing Enterprise Scan Webinterface ............................... 39
GLS
Glossary
OpenText Imaging Enterprise Scan
32 32 33 36
41
CLES100200-IGD-EN-2
Preface
Introduction i About This Documentation This documentation describes the installation of OpenText Imaging Enterprise Scan (Enterprise Scan), OpenText Document Pipelines relevant for scanning scenarios and Enterprise Scan Webinterface. For monitoring the Document Pipelines, you need to install OpenText Document Pipeline Info. For information about installing, see section 2.1.4 “Installing Document Pipeline Info” in OpenText Document Pipeline - Installation Guide (ARIDPDP).
i.i
Target Readership This documentation is intended for installers, and system administrators of Enterprise Scan. It assumes knowledge of the administration of a network system, and a basic knowledge of Enterprise Scan.
Recommended reading
OpenText recommends that you read the OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD) before you start installing Enterprise Scan.
ii Structure of This Guide This guide consists of the following chapters: “Introduction“ on page v General information about this documentation, related documents and contacts. “General Information and Requirements“ on page 11 Information about general installation requirements, as well as how to install, upgrade, and remove Enterprise Scan. “Installing Enterprise Scan“ on page 17 Information about installing and troubleshooting Enterprise Scan. “Using a Silent Installation and Mass Rollout“ on page 21 Information about installing Enterprise Scan silently and configuring the install.ini. “Installing OpenText Document Pipelines“ on page 29 Information about installing Document Pipelines locally for Enterprise Scan.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
v
Introduction
ii.i
Documentation Overview The following documentation is available for Enterprise Scan: Release Notes The Release Notes describe in detail the software supported by the product and important dependencies, as well as any last-minute changes regarding the documentation which should be made known. The current version of the Release Notes is available in the OpenText Knowledge Center. OpenText Imaging Enterprise Scan - Installation Guide (CLES-IGD) This manual covers the installation and upgrade of Enterprise Scan, the installation of the Document Pipelines and the Enterprise Scan Webinterface. OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD) This manual covers the administration and how to use Enterprise Scan. The following documentation is available for related topics: OpenText Document Pipelines - Overview and Import Interfaces (AR-CDP) This manual explains the OpenText Document Pipelines. It describes how to monitor the Document Pipelines, a description of their processes and components, advanced tasks and in-depth information. It also describes the doctools in detail. See also the Customization Guide or Scenario Guide of the respective leading application.
ii.ii
How to Find Documentation You can find the product documentation in the following locations: •
The product ISO image comprises the complete product in one *.iso file. The product ISO image is available in the OpenText Knowledge Center. To access the ISO image, select the product family page, and click the Downloads link.
•
The documentation for all products and all supported versions is available in the OpenText Knowledge Center. See the Release Notes for details and links. In the Knowledge Center, select the product family page, and then click the Documentation link. If the required product belongs to the OpenText Content Server family, click the Content Server Module Documentation link, and then select the product from the list. Note: You can find the latest information on manuals and online help files for each product in the corresponding Release Notes. This includes the identification codes of the current documentation.
vi
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
Introduction
ii.iii
Contact Information OpenText Online (http://online.opentext.com/) is a single point of access for the product information provided by OpenText. You can access the following support sources through OpenText Online: •
Communities
•
Knowledge Center
OpenText Online Communities ( https://communities.opentext.com/communities/ cs.dll/open/OpenTextOnlineCommunity) provide the following resources: OpenText Online Communities (http://communities.opentext.com/communities/ livelink.exe/open/OpenTextOnlineCommunity) •
Usage tips, help files, and best practices for customers and partners.
•
Information on product releases.
•
User groups and forums where you can ask questions of OpenText experts.
The OpenText Knowledge Center (https://knowledge.opentext.com) is OpenText's corporate extranet and primary site for technical support. The Knowledge Center is the official source for the following: •
Product downloads, patches, and documentation including Release Notes.
•
Discussion forums, Online Communities, and the Knowledge Base.
•
OpenText Developer Network (OTDN), which includes developer documentation and programming samples for OpenText products.
If you need additional assistance, you can find OpenText Corporate Support Contacts at http://support.opentext.com/.
iii Terms and Conventions It is assumed that the reader is familiar with the relevant operating system and current computer terminology. User interface This format is used for elements in the graphical user interface (GUI), such as buttons, names of icons, menu items, and fields. Filenames, commands,
and sample data This format is used for file names, paths, URLs, and commands at the command prompt. It is also used for example data, text to be entered in text boxes, and other literals. Note: If you copy command line examples from a PDF, be aware that PDFs can contain hidden characters. OpenText recommends copying from the HTML version of the document, if it is available.
CLES100200-IGD-EN-2
Installation Guide
vii
Introduction
KEY NAMES Key names appear in ALL CAPS, for example: Press CTRL+V. Angled brackets < > are used to denote a variable or placeholder. The user replaces the brackets and the descriptive content with the appropriate value. For example, becomes serv01. Internal cross-references Click the cross-reference to go directly to the reference target in the current document. External cross-references External cross-references are usually text references to other documents. However, if a document is available in HTML format, for example, in the Knowledge Center, external references may be active links to a specific section in the referenced document. Warnings, notes, and tips
Caution Cautions help you avoid irreversible problems. Read this information carefully and follow all instructions. Important Important notes help you avoid major problems. Note: Notes provide additional information about a task. Tip: Tips offer you quicker or easier ways of performing a task. Specific conventions
In this documentation, the following additional conventions are used: %Variable name%
The percent signs %...% are used to denote a Microsoft Windows environment variable. You should use the value that is set on your system. To find the value of all environment variables set on your Windows computer, type the set command at the command prompt. To find the value of a particular environment variable set on your Windows computer, type the echo %variable name% command at the command prompt (for example echo %TEMP%).
, The variable must be replaced by either HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE, depending on which registry settings you want to access. Settings located in the HKEY_CURRENT_USER Registry branch are user-specific. Settings located in the HKEY_LOCAL_MACHINE Registry branch are user-independent.
viii
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
Introduction
For details on Microsoft Registry branches and user specific settings, refer to your Microsoft documentation and online help. For example, search for “HKEY_CURRENT_USER” in Windows online help and read the paragraph labeled “Users” regarding “Default security settings”.
is used as an abbreviation of . You should use the value that is set on your system:
Windows platform Value of the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\IXOS_ARCHIVE_ROOT
UNIX platform Value of the system variable IXOS_ARCHIVE_ROOT
Tip: To display the variable, logon as root user and type the set command or the echo $IXOS_ARCHIVE_ROOT command at the command prompt.
iv About OpenText Imaging OpenText Imaging is the front end client software used with most products of Systems based on OpenText Archive Server. OpenText Imaging is used to display archived documents and to send documents to the archive or similar document repository. OpenText Imaging comprises the following independent packages: OpenText Imaging Viewers and DesktopLink The following clients are designed for end users: •
OpenText Imaging Windows Viewer (Windows Viewer) is a Windows client application designed for viewing various image and printlist formats, adding notes and annotations, and desktop scanning and archiving.
•
OpenText DesktopLink (DesktopLink) is a Windows client application that allows users to archive their documents in TIFF or PDF format and to link them to business objects managed in leading applications like SAP systems.
•
OpenText Imaging Java Viewer (Java Viewer) is a Java applet that is installed on the Web server and downloaded to the user's computer when they open a document. The user can view various image and printlist formats and add notes and annotations to the documents.
Administrators also need the following: OpenText Imaging Configuration (Imaging Configuration) to configure and administrate the Windows applications of OpenText Imaging, that is DesktopLink and Windows Viewer. OpenText Imaging Web Viewer OpenText Imaging Web Viewer (Web Viewer) is a pure HTML viewer designed for occasional users. It is installed on the Web Server and does not need to be
CLES100200-IGD-EN-2
Installation Guide
ix
Introduction
installed on client computers. The user can view various image and printlist formats, add notes and view annotations. OpenText Imaging Enterprise Scan The client is designed for end users and scan administrators: •
OpenText Imaging Enterprise Scan (Enterprise Scan) is a Windows application designed for mass scanning, indexing and archiving.
Administrators will also need to install and use the following components: •
OpenText Document Pipelines allows Enterprise Scan (Document Pipelines) to pass the documents to Archive Server and send the link to the leading applications.
•
OpenText Document Pipeline Info (Document Pipeline Info) is used for monitoring and controlling the Document Pipelines.
•
OpenText Archive Monitoring Web Client (Archive Monitoring Web Client) is used to monitor the Document Pipelines and the resources of the Document Pipeline workstation.
A detailed list of products supported by OpenText Imaging is provided in the Products Compatibility Matrix. For more information, see https:// knowledge.opentext.com/knowledge/llisapi.dll/properties/1040043376_722.
x
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
Chapter 1
General Information and Requirements The product OpenText Imaging Enterprise Scan is delivered as an ISO image in the Knowledge Center. You can download the ISO image here: https:// knowledge.opentext.com/knowledge/llisapi.dll/Open/13055578 The ISO image contains the following components: •
Enterprise Scan installation package with all required components and software
•
Documentation for Enterprise Scan
1.1 Methods of Installation You can install OpenText Imaging in the following ways:
1.1.1
•
Local installation on one workstation
•
Mass rollout or distribution on a large number of workstations
Local Installation Use local installation if you want to install Enterprise Scan on a dedicated workstation. If you want to install Enterprise Scan on a large number of computers, you can use mass rollout. For a detailed description of local installation, see “Installing Enterprise Scan” on page 18.
1.1.2
Mass Rollout and Distribution You can install OpenText Imaging Clients as well as additional languages silently and then distribute them on user workstations within the company. To do so, you copy the installation files to a file server, configure the configuration files to define what will be installed, and provide a command to start the preconfigured installation on the user workstations. For a detailed description of silent installation, see “Using a Silent Installation and Mass Rollout“ on page 21.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
11
Chapter 1 General Information and Requirements
1.2 Installations at a Glance The Enterprise Scan installation media contains the installation files for Enterprise Scan. You can start the installation from the setup navigation page, which you can access by, clicking Install the software on the Welcome page. If you do not want to use this page, you can find the complete path to the setup files in the sections that describe the local installations.
1.3 General Installation Requirements Before you start the installation or upgrade, see the Release Notes for detailed information on: •
Supported operating systems
•
SAP systems and SAP GUI versions
•
Compatibility of OpenText Imaging and Archive Server versions
•
Software and hardware requirements and restrictions
You can find the latest version of the Release Notes in the Knowledge Center: https://knowledge.opentext.com/knowledge/llisapi.dll/open/15881843 The following software must be available on the computer on which you want to install OpenText Imaging Clients: •
Version 3.1 of the Microsoft Windows Installer.
•
Microsoft .NET Framework 2.0 SP2 and 4.0. You can install it from the installation media under \redist\DotNet_20_SP2 or \redist \DotNet_40.
•
Microsoft Visual J# 2.0 redistributable. It is required for proper functioning of Enterprise Scan's scripting extension. You can install it from the installation media under \redist\jsharpredist_2.0_X86_en or \redist \jsharpredist_2.0_X64_en.
•
Microsoft Visual C++ 2005 x86 redistributable with minimum version 8.0.50727. You can install it from the installation media under \redist \VC80_Runtime.
•
Microsoft Visual C++ 2008 x86 redistributable with minimum version 9.0.21022. You can install it from the installation media under \redist \VC90_Runtime.
•
Microsoft Visual C++ 2010 x86 redistributable with minimum version 10.0.30319. You can install it from the installation media under \redist \VC100_Runtime.
Before you start the installation: •
12
OpenText recommends copying the installation media to a permanent network share and installing from the network location.
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
1.4. Removing Enterprise Scan
•
All applications, processes, services, and devices belonging to Systems based on OpenText Archive Server must be terminated or stopped before starting the installation on the client computer.
•
Sign in as a user with local administrator rights.
1.4 Removing Enterprise Scan Version 10.2.x Use the Remove setup type in the Program Maintenance dialog box of the setup, or use Add or Remove Programs in Control Panel. Version 9.5.x/9.7.x/10.0.x This versions do not need to be uninstalled. An automatic upgrade is provided. If you want to uninstall Enterprise Scan, use the Remove setup type in the Program Maintenance dialog box of the setup, or use Add or Remove Programs in Control Panel. Version 6.0 This version does not need to be uninstalled. An automatic upgrade is provided. If you want to uninstall Enterprise Scan, use the Remove setup type in the Program Maintenance dialog box of the setup, or use Add or Remove Programs in Control Panel. You need access to the 6.0 installation files when you uninstall the client. Access to original installation files For upgrading and removing version 6.0, you need to access the original installation files at the same location as they were during installation. Otherwise, you get an error message such as, “The feature you are trying to use is on a network resource that is unavailable.” This is a known bug in the MSI. To provide access to the installer files, you have the following options: •
Insert the original installation CD-ROM.
•
Map a path and navigate to a copy of the installation files in the network.
•
Copy the installation CD-ROM to a local drive. Then run this command from the command line: msiexec / i "\installername. msi" Reinstall=All ReinstallMode=vomus
The command line option forces Windows to reinstall the product, and if a newer version of the installer is used, it upgrades the existing installation. The installation can then be uninstalled normally through the Control Panel.
CLES100200-IGD-EN-2
Installation Guide
13
Chapter 2
Upgrading Enterprise Scan The installation setup provides an upgrade from version 6.0, 9.5.x, 9.7.x and 10.0.x. The settings will be automatically converted to the new version. For upgrading and removing version 6.0 make sure that the original installation files are available during upgrade. The settings of the previous installation will be used for the upgrade. For more information, see Access to original installation files on page 13. Context restrictions
When upgrading, there are certain restrictions on the installation context. The installation context refers to the settings in the Customer Information dialog box: •
Anyone who uses this computer: “Per-machine” context
•
Only for me: “Per-user” context
The following table shows the supported combinations: Installation context of previous version
Installation context of new version
Per-user
Per-machine
Per-machine
Per-machine
Note: With Enterprise Scan version 10.0.0 and later only “per-machine” installation is supported. Before you start the upgrade of Enterprise Scan, the Document Stacks must be empty. Make sure that all the documents in all document stacks are stored safely. There are two ways to do this: •
Archive the documents.
•
Export the documents to external storage and import them after the upgrade.
To upgrade Enterprise Scan: •
The steps for upgrading are the same as the steps for a new installation of Enterprise Scan. For more information, see “Installing Enterprise Scan” on page 18. The local installation automatically installs the same features that were already installed on the computer.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
15
Chapter 3
Installing Enterprise Scan 3.1 Requirements For general installation requirements, see “General Installation Requirements” on page 12. Additionally, consider the following requirements and information for some scenarios. SAP scenarios
FaxLink
For the configuration of SAP scenarios, see OpenText Archiving and Document Access for SAP Solutions - Scenario Guide (ER-CCS). With FaxLink, you can process and archive faxes received in Microsoft Outlook or Lotus Notes with Enterprise Scan. Refer to the Release Notes for supported versions of Microsoft Outlook and Lotus Notes. •
Install Microsoft Outlook to use the Microsoft Exchange Input Connector for faxes received in Microsoft Exchange before you install Enterprise Scan.
•
Install Lotus Notes Client to use the Lotus Notes Input Connector for faxes received in Lotus Notes before you have installed Enterprise Scan.
You can find the configuration of the FaxLink input connectors in section 9.7 “Configuring Fax Input” in OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD). Document Pipeline
For many archiving scenarios, you need a Document Pipeline to store the documents on the Archive Server and to send information about the document to the leading applications. You must create a dedicated Document Pipeline directory where the documents are temporarily stored. Do not use a non-local directory, except when using a stand-alone Document Pipeline. For more information on remote Document Pipeline, see “Installing Document Pipeline on a Stand-alone Computer” on page 31. To access the remote Document Pipeline, use UNC names instead of mapped drives. For installation of Document Pipelines, see “Installing OpenText Document Pipelines“ on page 29.
PDF support
You can archive documents in PDF format. There is an option for creating nonsearchable PDF files, and options for creating searchable PDF files, as follows: Internal PDF creator This software creates PDF files without search capability. You can read the archived files by using Acrobat Reader, but you cannot search for text in these files (see section 11.5.11 “Defining Advanced Settings for Archiving” in OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD)).
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
17
Chapter 3 Installing Enterprise Scan
OpenText Rendition Server Through the Document Pipeline for Content Server, the Rendition Server creates PDF files with search capability. You can read the archived files with Acrobat Reader, and you can search for text in these files by using the Find or Search function. For installation, see “Installing Document Pipeline for Content Server” on page 33. For configuration, see section 11.5.7 “Archiving Documents on Content Server Using Document Pipeline (Searchable PDF Files)” in OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD). Note: Software and licenses for OpenText Rendition Server must be purchased separately. Contact your OpenText Sales Representative. PDF creation using OCR doctool During archiving through the OpenText Document Pipeline, the OCR doctool creates searchable PDF or PDF/A files. This feature is available for Document Pipeline for Content Server, Document Pipeline for DocuLink, and OpenText Document Pipeline for SAP® Solutions (see section 11.5.11 “Defining Advanced Settings for Archiving” in OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD)).
3.2 Installing Enterprise Scan To install Enterprise Scan: 1.
Start the installation using the master setup: a.
b. c.
From the OpenText Imaging Enterprise Scan installation media, run :\Mastersetup.exe. Tip: Alternatively, you can start the setup program for Enterprise Scan directly from :\Win32Cln\ Enterprise Scan 10. 2.0. msi. Select Enterprise Scan. Proceed with the master setup and start the installation.
The Enterprise Scan installation wizard opens and guides you through the installation. 2.
In the Welcome dialog box, click Next.
3.
If a previous version of Enterprise Scan is installed on your computer, the Enterprise Scan Upgrade dialog box opens. If this dialog box opens, do one of the following, and then click Next. •
Click An upgrade from will be performed. to apply the settings used in the previous version.
•
Click A new clean installation of Enterprise Scan will start. to clear the settings and start a new installation. Note: A new installation overwrites some settings from previously installed programs, such as Document Pipeline folder, and Archive Server.
18
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
3.2. Installing Enterprise Scan
4.
In the License Agreement dialog box, read the license agreement, select the I accept the terms in the License Agreement check box, and then click Next.
5.
In the Setup Type dialog box, click Custom to perform the following actions, and then click Next. a.
To change the installation folder, click Change.
b.
To check how much disk space is required for installation, click Disk Space.
6.
In the Content Server dialog box, enter the name of Content Server where the documents will be stored, and then click Next.
7.
In the Document Pipeline dialog box, enter the following settings, and then click Next. Document Pipeline folder Path for the Document Pipeline directory where documents will be temporarily stored, for example C:\DPDIR. Notes •
This path must be readable and writeable for Windows users using the Enterprise Scan workstation. Setup does not create the directory as part of the installation, so it must either already exist or you must create it manually.
•
Use the same path for Enterprise Scan and for the Document Pipeline installation. For more information, see “Document Pipeline” on page 17.
Document Pipeline host Name of the computer where Document Pipeline is located, for example localhost. This is only required if Document Pipeline is installed as a standalone Document Pipeline on a separate computer. Note: If you want to use more than one Document Pipeline with Enterprise Scan, you must install all of them on the same computer. Archive Server Name of Archive Server on which the archive modes will be configured. Remote Pipeline To enable the Remote Pipeline, select the check box. Choose protocol HTTP or HTTPS. Enter the Port. The default value is 8080. For more information, see “Installing the Document Pipeline Remote Interface” on page 36 and section 11.5.8.1 “Configuring Remote Document Pipelines” in OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD).
CLES100200-IGD-EN-2
Installation Guide
19
Chapter 3 Installing Enterprise Scan
8.
In the Ready to Install the Enterprise Scan dialog box, click Install. Setup will copy all the necessary files, configure the registry and update the configuration files. Tip: This is the last opportunity to cancel the setup without making any changes on the computer. Tip: You must install the Document Pipelines required for your archiving scenarios. For more information, see “Installing OpenText Document Pipelines“ on page 29.
3.3 Troubleshooting the Installation The ScanClientSetup.log file contains detailed information about operations performed during the setup. You can find out which parameters have been used, which registry keys have been written, and more information about warning or error messages. If you contact OpenText Customer Support after an unsuccessful installation, you may be asked to send the Setup_ScanClient.log file. Windows Vista or Windows 7
The default location of the Setup_ScanClient.log file on Windows Vista or Windows 7 is in the %LocalAppData%\OpenText\ Enterprise Scan directory, for example C:\Documents and Settings\ Administrator\ Local\ Open Text\ Enterprise Scan\ Setup_ScanClient. log.
Windows XP
The default location of the Setup_ScanClient.log file on Windows XP is in the %LocalAppData%\OpenText\ Enterprise Scan directory, for example C:\Documents and Settings\ Administrator\ Local Setting\ Application Data\ Open Text\ Enterprise Scan\ Setup_ScanClient. log. Each time you run the setup, the same log file is used. New logs are added at the end of the file.
20
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
Chapter 4
Using a Silent Installation and Mass Rollout You can perform the Enterprise Scan installation silently and distribute it to user workstations. The silent installation uses the install.ini file for configuration of the installation settings. The install.ini file is located in the Win32Cln directory.
4.1 Configuring a Silent Installation This section describes a silent installation using the configured install.ini file. Notes •
Make sure you have write permissions for the computer you will be installing on.
•
Before starting the installation, install the msiexec program.
Tip: You can generate several different installations if you want to create variations of the setup program for different user groups. To complete a silent installation, you must perform these tasks, which are described in detail in the sections that follow:
4.1.1
•
Copy the installation files. For more information, see “Copying the Installation Files” on page 21.
•
Configure the installation components and parameters in the install.ini file. For more information, see “Configuring the install.ini File” on page 22.
•
Distribute the installation command and start the installation. For more information, see “Starting the Installation” on page 25.
Copying the Installation Files There are two ways to prepare the installation files: Copy only the install.ini file Copy only the install.ini file from the Win32Cln directory to a shared folder, which is further referenced as the . This method saves disk space but requires the installation media for the installation procedure. You can use several install.ini files to prepare different pre-configured installations. Rename them, for example install01.ini. Copy all files Copy all software components from the installation media to the shared folder, which is further referenced as the .
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
21
Chapter 4 Using a Silent Installation and Mass Rollout
With this method, installations are performed using the
. You do not need the installation media. You must copy all files in the root directory to the , but at least the directories Win32Cln and redist under the root directory.
Tip: The docu folder contains the user documentation in PDF format. You can also copy it to the to provide remote access to the user documentation. You can use several install.ini files to prepare different pre-configured installations. Rename them, for example install01.ini.
4.1.2
Configuring the install.ini File The install.ini configuration file controls the installation procedure. The install.ini file is a template that you can use to create your own ini files for installation. You can use more than one file to preconfigure different types of installations from a file server. Before you start the installation on user workstations, we recommend a test installation with the configured install.ini file. The different startup modes for running preconfigured installations are described in “Starting the Installation” on page 25. Make sure the files are writable before you start. You can edit the files with any ASCII editor, such as Notepad or WordPad. You can set default values for all parameters in the install.ini file and you can preconfigure the installation so that no entries from users are requested. This avoids potential user input errors and allows an unattended installation on a large number of computers using the setup commands or a software distribution tool. Important Change only the values, and do not change section names and value identifiers! This would affect the installation and may prevent client functioning after installation. The installation procedure works according to the following scheme: 1. It uses a default value. 2. If a value is set in install.ini, it will overwrite the default value. 3. If a value is not set in install.ini and a registry key is set, it will overwrite the default value. Note: The Release Notes provides information about registry entries corresponding to the installation parameters in install.ini. The file is divided into sections for the various installation dialogs and parameters. There are detailed comments in English for each section in the file. All parameters are described in the file as well. Lines with descriptions start with a semi-colon (“;”). The install.ini file contains the following sections:
22
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
4.1. Configuring a Silent Installation
[Common] Defines the installation target directory setting INSTALL_ROOT and creates the registry entry [HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE \CLIENT_INST_SCAN]INSTALL_ROOT. If INSTALL_ROOT is empty, the default value %PROGRAMFILES%\OpenText\Scan is used. ErrorMessage=YES Shows severe errors, that is errors that will abort the installation. ShowUpgradeDialog=YES Shows the upgrade dialog. If the user selects NO, the following registry trees will be deleted: •
HCU\\SOFTWARE\\IXOS\\IXOS_ARCHIVE\\6.0\\Scan
•
HKLM\\SOFTWARE\\IXOS\\IXOS_ARCHIVE\\6.0\\Scan
If no upgrade dialog is shown, the registry trees are not deleted. [LIVELINK_DIALOG] Defines the name of the Content Server and creates the registry entry [HKEY_LOCAL_MACHINE\ SOFTWARE\ IXOS\ IXOS_ARCHIVE\ 6.0\ Scan\ HKLM\ Extensions\ Ixos. Scan. Extension. Livelink. ChangeLogin ]"S:Server.
[ECR_DIALOG] Defines the Document Pipeline directory and creates the registry entry [HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\Common]DPDIR. If [ECR_DIALOG] is empty, the default value \OpenText \DPDIR is used. DocumentPipelineHost=localhost Defines the Document Pipeline name and creates the registry entry [HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\Common]DPHOST. RemoteInterfaceMode=no Defines the remote Document Pipeline name and creates the registry entry
[HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\Common]REMOTEINTERFACEMODE.
For more information on the remote Document Pipeline, see “Installing Enterprise Scan” on page 18.
RemoteDPLESPort=8080 Defines the remote Document Pipeline port and creates the registry entry
[HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\Common]REMOTEINTEDPLESPORT.
RemoteDPLESProtocol=http Defines the remote Document Pipeline protocol, for example http or https and creates the registry entry [HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE \Common]REMOTEINTERFACEMODE.
CLES100200-IGD-EN-2
Installation Guide
23
Chapter 4 Using a Silent Installation and Mass Rollout
ArchiveServerList= Defines the Archive Server name and creates the registry entry [HKEY_LOCAL_MACHINE\ SOFTWARE\ IXOS\ IXOS_ARCHIVE\ 6.0\ Scan\ HKLM\ Extension\ Ixos. Scan. Extension. ConfigureServerAndPipeline ]"S:Server.
You can use multiple Archive Server and separate them by |, for example hawaii|aria.
[CAPTURE_CENTER_SERVER] Defines the Capture Center server name and creates the registry entry [HKEY_LOCAL_MACHINE\ SOFTWARE\ IXOS\ Occ Server\ Scan]ServerName. Defines the Capture Center server port and creates the registry entry [HKEY_LOCAL_MACHINE\ SOFTWARE\ IXOS\ Occ Server\ Scan]PortName. [AddProject] Defines the path to launch additional executable batch files or registry files. For examples, see Example 4-1, “Default install.ini file” on page 24. Notes • •
Do not use .reg in the directory structure. You can only use the values ExecuteableFilePath1 to
ExecuteableFilePath9.
Installation with Active Directory Set IntelliMirrorInstallation=YES. Example 4-1: Default install.ini file The default install.ini file illustrates a preconfiguration of an installation. ; Version=OpenText Imaging Enterprise Scan 10.2.0 [Common] INSTALL_ROOT= ; Installation target directory ; Environment variables are expanded ; If empty, default is: %PROGRAMFILES%\OpenText\Scan ErrorMessage=YES ; If this value is different than 'NO', the installation will show error boxes. ShowUpgradeDialog=YES ; 'Yes' if you want to see the 'Open Text Clients Upgrade' dialog. UpgradeFromLastVersion=YES ; obsolete [LIVELINK_DIALOG] LivelinkServerHostname= ; Livelink Enterprise Server hostname [ECR_DIALOG] DocumentPipelineDirectory= ; Enter a path for the Livelink Document Pipeline folder. ; Environment variables are expanded ; If empty, the default is \OpenText\DPDIR ; The CommonAppDataFolder property is the full path to the file directory containing application data for all users. DocumentPipelineHost=localhost
24
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
4.1. Configuring a Silent Installation
; Hostname of Livelink Document Pipeline. RemoteInterfaceMode=no ; Remote Document Pipeline is configured. RemoteDPLESPort=8080 ; Enter a port configured for the Remote Document Pipeline. RemoteDPLESProtocol=http ; Enter a protocol to be used for Remote Document Pipeline (http/https). ArchiveServerList= ; List of possible Livelink Enterprise Archives to select, separated by |. ; Example: ArchiveServerList=hawaii|aria [CAPTURE_CENTER_SERVER] ;Name= ; Hostname of Capture Center Server ;Port= ; Port of Capture Center Server [AddProject] ; NOTE: ; Specify the path to additional executable, Batch files, or Registry files to launch. ; Only 'ExecuteableFilePath1' to 'ExecuteableFilePath9' will be taken by installation. No more values are allowed. ; Do not use '.reg' in the directory structure ; Environment variables are expanded ; Example1 : ExecuteableFilePath1=C:\temp\AddSetup\Sales.exe ; Example2 : ExecuteableFilePath2=\\server\patches\patch.bat ; Example3 : ExecuteableFilePath3=%TEMP%\registry\custom.reg ; ;ExecuteableFilePath1= ;ExecuteableFilePath2= ;ExecuteableFilePath3= ;ExecuteableFilePath4= ;ExecuteableFilePath5= ;ExecuteableFilePath6= ;ExecuteableFilePath7= ;ExecuteableFilePath8= ;ExecuteableFilePath9=
4.1.3
Starting the Installation To start the installation on user workstations: 1.
Distribute the start command to the individual workstation and run the start command on each workstation. You can also use central software distribution tools. For more information, see “Using Central Software Distribution” on page 27).
2.
If you are performing a non-silent installation, the users see the installation assistant and can change the predefined entries there. Use the following command: msiexec.exe /i " \Enterprise Scan 10.2.0.msi" SILENTFILE= \install.ini /l*v "\MsiIxClientSetup.log"
Example:
CLES100200-IGD-EN-2
Installation Guide
25
Chapter 4 Using a Silent Installation and Mass Rollout
msiexec.exe /i "\\server01\OpenText_Clients\Enterprise Scan 10.2.0.msi" SILENTFILE=\\server01\OpenText_Clients\install.ini /l*v "%TEMP%\OpenText\10.2.0\Enterprise Scan\MsiIxClientSetup.log"
Notes •
If the path to the install.ini file or the *.msi file contains any blank spaces, enclose the path in quotation marks to indicate that the whole path is a single parameter. It is acceptable to use quotation marks, even if the path does not contain blank spaces.
•
You can omit SILENTFILE=\install.ini in the command line if install.ini is located in the same directory the msi file and you are installing for the first time.
3.
as
If you are performing a silent installation, the users cannot change the installation settings, because the installation wizard does not appear. If you want to show the users a status bar during installation, use this command: msiexec.exe /i "\ Enterprise Scan 10.2.0.msi" SILENTFILE=\install.ini / qb /l*v "\MsiIxClientSetup.log"
If you want a fully silent installation without status bar display, use the /qn parameter instead of the /qb parameter. Example: msiexec.exe /i "\\server01\OpenText_Clients\Enterprise Scan 10.2.0.msi" SILENTFILE=\\server01\OpenText_Clients\install.ini /qb /l*v "%TEMP%\OpenText\10.2.0\Enterprise Scan\MsiIxClientSetup.log"
Notes •
If the path to the install.ini file or the *.msi file contains any blank spaces, enclose the path in quotation marks to indicate that the whole path is a single parameter. It is acceptable to use quotation marks, even if the path does not contain blank spaces.
•
You can omit SILENTFILE=\install.ini
in the command line if install.ini is located in the same directory as the msi file and you are installing for the first time. 4.
26
Other command line options - A number of command line options can be passed to the msiexec.exe program. Their syntax and semantics correspond to the ones used with the Windows Installer in command line mode. Details about these command line options can be found in the Microsoft Windows Installer documentation, for example in http://msdn.microsoft.com/library/default.asp? url=/library/en-us/msi/setup/command_line_options.asp.
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
4.2. Using Central Software Distribution
4.2 Using Central Software Distribution You can use central software distribution tools like Microsoft Systems Management Server (SMS) and ON Command CCM (CCM) for an installation on a large number of computers. The distribution procedure depends on the tool you use. For more information, refer to your manufacturer's handbook.
CLES100200-IGD-EN-2
Installation Guide
27
Chapter 5
Installing OpenText Document Pipelines This section describes how to install OpenText Document Pipelines for Enterprise Scan only. For details about other Document Pipeline installations, see OpenText Document Pipeline - Installation Guide (AR-IDPDP). This guide covers the installation of all Document Pipeline components on all supported systems. Installation files
Supported versions Silent installation
The Document Pipeline installation files are not included in the Enterprise Scan installation media. They are delivered with the respective product, for example Document Pipeline for Content Server is delivered with Content Server. For more information, see the particular sections below. For information about which Document Pipeline versions are supported for Enterprise Scan, see the Enterprise Scan Release Notes. You can install Document Pipelines silently, using the msiexec program. For a description of the silent installation, see https://knowledge.opentext.com/ knowledge/llisapi.dll/Open/15806655. Note: Silent installation is not supported for Document Pipeline for Content Server because the configuration information cannot be provided during silent installation.
5.1 Overview and Background Information In most scan scenarios, Document Pipelines pass the documents to the storage repository. Additionally, the Document Pipelines can pass document properties, or trigger further actions in the leading applications. The following overview provides a short description of each pipeline and links to more detailed information. OpenText Document Pipeline for DocuLink Technical name: SCR3 This pipeline is used for scan scenarios with OpenText DocuLink for SAP Solutions. You can start the archiving (early and late) of the scanned document directly in DocuLink. The pipeline stores the document in the required archive on Archive Server and passes the document information to DocuLink. OpenText Document Pipeline for SAP Solutions Technical name: R3SC This pipeline is used for typical SAP scan scenarios, such as storing with barcodes and storing for subsequent entry or assignment. The pipeline stores the document in the required archive on Archive Server and passes the information about the DocID and the barcode back to the SAP system.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
29
Chapter 5 Installing OpenText Document Pipelines
OpenText TCP Document Pipelines Technical name: SCDMS This pipeline is used for preindexing and late indexing scenarios with TCP, formerly known as Livelink ECM – Production Document Management. The pipeline stores the document in the required archive on Archive Server and the indexing information in Business Object Layer. In addition, depending on the configuration of the inbox DocTool, it also can be used to trigger a plug-in event. The pipeline is also used for workflow scenarios (psdt doctool). The pipeline stores the document in the required archive on Archive Server, starts a workflow in the process management system, and links the archived document to the process. For detailed information on the inbox DocTool, see section 9.5.2 “Special Customizing Steps for SCDMS Document Pipeline” in OpenText Document Pipelines - Overview and Import Interfaces (AR-CDP) in the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/14503093). For detailed information on the pipeline and the DocTools, see section 9.5.4.4 “Inbox” in OpenText Document Pipelines - Overview and Import Interfaces (ARCDP). Document Pipeline for Content Server Technical name: DPLES This pipeline is used for mass archiving from Enterprise Scan to Content Server. The pipeline offers asynchronous processing and additional processing steps like OCR. A user can keep on scanning and processing documents in Enterprise Scan while the pipeline continues to release documents to Content Server. In combination with OpenText Rendition Server, this pipeline is used for creating searchable PDF files from documents that have been scanned with Enterprise Scan. For more information, see section 11.5.7 “Archiving Documents on Content Server Using Document Pipeline (Searchable PDF Files)” in OpenText Imaging Enterprise Scan - User and Administration Guide (CLES-UGD). Document Pipeline Remote Interface The Document Pipeline Remote Interface is an HTTP\HTTPS connection to a Document Pipeline installed on a different computer. With the Document Pipeline Remote Interface, documents can be sent from the scan station to the Document Pipeline, using HTTP\HTTPS.
5.2 Requirements The Document Pipelines can either be installed on the Enterprise Scan computer or on a stand-alone computer. Additional configuration steps for the stand-alone installation are described in “Installing Document Pipeline on a Stand-alone Computer” on page 31. Sign in as a user with local administrator rights at installation. Upgrading Document Pipeline
30
An upgrade of Document Pipelines is not supported. You must remove previous versions and enter settings again. Use the Add or Remove Programs tool provided in Windows Control Panel. Also delete the installation directory () entry in the registry.
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
5.3. Installing Document Pipeline on a Stand-alone Computer
Monitoring tools
Archive modes
For monitoring the Document Pipelines, the OpenText Document Pipeline Info is needed. For the installation of the Document Pipeline Info, see section 2.1.4 “Installing Document Pipeline Info” in OpenText Document Pipeline - Installation Guide (AR-IDPDP). All Document Pipeline scan scenarios require an Archive Mode. The archive mode defines the logical archive where the documents will be stored, the indexing method, and several additional settings, for example a workflow name or the inbox configuration. For archive mode settings, see section 11 “Configuring Scan Stations” in OpenText Archive Server - Administration Guide (AR-ACN).
5.3 Installing Document Pipeline on a Stand-alone Computer You can install Document Pipelines either on the same workstation where Enterprise Scan has been installed or on a stand-alone computer. To install Document Pipeline on a stand-alone computer: 1.
Create and share a Document Pipeline directory (DPDIR) on the stand-alone computer where the Document Pipeline will be installed. Important
2.
•
This directory must be readable and writable for Windows users using the Enterprise Scan workstation.
•
Use the same directory during the Enterprise Scan and the Document Pipeline installations. On the Enterprise Scan workstation, enter the path using the Universal Naming Convention (UNC), that is \\\. On the standalone computer, use either the local directory path or the UNC path.
•
If you have installed Document Pipeline version 10.1.1, the default values for the DPDIR of Document Pipeline and Enterprise Scan are the same.
•
If have installed an older version of Document Pipeline, you must change the default DPDIR for one of the two products.
Install the Document Pipeline(s) with the relevant components on the standalone computer (see “Installing OpenText Document Pipelines” on page 32).
CLES100200-IGD-EN-2
Installation Guide
31
Chapter 5 Installing OpenText Document Pipelines
5.4 Installing OpenText Document Pipelines 5.4.1
Installing OpenText Document Pipeline for DocuLink Before you start the installation, read “Overview and Background Information” on page 29 and “Requirements” on page 30, and make sure that you have met the requirements. The installation file for the Document Pipeline for DocuLink is available in the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/ llisapi.dll/open/14711031). The installation of the Document Pipeline for DocuLink is described in section 3.1.3 “Installing Document Pipeline for DocuLink” in OpenText Document Pipeline Installation Guide (AR-IDPDP).
5.4.2
Installing OpenText Document Pipeline for SAP Solutions Before you start the installation, read “Overview and Background Information” on page 29 and “Requirements” on page 30, and make sure that you have met the requirements. The installation file for the OpenText Document Pipeline for SAP® Solutions in the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/ llisapi.dll/open/14711031). The installation of the OpenText Document Pipeline for SAP® Solutions is described in section 3.1.2 “Installing Document Pipeline for SAP Solutions” in OpenText Document Pipeline - Installation Guide (AR-IDPDP).
5.4.3
Installing OpenText TCP Document Pipelines Before you start the installation, read “Overview and Background Information” on page 29 and “Requirements” on page 30, and make sure that you have met the requirements. Customizing TCP scenarios might be complex, and for complete information, see section 28.2 “Indexing Scenarios” in OpenText Transactional Content Processing - Customization Guide (TCP-CGD). The installation file for the OpenText TCP Document Pipelines is available in the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/cs.dll/ Open/14503202). The installation of the OpenText TCP Document Pipelines is described in section 10.1 “Installing OpenText TCP Document Pipelines” in OpenText Transactional Content Processing - Installation Guide (TCP-IGD).
32
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
5.4. Installing OpenText Document Pipelines
5.4.4
Installing Document Pipeline for Content Server Before you start the installation, read “Overview and Background Information” on page 29 and “Requirements” on page 30, and make sure that you have met the requirements. The installation file for the Document Pipeline for Content Server is available in the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/ llisapi.dll/open/17753296). Notes •
Limitations for Windows 7 and Windows 2008 server when UAC = ON When modifying the Document Pipeline for Content Server installation, trigger the modification only by the Command prompt opened with the Run as Administrator option.
•
Limitations for Windows XP To install the Document Pipeline Base successfully on Windows XP operating systems, you must select the Run the service as user option during installation.
To install Document Pipeline for Content Server: 1.
Sign in as a user with administrator rights.
2.
Start the installation using the master setup. From the Content Server installation media, run :\Mastersetup.exe.
3.
In the Welcome dialog box, click Next.
4.
In the License Agreement dialog box, read the license agreement, select the I accept the terms in the License Agreement check box, and then click Agree.
5.
In the Selection dialog box, select the components you want to install, and then click Next. •
Document Pipeline for Content Server needs Document Pipeline Perl and Document Pipeline Base. The mastersetup selects the depending components automatically. If Document Pipeline Perl and Document Pipeline Base are not yet installed, see OpenText Document Pipeline - Installation Guide (AR-IDPDP) for a description how to install these components.
•
Document Pipeline Info is optional. It is used for monitoring purposes. For more information, see OpenText Document Pipeline - Installation Guide (ARIDPDP).
•
Document Pipeline Remote Interface is optional. It is used for an HTTP \HTTPS connection to an OpenText Document Pipeline installed on a different computer. For more information, see “Installing the Document Pipeline Remote Interface” on page 36.
CLES100200-IGD-EN-2
Installation Guide
33
Chapter 5 Installing OpenText Document Pipelines
•
6.
Runtime and Core Services are optional. They are used by Document Pipeline Remote Interface. For more information, see OpenText Runtime and Core Services - Installation Guide (ELCS-IGD).
Optional In the Prerequisites dialog box, the master setup indicates which programs must be already installed on the computer. Verify that the required programs are installed. If they are not installed, cancel the wizard, install the required programs, and then restart the wizard.
If the programs are installed, click Next. Tip: This dialog box is not displayed if you install Document Pipeline for Content Server only. 7.
In the Summary dialog box, check if all necessary components are selected. If you want to change the selected components, click Back to change. Click Install to start the installation. The installation of the selected components is performed in the same order as shown on the summary page.
8.
The OpenText Document Pipeline for Content Server installation wizard opens. Click Next.
9.
In the Custom Setup dialog box: a.
Choose the installation path. Click Browse to change the destination folder. Tip: The Reset button has no function in this version.
b. c.
To check how much disk space is required for the installation of the selected components, click Disk Usage. Click Next.
10. In the Content Server Connection dialog box, select Direct RPC connection or HTTP\HTTPS connection, and then click Next. For RPC connection, continue with Step 11. For HTTP/HTTPS connection, continue with Step 12 11. If you selected the RPC connection, enter the following Content Server settings. Obtain the information from your Content Server administrator. Content Server Default value is localhost. Domain of Content Server Domain of Content Server. Content Server User Login Default value is Admin. Default value in case of OTDS authenticated Content Server is
[email protected].
34
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
5.4. Installing OpenText Document Pipelines
The Content Server user must have system administration rights. If the password of Content Server User Login is changed, the Document Pipeline for Content Server setup has to be modified to set the new password. Content Server Password Password of the Content Server user. Content Server Port Default value is 2099. Continue with Step 15. 12. If you selected the HTTP/HTTPS connection, enter the following Content Server settings, and then click Next. Obtain the information from your Content Server system administrator. Content Server Default value is localhost. Content Server Administrator Login Default value is Admin. Default value in case of OTDS authenticated Content Server is
[email protected].
The Content Server administrator must have system administration rights. If the password of Content Server Administrator Login is changed, the Document Pipeline for Content Server setup has to be modified to set the new password. Content Server Administrator Password Password of the Content Server administrator. Port Following port numbers are applicable when the IIS server is used as a Web server for Content Server: Default value for HTTP connection is 80. Default value for HTTPS connection is 443. 13. If you selected the HTTP/HTTPS connection, enter the following Content Server and HTTP/HTTPS settings, and then click Next. Content Server CGI Default value is /livelink/livelink.exe. Use HTTPS Only select this check box if you want to use the HTTPS connection. Clear it if you are using the HTTP connection. Note: If you want to establish the HTTPS connection (SSL) between Enterprise Scan and Content Server, install the Trusted Root Certification Authorities using the web browser.
CLES100200-IGD-EN-2
Installation Guide
35
Chapter 5 Installing OpenText Document Pipelines
Verify Server Certificate Do not select this check box. It could be used for server certificates issued by public entrusted Certificate Authorities but this is not supported in this version. This option is only relevant for HTTPS. HTTP User Login In single sign-on scenarios, provide the Content Server Administrator Login provided in the Content Server Connection (1/3) dialog box. For more information, see Step 12. Also relevant if Verify Server Certificate is selected. HTTP Password In single sign-on scenarios, provide the Content Server Administrator Password provided in the Content Server Connection (1/3) dialog box, see Step 12. Also relevant if Verify Server Certificate is selected. 14. If you selected the HTTPS connection, enter the following HTTPS settings, and then click Next. CA Root Certificates Location Path of the server certificate. OpenText recommends storing the certificate generated using Secure Connect in C:\Program Files\OpenText \Certificates. 15. In the Ready to install dialog box, do one of the following: Click Back if you want to change any of your settings. Click Install to install the OpenText Document Pipeline for Content Server. 16. In the Completing the OpenText Document Pipeline for Content Server installation dialog box , click Finish. 17. Click Finish to close the master setup.
5.4.5
Installing the Document Pipeline Remote Interface The Document Pipeline Remote Interface is an HTTP\HTTPS connection to a Document Pipeline that is installed on a different computer. With the Document Pipeline Remote Interface, documents can be sent from the scan station to the Document Pipeline using HTTP\HTTPS.
Prerequisites
36
The following components must be installed and configured on the computer hosting the Document Pipeline: •
OpenText Runtime and Core Services (Java and Tomcat need to be installed)
•
OpenText Document Pipeline Perl
•
OpenText Document Pipeline Base
•
At least one “real” OpenText Document Pipeline, for example the OpenText Document Pipeline for SAP® Solutions.
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
5.4. Installing OpenText Document Pipelines
•
An HTTP\HTTPS connection between the scan station and the Document Pipeline computer must be possible. Note: It is not necessary to install any additional components on the scan station.
You can obtain the installation file for the Document Pipeline Remote Interface (dp_remote_interface-.msi) in the OpenText Knowledge Center (https:// knowledge.opentext.com/knowledge/llisapi.dll/open/14711031). The installation of Document Pipeline Remote Interface is described in OpenText Document Pipeline - Installation Guide (AR-IDPDP).
CLES100200-IGD-EN-2
Installation Guide
37
Chapter 6
Installing Enterprise Scan Webinterface The Enterprise Scan Webinterface module brings scanning capacity to the Content Server user interface. The indexing feature is also available. Users can scan an image and run an indexing session in the same user interface. Prerequisites
Content Server must be installed before installing the Enterprise Scan Webinterface. To install Enterprise Scan Webinterface: 1.
Start the setup program directly via :
2.
In the Content Server administration dialog box, click Install Module.
3.
From the list of modules that are available for installation, select the Enterprise Scan Webinterface module, and then click Install.
4.
Restart Content Server.
\OT_SCAN_MODULE_10.2.0\escanwebinterface_10.2.0_WIN.exe.
The Enterprise Scan Webinterface installation wizard opens and guides you through the installation.
Now the module is installed and listed in the installed modules.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
39
Glossary Archive Monitoring Web Client It is a graphical user interface for monitoring the Document Pipelines and additional data. Archive Server Archive Server stores documents on long-term storage media. It consists of server software and services, a database instance, connection to and management of storage systems, and administration tools. Archive Mode Specifies the different archiving scenarios used by Enterprise Scan. The archive mode is configured in the OpenText Administration Client. Barcode During mass scanning, Enterprise Scan can detect barcodes or patch codes and separate the documents automatically. Then the barcode or patch code is displayed in the Index field of the Properties tab. Batch Hierarchical document attribute in Enterprise Scan. In the hierarchy of attributes, batch is located above folder. Hierarchical attributes can be assigned to documents automatically during scanning or manually. The attributes are displayed in the Properties view. Capture Center Capture Center is a solution for automatic document classification and data extraction using optical character recognition. Enterprise Scan and Capture Center work together to automate ingestion of documents into repositories and of data into business solutions. Configuration files Configuration files contain configuration information for a particular program. When the program is executed, it consults the configuration file to see what parameters have been set. Important configuration files for OpenText Imaging Clients are the install.ini file, which contains the installation configuration for Windows Viewer, DesktopLink, and Enterprise Scan, and the viewer.cfg files, which contain the configuration information for Java Viewer and Web Viewer. DocTools Programs for automatically processing documents in a Document Pipeline.
CLES100200-IGD-EN-2
OpenText Imaging Enterprise Scan
41
Glossary
Document Group In Enterprise Scan you can subdivide documents in several groups. These groups can be used to divide the archiving tasks between several employees. Document Pipeline A collection of processing modules (DocTools) that are used, for example, to transfer or otherwise process documents to and in the Archive Server. Document Stack All scanned or imported documents that are currently displayed in Enterprise Scan. DPDIR The directory in which the documents are temporarily stored while being processed by the Document Pipeline. Endorser Some scanner models support endorsing, a process in which a stamp that is printed on each scanned sheet to confirm scanning. The endorser is displayed in the Properties tab in Enterprise Scan. Enterprise Scan Short name for OpenText Imaging Enterprise Scan. It is a component of OpenText Imaging. Enterprise Scan is designed for mass scanning scenarios: you can scan documents from various input sources, sort them into documents, and then archive these documents. FaxLink Functionality of Enterprise Scan that connects Enterprise Scan to fax or mail servers, such as Microsoft Exchange Server, or Lotus Domino Server. Folder Hierarchical document attribute in Enterprise Scan. In the hierarchy of attributes, folder is located below batch. Hierarchical attributes can be assigned to documents automatically during scanning or manually. The attributes are displayed in the Properties view. Index Special collection of information used to locate documents or data objects more rapidly during searches. The scan operator can define the index information in a form before archiving the document. The fields of this form are defined in Enterprise Scan itself, with the TCP Modeler or on Content Server.
42
OpenText Imaging Enterprise Scan
CLES100200-IGD-EN-2
Glossary
The term Index has also a second meaning in Enterprise Scan. In the Index field of the Properties tab, the recognized barcode or patch code is displayed. For more information, see Barcode. Indexing Provision of additional information (index) to speed up search functions. When record properties are indexed, values are entered in the properties fields of the records. In general, user input is required here, or the values are automatically extracted and entered from documents or from their context using special processing modules, for example in a Document Pipeline. Leading application Software solution connected to a Content Server product, for example SAP, Siebel, or Microsoft Office SharePoint Server. OpenText Administration Client Administrative tool for setting up and maintaining the Archive Server and its components, such as archives, devices, disk buffers, jobs, archive modes and users. OpenText Archive Monitoring Web Client See Archive Monitoring Web Client. OpenText Imaging Enterprise Scan See Enterprise Scan. Patch code See Barcode. Servtab files Configuration files of the Spawner, which specify which DocTools and processes to start and how to start them. Spawner Service that starts and terminates the DocTools and processes of the Document Pipelines.
CLES100200-IGD-EN-2
Installation Guide
43
