This document explains the procedure of installing, deploying and managing the T5-MBAP.
The information contained in this document is the proprietary and exclusive property of Tech5 except as otherwise indicated. No part of this document, in whole or in part, maybe reproduced, stored, transmitted, or used for design purposes without the prior written permission of Tech5. The information contained in this document is subject to change without notice. The information in this document is provided for informational purposes only. Tech5 specifically disclaims all warranties, express or limited, including, but not limited, to the implied warranties of merchantability and fitness for a particular purpose, except as provided for in a separate software license agreement.
This document may contain information of a sensitive nature. This information should not be given to persons other than those who are involved in the T5-MBAP or who will become involved during the life cycle.
1.2. T5-MBAP Overview
1.3. MBAP Components OverView
1.3.1. MBAP Components Description
2.1. MBAP Prerequisites
2.2. Java Installation steps
2.3. T5 Biometric SDKs Installation
2.3.1 Face SDK
18.104.22.168. Dependencies Installation
22.214.171.124. FaceSDK Installation
126.96.36.199. License request generation
2.3.2 Finger SDK
188.8.131.52. License request generation
184.108.40.206. SDK Prerequisites
2.3.3 IRIS SDK
220.127.116.11. SDK Prerequisites
2.4. T5 MBAP Installation
2.4.1. MBAP Software Download
2.4.2. MBAP Deployment
Testing MBAP Application
This document is intended to be consumed by Administrators and DevOps teams. It discusses the steps to check and install all the dependencies and components required for deploying fully functional Tech5-MBAP. T5-MBAP is a Multi Biometric Authentication platform primarily designed for a highly efficient and scalable 1:1 search engine.
This is an authentication platform of all three Biometric modalities like Face, Finger & Iris. MBAP is designed to do Authentication/Verification of any or all three modalities. It works with the cache db files that are generated by the T5-ABIS Search Engine. All the data enrolled in T5-ABIS Cache can be Verified using MBAP(when used with T5-ABIS). If T5-MBAP is used as individual component, you can enroll & verify records.
Check which version of Java is running on the servers:
If Java is not installed, proceed and download Java software. I we should unlink OpenJDK and before install SunJDK.
# java -version openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-b12) OpenJDK 64-Bit Server VM (build 25.191-b12, mixed mode)
Unlink OpenJDK by from /usr/bin/java as shown below:
# whereis java java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java/usr/share/man/man1/java.1.gz # unlink /usr/bin/java
Now download Java Runtime Environment and install Java as shown below:
# curl -L -b "oraclelicense=1" d.oracle.com/otn-pub/java/jdk/8u201-b09/42970487e3af4f5aa5bca3f542482c60/jre-8u201-linux-x64.tar.gz-O
And install this version of JRE and check the Java version once again.
#java -version java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
Following dependencies of Face/Finger/Iris SDKs depending on the modalities used should be installed.
Following packages are required for the FaceSDK to and should be installed on all the nodes on which Face modality will be configured.
All the packages are available in EPEL and Default packages if you are using CentOS.Incase of RHEL, rhel-7-server-optional-rpms and epel must be activated on Repo list.
$ yum -y install epel-release && yum install -y opencv openblas-serial lapack libgomp
boost-system boost-filesystem boost-program-options
#yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Download the FaceSDK RPMs from below URL:
Note: Please send an email to get the FTP credentials to download our SDK to email@example.com
Lets create a directory and download software to it.
# mkdir /opt/Tech5/software # cd /opt/Tech5/software/ # wget --ask-password ftp://ftp.tech5.tech/T5-FaceSDK_1.5/*
Once the RPMs are downloaded, use the script to install all these RPMs one by one as shown:
#cat InstallFaceRPMs.sh yum -y localinstall tech5-face_sdk-cpu-1.5-0.x86_64.rpm yum -y localinstall tech5-face_sdk-cpu-devel-1.5-0.x86_64.rpm yum -y localinstall tech5-face_sdk-age_gender_100-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-alignment_100-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-alignment_101-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-alignment_102-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-alignment_103-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-builder_100-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-builder_101-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-builder_102-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-builder_103-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-builder_104-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-face_detector_100-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-face_detector_101-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-face_detector_102-1.5-0.noarch.rpm yum -y localinstall tech5-face_sdk-face_detector_103-1.5-0.noarch.rpm
After the installation of above packages is complete, you should be able to see if the version of below:
# face_sdk_utils --version Face SDK utils. Version 1.5 XUXU(d350a6bf94c57d551ef00e724bfbd0bbcea4f8fc)
It confirms that Face SDK version 1.5 is installed successfully.
Run the below command to generate License request for FaceSDK and send it to Tech5 team,they will send the license file:
# /usr/bin/face_sdk_utils --request --out $HOME/face_sdk.req
We will send the face_sdk.lic file and that has to be copied into the folder /usr/share/face_sdk.
face_sdk_utils script requires read access to product_uuid attribute on device dmi/id (usually it is this /sys/devices/virtual/dmi/id/product_uuid file) for the util to work without errors.
We should create a License request for Finger SDK using the below steps.
Download License ReqGen from below URL:
License Generation Process:
Extract the LicGen files and run it on the Linux box where ABIS Finger will be deployed. We can generate 4 different licenses with this LicGen depending on the requirement. If you are looking for Finger ABIS license or Finger MBAP (1:1) license, depending on it generate license. For Testing we recommend to use trial licenses and for production environment you can request for
Matcher Pro licenses. Functionality wise both are same, Pro licenses are more binded to Hardware…
License Request for 1:1 Authentication Matcher Trial version:
This will generate tech5_auth_matcher_trial.srl license request file, please send it to us.
License Request for 1:1 Authentication Matcher Pro version:
This will generate tech5_auth_matcher.srl license request file, please send it to us.
License Request for 1:N Matcher Trial version:
This will generate tech5_gallery_matcher_trial.srl license request file, please send it to us.
License Request for 1:N Matcher Pro version:
This will generate tech5_gallery_matcher.srl license request file, please send it to us.
We will be sending the .lic file which has to be copied to the FingerABIS server and mention it in the configuration parameters.
18.104.22.168. No Special dependencies for finger SDK
We should install these package in the Iris Nodes for the IRIS SDK to work. We can get it from EPEL packages
in CentOS and from Optional pages for RHEL.
yum install -y libtiff libwebp jasper-libs ilmbase OpenEXR-libs
Get the copy of T5-MBAP software from the below drive url:
Download the software to Tech5 folder in /opt partition. This has to be done on all the servers where ever MBAP will be running.
# mkdir /opt/Tech5
Then Extract the tar file
# cd /opt/Tech5/ # tar xzf T5-MBAP-1.7_27thAug2019.tar.gz
This will extract all the ABIS containers to /opt/Tech5/T5-MBAP folder. Now we should create a cache folder(if it does not exists). Cache folder will be used to store Face/Iris/Finger cache.
# mkdir /opt/Tech5/T5-MBAP/cache
Get the IP addresses of the MBAP server. Then add the IP address and hostname of the host in the /etc/hosts file as shown in the below example:
Example of /etc/hosts file
# cat /etc/hosts ####### Master, DB and BMW Nodes ########## 192.168.234.2 rac1-c3-b01-master01 192.168.234.14 rac2-c3-b01-master02 192.168.234.26 rac3-c3-b01-master03 ####### Finger Nodes ###################### 192.168.234.3 rac1-c3-b02-fmat01 192.168.234.15 rac2-c3-b02-ftc01 192.168.234.23 rac2-c3-b11-fintc01 192.168.234.29 rac3-c3-b04-fintc02
After editing the hosts file, you should be able to ping MBAP node using its hostname.
Once after the software is downloaded and copied to the specified folder, we should now
change few settings in the configurations folder before starting the application.
a) Edit the cloud.properties file present in Conf folder and edit MBAP cache paths & logs path:
# vi /opt/Tech5/T5-MBAP/conf/cloud.properties logPath=/opt/Tech5/T5-MBAP/logs cachePath=/opt/Tech5/T5-MBAP/cache
b) After these two configuration files are updated, we should export the LD Library paths
and Native folder path of MBAP application like this:
# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib/:/usr/lib64/:/usr/lib/:/usr/local/li b64/:/opt/Tech5/T5-MBAP/native:
c) Now we can start the application by starting catalina.sh script in the bin folder as:
# cd /opt/Tech5/T5-MBAP/bin/ # sh catalina.sh start
d) We have to check the logs for MBAP application during startup to check if there are any
issues with the license or dependencies or something else and logs can be checked like:
# tail -F /opt/Tech5/T5-MBAP/logs/idAuthService.log.0 # tail -F /opt/Tech5/T5-MBAP/logs/catalina.out
e) Log should indicate that the Service got started without any issue and are in Ready
state. This confirms that the deployment process is completed successfully.
f) We should be able to access the Status page with the URL:
g) All the API calls can be sent to these URLs:
● Biometric Verification
● Verify with NIK