Opentext™ Invoice Capture Center For Sap Solutions Opentext™ Business Center Capture For Sap Solutions

OpenText™ Invoice Capture Center for
SAP® Solutions
OpenText™ Business Center Capture for
SAP® Solutions
Administrator's Guide
®
OpenText™ Invoice Capture Center for SAP Solutions
®
OpenText™ Business Center Capture for SAP Solutions
Administrator's Guide
Rev.: V7.5 SP4 / 16 (2016-03-16)
Open Text SA
40 Avenue Monterey, Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
Open Text Corporation
275 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: http://support.opentext.com
For more information, visit: http://www.opentext.com
Copyright  2016 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not exhaustive of
other trademarks, registered trademarks, product names, company names, brands and service names mentioned herein are property of
Open Text SA and/or Open Text ULC or other respective owners.
RecoStar is a registered trademark of Open Text Document Technologies GmbH
ACKNOWLEDGEMENTS
Portions copyright  2003-2015 AllMyPapers.
Portions copyright  2015 Artifex Software Inc.
This software is based in part on the work of the Independent JPEG group.
Portions copyright  2001 URW++. All rights reserved.
Portions copyright  2015 Bejing Wintone Science & Technology Corporation Ltd.
Portions copyright  2015 Tulpep.
Portions copyright  2015 Newtonsoft
Portions ([incr Tcl]) copyright  The Regents of the University of California
Portions ([incr Tcl]) copyright  Sun Microsystems, Inc.
Portions ([incr Tcl]) copyright  Lucent Technologies, Inc.
This work uses Boost C++ libraries.
SAP®, R/3® and SAP CRM® are registered trademarks of SAP AG.
Microsoft®, Microsoft SQL®, and Microsoft SharePoint® are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries.
Artifex®, the Artifex logo, Ghostscript®, and the Ghostscript logo are registered trademarks of Artifex Software Inc.
PostScript® is a trademark of Adobe Systems Incorporated.
PCL® is a trademark of Hewlett Packard Company.
All other products or company names are used for identification purposes only, and are trademarks of their respective owners.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text
Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the accuracy of this
publication.
Contents
1 Introduction 1
1.1 About the document .................................................................................................... 1
1.2 Functional overview .................................................................................................... 1
1.3 ICC/BCC runtime scenarios ........................................................................................ 3
1.4 Components of ICC/BCC ............................................................................................ 3
1.5 Customizing................................................................................................................. 4
1.6 Hot Spots ..................................................................................................................... 5
1.7 Achieving optimum recognition results....................................................................... 6
2 Installation 7
2.1 Planning the installation .............................................................................................. 7
2.1.1 System requirements ....................................................................................... 7
2.1.2 Image formats ................................................................................................. 9
2.1.3 Configurations ................................................................................................. 9
2.2 Preparing installation ................................................................................................. 13
2.2.1 Creating a domain user for Windows services .............................................. 13
2.2.2 Installing Microsoft .NET Framework .......................................................... 13
2.2.3 Installing SAP Connector for Microsoft .NET .............................................. 13
2.2.4 Installing Microsoft Visual C++ Redistributables ......................................... 13
2.2.5 User permissions ........................................................................................... 14
2.2.6 Installing the Microsoft SQL Server ............................................................. 14
2.3 Installing ICC/BCC ................................................................................................... 15
2.3.1 Stand-alone installation ................................................................................. 15
2.3.2 Installation of the server ................................................................................ 15
2.3.3 Installing a Validation Client ........................................................................ 16
2.3.4 Installation of a Recognition Node ................................................................ 17
2.3.5 Installing add-ons for Business Capture Center ............................................ 17
2.3.6 Creating installation log files ........................................................................ 17
2.4 Follow-up activities ................................................................................................... 18
2.4.1 Configuring Vendor Invoice Management (ICC) ......................................... 18
2.4.2 Configuring Business Center (BC)................................................................ 18
2.4.3 Configuring the archive server ...................................................................... 18
2.4.4 Preparing SAP ERP user accounts ................................................................ 18
2.4.5 Preparing SAP ERP login data ...................................................................... 18
2.4.6 Creating and configuring applications .......................................................... 18
2.4.7 Configuring the cluster .................................................................................. 19
2.4.8 Configuring the Windows Firewall for Validation Clients ........................... 19
2.4.9 Configuring SAP GUI ................................................................................... 19
2.4.10 Configuring the SLD Data Supplier (ICC) .................................................. 20
2.4.11 Upgrading existing applications .................................................................. 21
2.5 Optional follow-up activities ..................................................................................... 21
2.5.1 Moving the caches to a different location ..................................................... 21
2.5.2 Moving all ICC/BCC data to a different drive .............................................. 22
2.6 Installing updates ....................................................................................................... 22
2.6.1 Installing patches and service packs .............................................................. 22
2.6.2 Installing the Imaging Plug-in ....................................................................... 23
ICC/BCC Administrator's Guide Contents  iii

2.7 Upgrading ICC/BCC ................................................................................................. 23
2.7.1 Upgrading ICC/BCC ..................................................................................... 23
2.7.2 Upgrading to a newer version ....................................................................... 23
3 Installing Single Click Entry for SAPGUI (ICC) 25
4 Monitoring ICC/BCC 27
4.1 Monitoring ICC/BCC with external monitoring tools ............................................... 27
4.1.1 Monitoring ICC/BCC with Wily Introscope ................................................. 27
4.2 Monitoring ICC/BCC using the SAP Solution Manager ........................................... 28
4.2.1 Providing technical configuration information ............................................. 28
5 Technical operations 29
5.1 Overview of the Customizing Client ......................................................................... 29
5.2 Overview of components ........................................................................................... 30
5.2.1 Document processing in BC/VIM on the SAP ERP system ......................... 30
5.2.2 ICC/BCC Windows components................................................................... 30
5.2.3 Further involved components ........................................................................ 31
5.3 Overview of technical runtime scenarios .................................................................. 32
5.3.1 Recognition and validation of a document .................................................... 32
5.3.2 Downloading data from SAP ERP ................................................................ 32
5.3.3 Supervised learning on the Customizing Client ............................................ 33
5.4 Monitoring using the Customizing Client ................................................................. 33
5.4.1 Monitoring Hot Spots .................................................................................... 33
5.4.2 Monitoring jobs ............................................................................................. 34
5.4.3 Monitoring the Recognition Cluster .............................................................. 35
5.5 Logging and tracing ................................................................................................... 37
5.5.1 Logging ......................................................................................................... 37
5.5.2 Overview of tracing....................................................................................... 37
5.5.3 Tracers........................................................................................................... 37
5.5.4 Trace listeners ............................................................................................... 37
5.5.5 Trace root path .............................................................................................. 38
5.5.6 Trace levels ................................................................................................... 38
5.5.7 Trace configuration ....................................................................................... 38
5.5.8 Location of trace files and trace configuration files ...................................... 41
5.5.9 Format of traces............................................................................................. 41
5.5.10 Analyzing trace files ................................................................................... 42
5.5.11 Trace Viewer ............................................................................................... 42
5.5.12 SAP ERP format tracing ............................................................................. 49
5.6 Configuration data (production system) .................................................................... 50
5.6.1 Technical configuration data ......................................................................... 50
5.6.2 Application configuration data (customizing data) ....................................... 51
5.6.3 Runtime files ................................................................................................. 51
5.6.4 Registry entries.............................................................................................. 51
5.6.5 Databases ...................................................................................................... 51
5.6.6 Services ......................................................................................................... 52
5.6.7 Moving ICC/BCC data to a different location .............................................. 52
5.7 Backup and restore .................................................................................................... 56
iv  Contents ICC/BCC Administrator's Guide

5.8 Periodic activities ...................................................................................................... 57
5.8.1 Deleting trace files ........................................................................................ 57
5.8.2 Restricting the growth of the ICC/BCC database.......................................... 57
5.8.3 Creating backups of learning data ................................................................. 57
5.9 Load balancing .......................................................................................................... 58
5.9.1 Load Manager ............................................................................................... 58
5.9.2 Recognition Cluster setup ............................................................................. 59
5.9.3 Increasing throughput .................................................................................... 63
5.10 High availability ........................................................................................................ 64
5.10.1 Using two Recognition Servers ................................................................... 64
5.10.2 Installing two Recognition Servers in one Recognition Cluster .................. 66
5.11 Starting and stopping ................................................................................................. 67
5.11.1 Starting and stopping of Hot Spots on the Recognition Server ................... 67
5.11.2 Starting and stopping of services on the Recognition Server and the
Recognition Nodes .................................................................................................... 68
5.11.3 Starting and stopping of Customizing Client and Validation Client ........... 68
5.12 Configuring Lookup Lists ......................................................................................... 69
5.12.1 Reloading database files for LookUpList fields automatically ................... 69
5.13 Troubleshooting......................................................................................................... 70
5.14 Port usage .................................................................................................................. 71
5.15 Deleting an application .............................................................................................. 72
5.16 Version information................................................................................................... 72
5.16.1 Customizing Client...................................................................................... 72
5.16.2 Validation Client ......................................................................................... 72
5.16.3 File system .................................................................................................. 72
5.16.4 Registry ....................................................................................................... 72
5.16.5 SLD registration .......................................................................................... 73
6 Security 75
6.1 User management and authorization concept ............................................................ 75
6.1.1 Windows users .............................................................................................. 75
6.1.2 ERP users ...................................................................................................... 76
6.2 Delivered users .......................................................................................................... 80
6.3 Emergency user concept ............................................................................................ 80
6.4 Logging of security-relevant events .......................................................................... 80
6.5 Logging of application configuration data changes ................................................... 81
6.6 Encryption of communication channels .................................................................... 81
6.6.1 Files and databases ........................................................................................ 81
6.6.2 SAP ERP ....................................................................................................... 81
6.7 Secure configuration .................................................................................................. 82
6.8 Responsibilities ......................................................................................................... 82
7 Glossary of Terms 83
8 Index 89
ICC/BCC Administrator's Guide Contents  v

1 Introduction
1.1 About the document
This document describes installation, configuration, and administration of the following products:
 OpenText™ Invoice Capture Center for SAP® Solutions (ICC),
SAP name: OCR Option for SAP Invoice Management
 OpenText™ Business Center Capture for SAP® Solutions (BCC)
OCR component of SAP product: SAP Digital Content Processing
ICC and BCC are strongly related and share great parts of code. In addition, BCC can comprise ICC functionality, if a
special plug-in is installed. Therefore both products share the same documentation.
In this guide, all sections, that are only valid for one of the products, show the respective product acronym, that is, ICC
or BCC, in its heading. All remaining sections are valid for both products.
1.2 Functional overview

As an option for OpenText™ Vendor Invoice Management for SAP ® Solutions (VIM), OpenText™ Invoice Capture
Center for SAP® Solutions (ICC) extends VIM’s capabilities to automate capturing of machine-printed paper invoices.
As a component of OpenText™ Business Center Capture for SAP® Solutions (BCC), the software permits to automate
capturing of other machine-printed invoice-related documents.
For electronic processing documents are scanned on entry to the financial accounting department. The digital images of
the documents are stored in an archive. ICC/BCC Recognition is indirectly triggered by the early archiving mechanism
of SAP ERP.
ICC/BCC Administrator's Guide Introduction  1

