OpenText Business Center Capture For SAP Solutions 16.7.4 - Administration Guide English (CPBC160704-AGD-En-03)

OpenText™ Business Center Capture for
SAP® Solutions
Administration Guide
This guide describes how to install, configure, and administer

OpenText Business Center Capture for SAP Solutions.
CPBC160704-AGD-EN-03
OpenText™ Business Center Capture for SAP® Solutions
Administration Guide
CPBC160704-AGD-EN-03
Rev.: 2022-Feb-17
This documentation has been created for OpenText™ Business Center Capture for SAP® Solutions 16.7.4.
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 © 2022 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 Introduction ................................................................................ 9
1.1 About the document .......................................................................... 9
1.2 Functional overview .......................................................................... 9
1.3 BCC runtime scenarios .................................................................... 11
1.4 Components of BCC ....................................................................... 11
1.5 Customizing .................................................................................... 13
1.6 Hot Spots ....................................................................................... 14
1.7 Achieving optimum recognition results .............................................. 15
1.8 Supported image formats ................................................................. 16
1.8.1 Processing PDF files ....................................................................... 17
1.8.2 Processing TIFF files ....................................................................... 17
2 Installation ................................................................................ 19
2.1 Planning the installation ................................................................... 19
2.1.1 Installing BCC as standalone system ................................................ 20
2.1.2 Installing BCC for application development ....................................... 20
2.1.3 Installing BCC for application testing ................................................ 21
2.1.4 Installing BCC for a production system ............................................. 21
2.2 Preparing the installation ................................................................. 22
2.2.1 Creating a domain user for Microsoft Windows Services .................... 22
2.2.2 Installing Microsoft .NET Framework ................................................ 22
2.2.3 Installing Microsoft Visual C++ Redistributables ................................ 23
2.2.4 Installing SAP Connector for Microsoft .NET ..................................... 23
2.2.5 Setting user permissions ................................................................. 23
2.2.6 Installing Microsoft SQL Server ........................................................ 24
2.3 Installing BCC ................................................................................. 25
2.3.1 Installing the Recognition Server ...................................................... 25
2.3.2 Installing BCC on a Recognition Node .............................................. 26
2.3.3 Installing Asian languages ............................................................... 27
2.3.4 Installing solutions for BCC .............................................................. 27
2.3.5 Installing the Validation Client .......................................................... 28
2.3.6 Installing Single Click Entry for SAP GUI .......................................... 29
2.3.7 Creating installation log files ............................................................ 30
2.4 Follow-up activities .......................................................................... 30
2.4.1 Configuring Business Center ............................................................ 30
2.4.2 Configuring Archive Server .............................................................. 30
2.4.3 Preparing SAP ERP or SAP S/4HANA user accounts ........................ 30
2.4.4 Preparing SAP ERP or SAP S/4HANA login data .............................. 30
2.4.5 Creating and configuring applications ............................................... 31
2.4.6 Configuring the cluster ..................................................................... 31
CPBC160704-AGD-EN-03 Administration Guide iii

Table of Contents
2.4.7 Configuring the Microsoft Windows Firewall for Validation Clients ....... 31
2.4.8 Configuring SAP GUI ...................................................................... 31
2.4.9 Configuring the SLD Data Supplier for ICC ....................................... 32
2.4.10 Upgrading existing applications ........................................................ 33
2.5 Optional follow-up activities .............................................................. 34
2.5.1 Moving the caches to a different location .......................................... 34
2.5.2 Moving all BCC data to a different drive ............................................ 34
2.6 Installing updates ............................................................................ 34
2.6.1 Installing patches and service packs ................................................. 34
2.6.2 Installing the Imaging Plug-in ........................................................... 35
2.7 Upgrading ....................................................................................... 36
2.7.1 Upgrading ICC ................................................................................ 36
2.7.2 Upgrading BCC ............................................................................... 37
2.7.3 Upgrading Validation Client .............................................................. 38
3 Monitoring BCC ....................................................................... 39

3.1 Monitoring BCC with external monitoring tools .................................. 39
3.1.1 Monitoring BCC with Wily Introscope ................................................ 40
3.2 Monitoring BCC using the SAP Solution Manager ............................. 40
3.2.1 Providing technical configuration information ..................................... 40
4 Technical operations ............................................................... 43

4.1 Configuring Indian QR code signature check for invoices ................... 43
4.2 Overview of the Customizing Client .................................................. 44
4.3 Overview of components ................................................................. 45
4.3.1 Document processing in BC/VIM on the SAP ERP or SAP S/
4HANA system ............................................................................... 45
4.3.2 BCC Microsoft Windows components ............................................... 45
4.3.2.1 Standalone system .......................................................................... 46
4.3.2.2 Recognition Server and Validation Clients ........................................ 46
4.3.2.3 Recognition Server, Recognition Nodes, and Validation Clients ......... 46
4.3.3 Further involved components ........................................................... 47
4.4 Overview of technical runtime scenarios ........................................... 47
4.4.1 Recognition and validation of a document ......................................... 47
4.4.2 Downloading data from SAP ERP or SAP S/4HANA .......................... 48
4.4.3 Supervised learning on the Customizing Client .................................. 48
4.5 Monitoring BCC using the Customizing Client ................................... 48
4.5.1 Monitoring Hot Spots ....................................................................... 49
4.5.2 Monitoring jobs ............................................................................... 49
4.5.3 Monitoring the Recognition Cluster ................................................... 50
4.6 Logging and tracing ......................................................................... 52
4.6.1 Logging .......................................................................................... 52
4.6.2 Overview of tracing ......................................................................... 52
iv OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

Table of Contents
4.6.3 Tracers ........................................................................................... 52

4.6.4 Trace listeners ................................................................................ 52
4.6.5 Trace root path ............................................................................... 53
4.6.6 Trace levels .................................................................................... 53
4.6.7 Trace configuration ......................................................................... 54
4.6.8 Location of trace files and trace configuration files ............................. 56
4.6.9 Format of traces .............................................................................. 57
4.6.10 Analyzing trace files using Trace Viewer ........................................... 58
4.6.10.1 Selecting a trace configuration ......................................................... 60
4.6.10.2 Filtering messages .......................................................................... 61
4.6.10.3 Searching trace messages .............................................................. 62
4.7 Configuration data (production system) ............................................. 63
4.7.1 Technical configuration data ............................................................ 63
4.7.1.1 Load Manager files .......................................................................... 63
4.7.1.2 Hot Spot files .................................................................................. 63
4.7.1.3 Trace configuration files ................................................................... 63
4.7.1.4 Customizing Client .......................................................................... 64
4.7.2 Application configuration data (customizing data) .............................. 64
4.7.3 Runtime files ................................................................................... 64
4.7.3.1 Temporary files of Document Reader and Document Extraction ......... 64
4.7.3.2 Trace folder .................................................................................... 65
4.7.4 Registry entries ............................................................................... 65
4.7.5 Databases ...................................................................................... 65
4.7.5.1 SQL Server instance ....................................................................... 65
4.7.5.2 BCC database ................................................................................ 65
4.7.6 Microsoft Windows Services ............................................................ 66
4.7.7 Moving BCC data to a different location ............................................ 66
4.7.7.1 Moving the folder DOKuStarDispatchData to a different location ........ 67
4.7.7.2 Configuring the location of the ClientConfig.dfc file ............................ 68
4.7.7.3 Configuring cache location ............................................................... 68
4.7.7.4 Configuring trace file location ........................................................... 69
4.7.7.5 Configuring program data location of several components ................. 69
4.7.7.6 Configuring HotSpot folder locations ................................................. 69
4.7.7.7 Moving the BCC database to a different location ............................... 70
4.8 Backup and restore ......................................................................... 71
4.9 Periodic activities ............................................................................ 72
4.9.1 Deleting trace files ........................................................................... 72
4.9.2 Restricting the growth of the BCC database ...................................... 72
4.9.3 Creating backups of learning data .................................................... 72
4.10 Load balancing ............................................................................... 73
4.10.1 Understanding the Load Manager .................................................... 73
4.10.2 Cluster nodes ................................................................................. 74
CPBC160704-AGD-EN-03 Administration Guide v

Table of Contents
4.10.2.1 Configuring cluster nodes ................................................................ 74

4.10.2.2 Changing cluster node properties ..................................................... 76
4.10.2.3 Installing a higher number of cluster nodes ....................................... 77
4.10.2.4 Changing Runtime Node properties .................................................. 78
4.10.3 Increasing throughput ...................................................................... 79
4.10.3.1 Increasing the number of Recognition Nodes .................................... 79
4.10.3.2 Increasing the number of Recognition Clusters ................................. 79
4.11 High availability ............................................................................... 80
4.11.1 Using two Recognition Servers ........................................................ 80
4.11.1.1 System configuration ....................................................................... 80
4.11.1.2 Maintenance operations .................................................................. 81
4.11.1.3 Upgrade to new product version ....................................................... 81
4.11.1.4 Risk considerations ......................................................................... 82
4.11.2 Installing two Recognition Servers in one Recognition Cluster ............ 82
4.12 Starting and stopping ...................................................................... 83
4.12.1 Starting and stopping of Hot Spots on the Recognition Server ............ 83
4.12.2 Starting and stopping of services on the Recognition Server and
the Recognition Nodes .................................................................... 84
4.12.3 Starting and stopping of Customizing Client and Validation Client ....... 84
4.13 Configuring Lookup Lists ................................................................. 85
4.14 Troubleshooting .............................................................................. 85
4.15 Port usage ...................................................................................... 86
4.16 Deleting an application .................................................................... 88
5 Configuring security ............................................................... 89

5.1 User management and authorization concept ................................... 89
5.1.1 Microsoft Windows users ................................................................. 89
5.1.2 ERP users ...................................................................................... 90
5.1.2.1 Common authorizations ................................................................... 90
5.1.2.2 Authorizations for validation user and extraction user ........................ 91
5.1.2.3 Working with Single Sign-On ............................................................ 91
5.1.2.4 Authorizations for Recognition Server/Recognition Node users .......... 92
5.1.2.5 Authorizations for Customizing Client users ...................................... 92
5.1.2.6 Training module SAP ERP or SAP S/4HANA user ............................. 93
5.1.2.7 Feedback module SAP ERP or SAP S/4HANA user .......................... 93
5.1.2.8 Configuring SAP Feedback Link ....................................................... 94
5.2 Delivered users ............................................................................... 95
5.3 Emergency user concept ................................................................. 95
5.4 Logging of security-relevant events .................................................. 95
5.5 Logging of application configuration data changes ............................. 95
5.6 Encryption of communication channels ............................................. 96
5.6.1 Files and databases ........................................................................ 96
vi OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

Table of Contents
5.6.2 SAP ERP or SAP S/4HANA ............................................................. 96

5.7 Secure configuration ....................................................................... 97
5.8 Responsibilities ............................................................................... 98
GLS Glossary of Terms 99
CPBC160704-AGD-EN-03 Administration Guide vii

Chapter 1
Introduction
1.1 About the document

This document describes how to install, configure, and administer OpenText
Business Center Capture for SAP Solutions (BCC), OCR component of the SAP
product SAP Digital Content Processing.
1.2 Functional overview

As a component of OpenText™ Vendor Invoice Management for SAP® Solutions
(VIM), the software permits to automate capturing of other machine-printed invoice-
related documents. For several document types, plug-ins are available, which permit
to create an application with suitable preconfigured fields for the respective
documents.
OpenText Business Center Capture for SAP Solutions with Invoice Solutions plug-in
extends VIM's capabilities to automate capturing of machine-printed paper invoices.
For electronic processing, documents are scanned on entry to the financial

accounting department. The digital images of the documents are stored in an
archive. BCC recognition is indirectly triggered by the early archiving mechanism of
SAP ERP or SAP S/4HANA.
BCC recognition extracts the essential data, for example date, amount, order number
and so on for invoices, from the scanned documents in the archive.
For recognition of invoices, it uses a knowledge base that has been trained on
samples of thousands of invoices from many countries around the world. In
CPBC160704-AGD-EN-03 Administration Guide 9

Chapter 1 Introduction
addition, it uses fuzzy database matching: BCC recognition maps the read data (such
as names, addresses, vendor numbers, purchase order numbers) to SAP ERP or SAP
S/4HANA vendor master data and SAP ERP or SAP S/4HANA purchase order data
during analysis.
The extracted information is passed on to VIM.
Based on business rules, VIM decides whether the automatically extracted data must
be reviewed and possibly corrected or completed by a clerk. In this case, the
document is transferred to a Validation Client, which is a Microsoft Windows
program that is used by a clerk to check, correct, and complete the extracted data.
The validated data are then passed on to VIM.
10 OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

1.3. BCC runtime scenarios
1.3 BCC runtime scenarios

If you install BCC, you can create, configure, import, and process custom
applications. To extend a BCC system for solutions, install the corresponding BCC
plug-ins. To extend a BCC system for invoice applications, install the BCC invoice
plug-in, and ensure that VIM is available on SAP ERP or SAP S/4HANA.
By default, VIM routes invoice applications automatically if it is also present on the

corresponding SAP ERP or SAP S/4HANA system.
Note: Starting with BCC 16.3, ICC is no longer available. If you used ICC,
remove ICC, install BCC and the BCC Invoice Solution plug-in.
1.4 Components of BCC

A BCC system consists of the following components:
• Inbound Configuration or ICC Dispatcher

• Recognition Server, Recognition Node
• Customizing Client (user interface)
• Validation Client (user interface)
The heart of a BCC system is the Inbound Configuration or ICC Dispatcher, a

component of VIM, the other non-SAP parts BCC interacts with.
Data extraction is performed on a special server computer, normally a multi-

processor machine. This computer is the Recognition Server. In huge systems, the

Recognition Server can be supported by additional recognition computers, called

Recognition Nodes. The Recognition Server and its Recognition Nodes make up a
Recognition Cluster. The Recognition Server distributes the workload among the
nodes of the Recognition Cluster.
The Recognition Server owns a local database instance. The databases of this
instance contain data that the Recognition Server and the Recognition Nodes need to
deliver good extraction results:
• For invoices, vendor master data and purchase order data are compared with
read information.
• Recipient data are used to determine the recipient of an invoice.
• Learning data are used to extract data for fields that use Adaptive Recognition
(ART).
• Feedback data are used to extract data for fields using results of previously
processed documents.
Vendor master data, purchase order data, and learning data are downloaded from
SAP ERP or SAP S/4HANA periodically.
A BCC system has to be customized to meet the needs of the customer. Customizing
is done with a Microsoft Windows program, the Customizing Client. In addition, the
Customizing Client provides monitoring facilities, which can be used to monitor and
control a system at runtime. The Customizing Client is always installed on the
Recognition Server.
Finally, a BCC system contains several Validation Clients. The Validation Client is a
Microsoft Windows program that permits to review and eventually complete or
correct the extraction results of the Recognition step.

1.5. Customizing
1.5 Customizing
For customizing, you create applications with the Customizing Client. An
application bundles all settings that are needed to process documents of a certain
kind, for example which fields must be extracted in which extraction method.
For each application you must define the archive document type of the documents
that should be processed with this application. At runtime, when the Recognition
Server receives a new document image to process, it also obtains the archive
document type of the corresponding document; thus it can decide which application
has to be used to process the document image.
The applications are usually created in a development environment on a special

