OpenText Intelligent Capture For SAP Solutions 16.7.1 - Administration Guide English (CPIE160701-AGD-EN-04) PDF

OpenText™ Intelligent Capture for SAP®
Solutions
Administration Guide
This guide describes how to install and configure OpenText

Intelligent Capture for SAP® Solutions.
CPIE160701-AGD-EN-04
OpenText™ Intelligent Capture for SAP® Solutions
Administration Guide
CPIE160701-AGD-EN-04
Rev.: 2020-July-06
This documentation has been created for software version 16.7.1.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.
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
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2020 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
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
1 About Intelligent Capture for SAP® Solutions ........................ 5
1.1 How does it work? ............................................................................. 5
1.2 Technology ....................................................................................... 7
1.3 Machine learning ............................................................................... 7
1.4 Architecture and SAP integration ...................................................... 13
1.5 Solutions and profile configuration .................................................... 14
1.6 Supported languages ...................................................................... 16
1.7 Supported image formats ................................................................. 17
2 Installing Intelligent Capture for SAP® Solutions ................. 19

2.1 Installation procedure overview ........................................................ 19
2.2 Prerequisites for the installation ....................................................... 20
2.3 Installing Intelligent Capture for SAP® Solutions ................................ 20
2.4 Installing Asian languages ............................................................... 21
2.5 Installing the Validation Client .......................................................... 21
2.6 Installing Single Click Entry for SAP GUI .......................................... 22
2.7 Installing patches and service packs ................................................. 23
3 Upgrading Intelligent Capture for SAP® Solutions .............. 25
4 Configuring Intelligent Capture for SAP® Solutions ............ 27

4.1 Configuring authorizations for validation user .................................... 27
4.2 Adding a certificate for client/server authentication for secure
communication using HTTPS (optional) ............................................ 28
4.3 Configuring the web service ............................................................. 28
4.3.1 Specifying the application pool ......................................................... 29
4.3.2 Configuring SSL settings for secure communication using HTTPS
(optional) ........................................................................................ 29
4.3.3 Increasing the upload size (IIS 7.0 and later versions) ....................... 30
4.3.4 Configuring internal application settings ............................................ 31
4.4 Configuring tracing .......................................................................... 33
4.4.1 Tracers ........................................................................................... 33
4.4.2 Trace listeners ................................................................................ 33
4.4.3 Trace root path ............................................................................... 34
4.4.4 Trace levels .................................................................................... 34
4.4.5 Trace configuration ......................................................................... 35
4.4.6 Location of trace files and trace configuration files ............................. 38
4.4.7 Format of traces .............................................................................. 38
4.4.8 Analyzing trace files using Trace Viewer ........................................... 39
4.4.8.1 Selecting a trace configuration ......................................................... 41
4.4.8.2 Filtering messages .......................................................................... 42
CPIE160701-AGD-EN-04 Administration Guide iii

Table of Contents
4.4.8.3 Searching trace messages .............................................................. 43

4.5 Controlling cache behavior .............................................................. 44
4.6 Working with configuration data (production system) ......................... 45
4.6.1 Technical configuration data ............................................................ 45
4.6.1.1 Load Manager files .......................................................................... 45
4.6.1.2 Trace configuration files ................................................................... 46
4.6.2 Runtime files ................................................................................... 46
4.6.2.1 Temporary files of Document Reader and Document Extraction ......... 46
4.6.2.2 Trace folder .................................................................................... 46
4.6.3 Registry entries ............................................................................... 46
4.6.4 Microsoft Windows Services ............................................................ 46
4.6.5 Moving Intelligent Capture for SAP® Solutions data to a different
location .......................................................................................... 47
4.6.5.1 Configuring cache location ............................................................... 47
4.6.5.2 Configuring trace file location ........................................................... 47
4.6.5.3 Configuring program data location of components ............................. 47
4.7 Configuring load balancing .............................................................. 48
4.7.1 Understanding the Load Manager .................................................... 48
4.7.2 Configuring cluster nodes ................................................................ 49
4.7.2.1 Changing cluster node properties ..................................................... 50
4.7.2.2 Changing Intelligent Capture for SAP® Solutions Server Node
properties ....................................................................................... 51
4.8 Starting and stopping Microsoft Windows Services on the Intelligent
Capture for SAP® Solutions Server .................................................. 52
4.9 Setting up the SLD registration on the SAP system ........................... 52
5 Monitoring Intelligent Capture for SAP® Solutions .............. 55
6 Configuring high availability .................................................. 57
7 Configuring security ............................................................... 59

7.1 User management and authorization concept ................................... 59
7.2 Logging of security-relevant events .................................................. 59
7.3 Encryption of communication channels ............................................. 60
7.4 Secure configuration ....................................................................... 60
7.5 Security updates ............................................................................. 60
7.6 Responsibilities ............................................................................... 60
8 Troubleshooting ...................................................................... 61
iv OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

Chapter 1
About Intelligent Capture for SAP® Solutions
Information Extraction Service (IES) is used as a common technical term for both of
the following OpenText products:
• OpenText™ Intelligent Capture for SAP® Solutions, formerly known as

OpenText™ Information Extraction Service for SAP® Solutions (IES on premises)
• OpenText™ Core Capture for SAP® Solutions, formerly known as Core Capture
Services for SAP® Solutions (IES cloud)
1.1 How does it work?

Intelligent Capture for SAP® Solutions is the next generation data extraction service
for business documents processed in SAP context. It follows a new paradigm with
regards to integration, operation, deployment and usability.
As a single, unified extraction service, the solution supports OpenText™ Vendor

Invoice Management for SAP® Solutions (Vendor Invoice Management (VIM)) and
OpenText™ Business Center for SAP® Solutions (Business Center) on SAP ERP
Central Component (SAP ECC) and SAP S/4HANA.
Intelligent Capture for SAP® Solutions is easy to:
• Deploy: The configuration is completely done in VIM and Business Center. No

separate configuration in Intelligent Capture for SAP® Solutions is necessary.
• Operate: Intelligent Capture for SAP® Solutions only needs the connection to the
SAP system. No data persists in Intelligent Capture for SAP® Solutions.
• Use: Intelligent Capture for SAP® Solutions comes with preconfigured best
practice solutions for processing business documents which fit to VIM and
Business Center solutions.
Business Intelligent Capture for SAP® Solutions supports the following business scenarios:
scenarios/
solutions
Vendor Invoice Management
• OpenText™ Invoice Capture Center for SAP® Solutions. For more

information, see section 10 “ICC integration” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
• Intelligent Capture for SAP® Solutions. For more information, see section 9.2
“Integration with Information Extraction Service” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide (VIM-CGD).
CPIE160701-AGD-EN-04 Administration Guide 5

Chapter 1 About Intelligent Capture for SAP® Solutions
Business Center
• Solution for Incoming Sales Orders. For more information, see part III
“Solution for Incoming Sales Orders” in OpenText Business Center for SAP
Solutions - Scenario Guide (BOCP-CCS).
• Solution for Incoming Quotations. For more information, see part IV
“Solution for Incoming Quotations” in OpenText Business Center for SAP
• Solution for Incoming Delivery Notes. For more information, see part V
“Solution for Incoming Delivery Notes” in OpenText Business Center for SAP
• Solution for Incoming Order Confirmations. For more information, see part
VI “Solution for Incoming Order Confirmations” in OpenText Business Center
for SAP Solutions - Scenario Guide (BOCP-CCS).
• Solution for Incoming Remittance Advices. For more information, see part
VII “Solution for Incoming Remittance Advices” in OpenText Business Center
for SAP Solutions - Scenario Guide (BOCP-CCS).
• Solution for Incoming HR Documents. For more information, see part VIII
“Solution for Incoming HR documents” in OpenText Business Center for SAP
6 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

1.2. Technology
1.2 Technology
Intelligent Capture for SAP® Solutions recognition technology is based on adaptive
learning algorithms which learn from user feedback. This provides a fast project
setup as no rules or parameters for data extraction are required, and a fast success
rate for excellent recognition results. Intelligent Capture for SAP® Solutions
combines a proven invoice knowledge base with learning algorithms, which extends
the recognition rate within short time of productive use to a new level.
VIM and Beyond excellent recognition results, the tight integration of Intelligent Capture for
Business SAP® Solutions with VIM and Business Center provides an ideal technical footprint,
Center
integration
not requiring an external repository, but using SAP repository, not requiring any
data duplication from SAP system but keeping all data in the SAP system. The
connection to SAP is implemented based on REST based web services supporting
HTTP and HTTPS. This architecture is ideal for hosting Intelligent Capture for SAP®
Solutions on cloud platforms as an alternative to the on premises installation.
ICC and BCC Customers using OpenText™ Invoice Capture Center for SAP® Solutions (ICC) or
integration OpenText™ Business Center Capture for SAP® Solutions (BCC) can integrate
Intelligent Capture for SAP® Solutions, as it can run in parallel, also connecting to
the BC Inbound framework. You can use existing Validation Clients for processing
Intelligent Capture for SAP® Solutions profiles in parallel to ICC and BCC
applications.
Pre-learning of You can reuse validated extraction results from Invoice Capture Center (ICC), and
IES profiles Business Center Capture (BCC) to train IES profiles. This feature will be called Pre-
learning. For more information, see section 4 “Pre-learning of IES Profiles” in
OpenText Business Center for SAP Solutions - Administration and Security Guide (BOCP-
AGD), and section 9.2 “Integration with Information Extraction Service” in OpenText
Vendor Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
1.3 Machine learning

Field types The key advantage of Intelligent Capture for SAP® Solutions is the reduction of
implementation and configuration efforts, combined with fast learning success. That
is why Intelligent Capture for SAP® Solutions includes preconfigured scenarios.
All scenarios are based on intelligent field types for the data transfer to the VIM or
Business Center solution. These fields include:
• Amount
• Currency
• Classification
• Date
• Decimal
• Stringlist

• Lookup
• Partner
• String
• Table
Amount
Description
The amount field is a specialized decimal field which is limited to two
decimals. The amount field intepretes data with regards to the settings of
the format interpretation list, which defines the correct interpretation of
thousand and decimal separators.
Learning supported
Yes
Layout dependent
No
Use case
Item amount, total amount
Parameters
Format interpretation list
Header/table supported
Header/table
Classification
Description
Classification is a string field and learns to determine different classes for
different document types.
Learning supported
Yes
Layout dependent
Yes
Use case
Classification
Parameters
Class name
Header/table