ICC/BCC Recognition extracts the essential data (for example date, amount, order number etc. 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 addition, it uses fuzzy database matching: ICC/BCC Recognition maps the read data
– such as names, addresses, vendor numbers, purchase order numbers etc. – to SAP ERP vendor master data and SAP
ERP purchase order data during analysis.
The extracted information is passed on to VIM, or BC, respectively.
Based on business rules, VIM/BC decides whether the automatically extracted data have to be reviewed and possibly
corrected or completed by a clerk. In this case, the document is transferred to a Validation Client, which is a 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/BC.
2  Introduction ICC/BCC Administrator's Guide

1.3 ICC/BCC runtime scenarios
ICC and BCC are strongly related and share great parts of code.
If you install ICC, you can create, configure, import, and process Invoice applications and Custom applications. In this
case Vendor Invoice Management is required on SAP ERP.
If you already use ICC and also want to process BCC Solution Accelerators, you must remove ICC, install BCC, the
plug-ins for the respective Solution Accelerators, and in addition, the BCC Invoice plug-in.
If you install BCC, you can create, configure, import, and process Custom applications. If a BCC system should be
extended for Solution Accelerators, you must install the respective BCC plug-ins. If a BCC system should be extended
for Invoice applications, you must install the BCC Invoices plug-in and Vendor Invoice Management should be available
on SAP ERP.
If Business Center is present on SAP ERP, both, ICC and BCC connect to Business Center. Business Center routes
Invoice applications by default to Vendor Invoice Management automatically, if it is also present on the respective SAP
ERP system.
If ICC is installed, and Business Center is not present on SAP ERP, ICC will automatically connect to Vendor Invoice
Management.
1.4 Components of ICC/BCC

An ICC/BCC system consists of the following components:
 BC Inbound Configuration or ICC Dispatcher
 Recognition Server, Recognition Node
 Customizing Client (user interface)
 Validation Client (user interface)
The heart of an ICC/BCC system is the BC Inbound Configuration or ICC Dispatcher, a component of Business Center
/VIM, the other non-SAP parts of ICC/BCC interact with.
Data extraction is performed on a special server PC, normally a multi-processor machine. This server PC is the
Recognition Server. In huge systems the Recognition Server can be supported by additional recognition PCs, 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:
 Vendor master data and purchase order data are compared with read information.
 Recipient data are used to determine the recipient of an invoice (ICC).
 Learning data are used to extract data for fields that use Adaptive Recognition.
Vendor master data, purchase order data (ICC), and learning data are downloaded from SAP ERP periodically.
An ICC/BCC system has to be customized to meet the needs of the customer. Customizing is done with a 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, an ICC/BCC system contains several Validation Clients. The Validation Client is a Windows program that
permits to review and eventually complete or correct the extraction results of the Recognition step.

1.5 Customizing
Customizing is done by creating applications with the Customizing Client. An application bundles all settings that are
needed to process documents of a certain kind, for example which fields have to be extracted by which extraction
method.
For each application you have to 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 is to use to process the
document image.
The applications usually are created in a development environment on a special development Recognition Server
connected to a SAP ERP 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 system. The Validation Clients also need the
applications to control document validation. As soon as the applications have been saved in a SAP ERP system, they are
available for the Validation Clients connected to this SAP ERP system.

Besides the facility to save an application in SAP ERP (export), the Customizing Client also provides the facility to load
an application from SAP ERP 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 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. 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. An SAP Feedback Link is used to download feedback data which are needed for
different learning data extraction methods.
The Hot Spots have to be configured with the Customizing Client.

1.7 Achieving optimum recognition results
To achieve optimum character recognition results you should optimize quality of scanned images not only on the
production system but also during testing. Therefore, take the following into account:
 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.
Reduce possible errors or performance problems by using suitable operating procedures and suitable application settings
taking the following into account:
 Use separator sheets or barcode for attachment separation. Automatic separation should only be used if PDF
files have to be processed. Each activated method for attachment separation is checked at each page; if any of
the checked conditions is fulfilled, extraction is stopped.
 Use ICC 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. Ifdownloaded 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, testing environment is important. It
should be as similar to production environment as possible. With regard to testing, you should take the following into
account:
 Use the production scanning equipment already during development and test of your applications. Otherwise
recognition results during production may differ from result during testing making testing less efficient.
 Scan original documents, that is, do not use copies.
 Test with real documents, that is, don 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.

2 Installation
2.1 Planning the installation
2.1.1 System requirements

2.1.1.1 Hardware
Recognition Server and Recognition Node
 x86-compatible processing unit , current design
 3 GB RAM
 20 GB disk space
These are minimum requirements.
For each processor node, 2 GB RAM should be available. Thus on a machine with four processing nodes, 8 GB RAM
should be available.
The disk space required for production depends on the size of the invoices (medium number of pages), size of the
download data (number of downloaded PO lines), and the number of applications.
On the Recognition Server and each Recognition Node, Recognition and download data each use a separate cache per
application where data of the recently processed items are stored. Each cache can have up to 32 entries; as soon as this
maximum number is reached, the oldest entries are deleted. As default, the caches resides below the temporary files
folder of the user used for the Load Manager service (or the Windows\temp folder for a standalone test system where
Local System has been specified as user account for the services) on the system drive.
For Recognition you should plan 150MB disk space for processing single page invoices per application. Thus, if you
have five application with four pages per invoice on average, you should plan 5 * 4 * 150 MB = 3 GB.
For PO download data you should plan 300 MB disk space for 100,000 data records per download for a single
application. Thus, if you have five applications and 400,000 data records to be downloaded on average, you should plan
5 * 4 * 300 MB = 6 GB for download data.
In addition, you should plan several GB disk space for trace files, and for data of documents waiting for processing.
Add these requirements to the minimum of 20GB. For the above examples, you should have at least 35 GB available on
the system drive.
The caches can be moved to another location. For more information, see "Moving the caches to a different location" on
page 21.
Validation Client
 x86-compatible processing unit , current design
 1.5 GB RAM
 1 GB disk space
These are minimum requirements for applications processing documents of up to 10 pages. Provide 4 GB RAM for
applications processing documents of up to 35 pages. If documents with more than 35 pages may occur, provide 6 GB
RAM and activate Windows 4-Gigabyte Tuning.
ICC/BCC Administrator's Guide Installation  7

2.1.1.2 Software
The following Windows versions are supported (including 64-bit versions: WOW):
 Windows 2008 Server
 Windows 7 (for Validation Client)
 Windows 2008 Server R2
 Windows 8.1 (for Validation Client)
 Windows 2012 Server R2
Note: Whereas for development and testing, a workstation operating system such as Windows 7 may be used, it is
strongly recommended to use a server operating system such as Windows 2012 Server R2 for Recognition Server
and Recognition Nodes of a production system.
Caution
Do not modify format specifications on the Formats tab of the Region and Language dialog box and of
the Customize Format dialog box in Control Panel because this may affect checks and formatting within
ICC/BCC.
SAP-related requirements
SAP GUI is required on Windows 2008 Server 64 bit systems.

SAP Connector for Microsoft .NET for Windows 32bit, compiled with .NET Framework 4.5.1 is required.
ICC needs access to a SAP ERP system containing OpenText Vendor Invoice Management for SAP Solutions version
5.2 or higher.
BCC needs access to a SAP system containing OpenText Business Center for SAP Solutions version 16.
BCC supports the same SAP versions as OpenText Business Center for SAP Solutions version 16.
Important
BC Inbound Configuration replaces the ICC Dispatcher framework with VIM 7.5 SP3. If you install VIM 7.5
SP3, you must use BC Inbound Configuration. If you upgrade to VIM 7.5 SP3, you can still use the ICC
Dispatcher. However, keep in mind that ICC Dispatcher will be discarded in the future.
Other software requirements and supported scenarios
 ICC/BCC can be used with VMWare (ESX-Server).
 ICC/BCC needs a database in an instance of the Microsoft SQL Server (2008 R2 or 2012). For more
information, see "Installing the Microsoft SQL Server on page 14".
 NET Framework 4.5.1 is required.
2.1.1.3 Database space requirements

The ICC/BCC database contains a separate repository for the following.
 For each application where Adaptive Recognition is used
 For each Adaptive Classification field of any invoice application
Each repository can grow to a maximum of 2000 samples. For each sample document, the images and available character
recognition results for the processed pages and (for Adaptive Recognition only) the trained field data are stored.
Typically the data for a page sum up to about the image size depending on the amount of data on a page. If documents
with color images are trained you need much more space,
8  Installation ICC/BCC Administrator's Guide

Example: The application comprises 6 repositories, trained documents have 5 pages on average, and the processed binary
images have 40KB per page on average with a typical amount of text.
Then the repositories could grow up to about 6 * 2000 * (5* 40 * 2) = 4.8 GB if all repositories have reached the
maximum number of samples after intensive training activity.
ICC/BCC only adds images to the repository where recognition results are available. This affects the size of sample data
if one of the options in the Stop extraction section at the Skip Pages node of the Settings dialog box is used by an
invoice application.
If a database (CSV file) for a Lookup List field (SnapMatch automation method) is loaded, the growth of the database
amounts to about 5 to 7 times the size of the CSV file.
2.1.1.4 Network
The protocol TCP/IP must be supported. Windows File Sharing is needed for the Recognition Server and the
Recognition Nodes.
2.1.2 Image formats

ICC/BCC processes TIFF 6.0 binary images in the compression modes:
 uncompressed
 Fax Group 3
 Fax Group 4
 Packbits
 LZW
In addition, color and gray images in JPEG format can be processed.
Maximum image resolution:
 400 dpi.
All document formats used for invoices, such as DIN A4, Legal, Letter, and smaller formats, in portrait and landscape
orientation, are supported.
Minimum font size:
 Characters must be at least 1.5 mm high and 0.5 mm wide.
In addition, ICC/BCC can process PDF files.
2.1.3 Configurations
ICC/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.
ICC/BCC needs a database in a Microsoft SQL Server instance, which is used for download data/feedback data and
learning data of all applications. It is recommended to 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 ICC/BCC Server or use suitable instance on a different
computer. During installation of ICC/BCC, a dialog box asks for instance and database name.
The Recognition Server manages the connections to the SAP ERP 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 ICC/BCC and its applications. On a production system, the server also performs load balancing,
distributing recognition tasks to the different Recognition Nodes.
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 system and fetch documents available for correction. They work
independently from the Recognition Server and its Recognition nodes.
It is recommended to install ICC/BCC on a separate server. That means, do not install other application software, for
example an archive server, on the ICC/BCC Server.
2.1.3.1 Standalone system

ICC/BCC can be installed on a single computer for testing purposes. 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.3.2 Configuration 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 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.3.3 Configuration for application testing

For testing you will use a computer installed as Recognition Server including the Customizing Client, and an additional
Validation Client. Both will be connected to the SAP ERP test system:

The Recognition Server is used as server, for recognition, customizing, and monitoring.

2.1.3.4 Configuration 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 production system:
2.1.3.5 Processing different types of documents with ICC

ICC can process invoice applications and applications of type Custom. All these applications export data to VIM an
SAP side.
Starting with ICC 7.5 SP2, applications of type application Custom, which is also available in BCC, can be created,
configured, and processed with ICC. If you work with Custom applications, a VIM add-on must be installed on SAP
side.
Starting with ICC 7.5 SP2 it is no longer possible to create applications of type Custom Documents, but existing
applications of this type can still be used.
If you want to work also with BCC Solution Accelerators, you must upgrade to BCC. This upgrade process is described
in detail in the Business Center Capture Release Notes. Invoice applications can be processed with BCC if you install the
Business Center Capture Invoice Solution add-on.

2.2 Preparing installation
2.2.1 Creating a domain user for Windows services

ICC/BCC installs some 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.
Only for a stand-alone test system this is not necessary. In this case Local System can be used instead.
2.2.2 Installing Microsoft .NET Framework

On all computers of the ICC/BCC system, including the Validation Clients, Microsoft .NET Framework 4.5.1 is needed.
Install the Microsoft .NET Framework before you start the ICC/BCC installation:
 On Windows 2008 Server and Windows 2008 Server R2 systems, Microsoft .NET Framework 4.5.1 must be
installed using Control Panel (Turn Windows features on or off) before ICC/BCC is installed.
 On other Windows versions, you must install it before you start the ICC/BCC installation. You can download
the .NET Framework from the Microsoft Download Center on the Internet.
2.2.3 Installing SAP Connector for Microsoft .NET

On all computers of the ICC/BCC system, including the Validation Clients, SAP Connector for Microsoft .NET must be
installed.
The SAP Connector can be downloaded from http://service.sap.com/connectors. To be able to access the download site,
you need OSS and download authorization.
Important
Download the version for Windows 32bit (x86) even on a 64bit Windows system.
To download and install SAP Connector for Microsoft .NET:

1. Select SAP Connector for Microsoft .NET.
2. On the SAP CONNECTOR FOR MICROSOFT .NET DOWNLOAD SECTION, under Compiled with .NET
Framework 4.5.1 click SAP Connector for Microsoft .NET <version> for Windows 32bit (x86).
3. Unpack the downloaded ZIP file and then double-click the MSI file.
4. Install the software not only for the current user but for everyone. Install SAP Connector to its standard
location. ICC/BCC copies the needed files during installation.
2.2.4 Installing Microsoft Visual C++ Redistributables

On all computers of the ICC/BCC system, including the Validation Clients, the Microsoft Visual C++ Redistributables
must be installed.
ICC/BCC needs the current version of the following packages, which can be downloaded from the Microsoft Download
Center:
 Microsoft Visual C++ 2005 Redistributable (x86) (needed only for ICC)
 Microsoft Visual C++ 2008 Redistributable (x86)
 Microsoft Visual C++ 2013 Redistributable (x86)

2.2.5 User permissions
On Windows 2008 Server, switch off User Account Control. On Windows 7 and Windows 2008 Server R2 set User
Account Control to Never Notify. On Windows Server 2012 R2, grant the Customizing Client user full access to the
share DOKuStarDispatchData.
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.
2.2.6 Installing the Microsoft SQL Server

The ICC/BCC Server needs a database in an instance of the Microsoft SQL Server (2008 R2 or 2012). This database is
only used to store runtime data of ICC/BCC outside SAP. You can use an existing instance if available.
If you must install a new instance, it is recommended to use the free Express edition of Microsoft 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.
If you install ICC/BCC for the first time, you must provide a suitable instance of the Microsoft SQL Server and a
database in this instance before you install ICC/BCC. If you upgrade from an earlier ICC/BCC version, you can reuse the
existing instance, which typically has the name DOKUSTAR containing a database RdaDb10.
When you install ICC/BCC, 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 ICC/BCC Server, it is recommended to use 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 ICC/BCC
installation and the user that works with the Customizing Client have the right to create tables in the database.
Important
If you use an external SQL Server instance, you must install the SQL Server Tools on the ICC/BCC Server.

2.3 Installing ICC/BCC
To install ICC 7.5, you need the Invoice Capture Center 7.5 installation media. To install BCC 16, you need the Business
Center Capture 16 installation media. The installation process is identical for both products.
If you install BCC 16, take notice that the product will use Invoice Capture Center 7.5 as default name for
the installation folder.
2.3.1 Stand-alone installation

For testing purposes, all components of ICC/BCC can be installed on a single computer.
To install ICC/BCC on a single computer:
1. In the root folder of the respective installation media, start the setup.exe program. The required Microsoft
software components are checked.
2. On the Welcome page click Next
3. Accept the license agreement by selecting the respective check box and click Next.
4. On the Installation Mode page, accept the default installation mode Stand-alone.
5. Click Advanced to open the Custom Setup dialog box. This dialog box shows which features will be
installed depending on the selected installation mode.
6. If you want to install ICC/BCC at a different location, click Browse and choose the desired path in the
appearing folder dialog box.
7. Click Disk Usage to open the Disk Space Requirements dialog box. 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 ICC/BCC if there is not enough space on your system drive.
8. To proceed with the installation, click Next. The Service Account page opens. This page is used to specify a
user account that can be used for the Windows services created for ICC/BCC. For a stand-alone installation you
can click Local System. If you want to work with a domain user, enter the domain name, the user name, and
the corresponding password.
9. When you confirm with Next, setup is ready. Click Install in the next page to start installation.
10. The Select Database dialog box opens. Select the instance you installed for ICC/BCC use. If possible, use
the default database name RdaDB10 because there are many references to this file name in the documentation.
Important
2.3.2 Installation of the server

A single computer in your configuration has to be installed as Recognition Server. The Customizing Client is always
installed on the Recognition Server.
To install ICC/BCC on the Recognition Server:
4. On the Installation Mode page, click Server.

8. To proceed with the installation, click Next. The Service Account page opens. This page is used to specify a
user account that can be used for the Windows services created for ICC/BCC. The account must be a domain
account with administrator rights. Enter domain name, user name, and password.
9. When you confirm with Next, setup is ready. Click Install on the next page to start installation.
10. The Select Database dialog box opens. Select the instance you installed for ICC/BCC use. If possible, use
the default database name RdaDB10 because there are many references to this file name in the documentation.
Important
2.3.3 Installing a Validation Client

A Validation Client is used for correcting documents. A Validation Client cannot be used for recognition, or for
customizing and monitoring.
To install ICC/BCC on a Validation Client:
4. On the Installation Mode page, click Validation.
Tip: For unattended installation of Validation Clients, command script examples are available. Comments in the
example files describe how you can adapt the scripts to your configuration.

2.3.4 Installation of a Recognition Node
A Recognition Node is used for automatic data extraction in larger configurations. Customizing, monitoring, or
validation of documents cannot be performed on a Recognition Node.
To install ICC/BCC on a Recognition Node:
4. On the Installation Mode page, click Recognition.
8. To proceed with the installation, click Next. On the Invoice Capture Server page, type the name of the
computer used as Recognition Server and then click Next.
9. The Service Account page opens. This page is used to specify a user account that can be used for the
Windows services created for ICC/BCC. The account must be a domain account with administrator rights. Enter
domain name, user name, and password.
2.3.5 Installing add-ons for Business Capture Center

By default, BCC permits to create, configure, and process applications of the type Custom. To be able to process
invoices or to work with Solution Accelerators, you must install the respective add-ons.
For BCC version 16, five add-ons are available:
 BCC Invoice Solution
 BCC Delivery Notes Solution Accelerator
 BCC Sales Order Solution Accelerator
 BCC Mailroom for HR Accelerator
To install an add-on, start the program setup.exe of the respective installation media and follow the installation
instructions. Install the add-on on each computer of your BCC cluster configuration.
2.3.6 Creating installation log files

To create a standard log file during installation, start installation calling:
Setup.exe /L <logfilename>
To create a full log, call:
Setup.exe /L*v <logfilename>

2.4 Follow-up activities
2.4.1 Configuring Vendor Invoice Management (ICC)

Vendor Invoice Management has to be configured for Invoice Capture Center.
For more information, see the following sections of the OpenText™ Vendor Invoice Management for SAP® Solutions
Configuration Guide:
 Creating an ICC Archive Link Document Type
 Creating and Linking the Validation Determination ID
 Assigning Validation Agents.
ICC uses a 60 minute timeout for recognition jobs and a 600 minute timeout for downloads. Take care to specify
matching timeout values in Vendor Invoice Management.
2.4.2 Configuring Business Center (BC)

Business Center has to be configured for Business Capture Center.
For more information, see the following sections of the OpenText™ Business Center for SAP® Solutions Configuration
Guide:
 Creating an ArchiveLink document type
 Creating a validation
 Assigning an agent to an ArchiveLink document type.
2.4.3 Configuring the archive server

ICC/BCC stores recognition data as a ZIP file on the archive server. Make sure that the corresponding content type is
registered for the used archive server.
2.4.4 Preparing SAP ERP user accounts

To fetch recognition jobs and download data, ICC/BCC needs several SAP ERP user accounts with certain authorization.
For details, see User Management and Authorization Concept.
2.4.5 Preparing SAP ERP login data

On all computers of the ICC/BCC system, connections to a SAP ERP system have to be established.
To make this comfortable, you should supply a saplogon.ini file with login data of all required SAP ERP 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 Windows folder of the system drive.
To make sure that the configuration is valid, you should install SAP GUI and check whether the login mask appears
when the program is started.
2.4.6 Creating and configuring applications

Following installation, you have to create and configure applications before you can work with ICC/BCC (see ICC/BCC-
Customizing Guide).

2.4.7 Configuring the cluster
To enable Load Balancing on several computers and on several processors of a computer, the Load Manager has to be
configured 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 "Recognition Cluster Setup" on page 59.
2.4.8 Configuring the Windows Firewall for Validation Clients

To be able to use an active Windows Firewall on the Validation Clients, all ports used by the Validation Client must be
released. The Validation Clients use one or more of the following TCP ports specified by SAP ERP:
 3300+SID (Gateway)
 4800+SID (Secure Gateway)
 3600+SID (Message Server)
For more information, see “TCP/IP Ports Used by SAP Applications” (SAP Developer Network).
2.4.9 Configuring SAP GUI

SAP GUI 7.20:
Whereas SAP GUI stored the saplogon.ini file globally in the Windows folder of the system drive in previous
versions, SAP GUI 7.20 stores it user-specific under the ApplicationData folder by default. Thus the HotSpot
service (DOKuStar HotSpot 3.0) that is configured to work with the user Local System cannot find the file
and the Extraction and Download link does not work.
Therefore, if you work with SAPGUI 7.20, specify the location of the saplogon.ini file in the respective
environment variable (refer to the SAP documentation). Then SAPGUI 7.20 and the HotSpot service use the
environment variable to find the file.
Alternatively, you could modify the configuration of the HotSpot service and specify the same Windows user that works
with SAP GUI.
SAP GUI 7.40:
SAP GUI 7.40 is part of the installation package SAP Netweaver Business Client (NWBC). NWBC installation
switches the server configuration from saplogon.ini to SAPUILandscape.XML, which is not supported by the
SAP .NET connector used with ICC/BCC.
Therefore, either save saplogon.ini and restore it after installation of NWBC, or install only the SAPGUI part of the
NWBC installation package. In this case, SAP GUI still uses saplogon.ini.

2.4.10 Configuring the SLD Data Supplier (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.
Note: Configuration of the SLD Data Supplier for BCC will be described, as soon as it is supported by the SAP
Landscape Directory.
All components of an ICC system register in the SAP Landscape Directory. SLD registration is provided by a Windows
service Invoice Capture Center SLD Data Supplier 7.5, 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.
The service must be configured on each computer of the ICC system once after ICC has been installed.
To configure the SLD Data Supplier service:
1. In the Windows Start menu, go to the ICC/BCC program group, and under Tools click SLD Data Supplier
Settings. The SLD Data Supplier Settings dialog box opens:
2. Enter the NetWeaver settings SLD host, port, user, and password.
3. To test 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. In your Internet browser, navigate to http://<SLD host name>:50000/sld. and log in.
2. Click Administration, and then click Content Maintenance.
3. In the Subset list, click All With Instances, click Installed Product, 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.11 Upgrading existing applications

After installing a new version or a service pack, you must upgrade existing applications before document processing is
being started.
To upgrade an application:
1. Open the application.
2. Click Settings in the Setup group of the Application tab.
3. In the appearing Settings dialog box, click OK; the application is now being upgraded.
4. On the application menu point to Export Application and 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 and download data reside on the system drive below the subfolder
DOKuStar Professional/3.0/Cache of the temporary files folder of the user account that you specified in the
Service Account dialog box during installation.
To move the caches to a different location, for example to another partition or disk drive:
1. Log in with the respective user account.
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.

2.5.2 Moving all ICC/BCC data to a different drive
By default, ICC/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 ICC/BCC data can be moved to different locations. For more information, see "Moving ICC/BCC data to
a different location on page 52.
2.6 Installing updates
2.6.1 Installing patches and service packs

We recommend that you check the OpenText Knowledge Center (https://knowledge.opentext.com/) for Service Packs or
Patches that may have been posted after the initial release of ICC/BCC.
Service Packs are cumulative; that means a Service Pack contains all changes contained in previous Service Packs of the
respective ICC/BCC version. Therefore, it is sufficient to install only the latest Service Pack after installing /ICC/BCC.
For the same reason, the Release Notes of a Service Pack list the changes of all previous Service Packs.
On the other hand, a Service Pack can be installed on ICC/BCC with any previous Service Pack.
Patches are related to a Service Pack; that means, a Patch can only be installed on an ICC/BCC system where the
corresponding Service Pack has been installed. Patches are cumulative; that means, a Patch contains all changes
contained in previous Patches for the same Service Pack.
To install a Service Pack or a Patch:
1. Stop all Hot Spots; that means Extraction Link Hot Spots, Download Link Hot Spots (ICC applications), and
Feedback Link Hot Spots (BCC application) of all applications.
2. Click Cluster in the Server group of the General tab 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 (Recognition Server, Recognition Nodes, and Validation
Clients).
5. Upgrade each application: Open it, open the Settings dialog box and then close it with a click on OK.
6. Export all applications to SAP ERP. 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.
Afterward, the applications can no longer be used with an earlier Service Pack.
For further details refer to the Release Notes of a Service Pack, or the readme file of a Patch, respectively.

2.6.2 Installing the Imaging Plug-in
ICC/BCC uses an imaging component provided by the Recognition Engine. Starting with ICC 7.5 SP3 Patch1 / BCC
10.0 SP1 Patch01, this imaging component can be installed separately, and it is used by ICC/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 ICC/BCC. This makes bug fixes available as soon as a
new plug-in version is released; you do not have to wait until an ICC/BCC Patch or Service Pack is available. You can
install ICC/BCC Patches or Service Packs and new versions of the Imaging Plug-in as needed because ICC/BCC will
always use the newest version of the imaging component.
The About dialog box of Customizing Client and Validation Client indicates the version of the used imaging component
and whether the Imaging Plug-in is active.
The XML file created by ProductConfigInfoTool.exe now contains an Imaging tag. Its value shows the
version of the used imaging component and whether the Imaging Plug-in is active.
The Imaging Plug-in can be found in OpenText Knowledge Center as product Capture Imaging Plugin.
2.7 Upgrading ICC/BCC
2.7.1 Upgrading ICC/BCC

If you are using BCC and want to process also invoices, you must install the plug-in Business Center Capture Invoice
Solution.
If you are using ICC and want to process additional document types with Business Center on SAP ERP, you must do the
following:
1. Remove ICC.
2. Install BCC.
3. Install Business Center Capture Invoice Solution.
4. Install additional BCC plug-ins as needed.
2.7.2 Upgrading to a newer version

For information about upgrading, refer to the Release Notes of the new version. There you can find detailed information
in chapter 5 "Installation and Upgrade Notes."

3 Installing Single Click Entry for SAPGUI
(ICC)
The ICC installation media comprises a setup for SceSapGui. If SceSapGui 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
4.2 Using the Single Click Entry feature in the Vendor Invoice Management - User Guide.
To install SceSapGui:
1. Start the program setup.exe in the SceSapGui folder of the ICC installation media to start the installation
wizard.
2. Click Next on the Welcome page of the installation wizard.
3. If you want to install the software in a special folder, click Browse on the Select Installation Folder page,
select the desired folder in the appearing folder dialog box and confirm with OK.
4. By default, the software is installed for every user. To install it only for the current user, click Just me.
5. Click Next, and then click Next on the Confirm Installation page.
6. When the installation has been completed, click Close to close the installation wizard.
After SceSapGui has been installed, you must configure SAPGUI.
To configure SAPGUI and VIM for SceSapGui:
1. Start SAP GUI and 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. Use transaction N/OPT/SPRO to set the variable XML_AR_DELETE_EARLY. For SceSapGui, this variable
must not be set to the value X! For more information, see "16.3.2 Defining Frequently Used Default Values" in
VIM - Configuration Guide.
7. Configure clean-up of XML files for documents that have left the ICC Dispatcher. For more information, see
"7.4 Batch Program /OPT/VIM_ICC_CLEANUP" in VIM - Administration Guide.
If scripting should be restricted 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.
On the login screen, SAP GUI scripting is then available for every user.
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.
ICC/BCC Administrator's Guide Installing Single Click Entry for SAPGUI (ICC)  25
4 Monitoring ICC/BCC
For monitoring of an ICC/BCC system, you can use external monitoring tools.
For monitoring of SAP work items, use the ICC Admin Tool of the Vendor Invoice Management product in SAP ERP.
For more information about the ICC Admin Tool, see Vendor Invoice Management - Administration Guide, chapter
“Working with the ICC Admin Tool”.
4.1 Monitoring ICC/BCC with external monitoring tools

If you monitor ICC/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: ICC/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.
 Windows services: For document processing, the Windows services DOKuStar HotSpot, DOKuStar
Load Manager, and DOKuStar Tracing must be available. Therefore it is meaningful to monitor whether
these services are running. If a service is not running, start it.
4.1.1 Monitoring ICC/BCC with Wily Introscope

For monitoring with Wily Introscope, a Probe Builder Directives files (file extension .pbd) for ICC and for BCC are
available. These files specify 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. 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 ICC/BCC is connected to SAP.
ICC/BCC Administrator's Guide Monitoring ICC/BCC  27

 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 file icc.pbd, or bcc.pbd,
respectively), 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.
4.2 Monitoring ICC/BCC using the SAP Solution Manager

ICC/BCC can be administered using the SAP Solution Manager. For details, refer to the SAP Solution Manager
documentation
(http://help.sap.com/saphelp_sm71_sp01/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm).
4.2.1 Providing technical configuration information

To provide technical configuration information, open the start menu on the ICC/BCC Server, go to the ICC/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
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 Windows Authentication,
false in case of SQL Server Authentication.
Product Product name (Invoice Capture Center / Business Center Capture)
Version Version number (7.5 / 10.0)
Build Build number
ServicePack Installed service pack
Patch Installed patch
OwnerName Name of the product owner (Open Text)
28  Monitoring ICC/BCC ICC/BCC Administrator's Guide

5 Technical operations
5.1 Overview of the Customizing Client
The Customizing Client provides tools for the technical configuration of an ICC/BCC production system.
It also provides tools for monitoring of an ICC/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
ICC/BCC system and you can open several tools for the technical configuration of your system.
The views and the tools are accessible in the ribbon of the Customizing Client: There are buttons to open views and
buttons to start configuration tools.
When you click a configuration tool button, the tool is opened in a new window. When you click a view button, the view
is 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 view buttons and tool buttons are provided on different tabs of the ribbon. View buttons and tool buttons that belong
together in a way are presented on the same tab. A tab of the ribbon corresponds to a scope of the ICC/BCC system.
Selecting a different tab in the ribbon automatically changes the view.
The ribbon of the Customizing Client presents two tabs:
 Application
 General
On each tab you find the views and tools of one of the functional scopes of the Customizing Client:
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.
During application development you work mainly with the Application view.
The General tab provides monitoring facilities to the Customizing Client user. On the General tab you can switch
between several technical monitoring views: HotSpot view, Jobs view, and Cluster view. In addition, the General
tab provides the tools Trace Viewer and Load Manager Configuration tool, which are described in detail in this Guide.
ICC/BCC Administrator's Guide Technical operations  29

The views and tools of the General tab are needed for the technical configuration and for monitoring of an ICC/BCC
production system.
All tools of the Application tab work on the currently opened application whereas the General tab permits to show
global data of the Recognition Server – independently of the opened application.
The tools and views of the Application tab are not discussed in detail in this guide. For detailed information about
application development see Customizing Guide; for more information about Validation, see User`s Guide. This guide
concentrates on monitoring and technical configuration.
5.2 Overview of components

An ICC/BCC system consists of a central component in SAP ERP, the BC Inbound Configuration, or the ICC
Dispatcher, respectively, and of several Windows components.
5.2.1 Document processing in BC/VIM on the SAP ERP system

In BC, the modules of Inbound Configuration control document processing including BCC. For more information, see
"3.5 Business Center Capture" in Business Center - Configuration Guide.
The ICC Dispatcher is part of the VIM product in SAP ERP. For more information, see Vendor Invoice Management -
Configuration Guide, chapter “ICC Dispatcher.”
5.2.2 ICC/BCC Windows components

Each ICC/BCC system contains the following 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 ICC/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 Windows parts of an ICC/BCC system:
30  Technical operations ICC/BCC Administrator's Guide

5.2.2.1 Standalone system
Usually, a standalone system is used for developing, for testing, and for demo systems. All Windows components of the
ICC/BCC system are installed on one PC:
 Standalone PC
 Recognition Server with Customizing Client and databases
 Validation Client
5.2.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
5.2.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
5.2.3 Further involved components

The following components are involved in an ICC/BCC system, but are not part of it:
 Enterprise Scan
 SAP ERP archive

5.3 Overview of technical runtime scenarios
5.3.1 Recognition and validation of a document

Involved components:
 Enterprise Scan
 SAP ERP Archive
 BC Inbound Configuration or ICC Dispatcher, respectively
 Recognition Server (optional: Recognition Node)
For a specific archive document type, Enterprise Scan scans a document and archives the document image in the SAP
ERP archive using the early archiving scenario of SAP ERP. 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 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 have to 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 "3.5 Business Center Capture" in Business Center -
Configuration Guide.
5.3.2 Downloading data from SAP ERP

 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, which were provided by the
Validation Clients.
The Recognition Server imports the data into its local database.

5.3.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.
5.4 Monitoring using the Customizing Client

To monitor an ICC+VIM system, use the ICC Admin Tool of the Vendor Invoice Management product in SAP ERP.
For more information, see Vendor Invoice Management - Administration Guide, chapter “Working with the ICC Admin
Tool”.
To monitor a BCC system, use the Work Center for Inbound Administration of BC.
The Customizing Client (installed on the Recognition Server) provides views to monitor the Recognition Cluster of an
ICC/BCC system.
5.4.1 Monitoring Hot Spots

To show the list of Hot Spots:
 In the Customizing Client, in the Server group of the General tab, 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.

5.4.2 Monitoring jobs
To monitor jobs:
 In the Customizing Client, in the Server group of the General tab, click Jobs.
A list of all jobs that are being processed or waiting for processing is shown:
The State column indicates the operation state by a symbol:
Value 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 but are still waiting for a free processing node
are in state Pending.
The remaining columns show the following status information:
Column Description
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.
Profile Profile used by the operation.
Client Client ID started by the operation.
Started at Time at which the Operation started.

5.4.3 Monitoring the Recognition Cluster
To monitor the Recognition Cluster:
 In the Customizing Client, in the Server group of the General tab, click Cluster to monitor the Recognition
Cluster:
A list of all cluster nodes with state information is shown:
The first column indicates the cluster state by a symbol:
Symbol 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.
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.
The remaining columns show the following state information:
Column Description
Name Cluster node name composed of computer name, service type, and
instance number.
Profile Currently loaded profile.
Client Client ID that started the currently active operation.
Total Time Total active time of the cluster node since start of the Load Manager.
Operations Number of processed operations since start of the cluster node.

To configure a cluster node:
 Right-click the cluster node line. A context menu with the following commands appears:
Command Description
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.

5.5 Logging and tracing
5.5.1 Logging
Logging is done on the SAP ERP side of an ICC/BCC system. For more information, see Vendor Invoice Management -
Administration Guide, chapter “Working with the system log”, or Business Center - Configuration Guide, section "2.4
Logging", respectively.
5.5.2 Overview of tracing

ICC/BCC permits to generate trace data, which can be used 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
5.5.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, DOKuStar is a parent of
DOKuStar.Runtime.
A special tracer, called the RootTracer, is the parent of all tracers; it has no name.
5.5.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.
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.

5.5.5 Trace root path
ICC/BCC writes trace messages to trace files located relative to a root path for all applications. The default root path is
%ALLUSERSPROFILE%\Application Data\Open Text\Trace.
Note: Please take notice that the folder Application Data is a hidden folder. Therefore the Windows
Explorer only shows it if you have marked the respective option in the Folder Options.
To change the default trace folder:
1. Set the registry value TraceRootPath (type REG_SZ) at the key HKLM\SOFTWARE\Open Text and on
64-bit systems also at the key HKLM\SOFTWARE\Wow6432Node\Open Text to a new path.
2. To keep the trace configuration, copy the trace configuration files (extension .traceconfig) to the new trace
path.
3. If you want to use a remote trace folder, run the service with a domain user account instead of the
LocalSystem account.
4. After changing the path and the user, restart the ICC/BCC participant:
 On a Validation Client restart the Validation Client program.
 On the Recognition Server restart the ICC/BCC services and the Customizing Client program.
 On a Recognition Node restart the ICC/BCC services.
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.
5.5.6 Trace levels

Tracers and trace listeners have trace levels used to control the volume of the tracing output.
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 etc.
Finer Next debug level.
Finest Highest debug level.
Please note that 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.
5.5.7 Trace configuration

Several trace configuration files in the trace folder specify which trace messages a distinct ICC/BCC component writes
to the trace folder. For example, a trace configuration file defines the trace level for the trace messages. Only trace
messages with this specified trace level or higher are written to the trace folder.

The trace configuration files must reside in the current trace folder. Therefore do not forget to copy the trace
configuration files to the new location if you change the trace root path.
You may configure traces by editing the appropriate trace configuration file directly or by selecting a predefined trace
configuration in the Trace Viewer. For more information, see "Trace Viewer: main menu" on page 43.Selecting a
predefined trace configuration in the Trace Viewer changse the trace configuration files automatically.
The trace configuration file has three types of elements:
listener
This element configures a trace listener by specifying:
name any describing name,
type the full qualified name of the class which implements the listener,
threshold trace level (optional, default is Finest)
and 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:
level the 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:
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) and overwrite.
A file of type merge 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>
A file of type 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>
Examples for trace configuration files you can find in the folder TraceConfig in the ICC/BCC installation folder.

5.5.8 Location of trace files and trace configuration files
The following table shows where the trace files and trace configuration files of the particular programs are located.
Program / Service Trace file / Trace configuration file

Load Manager and Usually the Runtime and Extraction run within a cluster controlled by the Load
Cluster Nodes 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.
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
system.
Trace files
<TraceRoot>\DOKuStar Professional\HotSpot*.log
Trace config file
<TraceRoot>\HotSpot.traceconfig
Customizing Client and Trace files
Validation Client <TraceRoot>\rda1\rda1*.log
Trace config file
<TraceRoot>\rda.traceconfig
All services The windows event log is used to log creating, starting and stopping of the services.
5.5.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:
2011.03.04T10:17:45 Error: SYS2186 DOKuStarLoadManager 2264 DOKuStar.Cluster.Configuration 1 [[this is the
error message]]

5.5.10 Analyzing trace files
You can view and analyze all trace files with the Trace Viewer.
You can start the Trace Viewer:
 From the ICC/BCC program group
 From the Customizing Client.
To start the Trace Viewer:
1. Open the Customizing Client.
2. In the Tools group of the General tab, click Trace viewer.
5.5.11 Trace Viewer

5.5.11.1 Trace Viewer window
The Trace Viewer can be started from the Customizing Client by clicking Trace viewer in the Tools group of the
General tab. You can also start it directly from the ICC/BCC program group of the Windows start menu.
It is used to show trace messages created by the ICC/BCC components and permits 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.
When you start the Trace Viewer, it shows a list of all trace files found on the local machine on the left side. The list is
grouped by the different components:
The header shows the path of the trace folder as a link. If you click the link, the folder is opened in a Windows Explorer.
By default, all trace files are listed. If you click Only errors, or Only errors and warnings in Filter list, the trace
file list only shows trace files containing messages of the respective types.

5.5.11.2 Trace Viewer: main menu
File menu
Open
This command can be used to open a trace that is not available in the file list.
Exit
Terminates the Trace Viewer.
Edit menu
Clear all
Removes all messages from the messages view. To empty the trace file, click Save on the File menu
afterward.
Find
Opens the Find dialog box that permits to search in the currently open file.
Find next
If you have specified search parameters in the Find dialog box, this command searches the next appearance.
Find previous
If you have specified search parameters in the Find dialog box, this command searches the previous
appearance.
View menu
Filter
Opens the Filter dialog box where you can control which messages should be shown in the messages view.
Top window
If you click this command, the Trace Viewer window stays on top. To switch this feature off, use the
command again.
Columns
With this command you can control which columns are shown in the messages view. A click on a column
name adds a column if it is not shown currently, or removes it otherwise.
Tools menu
Trace Configurations
This command permits to select one of three trace configurations:
Debugging production system: This configuration 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: This configuration 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: This configuration is intended for production systems. It traces all errors, warnings, and info
traces, but does not produce too much trace data.
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.
Note: 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 above.
Options
Opens the Options dialog box where you can change the language of the Trace Viewer user interfaces.
Help menu
About Trace Viewer
Shows a dialog box with version information.
5.5.11.3 Trace Viewer: messages list view

When you double-click a file in the list, the contents of the file is shown in the messages list view on the right side:
The toolbar buttons above the messages list view permit to control which messages are displayed in the list view, see
below.

By double-clicking on a message in the list view you can open a Trace Message dialog box showing the complete
message and its details:
5.5.11.4 Trace Viewer – messages list view: toolbar

If the toolbar is not shown, right-click the header row of the messages view, and then click Toolbar.
Trace Configuration
Opens the Trace Configuration dialog box where you can select one of three trace configurations:
Debugging production system: This configuration 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: This configuration 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: This configuration is intended for production systems. It traces all errors, warnings, and info
traces, but does not produce too much trace data.
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.
Display Level
Permits to 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. In the above example, trace level Debug Fine is
just being used.
Display filter
A dialog box permits to set different kinds of filters that control which log messages are shown.
Find
The Find dialog box opens. It permits to search messages containing a string, word, or a regular expression. If
the command has already been used, the F3 function key can be used to jump to the next occurrence.
Auto scroll
If this button is pressed, the view shows the last lines, when trace messages are added.

5.5.11.5 Trace Viewer – messages list view: context menu
Open…
Opens a log file. The contents of the file is loaded and shown in the messages list view.
Save
If a log file has been saved in the current session, this command overwrites this file with the current contents
of the message list view. Otherwise a file dialog box opens.
Save as
Saves the contents of the messages list view to a file. A file dialog box opens, which permits to select path and
file name.
Clear
Deletes the current contents of the view.
Filter
The Filter dialog box opens. It permits to set different kinds of filters that control which log messages are
shown. For example, the Type filter permits to switch messages of the types Error, Info, Log and Warning
on or off separately.
Find
The Find dialog box opens. It permits to search messages containing a string, word, or a regular expression. If
the command has already been used, the F3 function key can be used to jump to the next occurrence.
Auto scroll
If this option is selected, the view shows the last lines, when log messages are added.
Columns
A submenu permits to control which columns of the trace messages are shown in the view.
Toolbar
If this option is selected, the view shows a separate tool bar, which permits to use the most important
functions of the view with a single mouse click.
Header
If this option is selected, the messages list view shows a header line with the column titles. The header line
can also be used to change the column widths by dragging the column borders of the header line with the
mouse.

5.5.11.6 Trace Viewer – messages list view: Filter dialog box
The Filter dialog box permits to specify which messages should be written to the messages list view:
Take notice that specified filters only affect the messages 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 open the Filter dialog box, use the Filter command on the context menu of the messages list view or the
corresponding toolbar button.
Different kinds of filters can be specified:
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.
The trace level can also be set using the toolbar of the messages list view. This toolbar is not shown by
default. It can be switched on or off with the Tool Bar command on the context menu of the messages list
view.
Computer
Here all computers of the cluster used by the project are listed. 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
Here all applications of the current project are listed. By default, all applications are enabled.
PID
Here the process IDs of all processes of the current project are listed. By default, all processes are enabled.

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 section is not empty, only matching messages are shown in the messages list view. The
check boxes permit to control text matching. If the Match case check box is selected, the message must
contain the string in exactly the same spelling with respect to upper and lower case letters. If the Match
whole word only check box is selected, the string will not be matched against a part of a word. If the
Regular expression check box is selected, the specified string is used as a regular expression.
5.5.11.7 Trace Viewer – searching trace messages

You can search for strings in the trace message files shown in the messages list view. You can also enter a regular
expression.
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: The string is searched in exactly the same spelling with regard to upper and lower case
letters
 Match whole word: The search string is not matched to a part of a word or stretching over two or more
words but only to a single word
 Regular expression: If you enter a regular expression, select this check box. The search string is
interpreted as a regular expression.
3. Click Find Next or Find Previous to search the message list. , The next or previous matching trace message
is selected in the messages list view.

5.5.12 SAP ERP format tracing
In addition to the ICC/BCC tracing described above, ICC/BCC also writes trace messages in SAP ERP format to a
further trace folder named Trace ICC. This additional trace folder is always located in the same folder as the regular
ICC/BCC trace root folder Trace. By default Trace and Trace ICC are located in
%ALLUSERSPROFILE%\Application Data\Open Text.
Changing the location of the regular trace folder by creating a registry entry as described above also changes the location
of the additional trace folder for SAP ERP format trace files.
There are no special trace configuration files for tracing in SAP ERP format. The regular trace configuration files control
both regular tracing and SAP ERP format tracing.
Changing the trace configuration with the Trace Configuration dialog box also changes the trace configuration for
SAP ERP format tracing.
The following table gives an overview of the SAP ERP format trace files:
Program / Service Trace file / Trace configuration file

Load Manager and Usually the Runtime and Extraction run within a cluster controlled by the Load
Cluster Nodes 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.
Trace files
<SAPFormatTraceRoot>\DOKuStar Load Manager\DOKuStarLoadManager*.trc
<SAPFormatTraceRoot>\DOKuStar Load Manager\DOKuStar.ClusterNode*.trc
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 system.
Trace files
<SAPFormatTraceRoot>\DOKuStar Professional\HotSpot*.trc
Trace config file
<TraceRoot>\HotSpot.traceconfig
Customizing Client and Trace files
Validation Client <SAPFormatTraceRoot>\rda1\rda1*.trc
Trace config file
<TraceRoot>\rda.traceconfig

5.6 Configuration data (production system)
After performing the installation steps described in chapter Installation, your ICC/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 machine participating in an ICC/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 Windows services.
The following sections describe which components are located on which participants and how the different participants
interact in respect to the components.
5.6.1 Technical configuration data

5.6.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 "Recognition Cluster Setup" on page 59). The Load Manager Configuration tool saves
the cluster configuration files into the folder %ALLUSERSPROFILE%\Application
Data\Captaris\DOKuStar Load Manager on the Cluster Master.
5.6.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.
5.6.1.3 Trace configuration files

Each participant of an ICC/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 37.
5.6.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
51.

5.6.2 Application configuration data (customizing data)
The application configuration data are saved in a SAP ERP table and are downloaded to an ICC/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. 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.
5.6.3 Runtime files

5.6.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 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.
5.6.3.2 Trace folder

Each participant of an ICC/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 37.
5.6.4 Registry entries

During installation, ICC/BCC adds some entries to the Windows registry, for example installation paths and version
information.
5.6.5 Databases
5.6.5.1 SQL Server instance
ICC/BCC needs a database in a suitable Microsoft SQL Server instance, which must be available when ICC/BCC is
installed. During installation, a dialog box asks for instance and database name. You can either install a 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 and by the user who customizes the system. The Validation users
have no access to the database.

5.6.5.2 ICC/BCC database
For invoice applications, Vendor master data and purchase order data are periodically downloaded from SAP ERP and
stored into the ICC/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 and
stored into the ICC/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.
5.6.6 Services
ICC/BCC is based on OpenText Capture Center. The runtime environment of OpenText Capture Center consists of
several programs and Windows services. In the standard configuration the following Capture Center Windows services
run on the Recognition Server (Master) and on the Recognition Nodes (Slaves):
 Load Manager Service (DOKuStar Load Manager)
 Hot Spot Service (DOKuStar HotSpot)
 Tracing Service (DOKuStar Tracing)
 Recognition Node
 Load Manager Service (DOKuStar Load Manager)
 Tracing Service (DOKuStar Tracing)
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 Windows services, there is also a special ICC/BCC service, the SLD Data Supplier
Service (Invoice Capture Center SLD Data Supplier). This service runs on each Windows component of an ICC/BCC
system. It registers ICC/BCC in the SAP System Landscape Directory.
5.6.7 Moving ICC/BCC data to a different location

Most of the configuration and runtime data of ICC/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.

5.6.7.1 Moving the share DOKuStarDispatchData to a different location
By default, the shared folder DOKuStarDispatchData is located in %PROGRAMDATA%\Open Text\DOKuStar
Dispatch\data on the system drive of the ICC/BCC Server. The subfolder config of DOKuStarDispatchData
contains the configuration.
To move the share to a different location on the ICC/BCC Server:
1. Stop all HotSpots and wait until processing has been completed.
2. Stop all clients.
3. Stop all ICC/BCC services on the Server and the Recognition Nodes (see "Starting and stopping of services on
the Recognition Server and the Recognition Nodes" on page 68).
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. Then share the new folder using the name DOKuStarDispatchData.
8. Be sure to provide the needed rights for all components of your ICC/BCC system.
9. Restart the services.
10. Restart the HotSpots.
If the share is moved to a different machine, the configuration path (=path to the config folder) changes. You must
adapt the configuration after moving the share.
To move the share:
1. Stop the HotSpots and wait until processing has been terminated.
2. Stop all running clients.
3. Stop all ICC/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 68).
4. Stop sharing the folder %PROGRAMDATA%\Open Text\DOKuStar Dispatch\data.
5. Create a folder on the different machine.
6. Move the contents of %PROGRAMDATA%\Open Text\DOKuStar Dispatch\data to the new folder on
the different machine.
7. Then share the new folder.
8. Be sure to provide the needed rights for all components of your ICC/BCC system.
9. Adjust the configuration location specification: On each ICC/BCC installation, even on the ICC/BCC Server
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.

5.6.7.2 Configuring location of file ClientConfig.dfc
On each computer where ICC/BCC is installed, the file ClientConfig.dfc specifies the location of the share
DOKuStarDispatchData containing the configuration data. By default this file is created in the folder
%PROGRAMDATA%\Captaris\DOKuStar Dispatch 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
ClientConfigPath containing absolute path and file name of the file.
5.6.7.3 Configuring cache location

The cache is located in a subfolder of the temp folder on the Server and each Recognition Node. To move the cache to a
different location, move the temp folder. For more information, see "Moving the caches to a different location" on page
21.
5.6.7.4 Configuring trace file location

Trace file location is controlled by a registry value on each ICC/BCC machine. For more information, see "Trace root
path" on page 38.
5.6.7.5 Configuring program data location of several components

By default, several ICC/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.
To move all these files to a different location, for example on a different drive:
1. Create a registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Open Text\Capture Common.
2. At this key, create a string value CommonApplicationDataPath containing the path for these program
data.
5.6.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
HotFolders.hcx in the folder %PROGRAMDATA%\Captaris\DOKuStar
Professional\3.0\HotFolders. If this file does not exist, the default location of the HotSpot data takes effect.
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.
The following 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. Especially 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.
5.6.7.7 Moving the ICC/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. On the application menu, click ICC Options.
4. In the ICC Options dialog box click Set Database Connection.
5. To switch to a different SQL Server, click Refresh and click the desired Server in the Server name list as
soon as the list has been updated.
6. To use SQL Server authentication, click Use SQL server authentication and enter user name and
password.
7. Click the desired database in the Database list.
8. Optionally, click Test Connection to make sure that the database can be reached.
9. Close the dialog boxes.
10. Import the applications.
Note: The Server name list shows only SQL Servers on computers in the current IP subnet. To switch to a
server in a different subnet, type <computer name>\<instance name> in the Server name box.

5.7 Backup and restore
The ICC/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 ICC/BCC database also contains learning data of Adaptive Recognition and Adaptive Classification. Typically
training is performed on a separate ICC/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, it is recommended to regularly backup 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) and How to: Restore a
Database Backup (SQL Server Management Studio).
The backup can occur while the databases are online and being used by the Recognition Server.
It is recommended to schedule backups and download operations for different times.
For more information about backup operations in SQL Server, see Backup Overview (SQL Server).

5.8 Periodic activities
5.8.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.
5.8.2 Restricting the growth of the ICC/BCC database

The ICC/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 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.
5.8.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.

5.9 Load balancing
5.9.1 Load Manager

In an ICC/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 PCs 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 Windows service, which runs on the Recognition Server and on each Recognition Node of the
Recognition Cluster. This 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 machine 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.

5.9.2 Recognition Cluster setup
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.
To modify the cluster configuration of the Recognition Cluster, start the Customizing Tool on the Recognition Server.
Click Cluster Setup in the Tools group of the General tab. The Configuration dialog box of the Load Manager
opens:
In the explorer view on the left side yon can use the context menus of the different nodes, to add or delete computers or
to add or remove cluster nodes. If you select a node, its properties are shown in the right part of the dialog box.
During installation, a Runtime Node for the computer acting as server is configured automatically. 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 ICC/BCC on additional Recognition Nodes.

5.9.2.1 Configuring cluster nodes
To configure the cluster, you create a computer node for each additional Recognition Node.
To configure cluster nodes:
1. Right-click the context menu of the Cluster node
2. Click Add Computer to Cluster.
3. In the URL Editor dialog box, In the Server name box, type the computer name and confirm with 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 ICC/BCC,
Extraction nodes are not needed!
4. At each additional Recognition node add one Runtime node for each processor. On the context menu you can
specify the number of needed Runtime Nodes:
Example: For a computer with two 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.
To show the properties of a Runtime Node:
 Select the Runtime Node in the tree view. Its properties are shown on the right side:
The following properties are displayed:
Property Description
Name Cannot be edited; comprised from the computer name, service type and
instance number.
AgentUrl Specifies the URL of the agent service for this cluster node within the
cluster. To edit the computer name, select the parameter line and then
click the ellipsis button at the end of the line.
Description Only for logging purposes.
Exclusive Profiles Permits to restrict a cluster node to specified profiles.
Priority Specifies the priority of the cluster node. The Load Manager prefers
cluster nodes with higher priority.
Within ICC/BCC you do not need to modify any properties.

5.9.2.2 Properties of the Cluster node
To show the properties of a Cluster node:
 Select the Cluster node in the tree view. Its properties are shown on the right side:
The following properties are displayed:
Property Description
LookupInterval Specifies the time interval after which the Load Manager checks whether the
cluster node is still alive.
Profiles This property can be used to view the profiles. Select the property and click the
ellipsis button that appears at the end of the line to open the Profile dialog box.
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. This may be needed
to activate new versions of database files for an Extraction project-
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 cluster node should need for start-up.

5.9.3 Increasing throughput
The throughput of an ICC/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 an ICC/BCC system depends on different factors:
 number of documents to be processed per hour,
 number of needed Validation stations,
 used hardware and system environment.
5.9.3.1 Increasing the number of Recognition Nodes

To increase the number of Recognition Cluster Nodes, install additional Recognition Nodes as described in "Installation
of a Recognition Node" on page 17. Add the respective computers to the Recognition Cluster of the Recognition Server.
For more information, see "Recognition Cluster Setup" on page 59.
5.9.3.2 Increasing the number of Recognition Clusters

If you have to process millions of documents per year and if you process several ICC/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.

5.10 High availability
The most critical part of an ICC/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. Therefore their high
availability is guaranteed.
The application configuration data are stored in SAP ERP. Therefore the high availability of the application
configuration data is guaranteed.
The Validation Clients and the Recognition Nodes are not critical at all. Therefore there is no failover 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, see SAP Netweaver Technical Operations Manual
(http://help.sap.com/saphelp_nw04/Helpdata/EN/08/5741114ae611d1894f0000e829fbbd/frameset.htm).
5.10.1 Using two Recognition Servers

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

5.10.1.2 Maintenance operations
If a 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.
Though it is not mandatory, it is recommended to upgrade Validation Clients too in case of a product update.
5.10.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 upgrade of the Validation Clients, a maintenance window of up to 8 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.
Steps 6 and 7 can exchanged or performed in parallel to reduce the time span in which no documents are validated.

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

5.11 Starting and stopping
5.11.1 Starting and stopping of Hot Spots on the Recognition Server

On the Recognition Server there are two different Hot Spots for each application running on the Server:
 Extraction Link Hot Spot
 Download Link Hot Spot for an invoice application
 Feedback Hot Spot for other types of applications
These Hot Spots are created automatically when an application is created or downloaded from SAP ERP, but they are not
active. They have to be configured and activated manually.
If an Extraction Link Hot Spot is active (= 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 data
extraction.
To start a Hot Spot:
1. Open the Customizing Client on the Recognition Server
2. In the Server group of the General tab 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!

5.11.2 Starting and stopping of services on the Recognition Server and
the Recognition Nodes
On the ICC/BCC participants the following Windows services are running:
 Recognition Server:
 DOKuStar HotSpot
 DOKuStar Load Manager
 DOKuStar Tracing
 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 an ICC/BCC service, use the Services dialog box in Control Panel.
5.11.3 Starting and stopping of Customizing Client and Validation Client

The Customizing Client and the Validation Client are normal Windows programs. They can be started by selecting the
appropriate items in the ICC/BCC program group or by double-clicking the respective shortcut on the Windows desktop.
To exit an ICC/BCC client program, open the application menu and then click Exit ICC.
The Validation Client can be configured to open an application automatically during startup. Create a copy of the ICC
Validation icon on the Windows desktop, open its Properties dialog box, and add the parameter
/app:<application name> to the command line at the Target property.

5.12 Configuring Lookup Lists
5.12.1 Reloading database files for LookUpList fields automatically

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 program LookupDatabaseUpdater.exe that you can find in the ICC/BCC
installation folder:
LookupDatabaseUpdater <ApplicationName> <TableName>
ApplicationName
Name of the application containing the table that should be updated.
TableName
Name of the lookup list table as shown in the Manage Lookup List dialog box of the Customizing Client.
The program uses the file that has been specified in the Manage Lookup List dialog box during configuration of the
application. Therefore you must replace this file with an updated version before the program is started. It is
recommended to place the database file in a folder that exists on both, development system and production system, for
example by using a subfolder of the share DOKuStarDispatchData. 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.

5.13 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. 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.
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 VIM/BC gets the status 89 = Error in validation.
The application log of a job with error status shows the more specific ICC/BCC error code. The following table gives an
overview of the error codes and the appropriate actions to solve the problem:
Error scenario ICC/BCC SAP ERP error Administrator action

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

5.14 Port usage
The following table lists ports used by ICC/BCC:
Port # Protocol Component Computer

135 TCP+UDP SQL Server (ICC/BCC instance) Server
3300+SID TCP Validation Client (depending on SAP ERP Validation Client
configuration)
configuration)
configuration)
20304 TCP Tracing Server,
Recognition Nodes
23000 TCP Load Manager Service Server + Recognition
Nodes
23062 TCP Hot Spot Service “DOKuStar Hot Spot 3.0” Server
Instance- TCP SQL Server (ICC/BCC instance) Server
specific
Dynamic TCP DOKuStarClusterNode.exe (used only locally) Server + Recognition
port 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 the protocol
TCP/IP, and then click Properties on the context menu.
3. On 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
ICC/BCC because this may cause connection errors.

5.15 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. For information
about deleting an application in SAP ERP, see Vendor Invoice Management - Administration Guide, chapter
“Deleting an ICC application from SAP tables” for VIM, or "Clean up" in chapter "Batch jobs for Inbound
Configuration" in Business Center - Configuration Guide, respectively.
5.16 Version information
5.16.1 Customizing Client

The version information is shown in the About dialog box. In the Customizing Client on the application menu, click
About to open the About dialog box.
5.16.2 Validation Client

The version information is shown in the About dialog box. In the Validation Client on the application menu, click
About to open the About dialog box.
5.16.3 File system

You find the version information in the ICC/BCC installation folder (C:\Program Files\Open Text\Invoice
Capture Center 7.5) in the file Invoice Capture Center Version.xml.
5.16.4 Registry
You find the version information in the registry key
HKEY LOCAL MACHINE/Software/Open Text/Invoice Capture Center/7.5 on Windows x86
systems
or
HKEY LOCAL MACHINE/Software/ Wow6432Node/Open Text/Invoice Capture Center/7.5 on
Windows x64 systems.

5.16.5 SLD registration
All Windows components of an ICC/BCC system register in the SAP System Landscape Directory. The SLD registration
is provided by a Windows service named Invoice Capture Center SLD Data Supplier, which is running on each
component. The registration takes place automatically when the SLD Data Supplier Service starts and periodically twice
a day.
The Data Supplier has to be configured once after installation.
To configure the SLD Data Supplier:
1. In the ICC/BCC program group of the Windows start menu, click Tools > SLD Data Supplier.
2. Enter the NetWeaver settings SLD host, port, user, and password.
3. To test the configuration click Test collect and send SLD data.

6 Security
6.1 User management and authorization concept
ICC/BCC has no own user management; it uses both Windows user management and SAP ERP user management. It is
not possible to define or change Windows users or SAP ERP users within ICC/BCC. The needed user accounts have to
be provided using the respective Windows and SAP ERP tools.
6.1.1 Windows users

For more information about using the Windows user management, see Best Practice Guide for Securing Active Directory
Installations or Windows Server 2003 - Security Guide (can be downloaded at http://www.microsoft.com/downloads).
6.1.1.1 Validation Client Windows user

To start the Validation Client, the Validation user has to be logged in to Windows. The 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 log in to SAP ERP using a prepared SAP ERP user. Without logging in to SAP, the Validation
user cannot work at all.
6.1.1.2 Recognition Server / Recognition Node Windows user

The Load Manager services on the Recognition Server and on the Recognition Nodes are running 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.
6.1.1.3 Customizing Client Windows user

To be able to start the Customizing Client, the Customizing Client user has to be logged in to 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.
After starting the Customizing Client, the user can work locally. For communication with SAP ERP the user must log in
to SAP using a prepared SAP ERP user.
ICC/BCC Administrator's Guide Security  75

6.1.2 ERP users
6.1.2.1 Common authorizations
The following authorizations are needed for all types of users for both products:
 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
In SAP ERP versions newer than release 7.10 (EHP 4 and later), you can choose a finer granularity for your
authorizations (see SAP Note 460089). Instead of the authorizations for RFC function groups, you can use authorizations
for each single function module.
The following authorizations can be replaced:
1. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SYST
replace with:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFCPING
2. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SRFC
replace with:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=RFC_PING
3. 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
4. S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=SDIFRUNTIME
replace with:
S_RFC:ACTVT=16,RFC_TYPE=FUNC,RFC_NAME=DDIF_FIELDINFO_GET
Replacing the other function group authorizations by the function module authorizations is possible, but it does not make
much sense, because nearly each function module within the groups is used.
6.1.2.2 Additional authorizations for Validation Client users

As soon as the Validation user has started the Validation Client, the user has to log in to SAP ERP using a prepared SAP
ERP user. This user needs the following authorizations:
For BCC/BC:
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OTX/PF01_IF_OCR
For ICC/VIM:
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC_CFG
76  Security ICC/BCC Administrator's Guide

For BCC/VIM and for ICC/VIM if BC is installed as well:
In addition to the ICC authorizations:
The following authorization can be replaced:
replace with:
 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.
6.1.2.3 Working with Single Sign-On

Single Sign-On can be used for the Validation Client.
Single Sign-On cannot be used if several SAP ERP users are associated with an SNC name. Otherwise an error message
"Login failed: System found several suitable SAP users for the SNC name of the caller." will occur. On the other hand, it
is still possible to use several clients for an SNC name.
To be able to work with Single Sign-On, you must specify a value in the Client box of the SAP Login dialog box.
6.1.2.4 Additional authorizations for Recognition Server / Recognition Node users

The Recognition Server communicates with the SAP ERP 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. The Recognition
Server and the Recognition Node use a prepared SAP ERP user. This SAP ERP user has to be defined in the technical
configuration of the SAP Extraction Link Hot Spot and of the SAP Download Link Hot Spot on the Recognition Server.
This user needs the following authorizations:
For BCC/BC:
For ICC/VIM:
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC_DL
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC_TR

replace with:
 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.
6.1.2.5 Additional authorizations for Customizing Client users

When the Customizing Client user wants to import an application configuration from SAP ERP or wants to export an
application configuration to SAP ERP, the user has to log in to SAP ERP using a prepared SAP ERP user. This user
needs the following authorizations.
For BCC/BC:
For ICC/VIM:
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC_CFGA
The Customizing Client user interface includes a Validation user interface for testing purposes. When the Customizing
Client wants to open a recognition job from SAP ERP in this interface, the user has to log in using a prepared Validation
Client SAP ERP user.
replace with:
 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.

6.1.2.6 Training module SAP ERP user
If you want to perform document training within the customizing client, you need the following authorizations.
For BCC/BC:
For ICC/VIM:
 S_RFC:ACTVT=16,RFC_TYPE=FUGR,RFC_NAME=/OPT/VIM_ICC_TR
Note: This user type includes the authorizations for validation .

For BCC / VIM, and for ICC / VIM if BC is installed as well:
replace with:
 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 user, you need two additional authorizations.
For BCC/BC:
 S_TCODE:TCD=OAWD
 S_WFAR_OBJ:OAARCHIV=*,OAOBJEKTE=/OTX/PF01R,OADOKUMENT=*,ACTVT01
For ICC/VIM:
 S_TCODE:TCD=OAWD
 S_WFAR_OBJ:OAARCHIV=*,OAOBJEKTE=/OPT/V1001,OADOKUMENT=*,ACTVT01
6.1.2.7 Feedback module SAP ERP user

The feedback module communicates with the SAP ERP system to ask for feedback data to improve recognition
capabilities. The feedback module uses a prepared SAP ERP user. This SAP ERP user has to be defined in the technical
configuration of the SAP Feedback Link Hot Spot.
The user needs the following authorizations:
For BCC/ICC:
For ICC (only in custom applications, not prepared in standard product) / VIM:
For BCC/VIM, and for ICC/VIM if BC is installed as well:

replace with:
 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 hotspot user can only work with the feedback related functions.
This SAP ERP user has to be defined in the technical configuration of the SAP Feedback Link Hot Spot.
6.2 Delivered users

ICC/BCC does not deliver any users.
6.3 Emergency user concept

ICC/BCC uses Windows user management. A Customizing Client user is a Windows administrator with administrator
rights on all systems involved (including databases). All customizing tasks of ICC/BCC can be done with certain
Windows and database rights.
Therefore, an emergency user concept is not applicable. If a user is locked or disabled, a different Windows user,
provided with the needed rights, can carry out the ICC/BCC customizing task.
6.4 Logging of security-relevant events

As ICC/BCC uses the Windows user management, the Windows features can be used to log security events in the
Windows event folder. In order to define which security events should be logged by Windows, you have to implement an
audit policy (see Windows Server 2003 - Security Guide (can be downloaded at http://www.microsoft.com/downloads)
for further information).
The security events occurring with respect to the databases also can be logged to the Windows event log. You just have
to change the settings of the SQL Server instance (for more information, see SQL Server 2005 Security Best Practices
(http://www.microsoft.com/sqlserver/2005/en/us/white-papers.aspx)).
Security-relevant events on the SAP ERP side can be logged using SAP ERP means.

6.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 system. Each time the configuration changes have been finished, the Customizing Client user uploads the
configuration from the development PC to the SAP ERP development system, test system, or production system. Then
the new configuration has to be downloaded from SAP ERP to the test or production Recognition Server.
Thus you can log the application configuration changes on the SAP ERP side using SAP ERP means or you can log the
application configuration changes on the production Recognition Server side using 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 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).
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).
6.6 Encryption of communication channels
6.6.1 Files and databases

By default all network communication in a Windows network is protected by the standard 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).
So, all network communication to file systems and databases in ICC/BCC is protected by IPSec.
6.6.2 SAP ERP

All participants of an ICC/BCC system communicate with the BC Inbound Configuration or the ICC Dispatcher in SAP
ERP 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.

6.7 Secure configuration
ICC/BCC provides a secure configuration by default:
 The application configuration is stored in SAP ERP.
 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 with a prepared SAP ERP user to download the application
configuration.
 The application configuration can be exported from a Recognition Server to SAP ERP using the Customizing
Client. The Customizing Client user has to log in to SAP ERP with a prepared SAP ERP user to upload the
application configuration.
 After the Validation Client user has logged in to SAP ERP, the application configuration is automatically
downloaded to the Validation Client.
 The Validation Client user has to log in to SAP ERP to get invoices to validate. Without logging in to SAP
ERP, the Validation Client user cannot work at all.
 SAP ERP user management controls which invoices a Validation Client user has to validate.
 The Customizing Client user has to log in to SAP ERP to get invoices to validate for testing purposes. Without
logging in to SAP ERP, the Customizing Client user does not get invoices 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 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 Windows group, for example “ICC_BCC users”.
 The heart of an ICC/BCC system, BC Inbound Configuration / ICC Dispatcher, is a SAP ERP component.
 The recognition jobs are managed by BC Inbound Configuration / ICC Dispatcher in SAP ERP.
6.8 Responsibilities
In an ICC/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 an ICC/BCC system there are additional user types and responsibilities. Refer to the VIM
documentation for further information.

7 Glossary of Terms
ACT
Abbreviation of Adaptive Classification Technology
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 have to 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 have to 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.
Adaptive Recognition (ART)

The Recognition Server and the Recognition Nodes have to 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 have to 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.
Application
An application bundles all settings that are needed to process documents of a certain kind, for example which fields have
to be extracted by which extraction method, or which fields should be visible in the Validation Client.
ART
Abbreviation of Adaptive Recognition Technology
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 in many business processes.
Cluster
See Recognition Cluster
ICC/BCC Administrator's Guide Glossary of Terms  83

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.
Content-Based Classification
See Adaptive Classification
Customizing
ICC/BCC provides various settings to adapt the system to customer needs. These customizing settings are bundled in
applications. To customize ICC/BCC for customer needs you have to create applications.
Customizing Client
The Customizing Client is a Windows program that is used on the development system to customize ICC/BCC, that is, to
create and configure applications. It is also used to test applications, to export them to a SAP ERP system, and to import
them on a test or production System. In addition, it is used to monitor and administer an ICC/BCC system.
Document Reader
In an ICC/BCC system the actual data extraction from document images and super-ordinate 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 regularly according to the configuration of the
Hot Spot. During customizing you specify whether vendor 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 regularly according to the configuration of the Hot Spot.
Feedback Link Hot Spot

For each BCC application, a separate SAP Feedback Link Hot Spot is created. This link is used to fetch feedback data
which are collected at the Validation Clients and are used to extract fields automatically, from SAP ERP regularly
according to the configuration of the Hot Spot.
Hot Spot
The Recognition Server uses Hot Spots to fetch recognition jobs, download data, and learning data from its SAP ERP
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. Each application uses Hot Spots of two different types. A SAP Extraction Link is used
to fetch new recognition jobs from SAP ERP. A SAP Download Link is used to fetch new data, such as vendor master
data and purchase order data.
84  Glossary of Terms ICC/BCC Administrator's Guide

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 ICC/BCC has to learn how to fill the field values. The learning data have to 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. Links are implemented
as so-called Hot Spots. The Hot Spots used for the Links connect to SAP ERP regularly at specified times and fetch
available jobs or data.
Load Manager
ICC/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
ICC/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 regularly to free Cluster Nodes for processing.
Purchase Order Data

For an invoice application, ICC/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 have to 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, ICC/BCC can derive the company code and target SAP ERP 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 system names has to be supplied if automatic company
code detection shall be used.
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.

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 ICC/BCC 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. The document is then made available
for Validation.
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 using a 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 ICC/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 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.
Requester Email Data

In an invoice application, ICC/BCC tries to extract the requester email address on invoices. To be able to use this feature,
the expected email addresses have to 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.
Server
See Recognition Server
Standalone System
For development and testing of applications, all components of ICC/BCC can be installed on a standalone system, that is,
on a single computer.
86  Glossary of Terms ICC/BCC Administrator's Guide

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.
Validation
The extracted invoice data can be checked and eventually corrected or completed by a user. The validation facilities of
ICC/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.
Validation Client
The Validation Client is a 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.
Vendor Invoice Management

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

For an invoice application, ICC/BCC periodically loads vendor master data from SAP ERP to its local database using a
SAP Download Link Hot Spot. ICC/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

8 Index
No index entries found.
ICC/BCC Administrator's Guide Index  89

Opentext™ Invoice Capture Center For Sap Solutions Opentext™ Business Center Capture For Sap Solutions

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Opentext™ Invoice Capture Center For Sap Solutions Opentext™ Business Center Capture For Sap Solutions

Încărcat de

Drepturi de autor:

Formate disponibile

OpenText™ Invoice Capture Center for

ICC/BCC Administrator's Guide Contents  iii

3 Installing Single Click Entry for SAPGUI (ICC) 25

iv  Contents ICC/BCC Administrator's Guide

ICC/BCC Administrator's Guide Contents  v

1.2 Functional overview

ICC/BCC Administrator's Guide Introduction  1

2  Introduction ICC/BCC Administrator's Guide

1.4 Components of ICC/BCC

ICC/BCC Administrator's Guide Introduction  3

4  Introduction ICC/BCC Administrator's Guide

1.6 Hot Spots

ICC/BCC Administrator's Guide Introduction  5

6  Introduction ICC/BCC Administrator's Guide

2.1.1 System requirements

ICC/BCC Administrator's Guide Installation  7

SAP GUI is required on Windows 2008 Server 64 bit systems.

2.1.1.3 Database space requirements

8  Installation ICC/BCC Administrator's Guide

2.1.2 Image formats

ICC/BCC Administrator's Guide Installation  9

2.1.3.1 Standalone system

2.1.3.2 Configuration for application development

2.1.3.3 Configuration for application testing

10  Installation ICC/BCC Administrator's Guide

ICC/BCC Administrator's Guide Installation  11

2.1.3.5 Processing different types of documents with ICC

12  Installation ICC/BCC Administrator's Guide

2.2.1 Creating a domain user for Windows services

2.2.2 Installing Microsoft .NET Framework

2.2.3 Installing SAP Connector for Microsoft .NET

To download and install SAP Connector for Microsoft .NET:

2.2.4 Installing Microsoft Visual C++ Redistributables

ICC/BCC Administrator's Guide Installation  13

2.2.6 Installing the Microsoft SQL Server

14  Installation ICC/BCC Administrator's Guide

2.3.1 Stand-alone installation

2.3.2 Installation of the server

ICC/BCC Administrator's Guide Installation  15

2.3.3 Installing a Validation Client

16  Installation ICC/BCC Administrator's Guide

2.3.5 Installing add-ons for Business Capture Center

2.3.6 Creating installation log files

ICC/BCC Administrator's Guide Installation  17

2.4.1 Configuring Vendor Invoice Management (ICC)

2.4.2 Configuring Business Center (BC)

2.4.3 Configuring the archive server

2.4.4 Preparing SAP ERP user accounts

2.4.5 Preparing SAP ERP login data

2.4.6 Creating and configuring applications

18  Installation ICC/BCC Administrator's Guide

2.4.8 Configuring the Windows Firewall for Validation Clients

2.4.9 Configuring SAP GUI

ICC/BCC Administrator's Guide Installation  19

Details about the installed product are then shown:

20  Installation ICC/BCC Administrator's Guide

2.4.11 Upgrading existing applications

2.5 Optional follow-up activities

2.5.1 Moving the caches to a different location

ICC/BCC Administrator's Guide Installation  21

2.6 Installing updates

2.6.1 Installing patches and service packs

22  Installation ICC/BCC Administrator's Guide