OpenText Intelligent Capture For SAP Solutions CE 23.2 - Installation and Administration Guide English (CPIE230200-AGD-EN-02)

OpenText™ Intelligent Capture for SAP®
Solutions
Installation and Administration Guide
Describes how to install and configure OpenText Intelligent

Capture for SAP Solutions.
CPIE230200-AGD-EN-02
OpenText™ Intelligent Capture for SAP® Solutions
Installation and Administration Guide
CPIE230200-AGD-EN-02
Rev.: 2023-July-20
This documentation has been created for OpenText™ Intelligent Capture for SAP® Solutions CE 23.2.
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 © 2023 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 Technical operations ......................................................................... 8
1.3.1 Improving the recognition process ...................................................... 8
1.3.2 Optimizing scan results ..................................................................... 8
1.3.3 Configuring Indian QR code signature check for invoices ..................... 9
2 Installing Intelligent Capture for SAP® Solutions ................. 11

2.1 Installation procedure overview ........................................................ 11
2.2 Prerequisites for the installation ....................................................... 12
2.3 Installing Intelligent Capture for SAP® Solutions ................................ 13
2.4 Installing Asian languages ............................................................... 14
2.5 Installing patches and service packs ................................................. 14
2.6 Installing the Imaging Plug-in ........................................................... 15
3 Installing Windows Validation Client ..................................... 17
4 Installing Single Click Entry for SAP GUI .............................. 19
5 Upgrading Intelligent Capture for SAP® Solutions .............. 21
6 Configuring Intelligent Capture for SAP® Solutions ............ 23

6.1 Adding a certificate for client/server authentication for secure
communication using HTTPS (optional) ............................................ 23
6.2 Configuring the web service ............................................................. 23
6.2.1 Specifying the application pool ......................................................... 24
6.2.2 Increasing the timeout setting for ASP.NET application sessions ........ 24
6.2.3 Configuring SSL settings for secure communication using HTTPS
(optional) ........................................................................................ 25
6.2.4 Increasing the upload size (IIS 7.0 and later versions) ....................... 25
6.2.5 Configuring internal application settings ............................................ 26
6.3 Configuring tracing .......................................................................... 28
6.3.1 Tracers ........................................................................................... 28
6.3.2 Trace listeners ................................................................................ 29
6.3.3 Trace root path ............................................................................... 29
6.3.4 Trace levels .................................................................................... 30
6.3.5 Trace configuration ......................................................................... 31
6.3.6 Location of trace files and trace configuration files ............................. 33
6.3.7 Format of traces .............................................................................. 33
6.3.8 Analyzing trace files using Trace Viewer ........................................... 34
6.3.8.1 Selecting a trace configuration ......................................................... 36
CPIE230200-AGD-EN-02 Installation and Administration Guide iii

Table of Contents
6.3.8.2 Filtering messages .......................................................................... 37

6.3.8.3 Searching trace messages .............................................................. 38
6.4 Controlling cache behavior .............................................................. 39
6.5 Working with configuration data (production system) ......................... 39
6.5.1 Technical configuration data ............................................................ 39
6.5.1.1 Load Manager files .......................................................................... 39
6.5.1.2 Trace configuration files ................................................................... 40
6.5.2 Runtime files ................................................................................... 40
6.5.2.1 Temporary files of Document Reader and Document Extraction ......... 40
6.5.2.2 Trace folder .................................................................................... 40
6.5.3 Registry entries ............................................................................... 40
6.5.4 Microsoft Windows Services ............................................................ 40
6.5.5 Moving Intelligent Capture for SAP® Solutions data to a different
location .......................................................................................... 41
6.5.5.1 Configuring cache location ............................................................... 41
6.5.5.2 Configuring trace file location ........................................................... 41
6.5.5.3 Configuring program data location of components ............................. 41
6.6 Configuring load balancing .............................................................. 42
6.6.1 Understanding the Load Manager .................................................... 42
6.6.2 Configuring cluster nodes ................................................................ 43
6.6.2.1 Changing cluster node properties ..................................................... 44
6.6.2.2 Changing IES Server Node properties .............................................. 45
6.6.2.3 Installing a higher number of cluster nodes ....................................... 46
6.7 Starting and stopping Microsoft Windows Services on the Intelligent
Capture for SAP® Solutions Server .................................................. 47
6.8 Setting up and configuring SLD registration ...................................... 47
6.8.1 Setting up the SLD registration for IES Webservice ........................... 47
6.8.2 Configuring the SLD Data Supplier for IES engine ............................. 48
7 Monitoring Intelligent Capture for SAP® Solutions .............. 51
8 Configuring high availability .................................................. 53
9 Configuring security ............................................................... 55