development Recognition Server connected to an SAP ERP or SAP S/4HANA
development system. The applications created with the Customizing Client on this
development Recognition Server are stored in a shared folder on the Recognition
Server and can immediately be used to process documents for testing purposes by
the Recognition Server and all its Recognition Nodes.
At any development state, the applications can be saved to the SAP ERP or SAP S/
4HANA system. The Validation Clients also need the applications to control
document validation. As soon as the applications have been saved on an SAP ERP or
SAP S/4HANA system, they are available for the Validation Clients connected to this
SAP ERP or SAP S/4HANA system.
Besides the facility to save an application on SAP ERP or SAP S/4HANA (export),
the Customizing Client also provides the facility to load an application from SAP
ERP or SAP S/4HANA to the Recognition Server (import). Using the export and
import facilities, the Customizing Client user can copy an application from a
development system to a test system or from a test system to a production system.

1.6 Hot Spots

The Recognition Server periodically fetches recognition jobs and downloads data
from the SAP ERP or SAP S/4HANA system. These periodical tasks are performed
by using the Hot Spot technology. A Hot Spot becomes active regularly after
expiring of a specified interval or at a specified time on specified days and then tries
to fetch new data.
An invoice application uses Hot Spots of two different types. An SAP Extraction
Link is used to fetch new recognition jobs from SAP ERP or SAP S/4HANA. Two
SAP Download Links are used to fetch new data, such as vendor master data and
purchase order data; the first is configured to perform a weekly full download,
whereas the second is configured to perform daily delta-download of purchase
order data.
An application for other document types also uses two different Hot Spot types. An
SAP Extraction Link is used to fetch new recognition jobs from SAP ERP or SAP S/
4HANA. An SAP Feedback Link is used to download feedback data which are
needed for different learning extraction methods.
You configure the Hot Spots with the Customizing Client.

1.7. Achieving optimum recognition results
1.7 Achieving optimum recognition results

To achieve optimum character recognition results, you should optimize the quality
of scanned images not only on the production system but also during testing:
Optimizing scan results
• Use professional scanning equipment to achieve optimum image quality.
• Optimize scanner settings. Documents should be scanned with 300 dpi and
compressed with Fax4. Lower resolution or other compression modes may
deteriorate recognition results. It is not recommended to use a resolution higher
than 300 dpi because this would increase data volume but would not improve
recognition quality.
• If possible, you should not use color scanning because color images would
increase data volume considerably slowing down processing whereas it would
not increase recognition quality in most cases.
• If documents of specific vendors have bad printing quality, bad paper quality, or
an unsuitable layout, contact the vendors.
• Chinese forms are usually smaller than documents from other countries. Images
of such forms should not have a white frame. To achieve optimal recognition
results, the forms should be aligned to the upper left corner of the image.
Reduce possible errors or performance problems by using suitable operating

procedures and suitable application settings:
Reducing errors
• Use separator sheets or barcode for attachment separation. Automatic separation

should only be used if PDF files must be processed. Each activated method for
attachment separation is checked at each page; if any of the checked conditions is
fulfilled, extraction is stopped.
• At an Invoice application, use parameters to limit runtime such as stopping

character recognition on attachments, skipping terms and conditions pages.
• Do not use documents that have run through a manual approval process.
Documents should not be stamped or marked. This deteriorates recognition
results.
• For invoice applications, achieve good quality of master data. If downloaded

data do not match the invoice material, they cannot be used to support
recognition.
To be able to optimize your applications, the operating procedures, and master data,
using a testing environment is important. It should be as similar to the production
environment as possible:

Testing
• Use the production scanning equipment already during development and test of
your applications. Otherwise recognition results during production may differ
from results during testing making testing less efficient.
• Scan original documents, that is, do not use copies.
• Test with real documents, that is, do not use synthetic test documents.
• For invoice applications: Take care to achieve a good relationship between
invoice and purchase orders, that is, an invoice should refer to a single purchase
order. In addition, use realistic purchase orders and vendor data; for example
copy live data from the production system.
1.8 Supported image formats

The incoming image-based files can have the following formats:
• TIFF
• JPG
• BMP
• GIF (only binary images)
• PNG
• PCX (only binary images)
• PDF
• PDF/A
• Emails received at a Mail Import Hot Spot: Attachments of the formats listed
above, and body (optional).
The incoming image-based files can have the following sizes:
• Maximum image format: DIN A0

• Minimum width: 10 pixels
• Minimum height: 10 pixels
• Maximum height: 24000 pixels
• Maximum width: 32000 pixels
With typical scanner resolutions, the following maximum resolution can be used for
different paper formats:
Paper format Color image Gray image Binary image

A4, Letter 1200 dpi 1800 dpi 1800 dpi
Legal 900 dpi 1200 dpi 1200 dpi

1.8. Supported image formats
Paper format Color image Gray image Binary image

A3, Tabloid 900 dpi 1200 dpi 1200 dpi
A2 600 dpi 900 dpi 900 dpi
A1 400 dpi 600 dpi 600 dpi
A0 300 dpi 400 dpi 400 dpi
If an image size exceeds the maximum size, image processing tries to halve
resolution to reduce the size.
During image processing, an uncompressed image is always created temporarily

that must not be larger than 512 MB. Therefore a color image must not comprise
more than 170 million pixels, a gray image not more than 512 million pixels.
These limits also apply to pages extracted from PDF files.
OpenText recommends to use 300 dpi images. A higher resolution does not improve
quality of recognition results in most cases while it increases disk space usage, and
decreases performance.
The minimum font size depends on image resolution and image quality.
1.8.1 Processing PDF files

When a PDF file is processed, it is split up and an image file is created for each page.
If the file contains electronic text, this text is also extracted. During character
recognition, text is read from the created images and the electronic text is also
evaluated. A voting algorithm is then used to provide character recognition results
with optimum quality.
Note: If PDF files containing an Asian language are processed or created, the
font Arial Unicode must be installed.
1.8.2 Processing TIFF files

Due to the complexity of the TIFF specification, sometimes image files contain
conflicting or invalid tag values. The Recognition Engine tries to load such files.
A frequent problem is caused by FAX compression and the

PhotometriceInterpretation tag: the Recognition Engine adheres to the TIFF 6.0
specification whereas other software often ignores PhotometricInterpretation for
FAX-compressed images.
Aldus revoked their specification of TIFF compression 6 for JPEG compression and
introduced TIFF compression 7 instead. The Recognition Engine prefers
compression 7 and supports the simplest case of compression 6. Tiff compression 8
is not supported.
Whereas baseline TIFF and a wide range of additional features are supported, there
are still unsupported tag values which are rarely used for document images.

The following table shows the supported values of important TIFF tags:
Tag Number Supported

values
BitsPerSample 258 1, 2, 4, 8
Compression 259 1 (uncompressed)
2 (CCITT 1D)
3 (Group 3 Fax)
4 (Group 4 Fax)
5 (LZW)
6 (JPEG revoked by Aldus)
7 (JPEG)
32773 (Packbits)
PhotometricInterpretation 262 0 (WhiteIsZero)
1 (BlackIsZero)
2 (RGB)
3 (Palette)
6 (YCbCr)
FillOrder 266 1 (LSB)
2 (MSB)
SamplesPerPixel 277 1 (binary, gray-value, or color palette images)
3 (color images)
Predictor 317 1 (binary, gray-value, or color palette images)
3 (color images)

Chapter 2
Installation
2.1 Planning the installation

Notes
• For information on supported platforms, hardware and software