1.3. Machine learning
Currency
Description
Currency is a specialized string field which identifies supported currencies
and currency symbols on the document and normalizes it to ISO names for
supported currencies.
Learning supported
Yes
Layout dependent
No
Use case
Document currency, amount currency
Parameters
Currency
Header/table
Date
Description
A date field is a strucured field which suppports typical date structures
(ddmmyyyy, mmddyyyy, month in letters and so on) for the supported
languages, depending on the settings of the format interpretation list. The
field is learned across layouts, considering typical surrounding keywords,
text and data structure.
Learning supported
Yes
Layout dependent
No
Use case
Document date
Parameters
Header/table
Decimal
Description
The decimal field supports up to 4 decimals. The decimal field intepretes
data with regards to the settings of the format interpretation list, which
defines the correct interpretation of thousand and decimal separators (“.” or
“,”). The field is learned across layouts, considering typical surrounding
keywords, text and data structure.

Learning supported
Yes
Layout dependent
No
Use case
Quantity, unit price
Parameters
Header/table
Partner
Description
The partner field is determining the business partner. The partner field
learns an ID for the partner related to the document layout. The partner field
can also learn multiple IDs related to one layout. The partner field is
connected to a staging table, which is used by the validation user for
retrieving the partner ID with F9.
Learning supported
Yes
Layout dependent
Yes
Use case
Supplier, customer
Parameters
Staging table
Header
String
Description
The string field does not have any normalization but learns a string as it is.
Learning supported
Yes
Layout dependent
No
Use case
Text, numbers
Parameters
String

1.3. Machine learning
Header/table
Stringlist
Description
The stringlist is a list of strings. The user shows some values and the field
type will then learn to extract all relevant strings.
Learning supported
Yes
Layout dependent
Yes
Use case
PO list, DN list
Parameters
Stringlist
-
Table
Description
One profile supports multiple tables. A table is a structure consisting of lines
and columns. For every column a field type needs to be defined, but only
field types showing “T” can be used for table columns. A table will be
learned related to a specific layout.
Learning supported
Yes
Layout dependent
Yes
Use case
Invoice table, sales order table
Parameters
Define field types for columns
Table
For more information about recognition and processing details for the fields of
invoice applications, see section 9 “Field references for IES” in OpenText Vendor
Invoice Management for SAP Solutions - Scenario Guide (VIM-CCS), section 4.5.2.4.5
“Defining custom fields” in OpenText Business Center for SAP Solutions - Configuration
Guide (BOCP-CGD), and section 4.5.2.4.6 “Defining custom table fields” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).

Intelligent field types include the knowledge about the data structure, potential local
formats, their meaning in different business contexts, tax compliance and how they
are used in SAP. As an example, a field type specifies date formats, for example
MMDDYYYY, DDMMYYYY, DD.MM.YYYY, DD/MM/YYYY, and date writing styles, for example
month spelled out, without the need of defining it for any solution.
Learning For the invoice solution the invoice knowledge base has been integrated and runs
algorithms combined with the intelligent field types leveraging a learning voting algorithm.
Thus Intelligent Capture for SAP® Solutions starts learning as soon as the first
document is processed. The learning is based on a combination of two different
algorithm types and a mixture of both:
• Layout based algorithms, for example business partner determination, and item
table recognition. These work based on the layout and where the data is typically
located on the document.
Layout based algorithms learn very fast, providing automatic recognition result
from the second pass of the same layout. For complex tables more passes may be
necessary.
• Layout independent algorithms, for example data, such as amounts, dates and
document references. These algorithms identify relevant data structures and
keywords and learn to extract this on documents with an entirely different
layout.
Layout independent algorithms take more time to learn data structures, related
keywords and surrounding text. What has been learned by this algorithm type
will also be applied to completely unknown documents containing the same data
structures, keywords and surrounding text. With this technique, the data entry
effort diminishes more and more, and the longer the system is in production it
learns more document layouts.
Learning Before using Intelligent Capture for SAP® Solutions, the user manually entered data
system from business documents. With Intelligent Capture for SAP® Solutions, the user
continues to do his daily work, and with this he provides feedback data to the
learning service, which learns to capture the data automatically starting from the
second pass of a document with either the same layout or showing the same data
type, for example date field with the same format and key word.
Learning is permanently active for adapting continuously to the documents

processed in customer environment.
For invoices the user starts from a higher level, because he will get “out of the box”
recognition results from the invoice knowledge base where applicable. They will
only need to enter data for additional fields that are not supported by the invoice
knowledge base, for example a material number, or that could not be extracted by
the invoice knowledge base for some reason, for example complex invoice line
items.
No training phase is required as the system learns unattended in the background.

The business user is the best source of knowledge for the learning process because

1.4. Architecture and SAP integration
they know exactly which is the relevant data to be captured for creating a business
object in SAP.
1.4 Architecture and SAP integration

Intelligent Capture for SAP® Solutions is a Microsoft Windows based data extraction
service which is called by SAP via REST based web services, supporting HTTP and
HTTPS.
Intelligent Capture for SAP® Solutions connects to VIM and Business Center using
the ABAP component Inbound Framework (IDF), where an Information Extraction
Service API complements the existing BCC APIs.
Intelligent Capture for SAP® Solutions provides three services which are called from
SAP by the Intelligent Capture for SAP® Solutions API:
• Configuration Service: Receives configuration data for recognition profiles

related to business scenarios.
• Extraction Service: Receives requests from IDF for extracting data from an image
file and provides result data.
• Feedback Service: Receives feedback data resulting from user feedback.
Depending on the configuration in the scenario, feedback can be returned after
validation in Validation Client or processing in VIM or Business Center.
OpenText recommends configuring feedback from the Validation Client in the
current version. The Feedback Service processes the learning data (model data)
and stores it in the SAP database. With this, the learning data is safely stored and
included in the backup process of the SAP repository.

1.5 Solutions and profile configuration

Intelligent Capture for SAP® Solutions supports all VIM and Business Center
solutions. For more information, see “Business scenarios/solutions” on page 5.
The configuration of the solutions is completely done in BC Inbound IMG, that

means there is no configuration needed on the Intelligent Capture for SAP®
Solutions Server. For more information, see the OpenText Business Center for SAP
Solutions - Configuration Guide (BOCP-CGD). Here you can find information about
the IDF configuration, business solutions, the application profile configuration, and
a description of the complete document processing data flow beginning with
inbound scanning or e-mail, and ending with starting the VIM or Business Center
workflow.
Profile configu- For every Intelligent Capture for SAP® Solutions scenario, at least one profile must
ration be configured. The number of profiles per scenario or overall number of profiles is
not limited.
A profile defines the set of fields that are required for extraction based on the fields
of the standard scenario. The profile also defines the behavior and sequence of the
fields in the Validation Client, which can be set as required, read-only or hidden.
The profile creation depends on the specific business requirement, such as different
company codes or countries.
The default fields can be extended by adding following custom fields: Date,
Decimal, Amount, Currency, Partner, Classification, String and Stringlist. . The
custom fields will also be shown in the Validation Client.

1.5. Solutions and profile configuration
Learning data The learning data will be stored in the repository of the SAP system.
configuration
Validation The Validation Client is the user interface for comfortable data completion and
Client configu- manual data entry. All user actions contribute to the continuous learning process.
ration
The client itself can be used on an unlimited number of workstations without
charge.
The Validation Client has no connection to the Intelligent Capture for SAP®
Solutions Server, it connects only to the SAP system using an RFC call and polls for
assignments. If a document is assigned to the validation step, the Validation Client
loads the profile settings, notably the list and sequence of fields, as well as the
invoice image, including the full text recognition details but without any connection
to the archive system.
You can configure the Validation Client in BC Inbound IMG. The configuration
defines if validation is used or not, which are the criteria for documents used for
validation, and which validation agents are assigned to the different profiles.
The profile configuration defines how data fields are shown in the Validation Client.
Data capturing The Validation Client provides comfort functions for fast and secure data capture:
• With Single Click Entry (SCE), the user can pick the data directly from the image
into the data fields and does not need to type the data. This avoids errors due to
typos.

• With Table Auto Completion (TAC), the user only needs to pick the data of the
first item line with Single Click Entry (SCE), Table Auto Completion (TAC)
automatically captures the data of all line items.
The image view highlights all data that has been recognized automatically and the
user can see at first glance if data is missing, for example line items.
1.6 Supported languages

Intelligent Capture for SAP® Solutions can extract information contained on
documents from foreign countries including:
• Character sets supported by the text recognition engine which supports most of
the languages worldwide with high precision.
• Data interpretation for different cultures and languages. Cultures refers to the
typical writing styles for data in a country. In Germany, for example, the date
format is typically 10.12.2018 and spelled out in words as 10. Dezember 2018.
In the United States it is 12/10/2018 and December 10, 2018. For the latter, the
language must also be understood for the correct interpretation of the month,
and the context may be required to determine whether the data is European or
the U.S. for the correct interpretation of the numeric date. In some countries, very
specific date formats need to be considered, such as the Emperor date in Japan.
Also, amounts are culture specific with regards to the use of decimal separators
and the number of decimals used. The same also applies to quantities.
• For some documents, such as invoices, country specific reference fields, local
taxes and tax compliance requirements, such as mandatory tax invoice, need to
be considered.
For more information of supported languages and character sets, see the Release
Notes of VIM and Business Center.

1.7. Supported image formats
Intelligent Capture for SAP® Solutions supports multi-country profiles. Countries

can be combined in one profile depending on the criteria of the business scenario,
such as:
• Country groups related to company codes in SAP.

• Country groups with the same tax system, for example VAT and GST.
• Country groups using the same data fields. A profile also defines data fields for
the screen in the Validation Client for data completion.
In Inbound IMG, the preferred culture for data interpretation can be configured. For
example, by selecting the UK as the first sequence, the date and amount fields are
interpreted with first priority for the UK format, but the formats of other cultures are
still recognized if no UK date or amount exist on the document.
1.7 Supported image formats

