B-COMM 3.10.0 Installation Manual
B-COMM 3.10.0 Installation Manual
All rights reserved. The document and its parts are copyrighted. Only Kaba GmbH has the right to
commercialize, market and distribute this document. This document, or any part of it, may not be copied
or reproduced, adapted, arranged, reworked or modified without the prior consent of Kaba GmbH.
All company, trademark or product names are trademarks or registered trademarks of their respective
owners and are protected.
1 Installation ...............................................................................................................................7
1.1 Hardware requirements ..................................................................................................7
1.2 Java and .NET Framework environment ........................................................................7
1.3 ARIOS-components/CardLink ........................................................................................8
1.4 Overview on software requirements ...............................................................................8
1.5 Selecting the "Common" or "Separate" installation type ................................................9
1.5.1 "Common" type of installation ............................................................................9
1.5.2 "Separate" type of installation (predefined data directory).................................9
1.5.3 "Separate" type of installation (selectable data directory)................................10
1.6 Installation examples ....................................................................................................11
1.6.1 Installation example 1: Server and GUI on one computer: ..............................11
1.6.2 Installation example 2: Server and GUI on 2 computers .................................12
1.6.3 Installation example 3: Server and GUI on 2 computers with Java application13
1.7 Installation in Windows operating systems...................................................................14
1.7.1 Selecting the installation routine ......................................................................14
1.7.2 Biometrics: installing Morpho biometrics software ...........................................30
1.7.3 Biometrics: MS Visual Studio Runtime.............................................................38
1.7.4 Checking the data execution prevention (DEP) ...............................................39
1.7.5 Biometrics: B-COMM settings ..........................................................................40
1.7.6 Biometrics: checking the installation ................................................................41
1.8 Installation in Unix/Linux and OS/400 operating systems ............................................42
1.8.1 Biometric enrollment under Linux.....................................................................43
1.9 Additional information about installation .......................................................................44
1.9.1 Update ..............................................................................................................44
1.9.2 Uninstalling B-COMM.......................................................................................44
1.9.3 Uninstalling Morpho software...........................................................................44
1.9.4 Services............................................................................................................45
1.9.5 Ports used in default configuration...................................................................45
1.9.6 Scanning viruses ..............................................................................................46
1.10 Data execution prevention ............................................................................................46
1.10.1 Deactivate the data execution prevention ........................................................46
1.10.2 Activate the data execution prevention again ..................................................47
1.10.3 Defining exceptions of the data execution prevention .....................................47
1.10.4 Reboot..............................................................................................................47
2 Index.......................................................................................................................................48
Reference Manual Vers. 3.10.0 Installation instruction General information
B-COMM
Pos: 1 /Software-Handbcher/B-COMM Java Installation/Allgemeines und einleitende Kapitel @ 6\mod_1268299965438_2.doc @ 23244 @ 12222222 @ 1
1 General information
1.1 About this manual
1.2 Validity
1.3 Addressees
Listed below are the most important changes and additions compared to the last
edition of the B-COMM manual:
Automated handling of the DEP procedures.
This manual contains the following orientation guides to find specific topics more
easily:
The table of contents at the beginning of the manual gives an overview of all
treated topics.
The header of each page contains the corresponding title of the chapter.
An index in alphabetical order can be found at the end of the manual.
Please pay special attention to the remarks that are marked with symbols. The
symbols used in this manual have the following meaning:
Remark
Tips and useful information. This information will help you to best use the
product and its functionality.
NOTICE!
Important information for a proper handling of the product. Ignoring this
Pos: 2 /=====Seitenumbruch===== @ 0\mod32_2.doc @ 444 @ @ 1
information can cause device malfunction.
1 Installation
1.1 Hardware requirements
These indications refer only to the B-COMM installation. This does not include the
memory size required by the Java environment JRE, the operating system and
other applications.
For the running operation, we cannot clearly specify the required memory size as it
depends on several factors. These include:
Booking volume
Installed components
Generation of mirror files
Debug level and others.
NOTICE!
The performance of JRE must match the performance of the corresponding version
of Sun microelectronics.
1.3 ARIOS-components/CardLink
Important!
The .NET Framework 4.0 version does not completely replace the previous
versions. Therefore, the installation of a single .NET Framework 4.0 is not enough
for certain functions, see table below.
Which type of installation is used depends on your operating system and the
allocation of rights on the system.
This type of installation is especially meant for cluster installations to store the
configuration data, for example, on a mapped directory.
B-COMM Server and B-COMM GUI are installed on one computer. In addition, an
application for data evaluation is installed on the same computer.
RMI TCP/IP
B-COMM Server BCOMMHelper
bcommjava.ini
bclan01.ini
bclan02.ini
Configuration files
An application that was not programmed in Java can communicate with B-COMM
Server with the help of the program module B-COMM Helper.
Please see the B-COMM manual for more detailed information about the program
module B-COMM Helper.
B-COMM Server and B-COMM GUI are installed on two different computers. In
addition, an application that is not written in Java is installed on another computer
for data evaluation.
Computer 1 Computer 2
RMI
Computer 3
B-COMM GUI
(Configuration
program)
bcommjava.ini
bclan01.ini
bclan02.ini
Configuration files
An application that was not programmed in Java can communicate with B-COMM
Server with the help of the program module B-COMM Helper.
Please see the B-COMM manual for more detailed information about the program
module B-COMM Helper.
1.6.3 Installation example 3: Server and GUI on 2 computers with Java application
B-COMM Server and B-COMM GUI are installed on several computers. In addition,
an application written in Java is installed on another computer for data evaluation.
Computer 1 Computer 2
RMI
B-COMM Server
RMI
Computer 3
B-COMM GUI
(Configuration-
program)
bcommjava.ini
Computer 4
bclan02.ini
Configuration files
An application that was programmed in Java can communicate directly with the
B-COMM Server via RMI. The program module B-COMM Helper is not required in
this case.
Important!
If the biometric functionality shall be installed, the data execution prevention must
be disabled, see chapter 1.10.
Operating systems Vista, WIN7, Server 2008/2003 and Windows XP with .NET
Framework
The installation routine instBCOMM.exe requires .NET Framework version 2.0.
and higher.
Remark
When using WIN7 64 bit together with Java 32 bit, the path to the java.exe file must
be set in the Path environment variable (e.g. C:\Programs\Java\jre7\bin).
Remark
If there is an existing .NET Framework, you will find it under StartSystem
ControlSoftware (Example for Windows XP).
After selecting the installation routine by double-click, the installation will start
automatically. The following example refers to the "Separate" installation; we also
recommend it as default installation.
Select the language for installation. It is the language in which the texts are
displayed during setup. Currently, German and English are supported only.
The labeling of the buttons depends on the language of the operating system.
Please confirm by pressing "Next".
The following screen shows additional information for setup. Please read these
notes carefully.
Confirm by pressing Next.
Select the target directory for the program files. The default target directory is
<program files of the operating system>/Kaba/B-COMM Java.
Accept the default value or enter your own path. As the Installer will not memorize
the directory selected for installation, the default directory is also proposed during
an update. In this case, enter the desired target directory when updating.
Confirm by pressing Next.
Fig. 10: Program installation: Selecting the directory for the program files.
Fig. 11: Program installation: Selecting the directory for the configuration files.
Remark
The installation routine of Morpho needs about 1 minute for loading. Do not start
or cancel any other function during this time. The installation procedure
explained in this document must be strictly adhered to!
Fig. 13: Program installation: Selecting Sagem Morphokit for biometric functions.
Under the Windows operating systems, you may select whether you want to create
shortcuts to individual B-COMM components in the start menu.
The shortcuts may be created for the following components:
B-COMM Server
B-COMM GUI
B-COMM ServiceManager
B-COMM Starter
B-COMM TerminalStatus
Adding users to the Dcc service group manually for WIN 7 and Windows
Vista
Search for local in the start menu search field. In this way, the correct link to Edit
local users and groups is displayed.
Select the Edit local users and groups menu.
Fig. 18: Opening the Edit local users and groups menu
Under Groups, you will find the DccService group created by the Installer.
Double click to open the following window.
Windows XP procedure
1. If the check box is ticked, a DccService user group will be generated
automatically during installation.
2. The Dcc web service URL must be registered manually and
permanently by means of a tool.
See description in the following step-by-step instructions, items 1 - 9.
3. The corresponding users must be included manually in the
DccService user group after installation.
This allows the users to obtain the necessary rights.
See description in the following step-by-step instructions,
items 10 - 11.
The DccService for limited users under Windows XP is executed from the
installation CD by means of a tool. This HttpNamespaceManager.exe tool must
be copied to the local drive if necessary.
The tool requires at least .Net-Framework 3.0 as program environment.
10. The setup created automatically a Call via: Start => Control Panel=>
new DccService user group. Administration => Computer Management,
then System => Local users and groups.
11. Add the user or users with limited Add the user(s) via the New user context
rights to the user group. menu (right mouse button).
This dialog shows the installation progress. The currently processed component is
indicated by a green dot.
You will get more details about the installation progress in the details mask.
Fig. 25: Program installation: Displaying details about the installation progress.
A message confirms that the installation has been completed successfully. The
installation is completed.
NOTICE!
Before installing make sure that
all older versions have been uninstalled completely from the target system
plugged-in Morpho dongles have been unplugged before installing
no reader (MSO 300 or MSO 1300) is plugged in.
The installation routine of Morpho needs about 1 minute for loading. Do not start
or cancel any other function during this time. The installation procedure
explained in this document must be strictly adhered to!
The biometrics software from Morpho is required for enrolling finger templates
using the readers
MSO 300 (from firmware version 8.04) or
MSO 1300
Remark
When installing B-COMM under a Windows 64-bit systen, also the 64-bit Java JRE
should be used.
The installation procedure depends largely on the type and extent of the existing
system environment. The following figure shows an overview of the installation
procedure under different start conditions. Some of the components are installed
automatically.
Before finishing the B-COMM installation, the mask for Morpho biometrics software
installation is automatically displayed provided the corresponding check box has
been ticked when installing B-COMM. This mask includes the actual biometrics
software and drivers for Microsoft Visual Studio.
The selection and installation of the individual components depends on the system
environment and must be specified for each single case; please see the figure in
chapter 1.7.2.2.
Fig. 28: Biometrics installation: Uninstall hint for Morpho enrollment software.
Fig. 29: Biometrics installation: This dialog shows the installation progress.
The installation of the license files ist finished after a short delay time.
Please confirm with Close.
The installation of the drivers starts automatically.
During the biometrics software installation, the drivers for the biometric readers are
installed first.
Follow the instructions on the screen during the installation.
The installation of the driver files ist finished after a short delay time.
Please confirm with Finish.
The installation of the Microsoft Visual Studio runtime starts automatically.
Microsoft Visual Studio 2005 must be installed if not existing on the target system.
The software is necessary for visualization of the fingerprints during the enrollment
process.
The installation starts automatically. Its just a short installation procedure without
any feedback messages.
Due to technical reasons the screenshots are in German.
As final step of the installation of the biometric features, a check of the data
execution prevention status is performed.
Background
In various Windows operating systems, a data execution protection is
implemented. By default, the DEP is activated in several operating systems, e.g.
Windows Vista and Windows 7. The check of the data execution prevention status
is used to determine the active status of the DEP on the target system and its
settings.
Check result
The check result is displayed as so-called DEP level in a certain mask. Depending
on the result, the actions to be taken are displayed as well.
After having installed all biometric components, make the required settings in
B-COMM.
The starts summarized in the following are valid for installations in which the
Installer finds Java JRE without problems.
Operating system Common Separate Installation routine
Unix/Linux with Yes Yes instBCOMM.sh
graphical interface
The installation is menu-guided,
similar to installation in
Windows operating systems.
Unix/Linux without Yes Yes instBCOMMConsole.sh
graphical interface
The installation is text-based.
OS/400 Yes Yes Enter the following in the
command interface:
java -jar"B-COMM-installer.jar"
text
The installation is text-based.
If Java Runtime is not automatically found by the Installer (an error message is
prompted), the path must be specified when starting the installation.
When using the Sagem enrollment functions under Linux operating systems, the
following hints must be observed.
Supported Linux distributions
Slackware 13.37
Slackware 13.37/64 mit multiLib
CentOS 5.7. SDL_TTF and SDL_image must be installed manually.
CentOS 5.7/64. SDL_TTF und SDL_image must be installed manually.
Ubuntu 10.04
openSuSE 11.4
For every used Linux distribution the following libraries are necessary. Note: Even
for the 64 bit operating systems the 32 bit versions of the libraries must be used!
1.9.1 Update
B-COMM installation files are used both for new installations and for updating
existing installations. If it is necessary to update any existing B-COMM installation,
you may do so by starting a new setup. The existing configurations are taken
without changes and used with the new version.
Before you update this software, please consider the following:
A running B-COMM software must be terminated before updating. All running
B-COMM services must be stopped.
As the Installer will not memorize the directory selected for installation, the
default directory is also proposed during an update. In this case, enter the
desired target directory when updating.
We recommend to deinstall all Sagem and Morpho components via the system
control menu of the computer before updating them. Doing this way you avoid to
run the installation routine twice (deinstallation and updating). This affects the
following components:
MorphoSmart SDK
MorphoKit x.x.x
Morpho Morphosmart USB Drivers
Morpho Scurit Licence Protection
The installation of B-COMM does not create any entries in the Windows registry.
For uninstalling, just delete the B-COMM directories and any existing shortcuts in
the start menu.
For uninstalling the Morpho biometric software, the data execution prevention must
be deactivated.
1.9.4 Services
Make sure to observe the following when creating services under the operating
systems Windows Vista, Windows 7 and Server 2008:
The wrapper file in the B-COMM directory must have administrator rights (right-click
on file Properties Compatibility Execute program as administrator). The
following wrapper files are available:
32-bit operating systems: wrapper-windows-x86-32.exe
64-bit operating systems: wrapper-windows-x86-64.exe
Performance losses may occur if virus scans of B-COMM directories take place in
a running system.
It is recommended to exclude the B-COMM data directories from an automatic
virus scan.
Caution
Incompatibilities between computer hardware and operating system.
After deactivating the data execution prevention the computer may be unable to
boot.
Before deactivating the data execution prevention please make sure if relating hints
do exist or contact the hardware manufacturer.
This problem is not caused by any Kaba product or system!
If the data execution prevention shall be reactivated after finishing the installation
completely, some exceptions must take place. The reactivation can be done via
the command box again:
1. Requires administrator rights (StartOpen the command line cmdOpen the
context menu via right mouse button Select Run as administrator).
2. Open the command box StartExecute
3. Launch the following command: bcdedit /set nx OptOut.
4. Confirm with OK.
5. Reboot the system.
6. Define the exceptions of the data execution prevention.
The following files must be excepted from the data execution prevention:
templ_conv.exe (B-COMM directory)
SagemSecurite_Licence_Protection.exe (\SagemSecurite\LicenceProtection)
SagemSecurite_Licence_Manager.exe (\SagemSecurite\LicenceProtection)
1.10.4 Reboot
2 Index
CardLink ...............................................................8 P