Documente Academic
Documente Profesional
Documente Cultură
Installation Guide
CLES100500-IGD-EN
OpenText Imaging Enterprise Scan
Installation Guide
CLES100500-IGD-EN
Rev.: 12. Sept. 2013
This documentation has been created for software version 10.5.
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
Tel: 35 2 264566 1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Email: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com
Disclaimer
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 v
i About This Documentation ................................................................. v
i.i Target Readership ............................................................................ v
i.ii Structure of This Documentation ........................................................ v
i.iii Documentation Overview .................................................................. vi
i.iv How to Find Documentation .............................................................. vi
ii Contact Information ......................................................................... vii
iii Terms and Conventions ................................................................... vii
GLS Glossary 43
For monitoring the Document Pipelines, you need to install OpenText Document
Pipeline Info. For more information, see section 2.1.4 “Installing Document Pipeline
Info” in OpenText Document Pipeline - Installation and Upgrade Guide (AR-IDPDP).
Recommended OpenText recommends that you read the OpenText Imaging Enterprise Scan - User and
reading Administration Guide (CLES-UGD) before you start installing Enterprise Scan.
“Introduction“ on page v
This chapter describes the contents of the manual and the conventions used. It
also gives an overview of the available documentation for Enterprise Scan.
“Installation Overview“ on page 11
This chapter describes the methods of installation, and general installation
requirements, as well as how to install, upgrade, and remove Enterprise Scan.
“Installing Enterprise Scan“ on page 15
This chapter describes how to install Enterprise Scan.
“Using a Silent Installation and Mass Rollout“ on page 19
This chapter describes how to install Enterprise Scan silently and how to
configure the install.ini.
“Installing Additional Languages“ on page 27
This chapter describes how to install other languages than English.
“Installing OpenText Document Pipelines“ on page 29
This chapter describes how to install Document Pipelines locally for Enterprise
Scan.
Glossary on page 43
This chapter describes the product specific technical terms.
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 OpenText Knowledge Center.
See also the Customization Guide or Scenario Guide of the respective leading
application.
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.
ii 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
• Usage tips, help files, and best practices for customers and partners.
• Information on product releases.
• User groups and forums where you can ask questions to OpenText experts.
If you need additional assistance, you can find OpenText Corporate Support
Contacts at http://support.opentext.com/.
Note: If you copy command line examples from a PDF, be aware that PDFs
can contain hidden characters. OpenText recommends that you copy from
the HTML version of the document, if it is available.
KEY NAMES
Key names appear in ALL CAPS, for example:
Press CTRL+V.
<Variable name>
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, <server_name> 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.
Caution
Cautions help you avoid irreversible problems. Read this information
carefully and follow all instructions.
Important
Important notes help you avoid major problems.
<Registry_branch>,
The <Registry_branch> 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.
For details on Microsoft Registry branches and user specific settings, refer to
your Microsoft documentation and online help. For example, search for
<IXOS_ROOT>
<IXOS_ROOT> is used as an abbreviation of <Open Text installation directory>.
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.
Enterprise Scan are delivered as an ISO image in the Knowledge Center. The ISO
image contains the installation package with all required components and software,
and the documentation. You can download the ISO image in Knowledge Center at
https://knowledge.opentext.com/knowledge/llisapi.dll/Open/13055578 .
Notes
• Only the products and versions specified in the Release Notes are supported.
Other versions have not been tested and are therefore not officially
supported for this version. The Release Notes contain the definitive list of
supported versions. Any other versions mentioned in the product
documentation are superseded by the versions specified in the Release
Notes.
• If no service pack, maintenance level, patch level or similar is explicitly
mentioned for a specific software version, OpenText supports each service
pack, maintenance level, and patch level released for a third-party product
version, unless explicitly stated otherwise. If details of a specific service
pack, patch and maintenance level, and so on are given, this one and all
subsequent ones are supported.
You can find the latest version of the Release Notes in Knowledge Center at https://
knowledge.opentext.com/knowledge/llisapi.dll/open/15881843.
The following software must be installed on the computer on which you want to
install Enterprise Scan:
• Version 3.1 of the Microsoft Windows Installer.
• Microsoft .NET Framework 4.0. You can install it from the installation media
under <CD-ROM>\redist\DotNet_40.
• Microsoft Visual C++ 2005 x86 redistributable with minimum version 8.0.61001.
You can install it from the installation media under <CD-ROM>\redist
\VC80_Runtime.
• Microsoft Visual C++ 2008 x86 redistributable with minimum version 9.0.30729.
You can install it from the installation media under <CD-ROM>\redist
\VC90_Runtime.
• Microsoft Visual C++ 2010 x86 redistributable with minimum version 10.0.40219.
You can install it from the installation media under <CD-ROM>\redist
\VC100_Runtime.
Context restric- When upgrading, there are certain restrictions on the installation context. The
tions 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
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.
• 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 16.
The local installation automatically installs the same features that were already
installed on the computer.
For silent installation, you select all features in the install.ini file, no matter
if they were installed in the older version or not.
Version 9.7.x/10.0.0/10.2.0
This versions do not need to be removed. An automatic upgrade is provided.
But if you want to remove Enterprise Scan, use the Remove installation type in
the Program Maintenance dialog box of the installation, or use Add or Remove
Programs in Control Panel.
2.1 Requirements
Make sure you fulfill the “Installation Requirements” on page 11. Additionally,
consider the following requirements and information for some scenarios.
SAP scenarios For the configuration of SAP scenarios, see OpenText Archiving and Document Access
for SAP Solutions - Scenario Guide (ER-CCS).
FaxLink With FaxLink, you can process and archive faxes received in Microsoft Outlook or
Lotus Notes with Enterprise Scan. For supported versions of Microsoft Outlook and
Lotus Notes, see the Release 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 install 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 For many archiving scenarios, you need a Document Pipeline to store the documents
Pipeline 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, see “Installing
OpenText Document Pipelines“ on page 29.
PDF support You can archive documents in PDF format. There is an option for creating non-
searchable PDF files, and options for creating searchable PDF files, as follows:
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).
Tip: Alternatively, you can start the installation for Enterprise Scan
directly from <CD-ROM>:\Win32Cln\Enterprise Scan 10.5.0.msi.
b. Select Enterprise Scan.
c. Proceed with the master setup and start 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.
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.
Notes
• This path must be readable and writeable for Windows users using
the Enterprise Scan computer. The installation 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 15.
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 Use Remote Pipeline.
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).
8. In the Ready to Install the Enterprise Scan dialog box, click Install.
The installation will copy all the necessary files, configure the registry and
update the configuration files.
Tip: This is the last opportunity to cancel the installation without making
any changes on the computer.
9. In the Installation Wizard Completed dialog box, click Finish.
10. Optional Install the Document Pipelines required for your archiving scenarios.
For more information, see “Installing OpenText Document Pipelines“
on page 29.
11. Optional The installation of English for GUI and Online Help is part of the
installation. If you need other languages, you must install them additionally.
For more information, see “Installing Additional Languages“ on page 27.
Notes
• If you start Enterprise Scan for the first time you have to confirm that
Enterprise Scan is allowed to communicate to private and/or public
networks.
• The default ports used by Enterprise Scan are 11989 and 11990. If these ports
are not available Enterprise Scan automatically chooses a port in the range of
11989 to 12489.
Each time you run the installation, the same log file is used. New logs are added at
the end of the file.
You can perform the Enterprise Scan installation silently and distribute it to user
computers. The silent installation uses the install.ini file for configuration of the
installation settings. The install.ini file is located in the Win32Cln directory.
Language in- The silent language installation does not need a configuration file. You can add an
stallation additional language on the user computers with a simple command. For more
information, see “Installing Additional Languages“ on page 27.
1. Copy the installation files. For more information, see “Copying the Installation
Files” on page 19.
2. Configure the installation components and parameters in the install.ini file.
For more information, see “Configuring the install.ini File” on page 20.
3. Distribute the start command, and then start the installation. For more
information, see “Starting the Silent Installation” on page 24.
Notes
• Make sure you have write permissions for the computer you will be
installing on.
• Before starting the installation, install the msiexec program.
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 configure 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 install.ini 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 (“;”).
[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
[ECR_DIALOG] DocumentPipelineDirectory=
Defines the Document Pipeline directory and creates the registry entry
[HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\Common]DPDIR.
If DocumentPipelineDirectory is empty, the default value
<CommonAppDataFolder>\OpenText\DPDIR is used.
LivelinkServerHostname=
Defines the Content Server name and creates the registry entry
[HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\6.0\Scan\HKLM
\Extensions\Ixos.Scan.Extension.Livelink.ChangeLogin]"S:Server.
If DocumentPipelineDirectory is empty, the default value
<CommonAppDataFolder>\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 16.
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.
ArchiveServerList=
Defines the Archive Server name and creates the registry entry
[HKEY_LOCAL_MACHINE\SOFTWARE\IXOS\IXOS_ARCHIVE\6.0\Scan\HKLM
\Extensions
\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.
vu_Language
• Default value: <empty>
• Description: Specifies default GUI language if not set within the request. Use
language identification as specified in ISO-639, for example en, de, pt, es, jp,
cs. For supported languages, see the Release Notes.
By default the system´s regional settings are used.
[AddProject]
Defines the path to launch additional executable batch files or registry files. For
examples, see Example 3-1, “Default install.ini file” on page 22.
Notes
• Do not use .reg in the directory structure.
• You can only use the values ExecuteableFilePath1 to
ExecuteableFilePath9.
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
; Has an affect only if 'ShowUpgradeDialog=NO' and the user interface level is
'silent' or 'basic'.
; Select 'Yes' if you want to upgrade from an older version of Open Text Clients and
; preserve your settings. Choosing 'NO' will initiate a new, clean Open Text Clients
installation.
[LIVELINK_DIALOG]
LivelinkServerHostname=
; Content Enterprise Server hostname
[ECR_DIALOG]
DocumentPipelineDirectory=
; Enter a path for the Document Pipeline folder.
; Environment variables are expanded
; If empty, the default is <CommonAppDataFolder>\OpenText\DPDIR
; The CommonAppDataFolder property is the full path to the file directory containing
application data for all users.
DocumentPipelineHost=localhost
; Hostname of 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 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=
Non-silent installation
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 "<directory_of_Enterprise_Scan_10.5.0.msi_file>
\Enterprise Scan
10.5.0.msi" SILENTFILE=<directory_of_install.ini_file>
\install.ini /l*v "<directory_of_log_file>
\MsiIxClientSetup.log"
Example:
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=<directory_of_install.ini_file>\install.ini
in the command line if the install.ini file is located in the same
directory as the msi file and you are installing for the first time.
Silent installation
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 "<directory_of_Enterprise_Scan_10.5.0_file>\
Enterprise Scan
10.5.0.msi" SILENTFILE=<directory_of_install.ini_file>
\install.ini /qb /l*v "<directory_of_log_file>
\MsiIxClientSetup.log"
Example:
Notes
• If you want a fully silent installation without status bar display, use
the /qn parameter instead of the /qb parameter.
• 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=<directory_of_install.ini_file>\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.
You can install languages other than English for GUI and Online Help. For
supported languages, see the Release Notes.
English is automatically installed with the installation of Enterprise Scan. You can
install other languages using the Language Setup. For each language, a msi
installation file is provided which you can install locally or with silent rollout. For
more information, see “To install additional languages as silent installation:“
on page 27.
The installation files for additional languages are not included in the installation
media. You can download the installation files in Knowledge Center at https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/13055578.
Notes
• All command-line options described here are standard command line
options of Windows Installer used in command line mode.
• For all installations in Terminal servers enabled environments, first change
to install mode for installing the applications.
If you want to generate a log file add the following parameter at the end of the
command:
/l*v "<directory_of_log_file>\Enterprise Scan - 10.5.0
Languages.msi.log"
If you install a new language Enterprise Scan does not change the language
after start. To change the default language, you must start the language
installation with the additional parameterSETASDEFAULTLANGUAGE=1.
Example:
msiexec.exe /i"\\server01\OpenText_Clients\Languages\Livelink
Enterprise Scan - 10.5.0 French Language.msi"
SETASDEFAULTLANGUAGE=1
This section describes how to install OpenText Document Pipelines for Enterprise
Scan only. For more information about other Document Pipeline installations, see
OpenText Document Pipeline - Installation and Upgrade Guide (AR-IDPDP). This guide
covers the installation of all Document Pipeline components on all supported
systems.
Installation files The installation files for Document Pipeline are not included in the installation
media. You can download the installation files with the respective product, for
example Document Pipeline for Content Server which is delivered with Content
Server. For more information, see the particular sections below.
Supported For information about which Document Pipeline versions are supported for
versions Enterprise Scan, see the Enterprise Scan Release Notes.
Silent installa- You can install Document Pipelines silently, using the msiexec program. For a
tion 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.2 Requirements
You can install Document Pipelines either on the Enterprise Scan computer or on a
stand-alone computer. For additional configuration steps for the stand-alone
installation, see “Installing Document Pipeline on a Stand-alone Computer”
on page 31.
Upgrading An upgrade of Document Pipelines is not supported. You must remove previous
Document versions and enter settings again. Use the Add or Remove Programs tool provided
Pipeline
in Windows Control Panel. Also delete the installation directory (<IXOS_ROOT>)
entry in the registry. For more information, see OpenText Document Pipeline -
Installation and Upgrade Guide (AR-IDPDP).
Monitoring tools For monitoring the Document Pipelines, the OpenText Document Pipeline Info is
needed. For more information, see section 2.1.4 “Installing Document Pipeline Info”
in OpenText Document Pipeline - Installation and Upgrade Guide (AR-IDPDP).
Archive modes 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).
Important
• This directory must be readable and writable for Windows users
using the Enterprise Scan computer.
• Use the same directory during the Enterprise Scan and the Document
Pipeline installations. On the Enterprise Scan computer, enter the
path using the Universal Naming Convention (UNC), that is
\\<Document Pipeline_host_name>\<directory_path>. On the
stand-alone computer, use either the local directory path or the UNC
path.
• If you have installed Document Pipeline version 10.1.1 or higher, 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.
2. Install the Document Pipeline(s) with the relevant components on the stand-
alone computer. For more information, see “Installing OpenText Document
Pipelines” on page 32.
The installation file for the Document Pipeline for DocuLink is available in the
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 and Upgrade Guide (AR-IDPDP).
The installation file for the OpenText Document Pipeline for SAP® Solutions is
available in the 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 and Upgrade Guide (AR-IDPDP).
The installation file for the OpenText TCP Document Pipelines is available in the
Knowledge Center (https://knowledge.opentext.com/knowledge/cs.dll/Open/
14503202).
The installation file for the Document Pipeline for Content Server is available in the
Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll/open/
17753296).
When modifying the Document Pipeline for Content Server installation, trigger
the modification only by the Command prompt opened with the Run as
Administrator option.
1. Start the installation using the master setup. From the Content Server
installation media, run <CD-ROM>:\Mastersetup.exe.
3. 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.
4. 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 master setup selects the depending
components automatically.
If Document Pipeline Perl and Document Pipeline Base are not yet installed,
see OpenText Document Pipeline - Installation and Upgrade 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 and Upgrade
Guide (AR-IDPDP).
• Document Pipeline Remote Interface is optional. It is used for an HTTP
\HTTPS connection to an Document Pipeline installed on a different
computer. For more information, see “Installing the Document Pipeline
Remote Interface” on page 36.
5. 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.
6. 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. In the Custom Setup dialog box, perform the following actions, and then click
Next.
b. To check how much disk space is required for installation, click Disk
Usage.
9. 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 10.
For HTTP/HTTPS connection, continue with Step 11
10. 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.
11. 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.
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.
12. If you selected the HTTP/HTTPS connection, enter the following Content Server
and HTTP/HTTPS settings, and then click Next.
Use HTTPS
Only select this check box if you want to use the HTTPS connection. Clear it
if you are using the HTTP connection.
Prerequisites 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.
• An HTTP\HTTPS connection between the scan station and the Document
Pipeline computer must be possible.
You can obtain the installation file for the Document Pipeline Remote Interface
(dp_remote_interface-<version>.msi) in the Knowledge Center (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/14711031).
Installation files The installation files for Enterprise Scan OCR are not included in the installation
media. You can download the installation files in the Knowledge Center (https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/13055578).
6.1 Requirements
You can install Enterprise Scan OCR on the Enterprise Scan computer only.
Upgrading An upgrade of Enterprise Scan OCR is not supported. You must remove previous
Enterprise Scan versions. Use the Add or Remove Programs tool provided in Windows Control
OCR
Panel.
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.
Tip: This is the last opportunity to cancel the setup without making any
changes on the computer.
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.
3. From the list of modules that are available for installation, select the Enterprise
Scan Webinterface module, and then click Install.
Archive Server
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
Capture Center
Configuration files
DocTools
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
Document Stack
DPDIR
The directory in which the documents are temporarily stored while being
processed by the Document Pipeline.
Endorser
Enterprise Scan
FaxLink
Folder
Index
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
Leading application
Administrative tool for setting up and maintaining the Archive Server and its
components, such as archives, devices, disk buffers, jobs, archive modes and
users.
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.