Intelligent Capture for SAP® Solutions processes:
• All document formats used for business documents like invoices, orders and so
on, such as DIN A4, legal, letter, and smaller formats, in portrait and landscape
orientation with a minimum font size of 1.5 mm high and 0.5 mm wide.
• JPEG for color and gray images with a maximum image resolution of 400 dpi.
• PDF
• TIFF 6.0 binary images in the compression modes:
– Uncompressed
– Fax Group 3
– Fax Group 4
– Packbits
– LZW

Chapter 2
Installing Intelligent Capture for SAP® Solutions
2.1 Installation procedure overview

Notes
• For more information on supported platforms, hardware and software

requirements, as well as product dependencies and restrictions, see the
Release Notes. You can find the latest version of the Release Notes in My
Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
15448194).
• The software is available on My Support as product ISO image. For more
information, see https://knowledge.opentext.com/knowledge/llisapi.dll/
Open/75964622. You may burn the ISO image on a DVD as the installation
medium. This documentation refers to the term <installation medium> as the
container for the ISO image. Alternatively, you can also mount the ISO
image. However, this is not explained by this documentation.
• Check My Support (https://knowledge.opentext.com/) for service packs or
patches that may have been posted after the initial release of Intelligent
Capture for SAP® Solutions.
Check also the patches for the Capture Imaging Plug-In component (https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/61183571) if a newer
version is available.
• The descriptions in this guide are based on the assumption that VIM and
Business Center are already installed and configured.
• Sign in as user with local administration rights.
Install and configure Intelligent Capture for SAP® Solutions in the following
sequence:
1. Install Intelligent Capture for SAP® Solutions. For more information, see
“Installing Intelligent Capture for SAP® Solutions” on page 20.
Notes
• Intelligent Capture for SAP® Solutions does not need a database but
stores data in the SAP database.
• Intelligent Capture for SAP® Solutions can be installed stand-alone.
• Intelligent Capture for SAP® Solutions can be installed and run together
with BCC on the same system if both products have the same version.
As a prerequisite, install first BCC. When running the Intelligent
Capture for SAP® Solutions setup it will be installed as add-on into the
same directory as BCC. Do not change this directory.

Chapter 2 Installing Intelligent Capture for SAP® Solutions
• The available system resources will be shared between both products

which you should consider when planning the system sizing.
2. Optional Install Asian languages.
3. Configure VIM respectively Business Center. For more information, see section
4.5.2 “Customizing Information Extraction Service” in OpenText Business Center
for SAP Solutions - Configuration Guide (BOCP-CGD).
4. Install the Validation Client. For more information, see “Installing the
Validation Client” on page 21.
Note: The Validation Client cannot be installed and run on the same
system as Intelligent Capture for SAP® Solutions.
5. Optional Install Single Click Entry for SAP GUI. For more information, see
“Installing Single Click Entry for SAP GUI” on page 22.
2.2 Prerequisites for the installation

Before you install Intelligent Capture for SAP® Solutions, install Microsoft Internet
Information Services (IIS).
To install and configure IIS:
1. Start the Server Manager.
2. On the Dashboard, click Add roles and features.
3. Proceed to the Server Roles page.
4. Select Web Server (IIS).
5. Open this node and its subnode Application Development, and then select
ASP.NET 4.5 and later versions.
6. Click Next and then click Install.
2.3 Installing Intelligent Capture for SAP® Solutions

To install Intelligent Capture for SAP® Solutions:
1. In the root folder of the installation media, start setup.exe, or run

<drive>:\Intelligent Capture for SAP Solutions 16.7.1.msi.
By default, the files are installed into the folder %ProgramFiles(x86)%\Open
Text\Intelligent Capture for SAP Solutions 16.7.1.
2. In the Welcome dialog box, click Next.
3. In the End-User License Agreement dialog box, accept the license agreement,
and then click Next.

2.4. Installing Asian languages
4. In the Destination Folder dialog box, check the path to the installation folder,
and then click Next.
If you want to install Intelligent Capture for SAP® Solutions at a different
location, click Change, and then choose the desired path in the appearing folder
dialog box.
5. Click Install.
6. Click Finish.
2.4 Installing Asian languages

If you want to process documents containing Asian languages, you must run the
Asian languages setup following the Intelligent Capture for SAP® Solutions
installation.
The Asian OCR option has its own installation media Asian Option <version> for
SAP Solutions.iso. Install the languages on the Intelligent Capture for SAP®
Solutions Server.
After the installation, the languages Chinese Simplified, Chinese Traditional,

Japanese, and Korean can be extracted from Asian documents.
To install the Asian languages option:
1. In the root folder of the installation media, run Setup.exe.

2. In the License Agreement dialog box, accept the license agreement, and then
click Install.
3. Click Finish.
2.5 Installing the Validation Client

The Validation Client is used for correcting documents, and cannot be used for
recognition, or for customizing and monitoring.
The software Validation Client for SAP® Solutions is available on My Support as

product ISO image. For more information, see https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/75964622.
Tip: For an unattended installation, a command script is available in a

subfolder.
To install the Validation Client:
1. In the root folder of the installation media, run Setup.exe.

click Next.

4. In the Destination Folder dialog box, install to the default folder or click
Change to choose another folder, and then click Next.
5. In the Ready to install Validation for SAP solutions dialog box, click Install.
6. In the Completed the installation dialog box, click Finish.
2.6 Installing Single Click Entry for SAP GUI

Install Single Click Entry for SAP GUI on all computers on which also SAP GUI is
installed, and where users are using the Single Click Entry functionality in VIM
Indexing Screen.
If Single Click Entry for SAP GUI is installed on a Vendor Invoice Management
system, it permits to capture data for fields on the index screen using the mouse. For
more information, see section 4.2 “Using the Single Click Entry feature” in OpenText
Vendor Invoice Management for SAP Solutions - User Guide (VIM-UGD), and section 4
“Installing Single Click Entry for SAP GUI” in OpenText Vendor Invoice Management
for SAP Solutions - Installation Guide (VIM-IGD).
To install Single Click Entry for SAP GUI:
1. Install Microsoft Redistributables. For more information which Microsoft

Redistributables must be installed, see the Release Notes in My Support (https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/58900990).
2. In the SceSapGui folder of the installation media, start SCE for SAP Solutions.
msi.
click Next.
5. In the Select Installation Folder dialog box, check the path to the installation
folder.
If you want to install Single Click Entry for SAP GUI at a different location, click
Change, and then choose the desired path in the appearing folder dialog box.
6. By default, the software is installed for every user. To install it only for the
current user, click Just me, and then click Next.
7. To start the installation, click Next.
8. Click Close.
After Single Click Entry for SAP GUI has been installed, configure SAP GUI.
To configure SAP GUI and VIM for Single Click Entry for SAP GUI:
1. Start SAP GUI, and then click Options in the system menu.

2.7. Installing patches and service packs
2. If the Enable Scripting check box at the user settings is cleared, select it.
3. Clear the two additional check boxes controlling notifications because otherwise
you get two notifications for each document that is opened on the index screen.
4. Click Apply.
5. In transaction RZ11 in the section sapgui/user_scripting, set Current value to

True.
6. In the section sapgui/user_scripting_disable_recording, set Current value to

False.
7. Use transaction N/OPT/SPRO to set the variable XML_AR_DELETE_EARLY. For

SceSapGui, do not set this variable to the value X. For more information, see
section 10.1 “Defining frequently used default values” in OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide (VIM-CGD).
8. Configure clean-up of XML files for documents that have left the ICC
Dispatcher. For more information, see section 6.3 “Batch Program /OPT/
VIM_ICC_DL_CLEANUP” in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM-AGD).
If you want to restrict scripting to specific users, additional configuration is needed.
To restrict scripting to specific users:
• In transaction RZ11, in the section sapgui/user_scripting_per_user, set Current

value to True.
After login, SAP GUI scripting remains available for those users that have the
authorization for the Execute(16) action of the authorization object S_SCR in
class BC_A.
On the login screen, SAP GUI scripting is then available for every user.
2.7 Installing patches and service packs