requirements, as well as product dependencies and restrictions, see the
Release Notes. You can find the latest version of the Release Notes in My
Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
58900990).
• Check My Support (https://knowledge.opentext.com/)) for service packs or
patches that may have been posted after the initial release of BCC.
Check also the patches for the Capture Imaging Plug-In component (https://
knowledge.opentext.com/knowledge/llisapi.dll/Open/61183571) if a newer
version is available.
• The software is available on OpenText My Support as product ISO image.
For more information, see https://knowledge.opentext.com/knowledge/
llisapi.dll/Open/62474529. You may burn the ISO image on a DVD as the
installation medium. This documentation refers to the term <installation
medium> as the container for the ISO image. Alternatively, you can also
mount the ISO image. However, this is not explained by this documentation.
• Sign in as user with local administration rights.
BCC allows different configurations ranging from a stand-alone system on a single

computer to a production system for high throughput with a Recognition Server,
several Recognition Nodes for automatic recognition, and several Validation Clients
for document correction.
BCC needs a database in an SQL Server instance, which is used for download data/
feedback data and learning data of all applications. You can use the Express Edition,
which is free of charge. Other editions can also be used. You can either install an
instance with a database on the BCC Server or use a suitable instance on a different
computer. During installation of BCC, a dialog box asks for instance and database
name.
The Recognition Server manages the connections to theSAP ERP or SAP S/4HANA
system that provides the applications with recognition tasks and required download
data.
The Recognition Server includes the Customizing Client, which is used for
application development and for configuration of BCC and its applications. On a
production system, the server also performs load balancing, distributing recognition
tasks to the different Recognition Nodes.

Chapter 2 Installation
The Recognition Nodes process recognition tasks assigned to them by the

Recognition Server. They use the applications and downloaded data, which are
stored on the server.
The Validation Clients log on to the SAP ERP or SAP S/4HANA system and fetch
documents available for correction. They work independently from the Recognition
Server and its Recognition nodes.
OpenText recommends installing BCC on a separate server. That means, do not

install other application software, for example OpenText™ Archive Center, on the
BCC Server.
2.1.1 Installing BCC as standalone system

For testing purposes, you can install BCC on a single computer. In this case, all
features are installed on a single computer, which is used as Recognition Server, as
Validation Client, and for customizing.
2.1.2 Installing BCC for application development

For application development, you can use a single computer installed as a
Recognition Server that includes the Customizing Client, and that is connected to the
SAP ERP or SAP S/4HANA development system. Optionally, you can install a
validation station on a separate computer to be able to test document correction at a
Validation Client.
The Recognition Server is used as server, for recognition, customizing and

monitoring.

2.1. Planning the installation
2.1.3 Installing BCC for application testing

For testing purposes, you can use a computer installed as Recognition Server that
includes the Customizing Client, and an additional Validation Client. Both will be
connected to the SAP ERP or SAP S/4HANA test system.
The Recognition Server is used as server, for recognition, customizing, and

monitoring.
2.1.4 Installing BCC for a production system

Compared to a test system, you need additional Recognition Nodes and additional
Validation Clients depending on the required throughput that all work with the SAP
ERP or SAP S/4HANA production system.

2.2 Preparing the installation

2.2.1 Creating a domain user for Microsoft Windows Services
BCC installs several Microsoft Windows Services, which must be accessed from
several computers of your configuration. For these services, prepare a domain user
account and add it to the local administrators group.
Add domain name, user name, and the corresponding password to the Microsoft
Windows Services created for BCC after the installation has been completed.
Only for a stand-alone test system this is not necessary. In this case, you can use
Local System instead.
2.2.2 Installing Microsoft .NET Framework

On all computers of the BCC system, including the Validation Clients,
Microsoft .NET Framework must be installed. For supported versions, see the
Release Notes.

2.2. Preparing the installation
2.2.3 Installing Microsoft Visual C++ Redistributables

On all computers of the BCC system, including the Validation Clients, Microsoft
Visual C++ Redistributables must be installed. For supported versions, see the
Release Notes.
2.2.4 Installing SAP Connector for Microsoft .NET

On all computers of the BCC system, including the Validation Clients, SAP
Connector for Microsoft .NET must be installed. For supported versions, see the
Release Notes.
You can download The SAP Connector from http://service.sap.com/connectors. To

be able to access the download site, you need OSS and download authorization.
Note: Download the version for Microsoft Windows 32-bit (x86), even on a 64-
bit Microsoft Windows system.
To download and install SAP Connector for Microsoft .NET:
1. On the SAP CONNECTOR FOR MICROSOFT .NET DOWNLOAD

SECTION, under Compiled with .NET Framework 4.0, click SAP Connector
for Microsoft .NET <version> for Windows 32bit (x86).
2. Unpack the downloaded ZIP file, and then run the MSI file.
Install the SAP Connector to its standard location.
3. On the Select Installation Folder page, select the option Everyone.
4. On the Optional setup steps page, select Install assemblies to GAC.

Alternatively, if you intend to use the WMI provider, select Register WMI
provider and install assemblies to GAC.
2.2.5 Setting user permissions

To work with user permissions:
• On operating systems that support this feature, you can alternatively start the
installation with Run as Administrator. In this case, you must also start the
Customizing Client with Run as Administrator each time.
• On Microsoft Windows 2019, set the read rights to the Load Manager User temp
folder for the user that works with the Customizing Client. If the Load Manager
runs as SYSTEM it is located in C:\Windows\Temp or configure the Load Manager
to use an other folder.

2.2.6 Installing Microsoft SQL Server

If you install BCC for the first time, you must provide a suitable instance of SQL
Server and a database in this instance before you install BCC. This database is only
used to store runtime data of BCC outside SAP. You can use an existing instance if
available.
If you use an SQL Server instance which is shared with other software products, for
example Archive Center, the collation settings requirements may not be the same. If
so, then BCC must get it´s own SQL instance for the database. You can configure the
collation settings for this SQL instance individually to Latin1_General_CI_AS,
independently of the settings of the other SQL instances or the SQL Server default
collation.
If you upgrade from an earlier BCC version or from ICC, you can reuse the existing
instance, which typically has the name DOKUSTAR containing a database RdaDb10.
To install SQL Server:
• When you install BCC, the setup shows a dialog box where you can select the
SQL Server instance and the database that should be used.
If you install a new SQL Server instance on the BCC Server:
• You can use the free SQL Server Express edition of SQL Server. This edition has
restrictions: It only supports 1 GB RAM, database size is restricted to 10 GB, and
it uses only a single processing node. If available, you can use another edition
instead.
• OpenText recommends using the following parameters when calling the SQL
Server setup:
/ACTION=Install /FEATURES=SQL /INSTANCENAME=DOKUSTAR
/SQLSYSADMINACCOUNTS="BUILTIN\Administrators" /TCPENABLED=1
/NPENABLED=1 /SQLSVCACCOUNT="NT AUTHORITY\Network Service"
/ADDCURRENTUSERASSQLADMIN /IACCEPTSQLSERVERLICENSETERMS
/SQLCOLLATION=Latin1_General_CI_AS
If you use a different instance, make sure that the user account that is specified
for the services during BCC installation and the user that works with the
Customizing Client have the right to create tables in the database.
Note: If you use an external SQL Server instance, install the SQL Server
Tools on the BCC Server.

2.3. Installing BCC
2.3 Installing BCC

2.3.1 Installing the Recognition Server
Install BCC as Recognition Server on a single computer in your BCC system.
Tips
• The Customizing Client is always installed on the Recognition Server.

• For an unattended installation, command script examples are available in a
subfolder. Comments in the example files describe how you can adapt the
scripts to your needs.
To install the Recognition Server:
1. In the root folder of the installation media, run Setup.exe.
2. In the Welcome dialog box, click Next.
3. In the License Agreement dialog box, accept the license agreement, and then
click Next.
4. On the Installation Mode page, select Server.
5. Optional To show which features will be installed depending on the selected

installation mode, click Advanced.
• To modify feature selection, click the symbol preceding the respective

component name, and then select the appropriate option on the appearing
context menu. To re-establish the default feature selection for the current
installation mode, click Reset.
• If you want to install BCC at a different location, click Browse, and then
choose the desired path in the appearing folder dialog box.
• Click Disk Usage to open the Disk Space Requirements page.
It shows a list of all your disk drives and for each drive the available and the
required disk space with your current installation location setting. This helps
you to decide where to install BCC if there is not enough space on your
system drive.
6. Click Next.
7. In the Ready to install Business Center Capture dialog box, click Install.
8. In the Select Database dialog box, in the Server name list, click the instance you
installed for BCC use. If possible, use the default database name RdaDB10
because there are many references to this file name in the documentation.
Tip: The Server name list only shows SQL Server instances on computers
within the current IP subnet. To switch to a server in a different subnet,
enter <computer name>\<instance name> in the Server name box.

In the Server name list also the following writing style is supported:
<computer name>,<port number>. The <port number> replaces the
<instance name>. The writing style <computer name>\<instance
name>,<port number> is not supported.
9. To use SQL Server authentication, click Use SQL server authentication, and
then enter user name and password.
10. Optional To secure the connection with SSL, click Use SQL encryption.
Additionally, you must enable the SQL server instance. For more information,
see “How to enable SSL encryption for an instance of SQL Server by using
Microsoft Management Console” on the Microsoft support page.
11. Click the desired database in the Database list.
12. Optional Click Test Connection to make sure that the database can be reached.
13. In the Completed the installation dialog box, click Finish.
2.3.2 Installing BCC on a Recognition Node

A Recognition Node is used for automatic data extraction in larger configurations.
Tips
• Customizing, monitoring, or validation of documents cannot be performed

on a Recognition Node.
To install BCC on a Recognition Node:
click Next.
4. In the Installation Mode dialog box, click Recognition node.
5. Optional To show which features will be installed depending on the selected

installation mode, click Advanced.
• To modify feature selection, click the symbol preceding the respective

component name, and then select the appropriate option on the appearing
context menu. To re-establish the default feature selection for the current
installation mode, click Reset.
• If you want to install BCC at a different location, click Browse, and then
choose the desired path in the appearing folder dialog box.

2.3. Installing BCC
• Click Disk Usage to open the Disk Space Requirements page.

It shows a list of all your disk drives and for each drive the available and the
required disk space with your current installation location setting. This helps
you to decide where to install BCC if there is not enough space on your
system drive.
6. Click Next.
7. In the Invoice Capture Server dialog box, enter the name of the computer used
as Recognition Server, and then click Next.
8. In the Ready to install Business Center Capture dialog box, click Install.
2.3.3 Installing Asian languages

If you want to process documents containing Asian languages, you must run the
Asian languages setup following the BCC installation.
The Asian OCR option has its own installation media Asian Option <version> for
SAP Solutions.iso. Install the languages on the BCC Server, or a stand-alone
installation, and on each Recognition Node.
After the installation, the languages Chinese Simplified, Chinese Traditional,

Japanese, and Korean can be extracted from Asian documents.
Tip: Extracting data does not work if you create an application with country
setting and the Asian languages option is not installed.
To install the Asian languages option:
click Install.
3. Click Finish.
2.3.4 Installing solutions for BCC

By default, BCC permits to create, configure, and process applications of the type
Custom. To be able to process invoices or to work with solutions, you must install
the respective plug-ins:
• Business Center Capture Delivery Note

• Business Center Capture Incoming Quotation
• Business Center Capture Invoice
• Business Center Capture Mailroom for HR

• Business Center Capture Order Confirmation

• Business Center Capture Remittance Advice
• Business Center Capture Sales Order
Tips
• Install the plug-in on each computer of your BCC cluster configuration.

To install a plug-in:
1. In the Plugins folder of the installation media, run Setup.exe.

click Next.
4. In the Ready to install dialog box, click Install.
2.3.5 Installing the Validation Client

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

product ISO image. For more information, see https://knowledge.opentext.com/
knowledge/llisapi.dll/Open/62474529.
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 the Validation Client:
1. In the root folder of the installation media, run Validation for SAP Solutions
CE 21.4.msi.

click Next.
4. In the Destination Folder dialog box, install to the default folder or click
Change to choose another folder, and then click Next.

2.3. Installing BCC
5. In the Ready to install Validation for SAP solutions dialog box, click Install.
2.3.6 Installing Single Click Entry for SAP GUI

Install Single Click Entry for SAP GUI on all computers on which also SAP GUI is
installed, and where users are using the Single Click Entry functionality in VIM
Indexing Screen.
If Single Click Entry for SAP GUI is installed on a Vendor Invoice Management
system, it permits to capture data for fields on the index screen using the mouse. For
more information, see section 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 13.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. In the SceSapGui folder of the installation media, start SCE for SAP Solutions.
msi.
click Next.
4. To start the installation, click Install.
5. 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.
If you want to restrict scripting to specific users, additional configuration is needed.

To restrict scripting to specific users:
• In transaction RZ11, in the section sapgui/user_scripting_per_user, set Current

value to True.
After login, SAP GUI scripting remains available for those users that have the
authorization for the Execute(16) action of the authorization object S_SCR in
class BC_A.
On the login screen, SAP GUI scripting is then available for every user.
2.3.7 Creating installation log files

To create a standard log file during installation:
• Run the installation using setup.exe /L <logfilename>.
Tip: To create a full log, use setup.exe /L*v <logfilename>.
2.4 Follow-up activities

2.4.1 Configuring Business Center
Configure Business Center for BCC. For more information, see section 5.1 “Business
Center Capture” in OpenText Vendor Invoice Management for SAP Solutions -
Configuration Guide for Foundation (BOCP-CGD).
2.4.2 Configuring Archive Server

BCC stores recognition data as a ZIP file on Archive Server. Make sure that the
corresponding content type is registered for the used Archive Server.
2.4.3 Preparing SAP ERP or SAP S/4HANA user accounts

To fetch recognition jobs and download data, BCC needs several SAP ERP or SAP S/
4HANA user accounts with certain authorization. For more information, see “User
management and authorization concept” on page 89.
2.4.4 Preparing SAP ERP or SAP S/4HANA login data

On all computers of the BCC system, connections to an SAP ERP or SAP S/4HANA
system must be established.
To make this comfortable, you should supply a saplogon.ini file with login data of
all required SAP ERP or SAP S/4HANA systems. You can either install SAP GUI
and use it to configure the login data, which are stored in the saplogon.ini file, or
you can copy a file with the needed login data to the Microsoft Windows folder of the
system drive.

2.4. Follow-up activities
To make sure that the configuration is valid, install SAP GUI, and then check
whether the login mask appears when the program is started.
2.4.5 Creating and configuring applications

Following installation, you must create and configure applications before you can
work with BCC. For more information, see OpenText Business Center Capture for SAP
Solutions - Customization Guide (CPBC-CGD).
2.4.6 Configuring the cluster

To enable Load Balancing on several computers and on several processors of a
computer, you must configure the Load Manager on the server. For the server and
its processors this is done automatically during installation or when processing is
started, respectively.
If your configuration contains additional Recognition Nodes, you must configure

them manually. For more information, see “Cluster nodes” on page 74.
2.4.7 Configuring the Microsoft Windows Firewall for

Validation Clients
To be able to use an active Microsoft Windows Firewall on the Validation Clients,
you must release all ports used by the Validation Client. The Validation Clients use
one or more of the following TCP ports specified by SAP ERP or SAP S/4HANA:
• 3300+SID (Gateway)
• 4800+SID (Secure Gateway)
• 3600+SID (Message Server)
For more information, see the SAP Help Portal (https://help.sap.com/viewer/ports).
2.4.8 Configuring SAP GUI

SAP GUI
SAP GUI is part of the installation package SAP Netweaver Business Client
(NWBC). NWBC installation switches the server configuration from saplogon.
ini to SAPUILandscape.xml. BCC supports SAPGUILandscape.xml and
SAPGUILandscapeglobal.xml.

2.4.9 Configuring the SLD Data Supplier for ICC

After you have installed ICC for the first time, or if you have upgraded from a
previous version, you must configure the SLD Data Supplier.
All components of an ICC system register in the SAP Landscape Directory. SLD
registration is provided by the Microsoft Windows service Invoice Capture Center
SLD Data Supplier <version>, which is running on all computers of an ICC system
(Server, Recognition Nodes, and Validation Clients). The service registers ICC
automatically twice a day and immediately after it is started.
You must configure the service on each computer of the ICC system once after ICC
has been installed.
To configure the SLD Data Supplier service:
1. On the Start menu, click OpenText > ICC/BCC > Tools > SLD Data Supplier
Settings.
2. In the 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.

2.4. Follow-up activities
4. In the Filter box, type INVOICE CAPT.CENT, and then click Go .
Details about the installed product are then shown:
For more information, see SAP Note 2130735 (RSLF_SAP_ICC_SLD_configuration_

guide.pdf).
2.4.10 Upgrading existing applications

After installing a new version or a service pack, you must upgrade existing
applications before document processing is being started.
Note: The technical field names have been changed with version 16.5, that is
you must use different mapping IDs in Business Center for BCC applications.
• For existing application, created before version 16.5 and upgraded to version
16.5, use the mapping ID CAPTURE.
• For applications newly created with version 16.5 and later, use the mapping
ID CAPT_BCC.

To upgrade an application:
1. Open the application.

2. On the Application tab, in the Setup group, click Settings.
3. In the appearing Settings dialog box, click OK.
The application is now being upgraded.
4. On the application menu, click Export Application, and then click To SAP to
export the application.
5. Close the application.
2.5 Optional follow-up activities

2.5.1 Moving the caches to a different location
The caches used to store temporary Recognition data reside in a subfolder of the
temporary files folder of the user account that you specified in the Service Account
dialog box during installation. these data can be moved to a different location. For
more information, see “Configuring cache location” on page 68.
2.5.2 Moving all BCC data to a different drive

By default, BCC 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, all BCC data can be moved to different locations. For more information,
see “Moving BCC data to a different location” on page 66.
2.6 Installing updates

2.6.1 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 BCC.
Service packs are cumulative, that is a service pack contains all changes contained in
previous service packs of the respective BCC version. Therefore, it is sufficient to
install only the latest service pack after installing BCC. 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 BCC 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 BCC
system where the corresponding service pack has been installed. Patches are

2.6. Installing updates
cumulative, that is a patch contains all changes contained in previous patches for the
same service pack.
Note: After installing patches and service packs, the applications can no longer
be used with an earlier service pack. For more information, see the Release
Notes of a service pack, or the patch notes of a patch, respectively.
To install a service pack or a patch:
1. Stop all Hot Spots: Extraction Link Hot Spots, Download Link Hot Spots
(invoice applications), and Feedback Link Hot Spots (applications for other
document types) of all applications.
2. On the General tab, in the Server group, click Cluster and wait until all Cluster
Nodes have finished processing, that is, until all are in state Ready.
3. Terminate the Customizing Client and all Validation Clients.
4. Install the service pack or patch on all participants, that is Recognition Server,
Recognition Nodes, and Validation Clients.
5. Upgrade each application: Open it, open the Settings dialog box, and then close
it clicking OK.
6. Export all applications to SAP ERP or SAP S/4HANA. The Validation Clients
download the upgraded applications automatically.
7. In VIM/BC reset all documents to Recognition that are waiting for validation.
8. Start all Hot Spots.
9. Start Validation Clients as needed.
2.6.2 Installing the Imaging Plug-in

BCC uses an imaging component provided by the Recognition Engine. You can
install this imaging component separately, and it is used by BCC if it provides a
newer version of the imaging component.
The different versions of the Imaging Plug-In are compatible. Thus you can install
and use always the newest version of the Imaging Plug-In without regard to version
and patch level of BCC. This makes bug fixes available as soon as a new Imaging
Plug-In version is released, and you do not must wait until an BCC Patch or Service
Pack is available. You can install BCC Patches or Service Packs and new versions of
the Imaging Plug-In as needed because BCC will always use the newest version of
the imaging component.
To verify the used version of Imaging Plug-In:
• In Customizing Client and Validation Client, click Help > About.

The About dialog box indicates the version of the used imaging component and
whether the Imaging Plug-In is active.

The XML file created by ProductConfigInfoTool.exe contains an Imaging

tag. Its value shows the version of the used imaging component and whether
the Imaging Plug-In is active.
To install the Imaging Plug-In:
1. Download the Imaging Plug-In as product Capture Imaging Plug-In in My

Support (https://knowledge.opentext.com/knowledge/llisapi.dll/Open/
61183571).
2. Optional To change the Imaging Plug-In installation folder, adapt the

ImgPluginInstallDir registry key in HKLM\SOFTWARE\OpenText\Capture
Common.
2.7 Upgrading
2.7.1 Upgrading ICC
If you are using ICC and want to process additional document types with Business
Center on SAP ERP or SAP S/4HANA, you must install the plug-in Business Center
Capture Invoice Solution.
Note: After the upgrade, the applications cannot longer be used with older
ICC versions.
To upgrade ICC:
1. Stop all Hot Spots, that is Extraction Link Hot Spots, and Download Link Hot
Spots of all applications.
2. On the General tab, in the Server group, click Cluster, and wait until all Cluster
Nodes have finished processing, that is until all are in state Ready.
3. Close the Customizing Client and all Validation Clients.
4. Remove ICC on all participants.
5. Remove SAP.Net Connector on all participants.
6. Install SAP.Net Connector on all participants.
a. In the Select Installation Folder dialog box, select the option Everyone.
b. In the Optional setup steps dialog box, select Install assemblies to GAC.
Alternatively, if you intend to use the WMI provider, select Register WMI
provider and install assemblies to GAC.
7. Install the SAP Connector to its standard location.
8. Install the new BCC version on all participants, that is on Recognition Server,

2.7. Upgrading
9. Install Invoice Solution plug-in.
it clicking OK.
11. Export all applications to SAP. The Validation Clients will download the
upgraded applications automatically.
12. In Business Center/Vendor Invoice Management, reset all documents to

“Recognition that are waiting for validation”.
14. Start Validation Clients, as needed.
2.7.2 Upgrading BCC

If you are using BCC and want to process also invoices, you must install the plug-in
Business Center Capture Invoice Solution.
Note: After the upgrade, the applications cannot longer be used with older
BCC versions.
To upgrade BCC:
1. Stop all Hot Spots, that is Extraction Link Hot Spots, and Download Link Hot
Spots of all applications.
2. On the General tab, in the Server group, click Cluster, and wait until all Cluster
Nodes have finished processing, that is until all are in state Ready.
3. Close the Customizing Client and all Validation Clients.
4. Remove BCC on all participants and also all installed solutions.
5. Install the new BCC version on all participants, that is on Recognition Server,
6. Install required solutions delivered with the new BCC version.
it clicking OK.
8. Export all applications to SAP. The Validation Clients will download the
upgraded applications automatically.
9. In Business Center/Vendor Invoice Management, reset all documents to

“Recognition that are waiting for validation”.
11. Start Validation Clients, as needed.

2.7.3 Upgrading Validation Client

To upgrade the Validation Client:
1. Uninstall all Validation Clients.
2. Install Validation Client. For more information, see “Installing the Validation
Client” on page 28.

Chapter 3
Monitoring BCC
For monitoring of a BCC system, you can use external monitoring tools, and the
Inbound Configuration and Inbound Administration work center in Business
Center. 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 (BOCP-CGD).
3.1 Monitoring BCC with external monitoring tools

If you monitor BCC 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: BCC 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. Also the size of the
database file in the SQL Server instance, which depends on the amount of
download data or feedback data, and number and size of repositories for
Adaptive technologies, should not exceed a maximum size, which can be
estimated. Therefore disk space should pose no problems if you provided
sufficient resources.
• Main memory: Because the Cluster Node processes on the 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 Services: For document processing, the Microsoft Windows
Services DOKuStar HotSpot, DOKuStar Load Manager must be available.
Therefore it is meaningful to monitor whether these services are running. If a
service is not running, start it.

Chapter 3 Monitoring BCC
3.1.1 Monitoring BCC with Wily Introscope

For monitoring with Wily Introscope, a Probe Builder Directives files (file
extension .pbd) for BCC is available. This file specifies four methods for monitoring:
• OnStart in class DOKuStar.Cluster.QueuedOperation. Is called when

processing of a document starts. Is called only while documents are being
processed. If no jobs are available for some time, these methods are not called.
• OnStop in class DOKuStar.Cluster.QueuedOperation. Is called when
processing of a document stops. Is called only while documents are being
processed. If no jobs are available for some time, these methods are not called.
• GetCurrentDocuments in class
DOKustar.Runtime.HotFolders.Connectors.LinkSAP.SAPConnector. Is called
regularly to fetch extraction jobs from SAP ERP or SAP S/4HANA. By default,
the method is called once per minute for each application. If the method is no
longer called, document processing stops because no new recognition jobs are
downloaded. For monitoring of this method it is necessary that the SAP
Extraction Link Hot Spot of at least one application is started so that BCC is
connected to SAP.
• Extract in class DOKuStar. Extraction.Server.NetExtractor is called when a
single page is processed.
To download Wily instrumentation, the .NET Agent, and the Probe Builder
Directives (bcc.pbd file), go to https://support.sap.com/software/patches/a-z-
index.html, and then click SAP Solution Manager > SAP Solution Manager 7.1 >
Entry by component > Agents for managed systems > WILY INTRO AGT
X.X .NET.
3.2 Monitoring BCC using the SAP Solution Manager

BCC can be administered using the SAP Solution Manager. For more information,
see the SAP Solution Manager documentation (https://help.sap.com/viewer/p/
SAP_Solution_Manager).
3.2.1 Providing technical configuration information

To provide technical configuration information, open the start menu on BCC, go to
the BCC program group, and under Tools click Product Config Info Tool. An XML
file ProductConfigInfo.xml is then created in the data share
DOKuStarDispatchData. Its tags contain the following information:
Tag Information
DataShare Path of the data share, that is \\<servername>
\DOKuStarDispatchData
User User account used for the DOKuStar Load Manager service

3.2. Monitoring BCC using the SAP Solution Manager
Tag Information
Cluster List of ClusterNode tags containing the names of all configured
cluster nodes. The first part of the name indicates the computer the
cluster is running on.
Trace Path of the trace folder
SqlServer Contains:
Server tag with the computer name,
Instance tag with the instance name,
Database tag with the name of the database file,
User tag with the user name in case of SQL Server Authentication,
IntegratedSecurity tag has value true in case of Microsoft
Windows Authentication, false in case of SQL Server
Authentication.
Product Product name (Business Center Capture)
Version Version number
Build Build number
ServicePack Installed service pack
Patch Installed patch
OwnerName Name of the product owner (Open Text)

Chapter 4
Technical operations
4.1 Configuring Indian QR code signature check for

invoices
BCC uses Indian e-invoice public keys for the verification of signed content, that is
BCC 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 4 Technical operations
4.2 Overview of the Customizing Client

The Customizing Client provides tools for the technical configuration of a BCC
production system. It also provides tools for monitoring of a BCC system which are
especially useful on standalone systems used for development and testing.
In the Customizing Client you can switch between several monitoring views to
monitor a special aspect of your BCC system and you can open several tools for the
technical configuration of your system. Tools are opened in a new window. Views
are opened within the Customizing Client window; the according view button in the
ribbon stays pressed to indicate which view is currently open in the Customizing
Client.
The ribbon of the Customizing Client presents two tabs:
• Application
The Application tab presents the Application view, and all tools needed for
application development. It provides the Settings dialog box and the Adaptive
dialog box. In addition the Application tab provides all facilities of the
Validation Client to test Validation within the Customizing Client. All tools of
the Application tab work on the currently opened application.
During application development you work mainly with the Application view.
• General
The views and tools of the General tab are needed for the technical configuration
and for monitoring of a BCC production system. You may need these facilities
during testing of your applications.
You can switch between several technical monitoring views: HotSpot view, Jobs
view, and Cluster view. In addition, the General tab provides the following
tools:
– Trace Viewer. For more information, see “Logging and tracing” on page 52.
– Cluster setup using the Load Manager. For more information, see “Load
balancing” on page 73.
The tools and views of the Application tab are not discussed in detail in this guide.
For detailed information about application development, see OpenText Business
Center Capture for SAP Solutions - Customization Guide (CPBC-CGD). For more
information about validation, see OpenText Validation for SAP Solutions - User Guide
(CPIE-UGD).

4.3. Overview of components
4.3 Overview of components

A BCC system consists of a central component in SAP ERP or SAP S/4HANA, the BC
Inbound Configuration, or the ICC Dispatcher, respectively, and of several Microsoft
Windows components.
4.3.1 Document processing in BC/VIM on the SAP ERP or

SAP S/4HANA system
In BC, the modules of Inbound Configuration control document processing
including BCC. For more information, see section 5.1 “Business Center Capture” in
OpenText Vendor Invoice Management for SAP Solutions - Configuration Guide for
Foundation (BOCP-CGD).
4.3.2 BCC Microsoft Windows components

Each BCC system contains the following Microsoft Windows components:
• Recognition Server
• Customizing Client (user interface)
• Validation Client (user interface)
The Recognition Server processes document images and provides recognition

results. The Customizing Client is used by a user to configure the Recognition
Server. The Customizing Client is always installed together with a Recognition
Server. The Validation Client is used by a user to validate, correct, and complete the
recognition results. The Validation Client and the Recognition Server do not interact
with each other; both interact only with the BC Inbound Configuration or the ICC
Dispatcher.
Huge BCC systems may also contain one or several
• Recognition Node(s)
A Recognition Node receives recognition jobs by the Recognition Server and

provides recognition results.
The following constellations are possible for the Microsoft Windows parts of a BCC
system:

4.3.2.1 Standalone system

Usually, a standalone system is used for developing, for testing, and for demo
systems. All Microsoft Windows components of the BCC system are installed on a
single PC:
• Standalone PC
– Recognition Server with Customizing Client and databases

– Validation Client
4.3.2.2 Recognition Server and Validation Clients

This constellation is used for testing and for production. According to the number of
processors of the Recognition Server machine, this scenario is suitable for small
applications up to huge applications with thousands of documents to be processed.
• Recognition Server Machine

• Validation PCs
4.3.2.3 Recognition Server, Recognition Nodes, and Validation Clients

This constellation is also used for production. It is suitable to process a very high
number of documents.
• Recognition Server Machine

• Recognition Node Machine(s)
– Recognition Node
• Validation PCs

4.4. Overview of technical runtime scenarios
4.3.3 Further involved components

The following components are involved in a BCC system, but are not part of it:
• Enterprise Scan
• SAP ERP or SAP S/4HANA Archive
4.4 Overview of technical runtime scenarios

4.4.1 Recognition and validation of a document
Involved components:
• Enterprise Scan
• SAP ERP or SAP S/4HANA Archive
• BC Inbound Configuration or ICC Dispatcher, respectively
• Recognition Server (optional: Recognition Node)
• Validation Client
For a specific archive document type, Enterprise Scan scans a document and
archives the document image in the SAP ERP or SAP S/4HANA archive using the
early archiving scenario of SAP ERP or SAP S/4HANA. The workflow that is
assigned to the archive document type triggers the BC Inbound Configuration, or
the ICC Dispatcher, respectively. There, an entry for the document is added. This
entry has the status Ready for OCR.
The Recognition Server periodically asks for new recognition jobs and gets a
recognition job for the document. The status of the document entry changes to Sent
to OCR.
The Recognition Server fetches the document image from the archive, processes the
image, sends the recognition results to VIM/BC, and archives a result XML file in the
SAP ERP or SAP S/4HANA archive. If there are additional Recognition Nodes, the
Recognition Server may delegate job processing and result export to a Recognition
Node.
After receiving the recognition results, the status of the invoice entry is changed to
Extraction Completed. Based on business rules, the VIM/BC decides whether or
not the recognition results must be validated by a user. If validation is required, the
status of the document entry is changed to Ready for Validation.
The user working at a Validation Client asks for new validation jobs and gets a
validation job for the document. The status of the document entry is changed to Sent
to Validation.
The Validation Client fetches the result XML file from the archive. The Validation
Client user validates, corrects, and completes the recognition results and sends the

validated results to VIM/BC. The status of the document entry is changed to

Validation Completed.
For more information about document processing in BCC, see OpenText Vendor
Invoice Management for SAP Solutions - Configuration Guide for Foundation (BOCP-
CGD).
4.4.2 Downloading data from SAP ERP or SAP S/4HANA

• BC Inbound Configuration, or ICC Dispatcher, respectively
For an invoice application, the Recognition Server periodically asks for vendor
master data and purchase order data.
For other application types, the Recognition Server periodically asks for feedback
data.
The Recognition Server imports the data into its local database.
4.4.3 Supervised learning on the Customizing Client

• Customizing Client
The user working at the Customizing Client validates a document. The user adds a
missing field value by clicking on the appropriate value on the document image
shown in the Customizing Client. Then the user clicks Train. The information where
the missing field value can be found is immediately used by the Recognition Server.
The server adds the information to the learning database.
4.5 Monitoring BCC using the Customizing Client

To monitor a BCC system, use the Inbound Administration work center of BC. 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 (BOCP-CGD).
The Customizing Client is installed on the Recognition Server and provides views to
monitor the Recognition Cluster of a BCC system.

4.5. Monitoring BCC using the Customizing Client
4.5.1 Monitoring Hot Spots

To show the list of Hot Spots:
• In the Customizing Client, on the General tab, in the Server group, click
HotSpot.
The State column indicates which Hot Spots are active. In a production system,
all Hot Spots of all applications should be in state Scheduled most of the time.
The Last run column shows when the Hot Spot was running last time and the
amount of data that were processed during this run.
4.5.2 Monitoring jobs

To monitor jobs:
• In the Customizing Client, on the General tab, in the Server group, click Jobs.
A list of all jobs that are being processed or waiting for processing is shown.
State
Indicates the operation state:
Pending
Job waits for processing.
Processing
Job is being processed.
OK
Job has been completed successfully.
Error
Job has terminated with error(s).
If several processing nodes are available in your configuration, several jobs

may be in state Processing at the same time. Additional jobs that have
already been downloaded from SAP ERP or SAP S/4HANA but are still
waiting for a free processing node are in state Pending.

Cluster Node
Name of the cluster node that currently processes this operation. As long as
a job is waiting for processing, this field is empty.
Operation Type
Operation type used by the operation.
Label
BatchID that started the currently active operation.
Started at
Time at which the operation started.
4.5.3 Monitoring the Recognition Cluster

To monitor the Recognition Cluster:
• In the Customizing Client, on the General tab, in the Server group, click
Cluster.
A list of all cluster nodes with state information is shown.
State
Indicates the cluster state:
Start-up
Cluster node is starting.
Ready
Cluster node is ready for operation.
Processing
Cluster node is executing an operation.
Suspended
Cluster node is suspended. No operations are assigned to this node.
Offline
Cluster node is off line, for example, slave PC is off, or network is
disturbed.

4.5. Monitoring BCC using the Customizing Client
Error
Cluster node is in a state of error and will be reset.
Closing
Cluster node is closing, for example due to a reset or a changed
configuration.
Name
Cluster node name composed of computer name, service type, and instance
number.
Loaded Operation Type
Currently loaded operation type.
Total Time
Total active time of the cluster node since the Load Manager started in the
format d.hh:mm:ss.
Operations
Number of processed operations since the Load Manager started.
Configured Operation Types
Operation types specified at the Exclusive Operation Type property of the
cluster node. If no exclusive operation types have been specified, the field is
empty.
Priority
Priority specified for the Cluster Node.
To configure a cluster node:
• Right-click a cluster node line, and then click one of the following:
Suspend Cluster Node

Excludes the cluster node from load balancing. A currently active operation
is completed before suspension takes effect.
Release Cluster Node
Releases a suspended cluster node to rejoin the load balancing.
Lookup Cluster Node
Updates the cluster node state (normally the Load Manager updates it once
per minute).
Reset Cluster Node
Terminates the current instance of the cluster node and starts a new one.

4.6 Logging and tracing

4.6.1 Logging
Logging is done on the SAP ERP or SAP S/4HANA side of a BCC system. For more
information, see section 3.5 “Configuring logging” in OpenText Vendor Invoice
Management for SAP Solutions - Configuration Guide for Foundation (BOCP-CGD).
4.6.2 Overview of tracing

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

• Hierarchical tracing architecture
• Easy configuration on-the-fly through XML configuration files or software
• Trace Viewer to view trace files, filter and search trace data, and observe
applications on several hosts
4.6.3 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.
For example DOKuStar.Runtime is a parent of DOKuStar.Runtime.Server, and

DOKuStar is a parent of DOKuStar.Runtime.
A special tracer, called the RootTracer, is the parent of all tracers and has no name.
4.6.4 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.

4.6. Logging and tracing
RemotingTraceListener
This listener writes trace messages to a remote sink, for example the Trace
Viewer in order to display trace messages on-the-fly.
ConsoleTraceListener
Writes trace messages to console output.
Trace listeners may trace at different levels. Every tracer may have assigned its own
collection of trace listeners but usually only the root tracer has them all and all other
tracers inherit them.
4.6.5 Trace root path

BCC writes trace messages to trace files located relative to a root path for all
applications. The default root path is Program Data\OpenText\Trace.
To change the default trace folder:
1. Set the registry value TraceRootPath (type REG_SZ) 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.
Trace configuration files are stored directly under the root path. Trace files are
written to a subfolder, typically the folder name is the application name, for example
DOKuStar Load Manager.
4.6.6 Trace levels

Tracers and trace listeners have trace levels used to control the volume of the tracing
output. You can unse following trace levels:
Fatal
Used in case of errors where the administrator has to be called immediately.
Those errors risk to crash down processing for example disk full.
Error
Used in case of errors that aborted the current job. Probably processing
continues with the next job.
Warning
An unexpected issue occurred and should be traced in order to be able to
analyze it later especially if it occurs again.
Info
This is the default level. It is use to trace normal progressing as an administrator
would see it in a monitor, for example:
• service has been started

• job <...> has been started

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

need to restart the load manager service.
4.6.7 Trace configuration

Several trace configuration files in the trace folder specify which trace messages are
written 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 58. 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 <install dir>
\TraceConfig folder.
4.6.8 Location of trace files and trace configuration files

Usually, the Runtime and Extraction 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

Hot Spot
The Hot Spot service is the connection between the Load Manager and the SAP
ERP or SAP S/4HANA system.
• Trace files
<TraceRoot>\DOKuStar Professional\HotSpot*.log
<TraceRoot>\HotSpot.traceconfig
Customizing Client
• Trace files
<TraceRoot>\rda1\rda1*.log
<TraceRoot>\rda.traceconfig
All services
The Microsoft Windows event log is used to log creating, starting, and stopping
of the services.
4.6.9 Format of traces

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

[[<Message>]]
DateTime
Time when the trace message was written, sortable format yyyy.MM.
ddTHH:mm:ss.
Level
Trace level Fatal, Error, Warning, Info, Fine, Finer or Finest.
Computer
Name of the host where the trace message was written.
Application
Name of the application that wrote the trace message.
PID
ID of the process that wrote the trace message.
Category
Trace category (hierarchically to reflect classes and modules).
ThreadId
ID of the thread that created the trace message.

Message
Trace message enwrapped with 2 squared brackets at begin and end. Note: A
trace message is multi-line; it may contain carriage return and line feed.
Example: 2018.09.04T10:17:45 Error: SYS2186 DOKuStarLoadManager 2264

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

The Trace Viewer is used to show trace messages created by the BCC 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 BCC 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 60.
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 61.
Find
You can search in the currently open file. For more information, see
“Searching trace messages” on page 62.
Tip: You can enable more functions in the main menu, or in the context
menu of the right area.
• Open: Opens a trace that is not available in the file list.

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

The contents of the file is shown in the messages list view on the right side.
3. Double-clicking a message in the messages list view.
The Trace Message dialog box shows the complete message and its details.

4.6.10.1 Selecting a trace configuration

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

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

4.6.10.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 émpty only matching messages are shown
in the messages list view. The check boxes permit to control text matching.
• If the Match case check box is selected, the message must contain the
string in exactly the same spelling with respect to upper and lower case
letters.
• If the Match whole word only check box is selected, the string will not
be matched against a part of a word.

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

used as a regular expression.
4.6.10.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

4.7. Configuration data (production system)
3. Click Find Next or Find Previous to search the message list. The next or
previous matching trace message is selected in the messages list view.
4.7 Configuration data (production system)

After performing the installation steps described in chapter
“Installation“ on page 19, your BCC configuration consists of a Recognition Server (=
Cluster Master) and optionally several simple Recognition Cluster Nodes (Cluster
Slaves), and one or many Validation Clients. On each computer participating in a
BCC system you have installed a different selection of components and you have
performed some configuration. As a result, the participants differ in terms of
configuration files, databases, available tools, and running Microsoft Microsoft
services.
The following sections describe which components are located on which participants
and how the different participants interact in respect to the components.
4.7.1 Technical configuration data

4.7.1.1 Load Manager files
A Recognition Cluster contains one Recognition Cluster Master (= Recognition
Server). The Cluster Master distributes the workload on the hardware of the
Recognition Cluster. The Cluster has to be configured on the Master with the Load
Manager Configuration tool (see “Cluster nodes” on page 74). The Load Manager
Configuration tool saves the cluster configuration files into the folder
%ALLUSERSPROFILE%\Application Data\Captaris\DOKuStar Load Manager on the
Cluster Master.
4.7.1.2 Hot Spot files

The connection of the Recognition Server to VIM/BC is provided by the Hot Spot
Service. The Hot Spot configuration files are saved into the folder
%ALLUSERSPROFILE%\Application Data\Captaris\DOKuStar Professional\3.0\
HotFolders on the Recognition Server.
4.7.1.3 Trace configuration files

Each participant of a BCC 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 “Logging and tracing” on page 52.

4.7.1.4 Customizing Client

The Customizing Client runs on the Recognition Server and keeps configuration
data in the folder %ALLUSERSPROFILE%\Application Data\Open Text\DOKuStar
Dispatch\data\config\RdaProject. For more information about application
configuration data, see “Application configuration data (customizing data)”
on page 64.
4.7.2 Application configuration data (customizing data)

The application configuration data are saved in an SAP ERP or SAP S/4HANA table
and are downloaded to a BCC participant on demand. The Recognition Server and
the Validation Clients keep the downloaded configuration data in the folder
%ALLUSERSPROFILE%\Application Data\Open Text\DOKuStar Dispatch\data\
config\RdaProject. The Recognition Nodes use the application configuration data
of the Recognition Server. They do not copy the configuration data to a local folder.
The Validation Clients download the application configuration data automatically

after the validation user has logged in to SAP ERP or SAP S/4HANA. The download
of the application configuration data on the Recognition Server is not performed
automatically. The administrator has to download the application configuration data
using the Customizing Client after a new version of the application configuration is
available in SAP ERP or SAP S/4HANA.
4.7.3 Runtime files

4.7.3.1 Temporary files of Document Reader and Document Extraction
On the Recognition 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 Recognition Cluster Node is running using the
LocalSystem account, the temporary files are written in the temp folder defined in
the system temp variable.
If the Load Manager Service is running using a domain account, the temporary files
are written into the temp folder defined in the user temp variable.

4.7.3.2 Trace folder

Each participant of a BCC system writes trace files to its local trace folder
%ALLUSERSPROFILE%\Application Data\Open Text\Trace.
The location of the Trace folder can be changed by creating a registry entry. For
more information, see “Logging and tracing” on page 52.
4.7.4 Registry entries

During installation, BCC adds some entries to the Microsoft Windows registry, for
example installation paths and version information.
4.7.5 Databases
4.7.5.1 SQL Server instance
BCC needs a database in a suitable SQL Server instance, which must be available
when BCC is installed. During installation, a dialog box asks for instance and
database name. You can either install an SQL Server instance on the Recognition
Server or use a database in an instance that is installed on a different computer.
The database is accessed by the Recognition Cluster (DOKuStar Load Manager

service) and by the user who customizes the system. If Microsoft Windows
authentication was selected to access the database, then the user account configured
for the DOKuStar Load Manager, and the user customizing the system must have
access rights for the database.
4.7.5.2 BCC database

For invoice applications, Vendor master data and purchase order data are
periodically downloaded from SAP ERP or SAP S/4HANA and stored in the BCC
database. In addition, this database includes recipient data, which have been
imported during customizing.
For other application types, feedback data needed for data extraction are
periodically downloaded from SAP ERP or SAP S/4HANA and stored in the BCC
database.
Several tables in the database contain the learning data for Adaptive Recognition
(ART) and Adaptive Classification (ACT). For each application there is a single table
with learning data for all Adaptive Recognition fields of the respective application.
For each adaptive classification field that has been added to an invoice application
there is a single table with learning data.
The database is used for all applications running on the Recognition Server, but each
application uses its own set of tables.

4.7.6 Microsoft Windows Services

BCC 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 Services
run on the Recognition Server and on the Recognition Nodes:
Recognition Server
• Load Manager Service (DOKuStar Load Manager)

• Hot Spot Service (DOKuStar HotSpot)
Recognition Node
• Load Manager Service (DOKuStar Load Manager)
The Load Manager Service on the Recognition Server distributes the workload on
the Recognition Nodes by communicating with the Load Manager Services on the
Nodes.
The connection of the Recognition Server to VIM/BC is provided by the Hot Spot
Service. The Hot Spot Service polls for recognition jobs. It also polls for vendor
master data and purchase order data or for feedback data, which are imported into
the database of the Recognition Server.
The Tracing service provides tracing.
In addition to the Capture Center Microsoft Windows Services, there is also a special
BCC service, the SLD Data Supplier Service (Invoice Capture Center SLD Data
Supplier). This service runs on each Microsoft Windows component of an BCC
system. It registers BCC in the SAP System Landscape Directory.
4.7.7 Moving BCC data to a different location

You can move most of the configuration and runtime data of BCC can be moved to a
different location.
Only a few configuration files, which are created below the Users folder when the
Customizing Client or the Document Extraction Design Studio is started, cannot be
moved; these files can be deleted afterward. If the programs are not used on a
production system, no configuration and runtime data remain on the system drive if
all other files are moved to a different location.

4.7.7.1 Moving the folder DOKuStarDispatchData to a different location

By default, the shared folder DOKuStarDispatchData is located in %PROGRAMDATA%
\Open Text\DOKuStar Dispatch\data. The subfolder config of the
DOKuStarDispatchData folder contains the configuration.
To move the share to a different location:
1. Stop all HotSpots and wait until processing has been completed.
2. Stop all clients.
3. Stop all BCC services on the server and the Recognition Nodes. For more
information, see “Starting and stopping of services on the Recognition Server
and the Recognition Nodes” on page 84.
4. Stop sharing the folder %PROGRAMDATA%\Open Text\DOKuStar Dispatch\data.
5. Create a folder at the new location.
6. Move the contents of %PROGRAMDATA%\Open Text\DOKuStar Dispatch\data to

the new folder.
7. Share the new folder using the name DOKuStarDispatchData.
8. Be sure to provide the needed rights for all components of your BCC system.
9. Restart the services.
10. Restart the HotSpots.
If the share is moved to a different computer, the configuration path (that is the path
to the config folder) changes. Adapt the configuration after moving the share.
To move the share to a different computer:
1. Stop the HotSpots and wait until processing has been terminated.
2. Stop all running clients.
3. Stop all BCC services on the server and on the Recognition Nodes (see “Starting
and stopping of services on the Recognition Server and the Recognition Nodes”
on page 84).
4. Stop sharing the folder %PROGRAMDATA%\Open Text\DOKuStar Dispatch\data.
5. Create a folder on the different computer.
6. Move the contents of %PROGRAMDATA%\Open Text\DOKuStar Dispatch\data to

the new folder on the different computer.
7. Share the new folder.
8. Be sure to provide all required rights for all components of your BCC system.

9. Adjust the configuration location specification: On each BCC installation, even

on BCC itself, edit the configuration file ClientConfig.dfc, which is located in
its local folder %PROGRAMDATA%\Captaris\DOKuStar Dispatch. This file
contains a tag named <DefaultServerConfigLocator> telling the client where
to look for the config folder. Change the value of the
<DefaultServerConfigLocator> tag according to your new shared folder.
10. Restart the services.
11. Start the HotSpots.
4.7.7.2 Configuring the location of the ClientConfig.dfc file

On each computer where BCC is installed, the ClientConfig.dfc file specifies the
location of the DOKuStarDispatchData share containing the configuration data. By
default, this file is created in the %PROGRAMDATA%\Captaris\DOKuStar Dispatch
folder on the system drive.
To specify a different location, go to the registry key Software\Wow6432Node\Open

Text\Invoice Capture Center, either under HKEY_LOCAL_MACHINE or under HKEY_
CURRENT_USER, and then create a value named ClientConfigPath containing
absolute path and file name of the file.
4.7.7.3 Configuring cache location

The cache is located in a DOKuStar Professional/3.0/Cache subfolder of the
temporary files folder on the server and each Recognition Node.
To move files created in the temporary files folder to a different location:
1. Create a registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenText\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.
To move the temporary files folder to a different location:
1. Log in with the user account that you specified as service account during
installation.
2. Use Control Panel to modify the user environment variable tmp accordingly.
3. For the change to take effect, restart the service DOKuStar Load Manager.

4.7.7.4 Configuring trace file location

The location of the trace file is controlled by a registry value on each BCC computer.
For more information, see “Trace root path” on page 53.
4.7.7.5 Configuring program data location of several components

By default, several BCC components create files in subfolders of the %PROGRAMDATA%
folder on the system drive:
• Load Manager: Configuration files

• Hot Spots: Configuration files and temporary files
• Adaptive Recognition: Inverted index files for Adaptive Recognition repositories
You can move the program data files, for example to a different drive.
To move program data files to a different location:
1. Create a registry key

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OpenText\Capture Common.
2. For this key, create a string value named CommonApplicationDataPath

containing the path for these program data.
4.7.7.6 Configuring HotSpot folder locations

By default, the HotSpot configuration files and folders for temporary files needed
during document import are both located in subfolders of the folder %PROGRAMDATA%
of the system drive.
For the configuration files and for the temporary file folder, another location can be
specified by a configuration file named HotFolders.hcx in the %PROGRAMDATA%
\Captaris\DOKuStar Professional\3.0\HotFolders folder. If this file does not
exist, the default location of the HotSpot data is used.
Note: If a different location for program data has been specified using the
respective registry value, the file HotFolders.hcx must reside in the respective
subfolder at the location specified by the registry value. In this case, you can
use the file to move the HotSpot files to yet another separate location.
For more information about specifying the location, see “Configuring program
data location of several components” on page 69.
Example: This example shows a configuration file moving the HotSpot files to folders on a
different local drive:
<?xml version="1.0"?>
<HotSpotServiceConfiguration
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/
XMLSchema" xmlns="http://www.DOKuStar.com/HotSpotService/V01">
<EngineConfiguration>
<ConnectorConfigurationFolder>D:\HotSpots\Config</ConnectorConfigurationFolder>

<ConnectorWorkingFolder>D:\HotSpots\Work</ConnectorWorkingFolder>
</EngineConfiguration>
</HotSpotServiceConfiguration>
Important
If you change the location of the configuration files, the HotSpots with their
properties get lost. You must create and configure them anew.
To configure HotSpot folder locations:
1. Stop all HotSpots and wait until all documents in progress have been processed.
Otherwise data for documents in progress get lost if you change the temporary
data folder.
2. If the HotFolders.hcx configuration file does not exist yet, create it in the
%PROGRAMDATA%\Captaris\DOKuStar Professional\3.0\HotFolders folder.
Copy the content from the example above.
3. Edit the file.
• In the ConnectorConfigurationFolder tag, specify the folder for the

HotSpot configuration files.
• In the ConnectorWorkingFolder tag, specify the location for the temporary
data.
Only specify folders that do exist and can be accessed by the HotSpot service.
Otherwise, the HotSpot service will not start. In particular, use a UNC path to a
shared folder if you switch a location to another computer; mapped network
drives will not work.
4. Restart the service.
Create and configure the HotSpots again if you changed the location of the
configuration files.
4.7.7.7 Moving the BCC database to a different location

To switch to a different database, which may reside in a different SQL Server
instance:
1. Start the Customizing Client.
2. Export all applications to files.
3. Delete all applications.
4. On the application menu, click Options.
5. In the Options dialog box, click Set Database Connection.
6. To switch to a different SQL Server, click Refresh, and then click the desired
server in the Server name list as soon as the list has been updated.

4.8. Backup and restore
Tip: The Server name list only shows SQL Server instances on computers
within the current IP subnet. To switch to a server in a different subnet,
enter <computer name>\<instance name> in the Server name box.
7. To use SQL Server authentication, click Use SQL server authentication, and
then enter user name and password.
8. Optional To secure the connection with SSL, click Use SQL encryption.
Additionally, you must enable the SQL server instance. For more information,
see “How to enable SSL encryption for an instance of SQL Server by using
Microsoft Management Console” on the Microsoft support page.
9. Click the desired database in the Database list.
10. Optional Click Test Connection to make sure that the database can be reached.
11. Close the dialog boxes.
12. Restart the Microsoft Windows Services DOKuStar Load Manager and
DOKuStar HotSpot.
13. Import the applications.
4.8 Backup and restore

The BCC database contains PO and vendor data of all invoice applications and
feedback data of other applications, which typically are updated by daily
downloads. Therefore periodical backups of the database are not useful because they
would become outdated within a few days.
The BCC database also contains learning data of Adaptive Recognition and
Adaptive Classification. Typically training is performed on a separate BCC system.
In this case backup is done by exporting the learning data to a file, which is then
imported on the production system, following a training session. If training is done
on the production system, OpenText recommends that you regularly back up
learning data using the Export Application command of the Customizing Client.
For more information, see How to: Back Up a Database (SQL Server Management
Studio) (http://msdn.microsoft.com/en-us/library/ms187510.aspx) and How to:
Restore a Database Backup (SQL Server Management Studio) (http://
msdn.microsoft.com/en-us/library/ms177429.aspx).
The backup can occur while the databases are online and being used by the
Recognition Server.
OpenText recommends scheduling backups and download operations for different

times.
For more information about backup operations in SQL Server, see Backup Overview
(SQL Server) (http://msdn.microsoft.com/en-us/library/ms175477.aspx).

4.9 Periodic activities

4.9.1 Deleting trace files
Tracing creates new trace files each day, or if a trace file reaches a size of 50 MB.
Trace files are deleted automatically after ten days.
4.9.2 Restricting the growth of the BCC database

The BCC database provides vendor master data, purchase order data, and recipient
data for each invoice application and feedback data for other applications. In
addition it contains learning data of applications that use Adaptive Recognition or
Adaptive Classification. For each invoice application there is a distinct set of
database tables in the database.
The recipient data are imported once for each invoice application during
configuration time from a file.
Vendor master data and purchase order data are imported periodically by SAP
Download Link Hot Spots. To optimize download performance of daily downloads
and to restrict growth of the Database, two SAP Download Hot Spots are created
when you create or import an invoice application.
The first Hot Spot is configured for weekly full download of all data where all data
in the database are deleted before the complete data are downloaded from SAP ERP
or SAP S/4HANA restricting growth of the database.
The second Hot Spot is configured for daily delta-download excluding vendor data
which reduces the volume of download data and ensures that purchase order data
are up-to-date. During a delta-download, only new data are downloaded and added
to the respective database. In this case the database grows continually because old
data are not deleted from the database.
4.9.3 Creating backups of learning data

If training is performed on the production system, create a backup of the learning
data on the Recognition Server daily using the Export Application command of the
Customizing Client for each affected application. If training is only performed by the
administrator at certain times, create a backup after each training session. You can
create a backup while the system is running.

4.10. Load balancing
4.10 Load balancing

4.10.1 Understanding the Load Manager
In a BCC system the actual data extraction from a document images and super-
ordinate tasks, like splitting of pages or export of results, are performed by a
component named Document Reader.
The Load Manager enables load balancing of multiple instances of the Document
Reader Runtime within a configured cluster of computers and/or 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 Recognition
Server and on each Recognition Node of the Recognition Cluster. This Microsoft
Windows service is started automatically after installation and at every system start.
The Load Manager on the Recognition Server is the master; it controls the load
balancing. This master receives job requests and distributes these tasks over Cluster
Nodes within the Recognition Cluster. Usually the Recognition Cluster contains as
many Cluster Nodes as processors. If the Recognition Server is a two-processor
machine and if there are no further Recognition Nodes, the Recognition Cluster will
consist of two Cluster Nodes. If the Recognition Server is a two-processor computer
and if there are two additional two-processor Recognition Nodes, the Recognition
Cluster consists of six Cluster Nodes.
A Cluster Node hosts a service of a specified type called the Service Type. For the
Document Reader, there are services for Document Extraction and the Document
Reader Runtime.

In order to process a job request, a Cluster Node usually must be initialized, for
example a Document Reader Runtime Cluster Node is initialized with the name of a
Document Reader project file. There may be more complex initializations on other
service types. Such initialization data are stored within Profiles, which are also
configured at the master. A job refers only to this profile name instead of specifying
all initialization data to carry out the task.
The Document Reader automatically creates and configures the appropriate profiles
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 of the Customizing Client on the Recognition
Server permit to monitor the Load Manager.
The Cluster configuration is managed centrally at the Recognition Server. The Load
Manager Configuration tool (provided by the Customizing Client) permits to
configure the Recognition Cluster.
4.10.2 Cluster nodes

After installation of the Recognition Server the Recognition Cluster is already pre-
configured. It contains one Runtime Node for each processor of the Recognition
Server. If your Recognition Cluster only consists of the Recognition Server and does
not contain any further Recognition Nodes the pre-configuration is sufficient. If your
Recognition Cluster consists of a Recognition Server and several Recognition Nodes
you must configure the Recognition Cluster using the Load Manager Configuration
tool.
At runtime, additional Runtime Nodes for each processor on that computer are
added automatically. Therefore you need to modify configuration only if you have
installed BCC on additional Recognition Nodes.
4.10.2.1 Configuring cluster nodes

To configure the cluster, you create a computer node for each additional Recognition
Node.
To configure cluster nodes:
1. Start the Customizing Tool on the Recognition Server.
2. On the General tab, in the Tools group, click Cluster Setup.
3. In the Load Manager Configuration dialog box, click Cluster, and then right-
click Add Computer to Cluster.

4. In the URL Editor dialog box, enter the computer name in the Server name box,
and then click OK.
Note: The context menu of the computer nodes permit to add Extraction
as well as Runtime nodes. Whether Extraction nodes are needed, depends
on the Document Reader project. Within BCC, Extraction nodes are not
needed.
5. On each additional Recognition Node, add one Runtime Node for each
processor.
To do so, right-click your computer name, click Add Runtime Nodes, and then
click the number of needed Runtime Nodes.
Example: For a computer with four processors, the configuration should look as follows:

With a high number of processing nodes you also need more RAM to be able to use them
effectively or throughput will decrease because of increased swapping. Typically, you need
about 1.5 GB per Runtime Node.
4.10.2.2 Changing cluster node properties
To change the properties of a cluster node:
1. Click the Cluster node in the tree view.
2. Click the property you want to change, and then define the value.
LookupInterval
Time interval after which the Load Manager checks whether the cluster
node is still alive.

Operation Types
Load Manager operation type.
Optimization Time Window
To prevent loading time, the Load Manager tries to assign an operation of
the currently loaded operation type to a node that becomes available. As
soon as the first operation in the Load Manager queue waits longer than the
specified time, it is assigned to the next available node. Enter the time in the
format hh:mm:ss.
Process Priority
With the default value BelowNormal, priority of the computationally
intensive Runtime Node processes is reduced. Otherwise other important
processes would often have to wait for processor time and would respond
slowly. If you set this property to Normal, priority is not reduced.
Reset Cycle
After the specified number of operations the cluster node is reset
automatically. This can also be used to ensure that the project is reloaded.
Reset on failure
If this property has the value True, the Load Manager tries to reset the
cluster node in case of failure.
Startup Time
Specifies the maximum time the Runtime Nodes should need for start-up. If
the start-up of a Runtime Node exceeds this limit, the corresponding
process is terminated. Enter the time in the format hh:mm:ss.
Use IPC Channel
As default, the Load Manager uses TCP for communication with the local
cluster nodes. If this property is set to True, it uses IPC channels (named
pipes) instead.
4.10.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 BCC 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 add_resources_to_services_sessions.reg file in My Support

(https://knowledge.opentext.com/knowledge/llisapi.dll/Open/62474529), 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.
4.10.2.4 Changing Runtime Node properties
Note: Within BCC you do not need to modify any properties.
To change the properties of a Runtime Node:
1. Click the Runtime Node in the tree view.
2. Click the property you want to change, and then define the value.

Name
Cannot be edited. It is omprised from the computer name, service type and
instance number.
AgentUrl
URL of the agent service for this cluster node within the cluster.
Description
Only for logging purposes.
Exclusive Operation Types
Restricts a cluster node to the specified Load Manager operation types.
Priority
Priority of the cluster node. The Load Manager prefers Runtime Nodes with
a higher priority value when it wants to assign an operation to a Runtime
Node. The default value is 0. To give a node a higher priority, enter a value
greater 0, to give a node lower priority, you can enter a negative value.
4.10.3 Increasing throughput

The throughput of a BCC system can be increased by adding further Recognition
Nodes to the Recognition Cluster or by setting up further Recognition clusters.
The suitable configuration for a BCC system depends on different factors:
• Number of documents to be processed per hour.

• Number of needed Validation stations.
• Used hardware and system environment.
4.10.3.1 Increasing the number of Recognition Nodes

To increase the number of Recognition Cluster Nodes, install additional Recognition
Nodes as described in “Installing BCC on a Recognition Node” on page 26. Add the
respective computers to the Recognition Cluster of the Recognition Server. For more
information, see “Cluster nodes” on page 74.
4.10.3.2 Increasing the number of Recognition Clusters

If you must process millions of documents per year and if you process several BCC
applications, you can setup several Recognition Clusters (= Recognition Server with
Recognition Nodes). Each Recognition Cluster is responsible for a distinct set of
applications. On each Recognition Server download and configure only this distinct
set of applications.

4.11 High availability

The most critical part of a BCC system is the BC Inbound Configuration, or the ICC
Dispatcher, respectively. These components are parts of Business Center or Vendor
Invoice Management in SAP ERP or SAP S/4HANA. Therefore their high availability
is guaranteed.
The application configuration data are stored in SAP ERP or SAP S/4HANA.
Therefore, the high availability of the application configuration data is guaranteed.
The Validation Clients and the Recognition Nodes are not critical at all. Therefore,
there is no fail-over scenario defined for them.
The high availability of the Recognition Server can be achieved with different
scenarios.
For more information about high availability in SAP ERP or SAP S/4HANA, see the
SAP Netweaver Technical Operations Manual (https://help.sap.com/doc/
erp2005_ehp_03/6.03/en-US/72/cd1e4261ea5433e10000000a155106/frameset.htm).
4.11.1 Using two Recognition Servers

4.11.1.1 System configuration
This scenario uses two Recognition Servers running in parallel. Each Recognition
Server is sized for the processing of about 75% of the overall invoice volume and
may comprise additional Recognition Nodes. Both Recognition Servers are polling
for jobs from the same SAP ERP or SAP S/4HANA system.
Both Recognition Servers are configured identically:
• Both servers are running the same applications.

• On both servers, downloads are performed for all applications.
• On server 1, Download Link1 of each application is started, on server 2,
Download Link 2 of each application is started. The time difference between
Download Link 1 and Download Link 2 should be about 4 hours.
• Each Recognition Server has its own local SQL database for best availability.
• Alternatively, the servers could use separate databases on the same external SQL
Server instance, which must be highly available.
• On both Recognition Servers, one CPU should be reserved for database
communication and for downloads.
If a Recognition Server becomes inoperable, available jobs are processed by the other
Recognition Cluster automatically. Optionally, the administrator can switch
Recognition Nodes to the working Recognition Cluster to increase throughput.

4.11. High availability
4.11.1.2 Maintenance operations

If a Microsoft Windows upgrade, patching, or restart is necessary, or if installation of
a product update (Patch or Service Pack) is necessary, always one Recognition
Server should be running.
To perform a maintenance operation:
1. Stop all Extraction Links on Recognition Server 1. All jobs are now fetched by
Server 2.
2. After processing has stopped on Server 1, perform the maintenance operation

on each computer of Recognition Cluster 1.
3. Start Extraction Links on Recognition Server 1.
4. Stop all Extraction Links on Recognition Server 2.
5. After processing has stopped on Server 2, perform the maintenance operation

on each computer of Recognition Server 2.
6. Start Extraction Links on Recognition Server 2.
Although not mandatory, OpenText recommends upgrading Validation Clients, too,

in case of a product update.
4.11.1.3 Upgrade to new product version

If Validation Clients are used, a special procedure is required to ensure that the
Validation Client runs the same software version as the Recognition Node that
processed the respective document.
During the upgrade procedure, one of the Recognition Servers is always running so
that document processing continues.
For an upgrade of the Validation Clients, a maintenance window of up to eight

hours is needed.
To perform an upgrade to a new version:
1. On Recognition Server 1, stop processing and perform the version upgrade.
2. Stop all Validation Clients.
3. Stop processing on Recognition Server 2.
4. Reset all work items in state Waiting for Validation to Recognition.
5. Start processing on Recognition Server 1.
6. Perform the version upgrade on Recognition Server 2 and start processing.
7. On each Validation Client, perform the version upgrade. Each upgraded

Validation Client can start processing.

The steps 6 and 7 can be exchanged or performed in parallel to reduce the time span
during which no documents are validated.
4.11.1.4 Risk considerations
Recognition Servers
• For a maintenance upgrade, no system downtime is required.

• Validation Client downtime is required during version upgrade.
• No system downtime if one of the Recognition Servers becomes inoperable.
There are still some risks that performance may decrease or processing may stop
due to external components:
• The SAP ERP or SAP S/4HANA system must provide jobs.

• The archive system must be available so that the needed images can be accessed.
• The network must be available.
• If an external SQL Server instance is used, the SQL databases must be available.
Validation Clients
The Validation Clients are completely independent of the Recognition Servers.
Risks due to external components:
• The SAP ERP or SAP S/4HANA system must provide jobs.

• The archive system must be available so that the needed images can be accessed.
• The network must be available.
If the Validation Clients are not operational due to one of the listed reasons, the
workflow can be configured to forward work items automatically so that document
processing continues.
4.11.2 Installing two Recognition Servers in one Recognition

Cluster
You can install and configure two Recognition Servers in your Recognition Cluster
and configure the Recognition Cluster on both Servers. Start the Hot Spots only on
one Recognition Server. Now the second Recognition Server behaves as a normal
Recognition Node.
To activate the second Recognition Sever in case of failure of the first Recognition
Server:
1. Restore the backups of the ART and ACT databases of the failed Recognition
Server on the new Recognition Server.

4.12. Starting and stopping
2. Run the Download Hot Spots to import the vendor master data and purchase
order data to the database of the new Recognition Server.
3. Import the recipient data for the applications.
4. Start the Hot Spots on the new Recognition Server.
4.12 Starting and stopping

4.12.1 Starting and stopping of Hot Spots on the Recognition
Server
On the Recognition Server there are up to three different Hot Spots for each
application running on the server:
• One Extraction Link Hot Spot

• Two Download Link Hot Spots for an invoice application
In addition, there is a single Feedback Hot Spot for each SAP ERP or SAP S/4HANA
system to which non-invoice applications are connected.
Extraction Link Hot Spots, Download Link Hots Spots, and a single Feedback Hot
Spot are created automatically when applications of the respective types are created
or downloaded from SAP ERP or SAP S/4HANA, but they are not active. You must
configure and activate them manually.
If an Extraction Link Hot Spot is active (that is running), the Recognition Server
periodically asks BC/VIM for recognition jobs.
If a Download Link Hot Spot is active, the Recognition Server periodically asks
BC/VIM for new download data (vendor master data and purchase order data) and
imports the new download data to the local database.
If a Feedback Hot Spot is active, the Recognition Server periodically asks BC/VIM for
feedback data needed for some data extraction methods of non-invoice applications.
To start a Hot Spot:
1. Open the Customizing Client on the Recognition Server.
2. On the General tab, in the Server group, click HotSpot.
3. Select the appropriate Hot Spot.
4. On the toolbar, click Start.
The Hot Spot‘s task is not performed immediately, but according to the scheduling
configuration of the Hot Spot. To immediately perform the Hot Spot‘s task, click
Run now on the toolbar.
To stop a Hot Spot, click Stop on the toolbar.

Note: If the Extraction Link Hot Spot is not running, the Recognition Server
does not ask for recognition jobs and does not deliver recognition data.
4.12.2 Starting and stopping of services on the Recognition

Server and the Recognition Nodes
On the BCC participants, the following Microsoft Windows Services are running:
Recognition Server
• DOKuStar HotSpot
• DOKuStar Load Manager
• Invoice Capture Center SLD Data Supplier
Recognition Node
• DOKuStar Load Manager

• DOKuStar Tracing
Validation Client
These services are started automatically after installation and at every system start.
In case of failures you may need to stop, start, or restart a service. To start or stop a
BCC service, use the Services dialog box in Control Panel.
Tip: If after system reboot a service does not automatically start although its
Startup Type is set to Automatic, set the Startup Type to Automatic (Delayed
Start).
4.12.3 Starting and stopping of Customizing Client and

Validation Client
To start the Customizing Client and the Validation Client:
• Selecting the appropriate items in the BCC program group or double-clicking

the respective shortcut on the Microsoft Windows desktop.
The Customizing Client and the Validation Client are normal Microsoft
Windows programs.
To exit the Customizing Client and the Validation Client:
• Open the application menu, and then click Exit.

4.13. Configuring Lookup Lists
To configure the Validation Client to open an application automatically during

startup:
1. Create a copy of the BCC Validation icon on the Microsoft Windows desktop.
2. Right-click Properties, and then in the Target box, add the parameter /
app:<application name>.
4.13 Configuring Lookup Lists

If the SnapMatch automation method is used for some fields and the corresponding
LookUpList database changes frequently, you can configure an automatic reload of
the database file instead of updating it manually with the Customizing Client.
To reload a database file, start the LookupDatabaseUpdater.exe program, which

you can find in the BCC installation folder: LookupDatabaseUpdater
<ApplicationName> <TableName>
ApplicationName
Name of the application containing the table to be updated.
TableName
For an invoice application, name of the lookup list table as shown in the Manage
Lookup List dialog box of the Customizing Client. For applications of other
types, name of the LookupList field.
The program uses the file that has been specified during configuration of the field.
Therefore, replace this file with an updated version before the program is started.
OpenText recommends placing the database file in a folder that exists on both,
development system and production system. For example, use a subfolder of the
DOKuStarDispatchData share. Typically, the program is started at most once a day
after the database file has been replaced with an updated version.
Note: The Lookup List database table update is not incremental. The contents
of the table is replaced completely by the items loaded from the database file.
4.14 Troubleshooting
The documents to be processed by the Recognition Server or to be validated by a
Validation Client are managed by BC Inbound Configuration, or the ICC Dispatcher
in SAP ERP or SAP S/4HANA. The Recognition Server asks these components for
recognition jobs and delivers recognition results to them. The Validation Client asks
these components for validation jobs and delivers the correction results to them. The
components manage a list of all documents and their current states. This list can be
monitored with BC/VIM tools in SAP ERP or SAP S/4HANA.
If the Recognition Server fails when processing a document image, the

corresponding entry in VIM/BC gets the status 87 = Error in extraction. If the
Validation Client fails while a document is being corrected, the corresponding entry
in BC/VIMgets the status 89 = Error in validation.

The application log of a job with error status shows the more specific BCC error
code. The following table gives an overview of the error codes and the appropriate
actions to solve the problem.
Error scenario BCC SAP ERP or SAP Administrator action

error S/4HANAerror
code message
87 Recognition Errors
Recognition service broken 001 Recognition service Check Recognition Server,
broken restart Recognition Services,
retry.
Empty image 002 Empty image Check image, delete job, and
rescan document.
Unknown image format 003 Unknown image Check image, delete job, and
format (Extraction) rescan document.
License error 004 License error Check license file, install
(Extraction) license file, order new license
file, retry.
Archive not accessible 005 Archive not Check archive connection,
(Recognition gets no image accessible set job back to retry.
data) (Extraction)
Other 006 Other error Check error details for more
(Extraction) information.
89 Validation Errors
Unknown image format 003 Unknown image Delete document.
format (Validation)
Archive not accessible 005 Archive not Cancel and retry to get
(Validation gets no image accessible document data.
and result files) (Validation)
Other 006 Other error Check error details for more
(Validation) information.
4.15 Port usage

The following table lists supported ports:
Port # Protocol Component Computer

135 TCP+UDP SQL Server (BCC instance) Server

4.15. Port usage
Port # Protocol Component Computer

3300+SID TCP Validation Client (depending Validation Client
on SAP ERP or SAP S/4HANA
configuration)
configuration)
configuration)
20304 TCP Tracing Server,
Recognition Nodes
23000 TCP Load Manager Service Server + Recognition
Nodes
23062 TCP Hot Spot Service DOKuStar Hot Server
Spot 3.0
Instance- TCP SQL Server (BCC instance) Server
specific
Dynamic port TCP DOKuStarClusterNode.exe, Server + Recognition
used only locally Nodes
To determine the instance-specific port number used by the SQL Server:
1. Start the SQL Server Configuration Manager.
2. Under SQL Server Network Configuration, click Protocols for <instance>,

right-click TCP/IP, and then right-click Properties,
3. In the TCP/IP Properties dialog box, click the IP Addresses tab.
4. By default, a dynamic port number is used. Switch to static port number as

described in the Online Help of the Configuration Manager, and then use the
specified static port number for configuration of the firewall.
Important
Take care not to mix IPv4 and IPv6 in your network configuration for localhost
and the ports used by BCC because this may cause connection errors.

4.16 Deleting an application

To delete an application:
1. To delete the current application, first close the application.
2. Click the application button in the top left corner of the Customizing Client
window, point to Delete Application, and click the respective application on
the submenu.
Important
The application is deleted locally on the Recognition Server. It is not deleted in
SAP ERP or SAP S/4HANA. For information about deleting an application in
SAP ERP, see OpenText Business Center for SAP Solutions - Administration and
Security Guide (BOCP-AGD).

Chapter 5
Configuring security
5.1 User management and authorization concept

BCC has no own user management. It uses both Microsoft Windows user
management and SAP ERP or SAP S/4HANA user management. It is not possible to
define or change Microsoft Windows users or SAP ERP or SAP S/4HANA users
within BCC. Provide the required user accounts using the respective Microsoft
Windows and SAP ERP or SAP S/4HANA tools.
5.1.1 Microsoft Windows users

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) or 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).
Validation Client user

To start the Validation Client, the validation user has to be logged in to Microsoft
Windows. The Microsoft Windows user account of the validation user does not need
any special rights or restrictions. As soon as the validation user starts the Validation
Client, the user has to sign in to SAP ERP or SAP S/4HANA using a prepared SAP
ERP or SAP S/4HANA user. For more information, see “ERP users” on page 90.
Without signing in to SAP, the validation user cannot work at all.
Recognition Server/Recognition Node user

The Load Manager services on the Recognition Server and on the Recognition Nodes
run using a domain user account.
This account has to be prepared before installation and must be entered during
installation. The Load Manager Service user must have local administrator rights.
Customizing Client user

To be able to start the Customizing Client, the Customizing Client user has to be
logged in to Microsoft Windows. The Customizing Client user can either use the
Load Manager Service user or another user. This other user has to be a local
administrator.

Chapter 5 Configuring security
After starting the Customizing Client, the user can work locally. For communication
with SAP ERP or SAP S/4HANA the user must log in to SAP using a prepared SAP
ERP or SAP S/4HANA user. For more information, see “ERP users” on page 90.
5.1.2 ERP users

5.1.2.1 Common authorizations
The following authorizations are needed for all types of users:
• 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=SDIFRUNTIME
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SYSU
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SYST
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SRFC
• S_RZL_ADM:ACTVT=03
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.
The following authorizations can be replaced:
• 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=SRFC
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_PING
• 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=FUNC,RFC_NAME=RFC_GET_FUNCTION_INTERFACE
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SDIFRUNTIME
replace with
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=DDIF_FIELDINFO_GET
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.

5.1. User management and authorization concept
5.1.2.2 Authorizations for validation user and extraction user

As soon as the validation user or extraction user has started the Validation Client,
the user has to log in to SAP ERP or SAP S/4HANA using a prepared SAP user. This
user needs the following authorizations:
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OTX/PF01_IF_OCR
• For BC Inbound Framework version 16.3.1 and later, full authorization for the J_
6NPF_RFC object is required for all users. For more information, see section 8.4
“Authorization objects” in OpenText Vendor Invoice Management for SAP Solutions
- Configuration Guide for Foundation (BOCP-CGD).
In SAP ERP or SAP S/4HANA versions newer than release 7.10 (EHP 4 and later),
you can choose a finer granularity for your authorizations. For more information,
see SAP Note 460089. Instead of the authorizations for RFC function groups, you can
use authorizations for each single function module.
You can replace the S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OTX/PF01_IF_

OCR authorization with the following:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_REJ_REASON
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_ALL_WITH_CNT
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_VAL_DOC_LIST
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_VAL_DOC_CNT
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_APPL_CONFIG
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_OCR_DATA_UPDATE_N
In this way, the Validation Client user does not have the right to store applications
or to download master data.
5.1.2.3 Working with Single Sign-On

You can use Single Sign-On for the Validation Client.
Single Sign-On cannot be used if several SAP ERP or SAP S/4HANA users are
associated with an SNC name. In this case, the error message “Login failed: System
found several suitable SAP users for the SNC name of the caller” will occur.
However, it is still possible to use several clients for an SNC name.
To be able to work with Single Sign-On:
• Specify a value in the Client box of the SAP Login dialog box.

5.1.2.4 Authorizations for Recognition Server/Recognition Node users

The Recognition Server communicates with the SAP ERP or SAP S/4HANA system
to ask for recognition jobs, for download data, and for learning data. Both the
Recognition Server and the Recognition Nodes export results to SAP ERP or SAP S/
4HANA. The Recognition Server and the Recognition Node use a prepared SAP ERP
user. This SAP ERP or SAP S/4HANA user has to be defined in the technical
configuration of SAP Extraction Link Hot Spots and SAP Download Link Hot Spots
on the Recognition Server.
The user needs the following authorizations:
• S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC_DL

S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_NEW_DOC_LIST
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME= /OTX/PF01_IF_GET_URL_FOR_IMG
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME= /OTX/PF01_IF_GET_URL_FOR_XML
In this way, the extraction client user does not have the right to store applications.
5.1.2.5 Authorizations for Customizing Client users

When the Customizing Client user wants to import an application configuration
from SAP ERP or SAP S/4HANA or wants to export an application configuration to
SAP ERP or SAP S/4HANA, the user has to log in to SAP ERP or SAP S/4HANA
using a prepared SAP ERP or SAP S/4HANA user. This user needs the following
authorizations.

S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_ALL_WITH_CNT
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_APPL_CONFIG
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_STORE_APPL_OBJECT
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_STORE_CONFIG_BLOB
In this way, the customizing client user only has the rights to import and export
applications.

5.1. User management and authorization concept
5.1.2.6 Training module SAP ERP or SAP S/4HANA user

If you want to perform document training within the customizing client, you need
the following authorizations.
For BCC/BC:

S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=/OTX/PF01_IF_GET_TR_DATA_N
In this way, the training client has no other authorizations than receiving training
data.
If you want to store images as training module SAP ERP or SAP S/4HANA user, you
need two additional authorizations.
• S_TCODE:TCD=OAWD
• S_WFAR_OBJ:OAARCHIV=*,OAOBJEKTE=/OTX/PF01R,OADOKUMENT=*,ACTVT01
5.1.2.7 Feedback module SAP ERP or SAP S/4HANA user

The feedback module communicates with the SAP ERP or SAP S/4HANA system to
ask for feedback data to improve recognition capabilities. The feedback module uses
a prepared SAP ERP or SAP S/4HANA user. This SAP ERP or SAP S/4HANA user
has to be defined in the technical configuration of the SAP Feedback Link Hot Spot.
The user needs the following authorizations:

S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME= /OTX/PF01_IF_GET_FB_LIST
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME= /OTX/PF01_IF_GET_FB_DATA
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME= /OTX/PF01_IF_ACK_FB_DOC
In this way, the Feedback Link Hot Spot user can only work with the feedback-
related functions.
This SAP ERP or SAP S/4HANA user has to be defined in the technical configuration
of the SAP Feedback Link Hot Spot.

5.1.2.8 Configuring SAP Feedback Link

To change the SAP Feedback Link configuration:
1. Start the Customizing Tool on the Recognition Server.
2. On the General tab, in the Tools group, click Cluster Setup.
3. In the Load Manager Configuration dialog box, select a runtime mode, and
then click the Exclusive Operation Types property.
Tip: The Exclusive Operation Types restrict a cluster node to the specified
Load Manager operation types.
4. Select Sitemap_BobFeedbackTransformer, add it to the Selected Operation

Types list, and then click OK.
The feedback learning is done on this runtime node exclusively.
Tip: The sitemap is located in <installation medium>\templatesRDA\

Feedback\BobFeedbackTransformer.sitemap.
5. Attach all other operation types to all other remaining runtime nodes.
Example: In the example, all operation types Sitemap_JobClass<number>_<name> must

be attached for exclusive use to all other runtime nodes except the one runtime node
which has operation type Sitemap_BobFeedbackTransformer already assigned.

5.2. Delivered users
5.2 Delivered users

BCC does not deliver any users.
5.3 Emergency user concept

BCC uses Microsoft Windows user management. A Customizing Client user is a
Microsoft Windows administrator with administrator rights on all systems involved
(including databases). All customizing tasks of BCC can be done with certain
Microsoft Windows and database rights.
Therefore, an emergency user concept is not applicable. If a user is locked or

disabled, a different Microsoft Windows user, provided with the needed rights, can
carry out the BCC customizing task.
5.4 Logging of security-relevant events

Because BCC uses the Microsoft Windows user management, the Microsoft
Windows features can be used 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).
The security events occurring with respect to the databases also can be logged to the
Microsoft Windows event log. You must change the settings of the SQL Server
instance.
Security-relevant events on the SAP ERP or SAP S/4HANA side can be logged using
SAP ERP or SAP S/4HANA means.
5.5 Logging of application configuration data