9.1 User management and authorization concept ................................... 55
9.2 Authorizations for validation user and extraction user ........................ 55
9.3 Logging of security-relevant events .................................................. 57
9.4 Encryption of communication channels ............................................. 57
9.5 Secure configuration ....................................................................... 57
9.6 Security updates ............................................................................. 57
9.7 Responsibilities ............................................................................... 58
10 Troubleshooting ...................................................................... 59
iv OpenText™ Intelligent Capture for SAP® Solutions CPIE230200-AGD-EN-02

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)
For more information, see the landing page for:
• Core Capture for SAP® Solutions on My Support (https://support.opentext.com/

csm?id=csm_enterprise_product&sys_id=f390d2c01b3a891061a7a8e22a4bcb5d)
• Core Capture for SAP® Solutions on My Support (https://support.opentext.com/
csm?id=csm_enterprise_product&sys_id=3920928c1bf6891061a7a8e22a4bcbd2)
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)) 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. 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 solutions.
For more information, see OpenText Capture for SAP Solutions - Best Practices Guide
(CPVIM-GIE).
Following scenarios/solutions are supported:
VIM
• Intelligent Capture for SAP® Solutions. For more information, see section 7.2
“Integration with Information Extraction Service” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Invoice Solution (VIM-CGD).
CPIE230200-AGD-EN-02 Installation and Administration Guide 5

Chapter 1 About Intelligent Capture for SAP® Solutions
• Solution for Incoming Sales Orders. For more information, see part II “Solution
for Incoming Sales Orders” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP-CCS).
• Solution for Incoming Quotations. For more information, see part III “Solution
for Incoming Quotations” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP-CCS).
• Solution for Incoming Delivery Notes. For more information, see part IV
“Solution for Incoming Delivery Notes” in OpenText Vendor Invoice Management
for SAP Solutions - Configuration Guide for Solutions Beyond Invoice (BOCP-CCS).
• Solution for Incoming Order Confirmations. For more information, see part V
“Solution for Incoming Order Confirmations” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Solutions Beyond Invoice
(BOCP-CCS).
• Solution for Incoming Remittance Advices. For more information, see part VI
“Solution for Incoming Remittance Advices” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Solutions Beyond Invoice
(BOCP-CCS).
6 OpenText™ Intelligent Capture for SAP® Solutions CPIE230200-AGD-EN-02

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 for invoices.
VIM integration Beyond excellent recognition results, the tight integration of Intelligent Capture for
SAP® Solutions with VIM provides an ideal technical footprint, 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. For more information, see
section 5.2.1.1 “Architecture” in OpenText Vendor Invoice Management for SAP
Solutions - Configuration Guide for Foundation (VIM-CGF).
BCC integration Customers using 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 Inbound component of OpenText Process Base. You can use
existing Windows Validation Clients for processing Intelligent Capture for SAP®
Solutions profiles in parallel to ICC and BCC applications.
Solutions and Intelligent Capture for SAP® Solutions supports all VIM solutions. For more
profile configu- information, see “Following scenarios/solutions are supported:”. The configuration
ration
of the solutions is completely done in the VIM Foundation Inbound component, that
means there is no configuration needed on the Intelligent Capture for SAP®
Solutions Server. For more information, see section 5.2.1.2 “Scenarios and Capture
profile concept” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Foundation (VIM-CGF). Here you can find information about
the IDF configuration, business solutions, the profile configuration, and a
description of the complete document processing data flow beginning with inbound
scanning or email, and ending with starting the VIM workflow.
Machine The key advantage of Intelligent Capture for SAP® Solutions is the reduction of
learning implementation and configuration efforts, combined with fast learning success. That
is why Intelligent Capture for SAP® Solutions includes preconfigured scenarios. For
more information, see section 5.2.1.4 “Machine learning” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (VIM-CGF).
Pre-learning of You can reuse validated extraction results from OpenText™ Invoice Capture Center
profiles for SAP® Solutions (ICC), and BCC to train Intelligent Capture for SAP® Solutions
profiles. This feature is called Pre-learning. For more information, see section 2.4
“Pre-learning of IES Profiles” in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM-AGD).