Check My Support (https://knowledge.opentext.com/) for service packs or patches
that may have been posted after the initial release of Intelligent Capture for SAP®
Solutions.
Service packs are cumulative, that is a service pack contains all changes contained in
previous service packs of the respective Intelligent Capture for SAP® Solutions
version. Therefore, it is sufficient to install only the latest service pack after installing
Intelligent Capture for SAP® Solutions. For the same reason, the Release Notes of a
service pack list the changes of all previous service packs.
However, you can install a service pack on Intelligent Capture for SAP® Solutions
with any previous service pack.
Patches are related to a service pack, that is you can only install a patch on an
Intelligent Capture for SAP® Solutions system where the corresponding service pack

has been installed. Patches are cumulative, that is a patch contains all changes
contained in previous patches for the same service pack.
To install a service pack or a patch:
1. In the Server group of the General tab, click Cluster, and wait until all cluster
nodes have finished processing, that is, until all are in state Ready.
2. In the Internet Information Services (IIS) Manager, stop the

InformationExtractionService web service.
3. Install the service pack or patch.
4. In the Internet Information Services (IIS) Manager, start the

InformationExtractionService web service.

Chapter 3
Upgrading Intelligent Capture for SAP® Solutions
You can continue to use existing profiles in VIM and Business Center. But you must
upgrade VIM and Business Center. For supported versions, see Release Notes.
To upgrade Intelligent Capture for SAP® Solutions:
1. Close Intelligent Capture for SAP® Solutions and all Validation Clients.
2. Stop the web site of InformationExtractionService web service in IIS

Manager.
3. Uninstall Intelligent Capture for SAP® Solutions and all Validation Clients.
4. Install Intelligent Capture for SAP® Solutions and Validation Client. For more
information, see “Installing Intelligent Capture for SAP® Solutions” on page 20
and “Installing the Validation Client” on page 21.
5. Check if the installation folder has been changed and update the physical path
information in the IIS Manager if needed.
6. Start the web site of InformationExtractionService web service in IIS

Manager.
7. Configure the web service. For more information, see “Configuring the web
service” on page 28.
8. Migrate the learning data. For more information, see section 4 “Pre-learning of
IES Profiles” in OpenText Business Center for SAP Solutions - Administration and
Security Guide (BOCP-AGD).
9. Update the profiles because the profile data format has been extended. For more
information, see section 4.5.2.5 “Activating and updating a profile” in OpenText
Business Center for SAP Solutions - Configuration Guide (BOCP-CGD).
When you start the new installed Validation Client the updated profiles will
automatically been loaded.
10. Test your Intelligent Capture for SAP® Solutions system.
To upgrade the Validation Client:
1. Uninstall all Validation Clients.
2. Install Validation Client. For more information, see “Installing the Validation
Client” on page 21.

Chapter 4
Configuring Intelligent Capture for SAP® Solutions
4.1 Configuring authorizations for validation user

As soon as the validation user has started the Validation Client, the user has to log in
to SAP ERP or SAP S/4HANA using a prepared SAP user. This user needs the
following authorizations:
• For BC Inbound Framework version 16.3.1 and later, full authorization for the J_
6NPF_RFC object is required for all users. For more information, see section 7.4
“Authorization objects” in OpenText Business Center for SAP Solutions -
Configuration Guide (BOCP-CGD).
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SYST
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=RFC1
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=RFC_METADATA
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME= /OTX/PF11_VALIDATION
As of SAP Basis Release 7.10 you can choose a finer granularity for authorizations.
For more information, see SAP Note 460089. You can execute the authorization
check on individual function modules, instead of entire function groups.
You can replace the following authorizations:
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SYST
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFCPING
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=RFC1
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_FUNCTION_SEARCH
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=RFC_METADATA
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_METADATA_GET
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OTX/PF11_VALIDATION
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/
PF11_VAL_GET_DATA
PF11_VAL_GET_PROFILES
PF11_VAL_GET_SETTINGS
PF11_VAL_SET_DATA

Chapter 4 Configuring Intelligent Capture for SAP® Solutions
You can also replace the other function group authorizations by the function module
authorizations but it is not necessary because nearly each function module within
the groups is used.
4.2 Adding a certificate for client/server

authentication for secure communication using
HTTPS (optional)
To setup secured communication using HTTPS, install a server and client certificate
on the system(s). Thereby, you can use a combined certificate for server and client
authentication. It should be issued to the name of the unique service URL (entry set
to subject attribute CN).
To install and configure the certificate:
1. Create or purchase the certificate. Ensure that you also have the private key.
2. Import the certificate into the Local Computer account. Ensure to select Allow
private key to be exported.
3. Assuming that the Internet Information Services (IIS) website is running under
ApplicationPoolIdentity, do the following:
a. Run certlm.msc.
b. In the console tree, expand Certificates - Local Computer > Personal >
Certificates.
c. In the result pane, right-click the appropriate certificate, and then click All
tasks > Manage Private Keys.
d. Add the %LOCALSYSTEM%\IIS_IUSRS user and grant it Full control.
e. Click Apply.
4.3 Configuring the web service

Install Internet Information Services (IIS) with activated ASP.NET features.
To configure the web service:
1. Start the Internet Information Services (IIS) Manager (inetmgr.exe).
2. On the Connections view, right-click Sites, and then click Add Web Sites.
3. In the Add Website dialog box, enter InformationExtractionService in the

Site name box.
4. In the Physical path box, enter the installation path of Intelligent Capture for
SAP® Solutions with its subfolder WebServiceAPI.
5. In the Type list, click http or https depending on your connection type, and
then enter the port in the Port box.

4.3. Configuring the web service
Note: The port must not be used by any other process.
6. Optional If you want to use a SSL certificate for HTTPS communication, click
Select, and then browse to the certificate file (optional). For more information,
see “Adding a certificate for client/server authentication for secure
communication using HTTPS (optional)” on page 28.
7. Click OK to close the Add Website dialog box.

The new web site is now shown as subnode InformationExtractionService in
the Connections view on the left side, and the node is selected.
8. On the Actions view on the right side, under Manage Web Site, check if web
site is already started. If not, click Start, and then click Browse.
The default web browser opens and shows a start message which indicates that
the web service is running.
9. In the web browser address, add status.aspx to the URL which is already
openend, and then press RETURN.
A webpage should be shown which shows information about the web service
and additional status information on the processed jobs.
4.3.1 Specifying the application pool

To specify the application pool:
1. On the Connections view, click Application pools.
2. In the Application Pools list, double-click the respective site name.
3. In the Edit Application Pool dialog box, select .NET CLR v4.0.30319 in
the .NET CLR version list if it is not already selected, and then click OK.
4.3.2 Configuring SSL settings for secure communication

using HTTPS (optional)
To configure SSL settings:
1. On the Connections view, at the Sites node, click

InformationExtractionService.
2. Double-click SSL Settings.
3. Select the Require SSL check box.
4. Under Client certificates, click the Require option, and then click Apply on the
Actions view.

4.3.3 Increasing the upload size (IIS 7.0 and later versions)
To increase the upload size to the web service, change the properties
maxAllowedContentLength, and maxRequestLength:
1. On the Connections view, below the Sites node, click

2. Double-click Configuration Editor.
3. On the Configuration Editor view, in the Section list, open the

System.webServer node.
4. On the Security subnode, click requestFiltering, open requestLimits, select the

maxAllowedContentLength property, and then enter the maximum upload
size you want to support (up to 4 GB). The default value is 30000000 bytes
(approximately 28,6 MB).
5. On the Actions view, click Apply.
6. On the Configuration Editor view, in the Section list, open the System.web
node.
7. Click httpRuntime, select the maxRequestLength property, and then enter the
maximum upload size you want to support (up to 2 GB). The default value is
4096 bytes (4 KB).
To increase the upload size for the Intelligent Capture for SAP® Solutions web
application which communicates via HTTPS, change the property
uploadReadAheadSize:
1. On the Connections view, below the Sites node, click

2. Double-click Configuration Editor.
3. On the Configuration Editor view, in the Section list, open the

System.webServer node.
4. Click serverRuntime, select the uploadReadAheadSize property, and then

enter the maximum upload size you want to support (up to 2 GB). The default
value is 4096 bytes (4 KB).

4.3. Configuring the web service
4.3.4 Configuring internal application settings

Internal application settings are stored in the web.config file.
To configure internal application settings:
1. In the Internet Information Services (IIS) Manager, on the home site

InformationExtractionService, in the Features View, open Application
Settings.
2. If one of the following settings are not listed you must add it.
In the Actions pane on the right side of the IIS Manager window, click Add,
define the settings, and then click OK.
CompressMultipartResponse
Compress the HTTP multipart which gets sent to the leading (SAP) system.
The default value is true and must not be changed.
CompressRepositoryBlobs
Compresses the data “blobs” which get transferred via HTTP(S) and stored
into the SAP repository. The default value is true and must not be changed.
EncryptRepositoryBlobs
Encrypts the data “blobs” which get transferred via HTTP(S) and stored
into the SAP repository. The default value is false and must not be changed.
DefaultOcrTimeout
Maximum runtime of an operation. If runtime exceeds this value, the
operation will be cancelled. The default value is 50 minutes and must not be
changed.
LoadManagerMasterServer
Hostname of the Load Manager Server. The default value is 127.0.0.1
(localhost) and must not be changed.
NoOfOcrRetries
The number of retries if an operation gets failed. Not used for productive
use because retry handling is set by leading (SAP) system. The default value
is 0 and must not be changed.
StopExtractAfterMaxPages
Text and field recognition of any document sent to extraction will stop after
a defined number of pages. With that all document pages will be visible in
Validation.
Single Click Entry (SCE) can only work for documents with fulltext which
may not exceed a certain number of documents. The useful limitation is a
value below internal recognition timeout, that is 60 minutes per document.
Depending on the running scenarios in you system and the characeristics of
the documents, the limit may be set to lower than 200 pages if you are
processing mostly invoices. Alternativelly, lower than 400 pages if you are
processing other documents than invoices, for example sales order and so

on. With that the documents will not run into a timeout and results will be
provided for the pages within the limit. You can set the limit to lower and
higher values depending on the document characteristics in your
environment. More granular profile settings for limiting recognition to
specific pages are planned to be available in BC Inbound IMG with the next
release.
SupportedSecurityProtocolTypes
Security protocols that are supported for secure communication via HTTPS.
The TLS protocol types Tls,Tls11,Tls12 are supported by default. A comma-
separated string or also a single value can be entered here. If the value is
empty, the default system setting will be used. For more intensive security
reason some SAP systems does not support older TLS protocols than Tls12.
In this case the setting should be changed to value Tls12 only.
TracingConfigFileName
Name of the configuration file which is used for application tracing setup.
The default value is InformationExtractionService.traceconfig and must
not be changed.
WebProxyAddress
Web proxy address if a proxy is used for outbound calls.
When you use client certificates for the communication via HTTPS (see “Adding
a certificate for client/server authentication for secure communication using
HTTPS (optional)” on page 28), set the following configuration parameters
accordingly:
StoreCertLocation
Each of the Microsoft Windows certificate stores has the following types
which you can use:
• localMachine (preferred setting)

• currentUser
ClientCertificateOption
Value that indicates if the certificate is automatically picked from the
certificate store or if the caller is allowed to pass in a specific client
certificate.
• manual (preferred setting)

• automatic
DistinguishedCertName
Subject value of the client certificate which is used for sending HTTP
requests to the leading SAP system(s). This value must match to an existing
subject name located in the local cert store, for example CN=*.opentext.
net, OU=SAP Solutions Development, O=OpenText, C=DE.

4.4. Configuring tracing
Additional there are a few settings which offers support for error analysis, for
example StoreRequestToFolder, which prints out the HTTP multipart request
to a text file on the local storage. But these settings should only be used by
administrators or customer service for temporary analysis.
4.4 Configuring tracing

You can use trace data to analyze and fix problems at runtime. The tracing
component has the following features:
• Output to multiple tracing targets.

• Hierarchical tracing architecture.
• Easy configuration on-the-fly through XML configuration files or software.
• Trace Viewer to view trace files, filter and search trace data, and observe
applications on several hosts.
4.4.1 Tracers
A tracer represents the source of a trace message. Tracers are named entities with a
hierarchical structure. Hierarchy levels are separated by dots. This corresponds to
the naming of .NET classes including namespaces. Therefore usually the class name,
for example DOKuStar.Runtime.Server, is used as name of the respective tracer.
The tracer name is used to configure the properties of the tracer such as the trace
level. You may use the full name of the trace or only a part of the name. If a
particular trace has not been configured explicitly, it inherits its configuration from
its parent tracer.
A special tracer, called the RootTracer, is the parent of all tracers and has no name.
4.4.2 Trace listeners

Trace listeners represent the destination of trace messages. The tracing system ships
with a collection of trace listeners:
RollingFileListener
This trace listener writes trace messages to a file. It generates a new file with a
unique file name for every process by merging the current time and the process
identifier into the file name. The output is flushed every 30 seconds. A new file
is created each day. Files older than 10 days (configurable) are removed.
RemotingTraceListener
This listener writes trace messages to a remote sink, for example the Trace
Viewer in order to display trace messages on-the-fly.
ConsoleTraceListener
Writes trace messages to console output.

Trace listeners may trace at different levels. Every tracer may have assigned its own
collection of trace listeners but usually only the root tracer has them all and all other
tracers inherit them.
4.4.3 Trace root path

Intelligent Capture for SAP® Solutions writes trace messages to trace files located
relative to a root path for all applications. The default root path is
%ALLUSERSPROFILE%\Application Data\Open Text\Trace.
Note: The Application Data folder is hidden. Therefore, select the respective
option in the Folder Options of Microsoft Windows Explorer to display the
folder.
To change the default trace folder:
1. Set the registry value TraceRootPath (type REG_SZ) at the key HKLM\SOFTWARE
\Open Text, and on 64-bit systems also at the key HKLM\SOFTWARE\
Wow6432Node\Open Text to a new path.
2. To keep the trace configuration, copy the trace configuration files

(extension .traceconfig) to the new trace path.
3. If you want to use a remote trace folder, run the service with a domain user
account instead of the LocalSystem account.
4. Restart the DOKuStar Load Manager Microsoft Windows service and the
DOKuStar Tracing Microsoft Windows service.
Trace configuration files are stored directly under the root path. Trace files are
written to a subfolder, typically the folder name is the application name, for example
DOKuStar Load Manager.
4.4.4 Trace levels

Tracers and trace listeners have trace levels used to control the volume of the tracing
output. You can use following trace levels:
Fatal
Used in case of errors where the administrator has to be called immediately.
Those errors risk to crash down processing for example disk full.
Error
Used in case of errors that aborted the current job. Probably processing
continues with the next job.
Warning
An unexpected issue occurred and should be traced in order to be able to
analyze it later especially if it occurs again.

Info
This is the default level. It is use to trace normal progressing as an administrator
would see it in a monitor, for example:
• service has been started

• job <...> has been started
• job <...> has terminated status <...>
• service has been stopped
Fine
First debug level, for example to additionally trace failed polling calls or
important parameters, and so on.
Finer
Next debug level.
Finest
Highest debug level.
Note: The default level is Info. Do not stress tracing using this level Info with
your debug messages.
Configuration is reread on-the-fly if the configuration file changes. You do not

need to restart the load manager service.
4.4.5 Trace configuration

Several trace configuration files in the trace folder specify which trace messages a
distinct Intelligent Capture for SAP® Solutions component writes to the trace folder.
For example, a trace configuration file defines the trace level for the trace messages.
Only trace messages with this specified trace level or higher are written to the trace
folder.
The trace configuration files must reside in the current trace folder. Therefore do not
forget to copy the trace configuration files to the new location if you change the trace
root path.
You may configure traces by editing the appropriate trace configuration file directly
or by selecting a predefined trace configuration in the Trace Viewer. For more
information, see “Analyzing trace files using Trace Viewer” on page 39. Selecting a
predefined trace configuration in the Trace Viewer changes the trace configuration
files automatically.
The trace configuration file has three types of elements:
listener
This element configures a trace listener by specifying the following:

name
Any describing name.
type
The full qualified name of the class which implements the listener.
threshold
Trace level (optional, default is Finest).
It also specifies other trace listener-specific parameters.
<listener name="file"
type="DOKuStar.Diagnostics.Tracing.RollingFileTraceListener">
<file value="DOKuStar Load Manager\\DOKuStarClusterNode.log" />
</listener>
<listener name="remote"
type="DOKuStar.Diagnostics.Tracing.RemoteTraceListener">
<url value="tcp://localhost:20304/DOKuStar.Diagnostics.Tracing" />
<threshold value="fine" />
</listener>
root
This element configures the root tracer by specifying the following:
level
Trace level.
listener-ref
The listeners. Usually all listeners are configured only at the root tracer, not
at the categories.
<root>
<listener-ref ref="file" />
<listener-ref ref="remote" />
<level value="fine" />
</root>
category
This element configures certain tracers by specifying the following:
name
Name of the tracer or part of its hierarchical name.
level
Trace level.
<category name="DOKuStar.Cluster.Operation">
</category>
There are two types of configuration files:
merge (default)
Configures only a few items and merges them with a configuration that may
have been initialized by software and already has specified its root tracer and
trace listeners so that you only want to change trace levels of certain categories.
Example:

<?xml version="1.0" encoding="utf-8" ?>

<trace>
</category>
<category name="DOKuStar.Cluster.ClusterNode">
</category>
<category name="DOKuStar.Cluster.Extraction">
</category>
</trace>
overwrite
Configures all features and completely resets an initial configuration made
through software. You must specify the root tracer and its listeners.
Example:
<?xml version="1.0" encoding="utf-8" ?>
<trace update="overwrite">
<listener name="file"
type="DOKuStar.Diagnostics.Tracing.RollingFileTraceListener">
<file value="DOKuStar Load Manager\\DOKuStarClusterNode.log" />
</listener>
<listener name="remote"
type="DOKuStar.Diagnostics.Tracing.RemoteTraceListener">
<url value="tcp://localhost:20304/DOKuStar.Diagnostics.Tracing" />
<threshold value="fine" />
</listener>
<root>
<listener-ref ref="file" />
<listener-ref ref="remote" />
</root>
</category>
<category name="DOKuStar.Cluster.ClusterNode">
</category>
<category name="DOKuStar.Cluster.Extraction">
</category>
</trace>
Tip: You can find examples for trace configuration files in the <Intelligent
Capture for SAP Solutions_install>\TraceConfig folder.

4.4.6 Location of trace files and trace configuration files

All kind of Intelligent Capture for SAP® Solutions requests run within a cluster
controlled by the Load Manager. There are separate trace files for the Load Manager
service and every cluster node. There are two configuration files, one for the Load
Manager service and one shared by all cluster nodes.
Load Manager and Cluster Nodes
• Trace files
<TraceRoot>\DOKuStar Load Manager\DOKuStarLoadManager*.log
<TraceRoot>\DOKuStar Load Manager\DOKuStar.ClusterNode*.log
• Trace config file
<TraceRoot>\DOKuStarLoadManager.traceconfig
<TraceRoot>\DOKuStarClusterNode.traceconfig
Customizing Client
• Trace files
<TraceRoot>\rda1\rda1*.log
• Trace config file
<TraceRoot>\rda.traceconfig
All services
The Microsoft Windows event log is used to log creating, starting, and stopping
of the services.
4.4.7 Format of traces

Traces written to trace files have the following format:
<DateTime> <Level>:<Computer> <Application> <PID> <Category> <ThreadId>

[[<Message>]]
DateTime
Time when the trace message was written, sortable format yyyy.MM.
ddTHH:mm:ss.
Level
Trace level Fatal, Error, Warning, Info, Fine, Finer or Finest.
Computer
Name of the host where the trace message was written.
Application
Name of the application that wrote the trace message.

PID
ID of the process that wrote the trace message.
Category
Trace category (hierarchically to reflect classes and modules).
ThreadId
ID of the thread that created the trace message.
Message
Trace message enwrapped with 2 squared brackets at begin and end. Note: A
trace message is multi-line; it may contain carriage return and line feed.
Example: 2018.09.04T10:17:45 Error: SYS2186 DOKuStarLoadManager 2264

DOKuStar.Cluster.Configuration 1 [[this is the error message]]
4.4.8 Analyzing trace files using Trace Viewer

The Trace Viewer is used to show trace messages created by the Intelligent Capture
for SAP® Solutions components and permits you to:
• View trace files.

• Search text using regular expression.
• Filter trace messages.
• Record trace information on-the-fly even on multiple computers simultaneously.
• Drop files into the viewer.
To analyze trace files with Trace Viewer:
1. In the Customizing Client, on the General tab, in the Tools group, click Trace
viewer.
Tip: Alternatively, you can start the Trace Viewer on the Microsoft
Windows start menu in the Intelligent Capture for SAP® Solutions
program group.
The Trace Viewer shows a list of all trace files found on the local computer. The
list is grouped by the different components.
Tip: If the toolbar is not shown, right-click in the right area, and then click
Toolbar.
Local Machine
You can open the trace folder by clicking the link in the header.
Filter
You can display only trace files containing messages of the respective types
by clicking All, Only errors, or Only errors and warnings in the Filter list.

Trace configuration
You can select one of three trace configurations. For more information, see
“Selecting a trace configuration” on page 41.
Display Level
You can specify one of seven different trace levels. In the most restrictive
level only fatal error messages are shown. In the most talkative trace level,
messages of all message types are shown.
The toolbar text indicates the currently selected trace level.
Display filter
You can set different kinds of filters that control which log messages are
shown. For more information, see “Filtering messages” on page 42.
Find
You can search in the currently open file. For more information, see
“Searching trace messages” on page 43.
Tip: You can enable more functions in the main menu, or in the context
menu of the right area.
• Open: Opens a trace that is not available in the file list.

• Set Trace folder: Permits to switch to a different folder containing trace
files.
• Clear all, clear: Removes all messages from the messages list view.
• Top window: Stays the Trace Viewer window on top. To switch this
feature off, use the command again.
• Columns: Controls which columns are shown in the messages list
view.
• Options: Opens the Options dialog box where you can change the
language of the Trace Viewer user interfaces.
• Auto scroll: If this option is selected, the view shows the last lines,
when log messages are added.
2. Double-click a file in the list.

The contents of the file is shown in the messages list view on the right side.
3. Double-clicking a message in the messages list view.

The Trace Message dialog box shows the complete message and its details.

4.4.8.1 Selecting a trace configuration

Notes
• This configuration affects the local computer. If you want to search an error
on a processing cluster, you may need to modify the trace configurations on
all computers of the cluster.
• The dialog box cannot indicate the current trace configuration, because you
could modify the trace configuration files using a text editor at any time,
creating a custom configuration differing from all three default
configurations described below.
To select a trace configuration:
1. Click Trace configuration.
2. Click one of the following trace configurations:
Debugging production system

Can be used to search for errors. Here all trace levels are set to the level
finest. This mode produces a large amount of trace data.
Development
Can be used to search for errors in your own code. Here the trace level for
all namespaces starting with DOKuStar is set to info, whereas all other
levels are set to finest. Thus you get the maximum amount of trace data for
project modules and plug-ins if you use a separate namespace.
Production
Intended for production systems. It traces all errors, warnings, and info
traces, but does not produce too much trace data.

4.4.8.2 Filtering messages

Specified filters only affect the messages list view of the Trace Viewer. They do not
modify the contents of the trace files and they do not control which messages are
written to trace files.
To filter messages:
1. In the toolbar, click Display filter. Alternatively, in the context menu of the
message list view, click Filter.
2. Select the filters:
Level
This filter permits to switch all trace messages off or to specify a trace level.
If the trace level is set to Error, only error messages are shown. The other
values add messages of other types successively. If the trace level is set to
Finest, messages of all types are shown.
Computer
Lists computers of the cluster used by the project. By default, messages
from all computers are shown. If you work with a cluster you can exclude
some computers or restrict output to the messages of a single computer.
Application
Lists all applications of the current project. By default, all applications are
enabled.
PID
Lists process IDs of all processes of the current project. By default, all
processes are enabled.
ThreadId
Lists thread IDs that created the trace message.
EventId
Lists event IDs that created the trace message.
Category
A category is a group of classes. This filter permits to restrict messages of
the type Info to functional units within the Document Reader during
debugging.
Find filter
If the text box in this area is not empty only matching messages are shown
in the messages list view. The check boxes permit to control text matching.
• If the Match case check box is selected, the message must contain the
string in exactly the same spelling with respect to upper and lower case
letters.
• If the Match whole word only check box is selected, the string will not
be matched against a part of a word.

• If the Regular expression check box is selected, the specified string is

used as a regular expression.
4.4.8.3 Searching trace messages

You can search for strings in the trace message files shown in the messages list view.
To search trace messages:
1. In the toolbar, click Find. Alternatively, in the context menu of the message list
view, click Find.
2. In the Find dialog box, enter the search string. You have the following
additional options: Match case, Match whole word only, Regular expression

3. Click Find Next or Find Previous to search the message list. The next or
previous matching trace message is selected in the messages list view.
4.5 Controlling cache behavior

During recognition, the Document Reader uses a cache to store input data and result
files. For each recognition job, a separate cache entry is created, which is a subfolder
of the cache folder with a GUID as unique name.
By default, the number of cache entries in each project cache is controlled in relation
to a specified cache size. If the number of entries reaches twice the specified number,
the oldest entries are deleted until the number of entries equals the specified cache
size. The default value of the cache size is 32.
To specify the cache size for the Load Manager, create a configuration file
DOKuStarClusterNode. exe.config in the Capture Document Reader program files
folder as described below and use the tag to the
To controll the cache behavior:
1. Go to the Intelligent Capture for SAP® Solutions program files folder, and then
open the configuration file DOKuStarClusterNode.exe.config.
If this file is not available you must create it first. Use the following format:
<?xml version="1.0"?>
<configuration>
. . .
<appSettings>
<add key="SaveIntermediateResult"value="false" />
<add key="CacheSize"value="32" />
</appSettings>
</configuration>
2. Go to the tag appSettings, and then change the parameters which are specified
as key and value attributes of an add tag.
3. Use a CacheSize parameter, for example:

<appSettings>
<add key="CacheSize"value="20" />
</appSettings>
4. Optional Optionally, you can use following parameters:
CacheLifeTime
Minimizes the cache size on a production system by switching to non-
buffered mode. The cache entries are deleted as soon as a job is terminated.
The specified cache size does not take effect in this case.
SaveIntermediateResult
Reduces further cache size by specifying that intermediate results that are
useful for error analysis but are not needed for the following processing
steps should not be stored in the cache folder.

4.6. Working with configuration data (production system)
Example: The example shows the respective part of the configuration file where the
appSettings tab and the two additional parameters have been added:
<?xml version="1.0"?>
<configuration>
. . .
<appSettings>
<add key="CacheLifetime"value="NonBuffered" />
<add key="SaveIntermediateResult"value="false" />
</appSettings>
</configuration>
Tip: To modify these parameter settings temporarily, for example to analyze

problems, you can set CacheLifetime to Buffered, and
SaveIntermediateResult to true.
4.6 Working with configuration data (production

system)
After performing the installation steps described in chapter “Installing Intelligent
Capture for SAP® Solutions“ on page 19, your Intelligent Capture for SAP®
Solutions configuration consists of a defined amount of server cluster nodes (=
Cluster Master).
The following sections describe which components are located on which participants
and how the different participants interact in respect to the components.
4.6.1 Technical configuration data

4.6.1.1 Load Manager files
An Intelligent Capture for SAP® Solutions Server Cluster contains one Intelligent
Capture for SAP® Solutions Cluster Master (= Intelligent Capture for SAP® Solutions
Server). The Cluster Master distributes the workload on the hardware of
the Intelligent Capture for SAP® Solutions Cluster. The Cluster has to be configured
on the Cluster Master with the Load Manager Configuration tool. For more
information, see “Configuring cluster nodes” on page 49. The Load Manager
Configuration tool saves the cluster configuration files into the folder
%ALLUSERSPROFILE%\Application Data\Captaris\DOKuStar Load Manager on the
Cluster Master.

4.6.1.2 Trace configuration files

Each participant of a Intelligent Capture for SAP® Solutions system writes trace files
to its local trace folder %ALLUSERSPROFILE%\Application Data\Open Text\Trace.
In the trace folder there are several trace configuration files specifying, for example,
the trace level of the trace messages. For more information, see “Configuring
tracing” on page 33.
4.6.2 Runtime files

4.6.2.1 Temporary files of Document Reader and Document Extraction
On the Intelligent Capture for SAP® Solutions Cluster Nodes the actual extraction is
done by a component named Document Extraction. Superordinate tasks, like
splitting of pages or export of results are done by a component named Document
Reader. Both components write temporary files into the Microsoft Windows temp
folder.
If the Load Manager Service of a Intelligent Capture for SAP® Solutions Cluster
Node is running using the LocalSystem account, which is the default, the
temporary files are written into the temp folder defined in the system temp variable.
4.6.2.2 Trace folder

You can change the location of the Trace folder by creating a registry entry. For
more information, see “Configuring tracing” on page 33.
4.6.3 Registry entries

During installation, Intelligent Capture for SAP® Solutions adds some entries to the
Microsoft Windows registry, for example installation paths and version information.
4.6.4 Microsoft Windows Services

Intelligent Capture for SAP® Solutions is based on OpenText™ Capture Center. The
runtime environment of Capture Center consists of several programs and Microsoft
Windows Services. In the standard configuration, the following Capture Center
Microsoft Windows Service runs on the Intelligent Capture for SAP® Solutions
Server:
• Load Manager Service (DOKuStar Load Manager)

The Load Manager Service on the Intelligent Capture for SAP® Solutions Server
distributes the workload on the Intelligent Capture for SAP® Solutions Server
Nodes by communicating with the Load Manager Services on the nodes.
The Microsoft Windows Service is started automatically after the installation and at
every system start. In case of failures, you may need to stop, start, or restart a
service. For more information, see “Starting and stopping Microsoft Windows
Services on the Intelligent Capture for SAP® Solutions Server” on page 52.

4.6. Working with configuration data (production system)
4.6.5 Moving Intelligent Capture for SAP® Solutions data to a

different location
By default, Intelligent Capture for SAP® Solutions stores all configuration files and
all temporary files in different folders on the system drive. Sometimes the system
drive is reserved for operating system data and it is not allowed to store any
application-specific data on the system drive. In this case, you can move most of the
configuration and runtime data of Intelligent Capture for SAP® Solutions to a
different location.
4.6.5.1 Configuring cache location

The caches used to store temporary recognition and download data reside in a
subfolder DOKuStar Professional/3.0/Cache of the temporary files folder on the
Intelligent Capture for SAP® Solutions Server and each Intelligent Capture for SAP®
Solutions Server Node. It uses the user account that you specified in the Service
Account dialog box during installation. You can move this data to a different
location.
To move files created in the temporary files folder to a different location:
1. Create the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open

Text\Capture Common.
2. At this key, create a string value tempPath containing the path for these data.
3. For the change to take effect, restart the service DOKuStar Load Manager.
Alternatively, you can move the location of the whole temporary files folder using
Control Panel.
4.6.5.2 Configuring trace file location

Trace file location is controlled by a registry value on each Intelligent Capture for
SAP® Solutions Server. For more information, see “Trace root path” on page 34.
4.6.5.3 Configuring program data location of components

By default, the Load Manager creates configuration files in subfolders of the
%PROGRAMDATA% folder on the system drive.
You can move the program data files, for example to a different drive.
To move program data files to a different location:
1. Create the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open

Text\Capture Common.
2. For this key, create a string value named CommonApplicationDataPath

containing the path for these program data.

4.7 Configuring load balancing

4.7.1 Understanding the Load Manager
The Load Manager enables load balancing of multiple instances of the Intelligent
Capture for SAP® Solutions Server on a multi-processor system. This provides a
scalable performance, and a load balancing capable of both multi-client and multi-
application.
The Load Manager is a Microsoft Windows Service which runs on the Intelligent
Capture for SAP® Solutions Server. This Microsoft Windows Service is started
automatically after installation and at every system start. The Load Manager on the
Intelligent Capture for SAP® Solutions Server is the master and controls the load
balancing. This master receives job requests and distributes these tasks. Usually the
Intelligent Capture for SAP® Solutions Cluster contains as many cluster nodes as
processors. If the Intelligent Capture for SAP® Solutions Server is a two-processor
computer and if there are no further Intelligent Capture for SAP® Solutions Server
Nodes, the Intelligent Capture for SAP® Solutions Cluster will consist of two Cluster
Nodes.
A Cluster Node hosts a service of a specified type called the Service Type. For the
Intelligent Capture for SAP® Solutions Server, the default services
types are Document Extraction, Learning (Feedback) and Configuration.
The Intelligent Capture for SAP® Solutions Server automatically creates and
configures the appropriate jobs which runs within specific Cluster Nodes at the
Load Manager. You do not need to configure them manually.
The Load Manager processes a job request by creating an operation. The Load
Manager keeps a list of waiting and active operations and manages them until their
execution has been completed.
The Jobs view and the Cluster view on the Intelligent Capture for SAP® Solutions
Server Cluster Monitor permit to monitor the Load Manager.
The cluster configuration is managed centrally at the Intelligent Capture for SAP®
Solutions Server. You can configure the Intelligent Capture for SAP® Solutions
Server Cluster with the Load Manager Configuration tool hosted within the Cluster
Monitor.
To open the Cluster Monitor:
1. Click the Start menu.
2. Type Cluster Monitor.
3. In the Apps list, select Cluster Monitor.

4.7. Configuring load balancing
To open the Load Manager Configuration:
• In the Cluster Monitor, on the Tools menu, click Cluster Configuration.
4.7.2 Configuring cluster nodes

The cluster nodes and load balancing will be configured automatically during
installation and/or when processing is started, that is after the first run of an
Intelligent Capture for SAP® Solutions job, triggered by the external SAP system and
passed to by internal Load Manager.
The pre-configuration of the Intelligent Capture for SAP® Solutions Server Cluster
will setup a defined number of cluster nodes which depends on the available system
hardware, that is one Intelligent Capture for SAP® Solutions Server Node for each
processor of the Intelligent Capture for SAP® Solutions Server. The pre-
configuration of the Intelligent Capture for SAP® Solutions Server Cluster will look
as follows on a computer with four processors:
With a high number of processing nodes, you also need more RAM to be able to use
them effectively or throughput will decrease because of increased swapping.
Typically, you need about 1.5 GB per Runtime Node.

4.7.2.1 Changing cluster node properties

To change the properties of a cluster node:
1. Open the Load Manager Configuration.
2. In the Load Manager Configuration dialog box, click the Cluster node you
want to change in the tree view.
3. Click the property you want to change, define the value, and then click OK.
LookupInterval
Time interval after which the Load Manager checks whether the cluster
node is still alive.
Operation Types
Load Manager operation type.
Optimization Time Window
To prevent loading time, the Load Manager tries to assign an operation of
the currently loaded operation type to a node that becomes available. As
soon as the first operation in the Load Manager queue waits longer than the
specified time, it is assigned to the next available node. Enter the time in the
format hh:mm:ss.
Process Priority
With the default value BelowNormal, priority of the computationally
intensive Runtime Node processes is reduced. Otherwise other important
processes would often have to wait for processor time and would respond
slowly. If you set this property to Normal, priority is not reduced.
Reset Cycle
After the specified number of operations the cluster node is reset
automatically. This can also be used to ensure that the project is reloaded.
Reset on failure
If this property has the value True, the Load Manager tries to reset the
cluster node in case of failure.
Startup Time
Specifies the maximum time the Runtime Nodes should need for start-up. If
the start-up of a Runtime Node exceeds this limit, the corresponding
process is terminated. Enter the time in the format hh:mm:ss.
Use IPC Channel
As default, the Load Manager uses TCP for communication with the local
cluster nodes. If this property is set to True, it uses IPC channels (named
pipes) instead.

4.7. Configuring load balancing
4.7.2.2 Changing Intelligent Capture for SAP® Solutions Server Node

properties
Note: Within Intelligent Capture for SAP® Solutions you do not need to
modify any properties.
To change the properties of a Intelligent Capture for SAP® Solutions Server

Node:
1. Open the Load Manager Configuration.
2. In the Load Manager Configuration dialog box, click the Intelligent Capture for
SAP® Solutions Server Node you want to change in the tree view.
3. Click the property you want to change, define the value, and then click OK.
Name
Cannot be edited. It is comprised from the computer name, service type and
instance number.
Agent Url
URL of the agent service for this cluster node within the cluster.
Description
Only for logging purposes.
Exclusive Operation Types
Restricts a cluster node to the specified Load Manager operation types.
Priority
Priority of the cluster node. The Load Manager prefers Runtime Nodes with
a higher priority value when it wants to assign an operation to a Runtime
Node. The default value is 0. To give a node a higher priority, enter a value
greater 0, to give a node lower priority, you can enter a negative value.

4.8 Starting and stopping Microsoft Windows

Services on the Intelligent Capture for SAP®
Solutions Server
Tip: If after system reboot a Microsoft Windows Service does not automatically
start although its Startup Type is set to Automatic, set the Startup Type to
Automatic (Delayed Start).
To stop, start, or restart a service:
1. Use Microsoft Windows shortcut keys WIN + R to launch Run.
2. Type services.msc into the dialog box.
3. Press Enter.
4.9 Setting up the SLD registration on the SAP

system
You set up the SLD registration on the SAP system with the Intelligent Capture for
SAP® Solutions application specific data.
To get the Intelligent Capture for SAP® Solutions application specific data:
1. Open the IIS manager, and then click the site with the default name
The settings should be the same as listed in step 2 and 3.
2. In the Actions view, click Basic Settings, and then copy the following settings:
• Site name: InformationExtractionService

• Application pool: InformationExtractionService
• Physical path: C:\Program Files (x86)\Open Text\Intelligent Capture
for SAP Solutions <version>\WebServiceAPI
3. In the Actions view, click Bindings, and then copy the following settings:
• Type: http
• Binding Information:
To set up the SLD registration on the SAP system:
1. Install SAP Diagnostics Agent, and then connect it to Solution Manager. For
more information, see SAP Note 1365123.
2. Upgrade the SAP Host Agent to the latest version. For more information, see
SAP Note 2598404.

4.9. Setting up the SLD registration on the SAP system
3. Open the Agent Administration in Solution Manager, and then click the Non-
authenticated Agents tab.
4. Update the Diagnostic Agent agent, and then click Trust Agents.
5. Open Landscape Management (LMDB), click Technical Systems > Select Type:
Microsoft Internet Information Services.
6. Expand the IIS tree.
a. Click Software, and then add and configure the Product Instances, and
Software Component Versions.
b. Click Technical Instances, and then copy the Intelligent Capture for SAP®
Solutions application specific data into the corresponding areas.
MSIIS Applications
• Site Name: InformationExtractionService

• Application Path: C:\Program Files (x86)\Open Text\
Intelligent Capture for SAP Solutions <version>
\WebServiceAPI
MSIIS Pools
• Name of Application Pool: InformationExtractionService
MSIIS Sites
• Site Name: InformationExtractionService

• Web Binding Info:
• Web Protocol: http

Chapter 5
Monitoring Intelligent Capture for SAP® Solutions
For monitoring of an Intelligent Capture for SAP® Solutions system, you can use
external monitoring tools, and the Inbound Configuration and Inbound
Administration work center in VIM or Business Center. For more information, see
section 4 “Business Center Workplace: Inbound Administration work center” in
OpenText Business Center for SAP Solutions - User Guide (BOCP-UGD), and section 4
“Inbound Configuration” in OpenText Business Center for SAP Solutions -
Configuration Guide (BOCP-CGD).
Monitoring Intelligent Capture for SAP® Solutions with external monitoring

tools
If you monitor Intelligent Capture for SAP® Solutions with external monitoring
tools, take the following considerations into account:
• CPU usage: On the server and on Recognition Nodes, CPU usage will often be at
100% while a document is being processed. Whereas a single page is processed in
a few seconds, processing may take up to several minutes for a document with a
large number of pages. Therefore high CPU usage may indicate a problem only if
it persists for more than about 5 to 10 minutes depending on the maximum
number of pages of your documents.
• Disk space: Intelligent Capture for SAP® Solutions does not collect and
accumulate data. Temporary files written during document processing are being
deleted when the document is exported. Trace files are deleted automatically
after several days. Therefore disk space should pose no problems if you provided
sufficient resources.
• Main memory: Because the Cluster Node processes on the Intelligent Capture for
SAP® Solutions Server and the Recognition Nodes are reset automatically after a
certain number of documents has been processed, main memory usage should
not grow on the long run. If you provided sufficient main memory depending on
the number of Cluster Nodes, main memory problems should not occur.
• Microsoft Windows Service: For document processing, the Microsoft Windows
Service DOKuStar Load Manager must be available. Therefore it is meaningful
to monitor whether this service is running. If a service is not running, start it.

Chapter 6
Configuring high availability
The most critical part of a Intelligent Capture for SAP® Solutions system is the BC
Inbound Configuration, or the ICC Dispatcher, respectively. These components are
parts of VIM or Business Center in SAP ERP. Therefore their high availability is
guaranteed.
The application configuration data are stored in SAP ERP. Therefore, the high
availability of the application configuration data is guaranteed.
The Operation Nodes which runs on the Intelligent Capture for SAP® Solutions
Server are not critical at all. Therefore, there is no fail-over scenario defined for
them.
For more information about high availability in SAP ERP, see the SAP Netweaver
Technical Operations Manual (https://help.sap.com/doc/erp2005_ehp_03/6.03/en-US/
72/cd1e4261ea5433e10000000a155106/frameset.htm).
In general, high availability can be achieved on the Intelligent Capture for SAP®
Solutions Server by configuration of a standard Microsoft Windows server. It
depends very much on the data center infrastructure.
There are several options for configuring high availability. Two most common
options are:
• Option 1: Simply add one or more additional Intelligent Capture for SAP®
Solutions Servers (VMs), and add load balancing to automatically distribute
requests to all servers. If one of the servers fails, the second server takes all
requests. The SAP system sends the requests to the load balancer, regardless of
how many servers are available in the background.
• Option 2: Take a snapshot of the Intelligent Capture for SAP® Solutions Server
(VM). If the monitoring states of the server VM fail, a new VM with the snapshot
is started immediately. As a result, Intelligent Capture for SAP® Solutions Server
is unavailable for a short period of time. But due to the asynchronous process,
there may be still enough documents in the system that are already OCR-ed but
not yet processed by the users. The users will therefore not notice that the
Intelligent Capture for SAP® Solutions Server is unavailable for a short period of
time.
Replacing the Intelligent Capture for SAP® Solutions Server is possible because this
server does not hold any data or status information: Learning data and profiles are
stored in the SAP database. Status data are stored in the SAP system: Requests,
Validation tasks or Feedback that could not be completed due to the switch to a new
server are repeated by the SAP system according to the settings for automatic retries.

Chapter 7
Configuring security
7.1 User management and authorization concept

Intelligent Capture for SAP® Solutions has no own user management. It uses
Microsoft Windows user management. It is not possible to define or change
Microsoft Windows users within Intelligent Capture for SAP® Solutions. Provide the
required user accounts using the respective Microsoft Windows if needed.
Per default the Load Manager service runs under Local System. There is no need to
change this setting to a domain user account as long as no remote communication
will be setup.
If you want to use a domain user account for running the service, you must prepare
it before the installation and enter during installation. In this case the Load Manager
Service user must have local administrator rights.
For more information about using the Microsoft Windows user management, see
Best Practice Guide for Securing Active Directory Installations (https://
docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-
practices/best-practices-for-securing-active-directory).
7.2 Logging of security-relevant events

Because Intelligent Capture for SAP® Solutions uses the Microsoft Windows user
management, you can use the Microsoft Windows features to log security events in
the Microsoft Windows event folder. To define which security events should be
logged by Microsoft Windows, implement an audit policy. For more information,
see the Microsoft Windows Server 2016 Security Guide (http://
download.microsoft.com/download/5/8/5/585DF9E9-
D3D6-410A-8B51-81C7FC9A727C/
Windows_Server_2016_Security_Guide_EN_US.pdf).
Security-relevant events on the SAP ERP side can be logged using SAP ERP means.

Chapter 7 Configuring security
7.3 Encryption of communication channels

All participants of a Intelligent Capture for SAP® Solutions system communicate
with the BC Inbound Configuration in SAP ERP by HTTP or HTTPS, depending on
the configuration of the web service.
7.4 Secure configuration

Intelligent Capture for SAP® Solutions provides a secure configuration by default:
• All application specific configuration is stored in SAP ERP.

• The heart of a Intelligent Capture for SAP® Solutions system, BC Inbound
Configuration/ICC Dispatcher, is an SAP ERP component.
• The repository is part of the SAP ERP system.
• HTTPS communication can be setup with the use of client/server certificates.
For those who participate in the customization and implementation of VIM with a
special focus on security aspects, see OpenText Vendor Invoice Management for SAP
Solutions - Security Guide (VIM-GSM).
7.5 Security updates

OpenText recommends to always apply latest security fixes from Microsoft.
Especially install security fix CVE-2020-0646 for Microsoft .NET Framework. For
more information, see https://portal.msrc.microsoft.com/en-US/security-guidance/
advisory/CVE-2020-0646.
Also refer to the information about unused OpenSSL files (Windows x86 and
Windows x64) in “Asian Language Option” available as patch note for CRE/CFPR
Asian Languages Option 7.8 and 16.6. For more information, see https://
knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=77613388&
objAction=browse&viewType=1.
7.6 Responsibilities
In an Intelligent Capture for SAP® Solutions system, no real users are involved.
On the VIM/Business Center SAP system, there are additional user types and
responsibilities.

Chapter 8
Troubleshooting
VIM or Business Center manages the documents which are then proceed by
Intelligent Capture for SAP® Solutions. The components manage a list of all
documents and their current states. This list can be monitored with defined tools in
SAP ERP. When a specific request cannot be processed by the Intelligent Capture for
SAP® Solutions Server, the corresponding entry in the SAP ERP system gets an error
status.
Communication issues
All communication between the SAP ERP system and the Intelligent Capture for
SAP® Solutions Server takes place using HTTP(S). All HTTP(S) request are
logged by the Intelligent Capture for SAP® Solutions Server and Intelligent
Capture for SAP® Solutions application level also. In general, there could be
various reasons for communication problems using HTTP(S).
IIS web server
Before the Intelligent Capture for SAP® Solutions web application receives any
incoming requests, IIS is checking for valid HTTP(S) first. By default, all IIS logs
are written to the local folder C:\inetpub\logs\LogFiles. The incoming
requests are logged to specific trace files having timestamp information in the
file name.
Example: No client certificate is send with the HTTPS request, although it is requested
by the service. In this case the IIS refuses the request with the following response: “HTTP
error code: 403 / HTTP error message: The page you are attempting to access requires
your browser to have a Secure Sockets Layer (SSL) client certificate that the Web server
recognizes.”
In case IIS reports the HTTP error code 403 13, disable the client revocation
check on the IIS web server as described in https://blogs.msdn.microsoft.com/
kaushal/2012/10/15/disable-client-certificate-revocation-crl-check-on-iis.
Intelligent Capture for SAP® Solutions web application
The Intelligent Capture for SAP® Solutions web application defines the
following specific HTTP response codes for temporary and permanent error
cases:
• Issue with action specific data: HTTP 400 (bad request)

• Unsupported action or protocol version: HTTP 501 (not implemented)
• Service unavailable (for example due to overload or repository not
accessible): HTTP 503 (service unavailable)
• Other permanent errors: HTTP 500 (internal server error)
If an error occurs refer to the application traces for more information. The
Intelligent Capture for SAP® Solutions web application logs are written to a

Chapter 8 Troubleshooting
specific trace folder and can be viewed using the Trace Viewer Tool. For more
information, see “Configuring tracing” on page 33.
Monitoring activity
The Intelligent Capture for SAP® Solutions setup installs following tools which
helps you monitoring the requests:
• Cluster Monitor. For more information, see “Configuring cluster nodes”

on page 49.
• Trace Viewer. For more information, see “Analyzing trace files using Trace
Viewer” on page 39.
Additional Intelligent Capture for SAP® Solutions offers a web page where
general information about the service and jobs which has been processed are
available. You can open the web page using http(s)://<hostname>:<port>/
status.aspx.
You can see the last jobs that were processed, together with eventual errors.
Only a limited number of jobs is shown. It may even happen that memory was
recently cleared and no details are shown, this is not an error. In this case check
the status again a few minutes later.
Restart web service and Microsoft Windows Service
Sometimes temporary issues can be resolved by restarting the Intelligent
Capture for SAP® Solutions web service on the IIS Manager and additionally
restarting the Microsoft Windows Service DOKuStar Load Manager.
If the status web page cannot be displayed on a web browser running on a
remote system, wait for a few minutes to see whether this is only a temporary
network problem. If the issue persists, restart the web service.
If some of the runtime jobs run into same error case, first stop the Intelligent
Capture for SAP® Solutions web service on the IIS Manager and, if the service
has been stopped, wait for a view minutes, and then restart the Microsoft
Windows Service DOKuStar Load Manager.

OpenText Intelligent Capture For SAP Solutions 16.7.1 - Administration Guide English (CPIE160701-AGD-EN-04) PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OpenText Intelligent Capture For SAP Solutions 16.7.1 - Administration Guide English (CPIE160701-AGD-EN-04) PDF

Hochgeladen von

Copyright:

Verfügbare Formate

OpenText™ Intelligent Capture for SAP®

This guide describes how to install and configure OpenText

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Copyright © 2020 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

2 Installing Intelligent Capture for SAP® Solutions ................. 19

3 Upgrading Intelligent Capture for SAP® Solutions .............. 25

4 Configuring Intelligent Capture for SAP® Solutions ............ 27

CPIE160701-AGD-EN-04 Administration Guide iii

4.4.8.3 Searching trace messages .............................................................. 43

5 Monitoring Intelligent Capture for SAP® Solutions .............. 55

6 Configuring high availability .................................................. 57

7 Configuring security ............................................................... 59

iv OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

About Intelligent Capture for SAP® Solutions

• OpenText™ Intelligent Capture for SAP® Solutions, formerly known as

1.1 How does it work?

As a single, unified extraction service, the solution supports OpenText™ Vendor

Intelligent Capture for SAP® Solutions is easy to:

• Deploy: The configuration is completely done in VIM and Business Center. No

• OpenText™ Invoice Capture Center for SAP® Solutions. For more

CPIE160701-AGD-EN-04 Administration Guide 5

6 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

1.3 Machine learning

CPIE160701-AGD-EN-04 Administration Guide 7

8 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

CPIE160701-AGD-EN-04 Administration Guide 9

10 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

CPIE160701-AGD-EN-04 Administration Guide 11

Learning is permanently active for adapting continuously to the documents

No training phase is required as the system learns unattended in the background.

12 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

1.4 Architecture and SAP integration

• Configuration Service: Receives configuration data for recognition profiles

CPIE160701-AGD-EN-04 Administration Guide 13

1.5 Solutions and profile configuration

The configuration of the solutions is completely done in BC Inbound IMG, that

14 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

CPIE160701-AGD-EN-04 Administration Guide 15

1.6 Supported languages

16 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

Intelligent Capture for SAP® Solutions supports multi-country profiles. Countries

• Country groups related to company codes in SAP.

1.7 Supported image formats

CPIE160701-AGD-EN-04 Administration Guide 17

2.1 Installation procedure overview

• For more information on supported platforms, hardware and software

CPIE160701-AGD-EN-04 Administration Guide 19

• The available system resources will be shared between both products

2. Optional Install Asian languages.

2.2 Prerequisites for the installation

To install and configure IIS:

1. Start the Server Manager.

2. On the Dashboard, click Add roles and features.

3. Proceed to the Server Roles page.

4. Select Web Server (IIS).

6. Click Next and then click Install.

2.3 Installing Intelligent Capture for SAP® Solutions

1. In the root folder of the installation media, start setup.exe, or run

2. In the Welcome dialog box, click Next.

20 OpenText™ Intelligent Capture for SAP® Solutions CPIE160701-AGD-EN-04

2.4 Installing Asian languages