changes
The application configuration is developed locally on a PC using the Customizing
Client and is then exported to the SAP ERP or SAP S/4HANA system. Each time the
configuration changes have been finished, the Customizing Client user uploads the
configuration from the development PC to the SAP ERP or SAP S/4HANA
development system, test system, or production system. Then the new configuration
has to be downloaded from SAP ERP or SAP S/4HANA to the test or production
Recognition Server.
Thus you can log the application configuration changes on the SAP ERP or SAP S/
4HANA side using SAP ERP or SAP S/4HANA means or you can log the application
configuration changes on the production Recognition Server side using Microsoft
Windows means.

On the Recognition Server, the application configuration can be found in the folder
%ALLUSERSPROFILE%\Application Data\Open Text\DOKuStar Dispatch\data\
config\RdaProject. Changes to this folder can be logged to the Microsoft
Windows event log.
To log changes:
1. Enable object access auditing by defining auditing policy settings for the object
access event category on the server. For more information, see “Define or
modify auditing policy settings for an event category” (http://
technet.microsoft.com/en-us/library/cc787268.aspx).
2. Apply appropriate auditing policy settings for the RdaProject folder. For more
information, see “Apply or Modify Auditing Policy Settings for a Local File or
Folder” (http://technet.microsoft.com/en-us/library/cc771070.aspx).
5.6 Encryption of communication channels

5.6.1 Files and databases
By default, all network communication in a Microsoft Windows network is
protected by the standard Microsoft Windows security protocol IPSec. IPSec
supports network-level peer authentication, data origin authentication, data
integrity, encryption, and replay protection. For more information, see “IPSec”
(http://technet.microsoft.com/en-us/network/bb531150.aspx).
That is all network communication to file systems and databases in BCC is protected
by IPSec.
5.6.2 SAP ERP or SAP S/4HANA

All participants of a BCC system communicate with the BC Inbound Configuration
or the ICC Dispatcher in SAP ERP or SAP S/4HANA by making RFC calls using the
SAP .NET connector. You can use Secure Network Communication (SNC) to secure
RFC connections. For more information, see “Encryption for RFC” (http://
help.sap.com/saphelp_nw04s/helpdata/en/59/20e19303b3f5448bef6bf502d44c7d/
content.htm). SAP archives are accessed using HTTP or HTTPS, depending on the
configuration of the archive.

5.7. Secure configuration
5.7 Secure configuration

BCC provides a secure configuration by default:
• The application configuration is stored in SAP ERP or SAP S/4HANA.

• The application configuration can be downloaded to a Recognition Server using
the Customizing Client. The Customizing Client user has to log in to SAP ERP or
SAP S/4HANA with a prepared SAP ERP or SAP S/4HANA user to download
the application configuration.
• The application configuration can be exported from a Recognition Server to SAP
ERP or SAP S/4HANA using the Customizing Client. The Customizing Client
user has to log in to SAP ERP or SAP S/4HANA with a prepared SAP ERP or
SAP S/4HANA user to upload the application configuration.
• After the Validation Client user has logged in to SAP ERP or SAP S/4HANA, the
application configuration is automatically downloaded to the Validation Client.
• The Validation Client user has to log in to SAP ERP or SAP S/4HANA to get
documents to validate. Without logging in to SAP ERP or SAP S/4HANA, the
Validation Client user cannot work at all.
• SAP ERP or SAP S/4HANA user management controls which documents a
Validation Client user has to validate.
• The Customizing Client user has to log in to SAP ERP or SAP S/4HANA to get
documents to validate for testing purposes. Without logging in to SAP ERP or
SAP S/4HANA, the Customizing Client user does not get documents to validate.
• The databases on the Recognition Server are private databases of the Recognition
Cluster.
• The Validation Client user has no access to these databases.
• By default, only the Recognition Server Microsoft Windows user and all local
administrators have access to the databases. Instead of using the administrators
group, access to the databases can be restricted to users belonging to a user-
defined Microsoft Windows group, for example “BCC users”.
• The heart of a BCC system, BC Inbound Configuration/ICC Dispatcher, is an SAP
ERP or SAP S/4HANA component.
• The recognition jobs are managed by BC Inbound Configuration/ICC Dispatcher
in SAP ERP or SAP S/4HANA.

5.8 Responsibilities
In a BCC system, there are two types of real users: the Customizing Client user and
the Validation Client user.
The Customizing Client user has the following responsibilities:
• Creating, testing, modifying application configurations

• Uploading finished configurations to SAP
• Downloading configurations from SAP to test or production Recognition Servers
• Setting technical configuration parameters
• Training of fields
The user working at a Validation Client has the following responsibilities:
• Validating and completing recognition results
On the SAP side of a BCC system, there are additional user types and
responsibilities.

Glossary of Terms
ACT
Abbreviation of Adaptive Classification Technology.
See also: Adaptive Classification (ACT)
Adaptive Recognition (ART)

The Recognition Server and the Recognition Nodes must learn how to extract
data for an Adaptive Recognition field. They need a sample for each kind of
invoice, for example an invoice of each vendor, and the position where the field
can be extracted on this kind of invoice. These samples (= templates) and the
according position information must be provided by training. During training,
the field is captured manually using the mouse. The layout of the document and
the positions of the respective field are then stored in a learning database. If a
similar document is processed later on, Adaptive Recognition finds a matching
sample in the learning database, and extracts the field at the learned position.
Adaptive Classification (ACT)

An adaptive classification field does some sort of classification of a document.
Normally the field value is one of a set of terms. The term itself is not contained in
the text of the document but can be determined by examining the entire contents
of the document. When configuring an adaptive classification field you enter the
set of valid terms for the field. At runtime the adaptive classification field is
presented to the user with a combo box containing the list of terms. The
Recognition Server and the Recognition Nodes must learn how to select the
correct term for an adaptive classification field from the set of terms. They need a
sample for each kind of invoice and the correct term for each sample. These
samples and the according term must be provided by training. During training,
the term is selected manually by the user. The document and the term are then
stored in a learning database. If a similar document is processed later on,
adaptive classification finds a matching sample in the learning database, and uses
the learned term.
Application
An application bundles all settings that are needed to process documents of a
certain kind, for example which fields must be extracted by which extraction
method, or which fields should be visible in the Validation Client.
ART
Abbreviation of Adaptive Recognition Technology.
See also: Adaptive Recognition (ART)
BC
See: Business Center (BC)

Glossary of Terms
BCC
Abbreviation of Business Center Capture.
Business Center (BC)

OpenText Business Center for SAP Solutions is a platform that accelerates
processing of documents and approval workflow in SAP ERP or SAP S/4HANA
in many business processes.
Cluster Node
A Cluster Node is a component of a Recognition Cluster performing job
processing. The Recognition Cluster contains one Cluster Node for each processor
of the Recognition Cluster. The Load Manager performs load balancing and
distributes recognition jobs among all Cluster Nodes of the Recognition Cluster. If
there is only a Recognition Server and no Recognition Nodes, there will be as
many Cluster Nodes as processors in the Recognition Server machine. If the
Recognition Cluster consists of a Recognition Server and several Recognition
Nodes, there will be as many Cluster Nodes as processors in the Recognition
Server machine and in all Recognition Node machines.
Cluster
See Recognition Cluster.
Content-Based Classification
See Adaptive Classification.
Customizing Client
The Customizing Client is a Microsoft Windows program that is used on the
development system to customize BCC, that is, to create and configure
applications. It is also used to test applications, to export them to an SAP ERP or
SAP S/4HANA system, and to import them on a test or production System. In
addition, it is used to monitor and administer a BCC system.
Customizing
BCC provides various settings to adapt the system to customer needs. These
customizing settings are bundled in applications. To customize BCC for customer
needs, you must create applications.
Document Reader
In a BCC system the actual data extraction from document images and
superordinate tasks, like splitting of pages or export of results, are performed by a
component named Document Reader.
Download Link Hot Spot

For each invoice application, a separate SAP Download Link Hot Spot is created.
This link is used to fetch download data such as vendor master data or purchase
order data from SAP ERP or SAP S/4HANA regularly according to the
configuration of the Hot Spot. During customizing you specify whether vendor

Glossary of Terms
master table, purchase order data, or also purchase order item data should be
downloaded.
Extraction Link Hot Spot

For each application, a separate SAP Extraction Link Hot Spot is created. This link
is used to fetch recognition jobs from SAP ERP or SAP S/4HANA regularly
according to the configuration of the Hot Spot.
Feedback Link Hot Spot

For non-invoice applications, a single SAP Feedback Link Hot Spot is created
when the first non-invoice application is created or imported. This link is used to
fetch feedback data from SAP ERP or SAP S/4HANA regularly according to the
configuration of the Hot Spot. Feedback data are collected at the Validation
Clients or on the SAP ERP or SAP S/4HANA system and are used to extract fields
automatically. For additional non-invoice applications, the respective archive
document types must be added manually to the Feedback Link configuration. If
such applications use further SAP ERP or SAP S/4HANA systems, additional SAP
Feedback Link Hot Spots must be created and configured manually.
Hot Spot
The Recognition Server uses Hot Spots to fetch recognition jobs, download data,
and learning data from its SAP ERP or SAP S/4HANA system. A Hot Spot
becomes active regularly after expiring of a specified interval or at a specified
time on specified days and then tries to fetch new data. SAP Extraction Links are
used to fetch new recognition jobs from SAP ERP or SAP S/4HANA. SAP
Download Links are used to fetch new data for invoice applications, such as
vendor master data and purchase order data. An SAP Feedback Link is used to
download feedback data for some extraction methods used by non-invoice
applications.
ICC
Abbreviation of Invoice Capture Center.
Invoice Application
See: Application
Learning
While special, optimized methods are used to extract the standard fields, for
adaptive recognition fields and adaptive classification fields BCC has to learn
how to fill the field values. The learning data must be provided by training. The
Recognition Server keeps the learning data in its local database.
Link
Links are used to download recognition jobs, download data, and feedback data
from SAP ERP or SAP S/4HANA. Links are implemented as so-called Hot Spots.
The Hot Spots used for the Links connect to SAP ERP or SAP S/4HANA regularly
at specified times and fetch available jobs or data.

Glossary of Terms
Load Manager
BCC uses load balancing in order to distribute recognition jobs on several
processors of the Recognition Server and on additional Recognition Nodes. Load
balancing is performed by the Load Manager. During configuration of the BCC
system, you configure the Load Manager on the Recognition Server and create
computer nodes for all additional Recognition Nodes and Runtime Nodes for all
processors on each Recognition Node.
Master
On a Recognition Cluster, the Load Manager performs load balancing over all
processors of the server and the Recognition Nodes. The Load Manager on the
server acts as Master. It transfers recognition jobs that are fetched from SAP ERP
or SAP S/4HANA regularly to free Cluster Nodes for processing.
Purchase Order Data

For an invoice application, BCC is able to check the purchase order number and
the invoice line items against downloaded data. To use this feature, download of
a purchase order table, and optionally additional purchase order item data must
be enabled in the configuration of the SAP Download Link Hot Spot. In the
application settings you can then specify that PO numbers should be checked, or
that line items should be checked against downloaded purchase order item data.
Recipient Data
For an invoice application, BCC can derive the company code and target SAP ERP
or SAP S/4HANA system automatically using recipient address data found on the
invoice. During application configuration, a database containing recipient data
together with the corresponding company codes and SAP ERP or SAP S/4HANA
system names has to be supplied if automatic company code detection shall be
used.
Recognition Cluster
The Recognition Cluster is used for automatic data extraction. On smaller systems
with low throughput it consists of the Recognition Server - typically a computer
with several processors - that also hosts the Customizing Client. On large systems
with high throughput, further Recognition Nodes can be added. The Load
Manager performs load balancing and distributes recognition jobs among all
processors of the server and the Recognition Nodes.
Recognition Job
Scanned documents are first stored in an archive (early archiving). Then a
workflow is started that creates entries for the documents in the BC Inbound
Configuration / ICC Dispatcher Infrastructure. The Recognition Server fetches
available entries from VIM/BC regularly, creates Recognition jobs, and transfers
them to the input queue of the Load Manager. The Load Manager assigns the first
waiting recognition job to the next Cluster Node that becomes available. The
Cluster Node fetches the document from the archive, processes it, and transfers
the result data to SAP ERP or SAP S/4HANA. The document is then made
available for Validation.

Glossary of Terms
Recognition Node
For huge systems the Recognition Server can be supported by additional
machines, installed as Recognition Nodes. The Load Manager on the Recognition
Server fetches jobs from SAP ERP or SAP S/4HANA using an SAP Extraction Link
and distributes the jobs among all processors of the server and the different
Recognition Nodes. By adding Recognition Nodes, the processing power of the
whole Recognition Cluster can be adapted to the required throughput.
Recognition Server
Document processing is performed on a Recognition Cluster consisting of a
Recognition Server and possibly additional Recognition Nodes. The Recognition
Server comprises the Customizing Client that is used to customize, configure, and
monitor the BCC system. It also comprises the databases containing vendor
master data, purchase order data, feedback data, and learning data. It also hosts
the Hot Spots that are used to fetch jobs, download data, and feedback data from
the SAP ERP or SAP S/4HANA system regularly. The Load Manager of the
Recognition Server is the master of the recognition cluster. It contains the cluster
configuration and distributes recognition jobs on the processors of the server and
additional Recognition Nodes.
Recognition
Recognition comprises the extraction of essential data, such as date, amount,
order number etc., from the scanned documents and the intelligent verification of
these data. Recognition is performed by the Recognition Cluster.
Requester Email Data

In an invoice application, BCC tries to extract the requester email address on
invoices. To be able to use this feature, the expected email addresses must be
entered during configuration of an application.
Slave
On a Recognition Cluster, the Load Manager performs load balancing over all
processors of the server and the Recognition Nodes. The Load Manager acts as a
Slave on each Recognition Node. When a Runtime Node terminates a job, it waits
until the Load Manager on the server that acts as Master supplies it with a new
job.
Standalone System
For development and testing of applications, all components of BCC can be
installed on a standalone system, that is, on a single computer.
Training
To be able to extract adaptive recognition fields or adaptive classification fields
automatically, some training has to be performed first. Training can be performed
manually by the user on the Customizing Client.

Glossary of Terms
Validation Client
The Validation Client is a Microsoft Windows program that is used by a clerk to
check and correct data that have been extracted automatically and to capture
additional fields that could not be read automatically. The corrected and
completed data are then passed on to SAP ERP or SAP S/4HANA.
Validation
The extracted invoice data can be checked and eventually corrected or completed
by a user. The validation facilities of BCC are provided by the Validation Client
program and also by the Customizing Client program. Validation on the
Customizing Client is only performed for developing and testing purposes.
Vendor Invoice Management

Vendor Invoice Management is a complete application for optimizing vendor
invoice processes in SAP ERP or SAP S/4HANA applications, along with built-in
reporting and analytics to continuously improve processes.
Vendor Master Data

For an invoice application, BCC periodically loads vendor master data from SAP
ERP or SAP S/4HANA to its local database using an SAP Download Link Hot
Spot. BCC compares the vendor information that has been extracted from an
invoice image with vendor master data downloaded from SAP to identify the
vendor id.
VIM
Abbreviation of Vendor Invoice Management.

OpenText Business Center Capture For SAP Solutions 16.7.4 - Administration Guide English (CPBC160704-AGD-En-03)

Uploaded by

Copyright:

Available Formats

You might also like

OpenText Business Center Capture For SAP Solutions 16.7.4 - Administration Guide English (CPBC160704-AGD-En-03)

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 Business Center Capture For SAP Solutions 16.7.4 - Administration Guide English (CPBC160704-AGD-En-03)

Uploaded by

Copyright:

Available Formats

OpenText™ Business Center Capture for

This guide describes how to install, configure, and administer

Open Text Corporation

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

Copyright © 2022 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

CPBC160704-AGD-EN-03 Administration Guide iii

3 Monitoring BCC ....................................................................... 39

4 Technical operations ............................................................... 43

iv OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

4.6.3 Tracers ........................................................................................... 52

CPBC160704-AGD-EN-03 Administration Guide v

4.10.2.1 Configuring cluster nodes ................................................................ 74

5 Configuring security ............................................................... 89

vi OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

5.6.2 SAP ERP or SAP S/4HANA ............................................................. 96

GLS Glossary of Terms 99

CPBC160704-AGD-EN-03 Administration Guide vii

1.1 About the document

1.2 Functional overview

For electronic processing, documents are scanned on entry to the financial

CPBC160704-AGD-EN-03 Administration Guide 9

The extracted information is passed on to VIM.

10 OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

1.3 BCC runtime scenarios

By default, VIM routes invoice applications automatically if it is also present on the

1.4 Components of BCC

• Inbound Configuration or ICC Dispatcher

The heart of a BCC system is the Inbound Configuration or ICC Dispatcher, a

Data extraction is performed on a special server computer, normally a multi-

CPBC160704-AGD-EN-03 Administration Guide 11

Recognition Server can be supported by additional recognition computers, called

12 OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

The applications are usually created in a development environment on a special

CPBC160704-AGD-EN-03 Administration Guide 13

1.6 Hot Spots

You configure the Hot Spots with the Customizing Client.

14 OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

1.7 Achieving optimum recognition results

Optimizing scan results

• Use professional scanning equipment to achieve optimum image quality.

Reduce possible errors or performance problems by using suitable operating

• Use separator sheets or barcode for attachment separation. Automatic separation

• At an Invoice application, use parameters to limit runtime such as stopping

• For invoice applications, achieve good quality of master data. If downloaded

CPBC160704-AGD-EN-03 Administration Guide 15

1.8 Supported image formats

The incoming image-based files can have the following sizes:

• Maximum image format: DIN A0

Paper format Color image Gray image Binary image

16 OpenText™ Business Center Capture for SAP® Solutions CPBC160704-AGD-EN-03

Paper format Color image Gray image Binary image

During image processing, an uncompressed image is always created temporarily

These limits also apply to pages extracted from PDF files.

1.8.1 Processing PDF files

1.8.2 Processing TIFF files

A frequent problem is caused by FAX compression and the

CPBC160704-AGD-EN-03 Administration Guide 17