Chapter 1 About Intelligent Capture for SAP® Solutions
1.3 Technical operations

1.3.1 Improving the recognition process
You can use separator sheets for attachment separation. Each activated method for
attachment separation is checked at each page and will force extraction to stop. For
more information, see also section 3.21 “Stopping recognition using a separator
sheet (patch code sheet)” in OpenText Capture Validation for SAP Solutions - User Guide
(CPIE-UGD).
Note: Use automatic separation only for processing PDF files.
You can find the separator sheet as TIFF and PDF file in the SampleImagesIES
subfolder within the installation folder or on My Support (https://
knowledge.opentext.com/) searching for separatorsheet.zip.
1.3.2 Optimizing scan results

To achieve optimum character recognition results, optimize the quality of scanned
images not only on the production system but also during testing.
• Sort the paper pages for scanning according to the configured profiles, based on
contents and paper quality. This should be done in the following ways:
– Sort the documents according to the contents (for example invoices), because
the documents will be dealt with differently in terms of their technical
processing, workflows, storage durations, and access rights.
– Sort the documents according to their legibility (for example bad, medium,
good). In some cases it is necessary to insert separator sheets between the
individual documents. The documents are separated for further processing.
• Use professional scanning equipment to achieve optimal image quality.
• Optimize the scanner settings. Documents should be scanned with 300 dpi and
compressed with Fax4. Lower resolution or other compression modes may
worsen the recognition results. OpenText recommends not to use a resolution
higher than 300 dpi, as this increases the data volume but not the recognition
quality.
• If possible, do not use color scanning, as color images significantly increase the
data volume and slow down processing, while recognition quality is not
increased in most cases.
• Especially for barcode detection either switch the scanner to binary mode or turn
off compression if you want to keep the grayscale mode.
• If documents of specific vendors have bad printing quality, bad paper quality, or
an unsuitable layout, contact the vendors. Crumpled, creased or wrinkled paper
cannot produce reliably good results as the geometry is skewed.

1.3. Technical operations
If documents from certain vendors have poor print quality, bad paper quality, or
unsuitable layout, contact the vendors. Crumpled, creased, or wrinkled paper
cannot produce reliably good results because the geometry will be distorted.
• Chinese forms are usually smaller than documents from other countries. Images
of such forms should not have a white frame. For optimal recognition results,
forms should be aligned with the upper left corner of the image.
• Documents should not be stamped or marked. This deteriorates the recognition
results.
1.3.3 Configuring Indian QR code signature check for

invoices
Intelligent Capture for SAP® Solutions uses Indian e-invoice public keys for the
verification of signed content, that is Intelligent Capture for SAP® Solutions captures
the Indian QR code and checks if the contained signature is valid.
Note: The certificates are regularly updated on the portal. Make sure that you
always use the latest certificate.
To configure the Indian QR code signature check for invoices:
1. On https://einvoice1-trial.nic.in/Others/Publickeys, download all certificates for

Production purposes.
Note: You must install all certificates, because it is not known in which
period the invoice was signed.
2. Copy the certificates to the Certificates Store.
a. Click Start, type certificate, and then select Manage computer

