Content Comparison

This is a step-by-step guide on how to configure the tech5 Windows Biosdk with the registration client.

Tech5 Windows Client OmniMatch BioSDK(v5.0.0):

\uD83D\uDCD8 Instructions

1. Compress the tech5 jars into a single zip file and name it sdkDependecy.zip.

2. Go to the Mosip artifactory project, navigate to the directory “artifactory-ref-impl/artifacts/src/sdk/” and create a new folder named tech5. Under this folder add the zip file created in Step #1.

3. Modify the artifactory project’s docker file to include the path of the sdkDependecy zipped folder. I.e add the following code to the docker file.

   Code Block
   # environment variable for tech5 jar path ENV tech5_zip_path=${base_path}/libs-release-local/sdk/tech5 COPY /src/sdk/tech5/* ${tech5_zip_path}/

4. Build and deploy the artifactory project and Restart the artifactory server in Rancher.

5. Next in the registration client deployment .yml file, add the name and URL of the tech5 SDK to the environment list.
   

   Image Added

6. Build and deploy the registration client and Restart the registration-service in Rancher.

7. Obtain the native tech5 folder and extract it.

8. Copy the folder path of the extracted folder in Step #7 and add it to your windows system environment variables inside the path as shown in the image

Example:
D:\MOSIP\Mosip Environment\Native\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK

D:\MOSIP\Mosip Environment\Native\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK\bin

D:\MOSIP\Mosip Environment\Native\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK\lib

...

9. To use the T5-BioSDK, system must have valid license. Follow below steps to create license requests.

• Go to the location of tech5 biosdk -> inside bin folder → open the path in the command prompt:
  Example :   D:\MOSIP\Mosip Environment\Native\Tech5 Windows SDK\Tech5\T5OmniMatchBioSDK\bin 

• Run this command t5omnimatch_sdk_utility_x64.exe as shown in the image

• In the output you will find the command to generate the request file,copy the command t5omnimatch_sdk_utility_x64.exe –request

• Image Added

• Run the command t5omnimatch_sdk_utility_x64.exe –request inside the path of bin folder to get the request file.

  Image Added

...

• Send the request files to TECH5 team to get the licenses.

10. Place the  config.properties (Take the config properties from tech5 native folder) and license file to the root folder of the registration client.
    

    Image Added

11. Inside the config.properties change the folder path and licence file path and save.
    

    Image Added

12. Modify the run.bat file with tech5 biosdk path as shown below.(Replace entire run.bat file with below content).

    Code Block

    @echo off if exist .UNKNOWN_JARS ( FOR /F "tokens=* delims=" %%x in (.UNKNOWN_JARS) DO DEL /Q lib\%%x ) if exist .TEMP ( echo Starting Registration Client after Upgrade xcopy /f/k/y/v/q .TEMP lib && rmdir /s /q .TEMP && start jre\bin\javaw -Xmx2048m -Xms2048m -Dai.tech5.biosdk.provider.config=./config.properties -DuseMosipLogger=true -Dfile.encoding=UTF-8 -cp lib/*;/* io.mosip.registration.controller.Initialization > startup.log 2>&1 ) else ( echo Starting Registration Client start jre\bin\javaw -Xmx2048m -Xms2048m -Dfile.encoding=UTF-8 -Dai.tech5.biosdk.provider.config=./config.properties -DuseMosipLogger=true -cp lib/*;/* io.mosip.registration.controller.Initialization > startup.log 2>&1 )

13. Modify the properties in the mosip-config repository, registration-default.properties to enable local deduplication and then restart the config server in the rancher.

    Code Block

    mosip.biometric.sdk.providers.finger.tech5.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider mosip.biometric.sdk.providers.finger.tech5.version=0.9 mosip.biometric.sdk.providers.finger.tech5.args= mosip.biometric.sdk.providers.finger.tech5.threshold=60 mosip.biometric.sdk.providers.iris.tech5.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider mosip.biometric.sdk.providers.iris.tech5.version=0.9 mosip.biometric.sdk.providers.iris.tech5.args= mosip.biometric.sdk.providers.iris.tech5.threshold=60 mosip.biometric.sdk.providers.face.tech5.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider mosip.biometric.sdk.providers.face.tech5.version=0.9 mosip.biometric.sdk.providers.face.tech5.args= mosip.biometric.sdk.providers.face.tech5.threshold=60 mosip.biometric.sdk.provider.finger.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider mosip.biometric.sdk.provider.iris.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider mosip.biometric.sdk.provider.face.classname=ai.tech5.mosip.biosdk.provider.OmniMatchBioSDKProvider mosip.registration.mds.deduplication.enable.flag=Y

...

Tech5 Windows Client BioSDK(v4.3.0):

\uD83D\uDCD8 Instructions

14. Compress the tech5 jars into a single zip file and name it sdkDependecy.zip.

15. Go to the Mosip artifactory project, navigate to the directory “artifactory-ref-impl/artifacts/src/sdk/” and create a new folder named tech5. Under this folder add the zip file created in Step #1.

16. Modify the artifactory project’s docker file to include the path of the sdkDependecy zipped folder. I.e add the following code to the docker file.

    Code Block
    # environment variable for tech5 jar path ENV tech5_zip_path=${base_path}/libs-release-local/sdk/tech5 COPY /src/sdk/tech5/* ${tech5_zip_path}/

17. Build and deploy the artifactory project.

18. Next in the registration client deployment .yml file, add the name and URL of the tech5 SDK to the environment list.

    Image Modified

19. Build and deploy the registration client.

20. Obtain the native tech5 folder and extract it.

21. Copy the folder path of the extracted folder in Step #7 and add it to your windows system environment variables list with under a new variable named FACE_SDK_BIN_ROOT.

    Image Modified

22. To use the T5-BioSDK, system must have valid license. Follow below steps to create license requests.
    
    Open the command prompt and run the below command to generate the face & finger license request files

    Code Block
    face_sdk_utils --request --out TPM_new_face_sdk.req fingersdk_utils --request --output TPM_new_finger_sdk.req

...

...

\uD83D\uDCCB Related articles