Professional Documents
Culture Documents
Fci Installation Manual de - De.en
Fci Installation Manual de - De.en
com
Disclaimer
The information contained in this document is subject to change without prior notice. This
document is made available without any guarantee on the part of FIS regarding the
correctness, completeness and use of the information and data contained therein.
It is for informational purposes only. FIS assumes no liability for errors in or for the
completeness of the document, in particular not for the information, graphics, links or other
information and content contained therein. FIS shall not be liable for any damages, express
or implied, that may result from the use of the document, including but not limited to
merchantability, fitness for a particular purpose, and non-infringement of applicable law,
unless damages are caused by were caused intentionally or through gross negligence on the
part of FIS. This includes in particular direct, special, indirect damage as well as incidental and
consequential damage.
02/01/2022 Page 2 of 28
FIS/fci installation manual
Table of Contents
02/01/2022 Page 3 of 28
FIS/fci installation manual
foreword
The reader
Registered trademarks
FIS/edc and FIS/fci are registered trademarks of FIS GmbH SAP R/3 and
ABAP are registered trademarks of SAP AG, Walldorf.
All other product and brand names are registered or unregistered trademarks of their
respective owners.
A notice:
After the introduction of FIS/fci / FIS/edc, the settings described in this documentation should
only be changed after consultation with the project team at FIS GmbH, as some parameters are
required for a proper process flow.
Editor:
Röthleiner Weg 1
D-97506 Grafenrheinfeld
Web: http://www.fis-gmbh.de
02/01/2022 Page 4 of 28
FIS/fci installation manual
1. General information
Read the current release notes before installing or updating!
02/01/2022 Page 5 of 28
FIS/fci installation manual
2. Requirements
FIS/fci runs on commercially available standard PCs with Windows operating systems. The hardware
and software requirements are listed in the separately available system requirements.
The values listed there are minimum requirements. Depending on the type
of application, faster processors and more RAM can significantly increase the
processing speed.
02/01/2022 Page 6 of 28
FIS/fci installation manual
3. System overview
This diagram represents an example system environment of a typical FIS/fci installation.
02/01/2022 Page 7 of 28
FIS/fci installation manual
4. FIS/fci installation
FIS/fci requires a data provider (backbone) to operate, which manages the individual
processes and their data.
When installing the individual software components, the following sequence should be
observed depending on the data provider.
FciServer:
1. FIS/fci
2. FIS/fci Engines (Management and Discovery Servers)
3. FciServer (management server)
4. FIS/fci demos (optional)
InputAccel:
1. FIS/fci
2. FIS/fci Engines (Management and Discovery Servers)
3. FIS/fci demos (optional)
4. InputAccel Server (Management Server)
5. InputAccel Client
To learn more about installing the Captiva InputAccel components, please refer to the Captiva
installation documentation (located on the installation DVD or on the Captiva website).
4.1. FIS/fci
Installation FIS/fci
02/01/2022 Page 8 of 28
FIS/fci installation manual
5. In the subsequent window, all FIS/fci core components are installed in the default directory
by pressing "Install". In order to keep the package size of the FCI installation manageable,
the recognition engines are stored in a separate setup (seeFIS/fci recognition engines 13).
02/01/2022 Page 9 of 28
FIS/fci installation manual
6. When installing a post-processing station, the display can be expanded by clicking on the
"Options" button. If the DPS module is configured and activated on the administration
server, the "Fully-Qualified Host Name" of the server can be entered here as Configserver.
Otherwise this field should be left blank.
In addition, you can choose between a client or server installation ("Install Client only").
Select the installation directory and then start the installation by clicking on "Install".
02/01/2022 Page 10 of 28
FIS/fci installation manual
7. FIS/fci is now being installed, the progress bar provides information about the status of the
installation. Additional windows are opened during the installation process that must not be closed
manually.
02/01/2022 Page 11 of 28
FIS/fci installation manual
8. The required Microsoft redistributables are automatically installed by the setup. If these
components could be installed successfully, the message "Installed <Version>" appears. If
an error message is listed for a sub-component, the reason for this could be that a newer
version is already available on the system. This situation can be accepted (example see
screenshot below).
02/01/2022 Page 12 of 28
FIS/fci installation manual
The detection engines are installed separately from the FIS/fci setup. They are only required on
the recognition computers.
By default, the engines are installed on the same directory level as FCI:
02/01/2022 Page 13 of 28
FIS/fci installation manual
2. Various requirements are checked and, if necessary, packages such as e.gMicrosoft Visual C++ 2015
Redistributable (x64)installed in the background.
02/01/2022 Page 14 of 28
FIS/fci installation manual
4. Select installation path (it is recommended to keep the default). The installation path is
entered in the Windows registry for later updates.
02/01/2022 Page 15 of 28
FIS/fci installation manual
6. Complete installation
02/01/2022 Page 16 of 28
FIS/fci installation manual
In order to be able to use the individual engines when operating FCI, they
must be licensed or activated via the corresponding feature codes.
With the release of the engines as a separate package, the Kadmos detection
engine has been removed. Make sure that "kadmos" is replaced as the reco
engine in the PGR settings.
02/01/2022 Page 17 of 28
FIS/fci installation manual
If the storage location of the FCI engines deviates from the standard, this path must be
stored in the SMC in the 'local settings'.
The installation of the FIS/fci demos includes some example applications including the standard
FIS/fci process for Captiva InputAccel, which can be used as a template for your own customer-
specific projects. The process definition for the FciServer is already part of the configuration file
(*.cfg) of the application.
02/01/2022 Page 18 of 28
FIS/fci installation manual
02/01/2022 Page 19 of 28
FIS/fci installation manual
You have the option of selecting the installation directory and the applications to be
installed:
02/01/2022 Page 20 of 28
FIS/fci installation manual
02/01/2022 Page 21 of 28
FIS/fci installation manual
Since the Reco engines have been removed from the FCI installation package, the installation of a
post-processing station is simplified and accelerated. Only a normal FIS/fci installation has to be
carried out:
When using an InputAccel server as a data provider, the following component must also
be installed:
4.5.1. requirements
· .NET 4.5:
. \redis\NDP452-KB2901907-x86-x64-AllOS-ENU.exe /q /l dotnetlog.txt /norestart
The following command line (cmd) can be used to install the FIS/fci client components for
running a FIS/fci correction station:
eg
02/01/2022 Page 22 of 28
FIS/fci installation manual
The following command line (cmd) can be used to install the IA Client components to run a
FIS/fci correction station:
See "InputAccel Client Components Installer Properties" in the InputAccel documentation for
more information on this topic.
02/01/2022 Page 23 of 28
FIS/fci installation manual
1. Set providers
2. Setting up the FIS/fci database
3. Setting up the fuzzy server
4. Install and configure process
5. Test process
6. Set up services
1.Set providers
To set the provider, please read the "Provider selection" chapter in the
operating manual.
Also make sure that all required module licenses have been imported (see FIS/fci operating
manual: Chapter Licenses/Import).
A complete FIS/fci database is already included in the scope of installation of the FIS/fci demos,
which contains all suppliers that match the example documents from the example applications.
After installation, the DSN file of the example applications (%FCIAPP%\common\dsn\fcidemo.dsn)
is already configured so that the connection to the Express database is possible directly. The
database is automatically attached to the database server on the first connection attempt via the
"AttachDBFilename" mechanism.
If you do not want to use the supplied database, SQL scripts for creating an empty FIS/fci
database for MSSQL databases are available under %FCIAPP%
\common\database\scripts\<Database>:
a. KB_CreateTables_<Database>.sql
b. KB_CreateViewsProcsTriggers_<Database>.sql
In this case you have to create and configure the DSN connection manually.
To check the functionality of the fuzzy server, the program link %FCIAPP%
\fci_edc\tables\startserver can be run. The fuzzy server should then be started with an
interface. Changes to global parameters of the fuzzy server can be made in the globals.tcl file
if, for example, the DSN file from the FIS/fci demos installation is not to be used.
02/01/2022 Page 24 of 28
FIS/fci installation manual
The course of a recognition run with FIS/fci is based on a process specially created for this
purpose. Accordingly, an FIS/fci process must be installed for each application. To do this,
start the FIS/fci system management console and follow the instructions for loading a process
(see FIS/fci Administration Manual: Chapter Processes).
It may be necessary to adjust some configuration parameters such as the import or export
path.
5. Test process
The module tester in the SMC (FIS/fci system management console) can be used to test the
established process. It offers the option of starting the FIS/fci modules in order to process the
process steps individually and thus ensure functionality. Problems or errors that occur are
displayed directly in the log window (see FIS/fci administration manual: Tester function
group).
When using InputAccel as a data provider, the modules can be operated as a service for
productive FCI operation. To install predefined services, load the SMC configuration file
%FCIAPP%\common\smc\demo.fsc in the SMC under the File / Open menu. All necessary
service definitions should now be loaded under Computer / Services and can be assigned and
then installed (see also FCI Administration Manual: Chapter Services).
The FPM replaces the service operation of the FCI modules by taking over the management and control of
the modules running on the administration and recognition server.
For more information on installing and setting up, see the administration manual FCI
(chapter: FCI Process Monitor).
When using an FciServer as data provider, the operation of the FPM is mandatory.
02/01/2022 Page 25 of 28
FIS/fci installation manual
02/01/2022 Page 26 of 28
FIS/fci installation manual
6. Updates
FIS/fci updates
To update a FIS/fci installation, simply call up the setup of the new version. The update will be
carried out automatically. The prerequisite is that the original installation files have not been
changed. Otherwise the update cannot be carried out correctly, which can lead to a faulty
installation.
When updating the basic component FIS/fci, it may be necessary to update the FIS/fci
recognition engines as well. You can find out about the version dependencies from FIS
Support.
FIS/fci demos
FIS/fci demos should only be updated if the original configuration files have not been
changed. Otherwise the update could be faulty. Since the example applications usually
contain customer-specific adjustments, an update of the FIS/fci demos is generally not
recommended. In order to port old applications to a new FIS/fci version, special update
programs or instructions are made available on request (please always refer to the FIS/fci
Release Notes).
Updates should only be carried out if the original installation files have not
been changed (e.g. TCL files, TCL packages). This leads to an incorrect
installation. In this case, the modified files should be deleted and the
installation repaired.
InputAccel updates
02/01/2022 Page 27 of 28
FIS/fci installation manual
7. Uninstall
The individual software components should be uninstalled via Start / Control Panel / Software.
The order in which the components are uninstalled is irrelevant. The directories and files that
have not been completely removed by the uninstallation can be deleted manually.
The following window shows the FIS/fci uninstallation dialog. FIS/fci can be uninstalled by clicking
on "Uninstall".
Manually deleting any files or folders prior to proper uninstallation may result
in uninstallation failures.
02/01/2022 Page 28 of 28