certificates.
b. In Certificates - Local Computer > Personal > Certificates, right-click, and
then click All Tasks > Import.
c. In the Certificates Import Wizard, click Next.
In the Store Location field, Local Machine must be selected.
d. In the File to Import dialog box, search for the certificate, and then click
Next.
Tip: You must upload all certificates individually unless you use the
procedure described in the dialog box.
e. In the Certificate Store dialog box, place all certificates in the Personal
certificate store, and then click Next.
f. In the Completing the Certificates Import Wizard dialog box, click Finish.
g. Repeat these steps for all certificates.

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 on
OpenText My Support (https://knowledge.opentext.com/).
• The software is available on My Support (https://knowledge.opentext.com/)
as product ISO image searching for opentext intelligent capture for sap
solutions ce <version>.iso. For <version>, enter for example 23.2
corresponding to the version of the OpenText products you use.
• 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.
• Install the most recent version and patch for the Capture Imaging Plug-In on
the Intelligent Capture for SAP® Solutions server. For more information, see
“Installing the Imaging Plug-in” on page 15. For supported versions, see the
Release Notes.
• The descriptions in this guide are based on the assumption that VIM 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 13.
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. For more information, see section 5.2 “Information Extraction
Service” in OpenText Vendor Invoice Management for SAP Solutions - Configuration
Guide for Foundation (VIM-CGF).
4. Install Windows Validation Client. For more information, see “Installing

Windows Validation Client“ on page 17.
Note: Windows Validation Client cannot be installed and run on the same
computer 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 19.
2.2 Prerequisites for the installation

Before you install Intelligent Capture for SAP® Solutions, install Microsoft Internet
Information Services (IIS).
If you want to use HTTP/2 you must enable the HTTPS communication on Windows
Server 2016 and 2019. For more information, see HTTP/2 on IIS (https://
docs.microsoft.com/en-us/iis/get-started/whats-new-in-iis-10/http2-on-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
2.3 Installing Intelligent Capture for SAP® Solutions

Intelligent Capture for SAP® Solutions supports the automatic uninstallation of a
previous installed version back to version 16.5. After running the msi file the
uninstallation happens completely unattended.
Notes
• Before you run the installation save the web.config file located in
<installdir>/WebServiceAPI. Already customized data will be unavailable
as soon as the automatic update process removes the previous installed
Intelligent Capture for SAP® Solutions.
• After you run the installation you must copy all already customized values
from the saved web.config file to the web.config file which has been newly
installed. Do not replace and overwrite the new installed web.config file
with the saved one.
To install Intelligent Capture for SAP® Solutions:
1. In the root folder of the installation media, run <drive>:\Intelligent Capture

for SAP Solutions.msi.
By default, the files are installed into the folder %ProgramFiles(x86)%\Open

Text\Intelligent Capture for SAP Solutions CE <version>.
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.
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.

Chapter 2 Installing Intelligent Capture for SAP® Solutions
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, Korean, Thai, and Vietnamese 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 patches and service packs

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.
Example: Version 16.7.1 is version 16.7 with service pack 1.
Patches 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.

2.6. Installing the Imaging Plug-in
3. Install the service pack or patch.

4. In the Internet Information Services (IIS) Manager, start the
InformationExtractionService web service.
2.6 Installing the Imaging Plug-in

Intelligent Capture for SAP® Solutions uses an imaging component provided by the
Recognition Engine. You can install this imaging component separately, and it is
used by Intelligent Capture for SAP® Solutions if it provides a newer version of the
imaging component. The different versions of the Imaging Plug-In are compatible.
Install and use always the most recent version of the Imaging Plug-In without
regard to version and patch level of Intelligent Capture for SAP® Solutions. This
makes bug fixes available as soon as a new Imaging Plug-In version is released, and
you do not must wait until an Intelligent Capture for SAP® Solutions Patch is
available. Intelligent Capture for SAP® Solutions will always use the newest version
of the imaging component.
To install the Imaging Plug-In:
1. Download Capture Imaging Plug-In on My Support (https://

knowledge.opentext.com/) searching for Capture Imaging Plug-In.
2. Optional To change the Imaging Plug-In installation folder, adapt the

ImgPluginInstallDir registry key in HKLM\SOFTWARE\OpenText\Capture
Common.

Chapter 3
Installing Windows Validation Client
Windows Validation Client is used for correcting documents, and cannot be used for
recognition, or for customizing and monitoring.
Windows Validation Client supports the automatic uninstallation of a previous

installed version back to version 16.3. After running the msi file the uninstallation
happens completely unattended.
Tip: For an unattended installation, a command script is available in a

subfolder.
To install Windows Validation Client:
1. Download Windows Validation Client for SAP® Solutions as product ISO

image from My Support (https://knowledge.opentext.com/).
Tip: In My Support, search for

validationforsapsolutions<version>.iso. For <version>, enter for
example 23.2 corresponding to the version of the OpenText products you
use.
2. In the root folder of the installation media, run Validation for SAP Solutions
CE.msi.
click Next.
5. In the Destination Folder dialog box, install to the default folder or click
Change to choose another folder, and then click Next.
6. In the Ready to install Validation for SAP solutions dialog box, click Install.
7. In the Completed the installation dialog box, click Finish.

Chapter 4
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 5.2 “Using the Single Click Entry feature” in OpenText
Vendor Invoice Management for SAP Solutions - User Guide for Invoice Solution (VIM-
UGD) and section 14.3 “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 the most recent version and patch for SCESAPGUI Plug-In. You can find
them on My Support (https://knowledge.opentext.com/) searching for SCE for
SAP solutions.zip.
2. In the root folder of the installation media, run SCE for SAP Solutions.msi.
click Next.
5. To start the installation, click Install.
6. Click Finish.
After Single Click Entry for SAP GUI has been installed, configure SAP GUI.
To configure SAP GUI for Single Click Entry for SAP GUI:
1. Start SAP GUI, and then click Options in the system menu.
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.

Chapter 4 Installing Single Click Entry for SAP GUI
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.

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

Manager.
3. Uninstall Intelligent Capture for SAP® Solutions and all Windows Validation
Clients.
4. Install Intelligent Capture for SAP® Solutions and Windows Validation Client.
For more information, see “Installing Intelligent Capture for SAP® Solutions”
on page 13 and “Installing Windows Validation Client“ on page 17.
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 23.
8. Migrate the learning data. For more information, see section 2.4 “Pre-learning of
IES Profiles” in OpenText Vendor Invoice Management for SAP Solutions -
Administration Guide (VIM-AGD).
9. Update the profiles because the profile data format has been extended. For more
information, see section 5.2.3.16 “Activating and updating a Capture profile” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Foundation (VIM-CGF).
When you start the new installed Windows Validation Client the updated
profiles will automatically been loaded.
10. Test your Intelligent Capture for SAP® Solutions system.
To upgrade Windows Validation Client:
1. Uninstall all Windows Validation Clients.
2. Install Windows Validation Client. For more information, see “Installing

Windows Validation Client“ on page 17.

Chapter 6
Configuring Intelligent Capture for SAP® Solutions
6.1 Adding a certificate for client/server

authentication for secure communication using
HTTPS (optional)
To setup secured communication using HTTPS, you can add a server and client
certificate on the system(s) which is intended to be used for setup the most secure
communication option.
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.
6.2 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.

Chapter 6 Configuring Intelligent Capture for SAP® Solutions
5. In the Type list, click http or https depending on your connection type, and
then enter the port in the Port box.
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 23.
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.
6.2.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.
6.2.2 Increasing the timeout setting for ASP.NET application

sessions
The default timeout setting of an ASP.NET application session is 20 minutes. This
means that any incoming http request will be stopped after this period of time. To
extend the duration of the ASP.NET application session, you can increase the
timeout setting.
To increase the timeout setting:
1. On the Connections view, click Application pools.
2. In the Application Pools list, click Intelligent Capture for SAP® Solutions.
3. Right-click, and then click Set Application Pool Defaults.

6.2. Configuring the web service
4. Change the Idle Time-out (minutes) parameter to a value greater than the
default 20 minutes. OpenText recommends to increase the timeout value to 4
hours 15 minutes. This value is similar to the DefaultOcrTimeout setting used
to extract process calls and configured in the application settings in the web.
config file. Do not set the value greater than 4 hours 29 minutes, because the
leading VIM application (SAP system) has a preset default timeout of 4 hours 30
minuntes, which ends the extraction process in any case.
6.2.3 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. If certificates are used for secure communication, click the Require option
under Client certificates.
5. On the Actions view, click Apply.
6.2.4 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 in the web.config is
30000000 bytes (approximately 28,6 MB). You only need to change this value if
it should be increased to a higher value than 28,6 MB.
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).
6.2.5 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.
ClientCallerHttpTimeout
Http timeout used for outbound calls. Must be set in seconds. If no value is
used the default value is 100 seconds.
EncryptRepositoryBlobs
Encrypts the data “blobs” which get transferred using HTTP(S) and stored
into the SAP repository. The default value is false and must not be changed.

6.2. Configuring the web service
DefaultOcrTimeout
Maximum runtime of an operation. If runtime exceeds this value, the
operation will be cancelled. The default value is 4 hours 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.
SendResponseInExternalProcess
If set to true the result call gets executed within a separate cluster node
instance instead of the IIS container.
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. Must be set in the
format http(s)//:<hostname>:<port>.
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 23), 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.
Note: No blanks are allowed between each <attribute>=<value> pair.
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.
6.3 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.
6.3.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.

6.3. Configuring tracing
6.3.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.
6.3.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\
OpenText, and on 64-bit systems also at the key HKLM\SOFTWARE\Wow6432Node\
OpenText to a new path.
2. To keep the trace configuration, copy the trace configuration files

(extension .traceconfig) to the new trace path.
3. Restart the DOKuStar Load Manager 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.

6.3.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.

6.3.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 34. 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.
6.3.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
All services
The Microsoft Windows event log is used to log creating, starting, and stopping
of the services.
6.3.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]]
6.3.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 Validation for SAP® Solutions, and 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 36.
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 37.
Find
You can search in the currently open file. For more information, see
“Searching trace messages” on page 38.
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.

6.3.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.

6.3.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.
6.3.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

6.4. Controlling cache behavior
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.
6.4 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.
Document Reader engine controls the cache size automatically.
6.5 Working with configuration data (production

system)
After performing the installation steps described in chapter “Installing Intelligent
Capture for SAP® Solutions“ on page 11, 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.
6.5.1 Technical configuration data

6.5.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 43. The Load Manager
Configuration tool saves the cluster configuration files into the folder
%ALLUSERSPROFILE%\Application Data\Captaris\DOKuStar Load Manager on the
Cluster Master.

6.5.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 28.
6.5.2 Runtime files

6.5.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.
6.5.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 28.
6.5.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.
6.5.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 47.

6.5. Working with configuration data (production system)
6.5.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.
6.5.5.1 Configuring cache location

The caches used to store temporary recognition and download data reside in a
subfolder IEECache 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.
6.5.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 29.
6.5.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.

6.6 Configuring load balancing

6.6.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.

6.6. Configuring load balancing
To open the Load Manager Configuration:
• In the Cluster Monitor, on the Tools menu, click Cluster Configuration.
6.6.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.

6.6.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.

6.6. Configuring load balancing
6.6.2.2 Changing IES 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.

6.6.2.3 Installing a higher number of cluster nodes
Note: OpenText does not recommend to create more than 16 cluster nodes on
one machine. Especially for failover it is a single point of failure.
The default configuration of the Windows OS memory model grants non-interactive

(service) sessions much less of “desktop heap” space for creating windows than to
interactive sessions (desktop applications). For more information, see https://
docs.microsoft.com/en-us/archive/blogs/ntdebugging/desktop-heap-overview and
https://docs.microsoft.com/en-us/archive/blogs/ntdebugging/desktop-heap-part-2.
For this reason, you must change the “desktop heap” value for the non-interactive
(service) sessions in the Intelligent Capture for SAP® Solutions configurations using
more than 16 cluster nodes hosted on a single computer.
To configure the “desktop heap” size for non-interactive (service) sessions:
1. Backup your registry before you make any changes.
2. Download the AddResourcesToServices.zip file from My Support (https://

knowledge.opentext.com/), and then merge the file with the registry.
3. Open the registry value KEY_LOCAL_MACHINE\System\CurrentControlSet\

Control\Session Manager\SubSystems\Windows.
Example: %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows

SharedSection=1024,20480,2048 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4
ProfileControl=Off MaxRequestThreads=16
4. Change the values as needed for your system. The critical segment is
SharedSection=1024,20480,2048.
• 20480 is the desktop heap size for interactive sessions in kilobytes.

• 2048 is the size of non-interactive (services) sessions in kilobytes. The default
value is 768. OpenText recommends using the size 2048 for systems hosting
up to 64 cluster nodes. The number should grow up to 3096 if you plan
using more than 64 cluster nodes.
Note: The change affects the desktop heap of all services. Stay within the
range recommended by OpenText and do not make it larger than
necessary. By increasing the desktop heap size for non-interactive session
too much you will push the system to consume more resource and you
may run into problems with the total available desktop heap size.

6.7. Starting and stopping Microsoft Windows Services on the Intelligent Capture for SAP® Solutions Server
6.7 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.
6.8 Setting up and configuring SLD registration

6.8.1 Setting up the SLD registration for IES Webservice
You must 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
InformationExtractionService (could also be named different).
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 (default installation): C:\Program Files (x86)\Open Text\
Intelligent Capture for SAP Solutions CE <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.

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 CE <version>\WebServiceAPI
MSIIS Pools
• Name of Application Pool: InformationExtractionService
MSIIS Sites
• Site Name: InformationExtractionService

• Web Binding Info:
• Web Protocol: http
6.8.2 Configuring the SLD Data Supplier for IES engine

After you have installed IES for the first time, or if you have upgraded from a
previous version, you must configure the SLD Data Supplier.
All components of an IES system register in the SAP Landscape Directory. SLD
registration is provided by the Microsoft Windows service Information Extraction
Service SLD Data Supplier <version>. The service registers IES automatically twice a
day and immediately after it is started.
You must configure the service on each Microsoft Windows computer on which you
use IES.
To configure the SLD Data Supplier service:
1. On the Start menu, click OpenText Intelligent Capture for SAP Solutions CE
<version> > IES SLD Data Supplier Settings.

6.8. Setting up and configuring SLD registration
2. In the IES SLD Data Supplier Settings dialog box, enter the NetWeaver
settings SLD host, port, user, and password.
3. Optional To test the configuration, click Test collect and send data.
After you have configured the SLD Data Supplier, you can check registration by
logging in to the System Landscape Directory of the specified host.
To check SLD registration:
1. Open http://<SLD host name>:50000/sld, and then sign in.

2. Click Administration, and then click Content Maintenance.
3. In the Subset list, click All With Instances > Installed Product.
4. In the Filter box, type INFORM. CAPT., and then click Go .

Chapter 7
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. For more information, see section 3.6 “Inbound
Administration work center” in OpenText Vendor Invoice Management for SAP
Solutions - Administration Guide (VIM-AGD), and section 4 “Inbound Configuration”
in OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Foundation (VIM-CGF).
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 8
Configuring high availability
The most critical part of a Intelligent Capture for SAP® Solutions system is the
Inbound Configuration, or the Inbound Handler, respectively. These components
are parts of VIM 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 9
Configuring security
9.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).
9.2 Authorizations for validation user and extraction

user
As soon as the validation user has started Windows 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:
• Full authorization for the J_6NPF_RFC object is required for all users. For more
information, see section 8.4 “Authorization objects” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (VIM-CGF).
• Authorization for the S_WFAR_OBJ (ACTVT=03) object is required for all users for
the related content repository (OAARCHIV) and document type (OADOKUMENT).
• 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
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME= /OTX/PF01_IF_OCR
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME= /OTX/PF11_ASYNC

Chapter 9 Configuring security
• S_TABU_NAM:ACTVT=03,TABLE=V_CURC
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/PF01_IF_OCR
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/
PF01_IF_LOOKUP_VAL
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OTX/PF11_VALIDATION
replace with
PF11_VAL_GET_DATA
PF11_VAL_GET_PROFILES
PF11_VAL_GET_SETTINGS
PF11_VAL_SET_DATA
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF11_VAL_LOOKUP
PF11_VAL_GET_ADHOC
PF11_VAL_GET_PAGES
PF11_VAL_SET_TIMEOUT
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OTX/PF11_ASYNC
replace with
PF11_ASYNC_SET_VAL_DATA
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.

9.3. Logging of security-relevant events
9.3 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.
9.4 Encryption of communication channels

All participants of a Intelligent Capture for SAP® Solutions system communicate
with the Inbound Configuration in SAP ERP by HTTP or HTTPS, depending on the
configuration of the web service.
9.5 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, Inbound
Configuration/Inbound Handler, is an SAP ERP component.
• The repository is part of the SAP ERP system.
• HTTPS communication can be setup with or without the use of client 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).
9.6 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. For more information, see https://
knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=77613388&
objAction=browse&viewType=1.

Chapter 9 Configuring security
9.7 Responsibilities
In an Intelligent Capture for SAP® Solutions system, no real users are involved.
On the VIM SAP system, there are additional user types and responsibilities.

Chapter 10
Troubleshooting
VIM 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.
Connection problems
• If the connection test has a timeout, check the trace viewer on the OCR server
for details.
– Possible problems:
○ Wrong callback URL or port

○ SSL connection from OCR to SAP. For example, the SAP server
certificate is not trusted by IES or IES client certificate is not trusted by
SAP.
○ Error during execution of the request in IES.
– Solutions:
○ Open the URL of the SICF service for a result in a browser installed on
the IES server.
○ Enhance the log level of the SAP ICM log, and then check the ICM log
file for errors related to the connection from SAP to OCR or from OCR
to SAP.
• The SM59 connection test must display a message like “Intelligent Capture
for SAP® Solutions <version> - web service started.”. Otherwise the Web
Server is not correctly configured.
• Requests are not processed successfully. The error message “503 - Service
Unavailable” is sent from IES (the result service is working but the repository
service is not working as expected). Check the configuration of the repository
service in TC SICF and in the connection settings.
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).

Chapter 10 Troubleshooting
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
specific trace folder and can be viewed using the Trace Viewer Tool. For more
information, see “Configuring tracing” on page 28.
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 43.
• Trace Viewer. For more information, see “Analyzing trace files using Trace
Viewer” on page 34.
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.
Windows Validation Client logfiles
You can find the Windows Validation Client logfiles using the Trace Viewer.
To download the Windows Validation Client logfiles:
• Open Trace Viewer. To do so, in the installation folder, run

DOKuStarTraceViewer.exe.
Trace Viewer displays the logfiles folder: <directory>\:ProgramData\
OpenText\Trace
To set Trace Viewer to debug mode:
1. Open Trace Viewer, and then click Trace Configuration.
2. In the Trace Configuration dialog box, click Debugging production

system, and then click OK.

OpenText Intelligent Capture For SAP Solutions CE 23.2 - Installation and Administration Guide English (CPIE230200-AGD-EN-02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Intelligent Capture For SAP Solutions CE 23.2 - Installation and Administration Guide English (CPIE230200-AGD-EN-02)

Uploaded by

Copyright:

Available Formats

OpenText™ Intelligent Capture for SAP®

Installation and Administration Guide

Describes how to install and configure OpenText Intelligent

Open Text Corporation

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

Copyright © 2023 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

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

3 Installing Windows Validation Client ..................................... 17

4 Installing Single Click Entry for SAP GUI .............................. 19

5 Upgrading Intelligent Capture for SAP® Solutions .............. 21

6 Configuring Intelligent Capture for SAP® Solutions ............ 23

CPIE230200-AGD-EN-02 Installation and Administration Guide iii

6.3.8.2 Filtering messages .......................................................................... 37

7 Monitoring Intelligent Capture for SAP® Solutions .............. 51

8 Configuring high availability .................................................. 53

9 Configuring security ............................................................... 55

iv OpenText™ Intelligent Capture for SAP® Solutions CPIE230200-AGD-EN-02

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

For more information, see the landing page for:

• Core Capture for SAP® Solutions on My Support (https://support.opentext.com/

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. No separate configuration

Following scenarios/solutions are supported:

CPIE230200-AGD-EN-02 Installation and Administration Guide 5

6 OpenText™ Intelligent Capture for SAP® Solutions CPIE230200-AGD-EN-02

CPIE230200-AGD-EN-02 Installation and Administration Guide 7

1.3 Technical operations

Note: Use automatic separation only for processing PDF files.

1.3.2 Optimizing scan results

8 OpenText™ Intelligent Capture for SAP® Solutions CPIE230200-AGD-EN-02

1.3.3 Configuring Indian QR code signature check for

To configure the Indian QR code signature check for invoices:

1. On https://einvoice1-trial.nic.in/Others/Publickeys, download all certificates for

2. Copy the certificates to the Certificates Store.

a. Click Start, type certificate, and then select Manage computer

CPIE230200-AGD-EN-02 Installation and Administration Guide 9

2.1 Installation procedure overview

• For more information on supported platforms, hardware and software

CPIE230200-AGD-EN-02 Installation and Administration Guide 11

• The available system resources will be shared between both products

2. Optional Install Asian languages.

4. Install Windows Validation Client. For more information, see “Installing

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.

12 OpenText™ Intelligent Capture for SAP® Solutions CPIE230200-AGD-EN-02

2.3 Installing Intelligent Capture for SAP® Solutions

To install Intelligent Capture for SAP® Solutions:

1. In the root folder of the installation media, run <drive>:\Intelligent Capture

By default, the files are installed into the folder %ProgramFiles(x86)%\Open

2. In the Welcome dialog box, click Next.

CPIE230200-AGD-EN-02 Installation and Administration Guide 13

2.4 Installing Asian languages

After the installation, the languages Chinese Simplified, Chinese Traditional,

To install the Asian languages option:

1. In the root folder of the installation media, run Setup.exe.