Skip to main content
Kofax

Installation and configuration steps for FraudOne Release 4.4

Summary

The below described steps describes the initial installation and configuration of FraudOne based on the initial shipment from Kofax eDelivery Website. After you followed the instruction you will have a running FraudOne environment. This approach is premised on IBM DB2 Database. 13675

Overview:

Step 1: Prerequisites
Step 2-20: Download, Basic Installation, AdminClient
Step 21-44: Configuration of SignBase, AttachManager, ServerManager
Step 45-77: Configuration of WFRouter, CRS
Step 78-124: Configuration of SignCheck, ASV
Step 125–132: Configuration of JavaClient
Step 133- 147: Configuration of Getter

  1. Prerequisites needed to follow the next 147 steps:
    (As in the Release 44 Installation guideline described)
    1. A suitable DB2 ODBC and JDBC driver is installed
    2. Java SE 1.8 (32bit and 64bit) is installed
    3. The DB2 Database is preconfigured
    4. Administrative rights are granted to the user performing the installation
  2. Download the FraudOne Release 44 from Kofax eDelivery Website @ https://delivery.kofax.com (“FraudOne 4.4.0 for DB2 ZIP”)
  3. Unpack C:\downloads\FraudOne_4.4.0_for DB2.zip to E:\FraudOne for DB2
  4. Create a target directory E:\FraudOne-RTM
  5. Create subdirectories for the corresponding installations:
    1. AdminClient
    2. JavaClient
    3. Server
    4. ServerMonitor
  6. Open a Windows command line window and switch to “E:\FraudOne for DB2”
  7. Run the commands
    1. InstAdminClient.cmd E:\FraudOne-RTM\AdminClient
    2. InstDBScripts.cmd E:\FraudOne-RTM\Server
    3. InstJClient.cmd E:\FraudOne-RTM\JavaClient
    4. InstLicense.cmd E:\FraudOne-RTM\Server
    5. InstServer.cmd E:\FraudOne-RTM\Server
    6. InstSrvMon.cmd E:\FraudOne-RTM\ServerMonitor
  8. Switch to E:\FraudOne-RTM\Server\SignPlus\Scripts to configure the database initialization
  9. 9. Edit SBDebTab.cmd, add the correct path for the DB2 JDBC Jar files
    @java -classpath DDLGenerator.jar;.;%DB2UDBCP% SBDebTab %*
  10. Repeat the edit for SCDebTab.cmd
    @java -classpath DDLGenerator.jar;.;%DB2UDBCP% SCDebTab %*
  11. Edit SBDebTab.properties, check and set following parameters
    DisplayOnly=No
    #TargetDBMS = DB2ZOS
    TargetDBMS = DB2UDBSBCS
    #TargetDBMS = ORACLE
    #TargetDBMS = MSSQL
    DBSchema=R44
  12. Edit SCDebTab.properties, check and set following parameters
    DisplayOnly=No
    #TargetDBMS = DB2ZOS TargetDBMS = DB2UDBSBCS
    #TargetDBMS = ORACLE
    #TargetDBMS = MSSQL
    DBSchema=R44
  13. Select the 64-bit Java virtual machine (please adjust to your system)
    set path=c:\Java64\jdk1.8.0_60\bin;%path%

    Hint: you can also use a 32bit JVM if you make step 14 and 15 with type 4 URLS: SBDEBTab.cmd –d //<db2-server>:<db2-port>/<dbname>

  14. Initialise the SignBase database (Assumes that database has been created, user and passwort are set on DB2-Server)
    SBDebTab.cmd -d R44TRAIN -u spadmins -x 3wayxcft
  15. Initialise the SignCheck database (Assumes that database has been created, user and passwort are set on DB2-Server)
    SCDebTab.cmd -d R44TRAIN -u spadmins -x 3wayxcft
  16. Switch to the FraudOne Server directory (cd ..)
  17. Initialize the configuration registry for the local server
    SetupCfg.cmd -initlocal %COMPUTERNAME% :2000 R44TRAIN
    Provide a DATABASE user-id and password when prompted (signplus/signplus)
  18. Start the default server configuration to get a SignBase configuration server start SRVMNGR4.exe
  19. Load the base configuration package into the database SetupCfg.cmd -importworkspace FraudOneBaseConfiguration.zip clear *:* samples:Samples Provide the FraudOne super-user when prompted (softpro/any)
  20. Close the command line window to drop the path to the 64-Bit JVM
  21. Open a new command line window
  22. Switch to E:\FraudOne-RTM\AdminClient\SignPlus
  23. Start the Admin Client
    adminClient.cmd
  24. Open the configuration files editor Menu: Admin -> System Configuration
  25. Select Instance Type “adminclient” and File “admin.properties” and open the editor window for the file
  26. Add the customer’s BNO to the BNO.List parameter. for example
    BNO.List = 999 001 002
  27. Configure the Global Fraud Signatures and RuleBlock editing features (disabled by default). Add the lines
    CRS_Editor.RuleBlocks.Enabled = 1
    Blacklist.GlobalFraudSignatureList.Visible = 1
  28. Save the changed file and close the editor
  29. Apply the changes
  30. Stop and restart the Admin Client
  31. Add a SrvMngr4.ini common section.
    Assumes you choose R44-905 as Machine name. Please see step 17
    Machine R44-905, Instance Type ServerManager, Instance Name *) Contents as documented (see Admin Guide) for configuration parameters
    Locale=English_United States
    Database=R44TRAIN
    SBSchema=R44
    Userid=signplus
    Password=signplus
    SignSec=Y
    SignBase=U
    ForwardOnlyCursors=No
    HistoriseAImages=Y
    Schedule=N
    SchemaFile=crs.xsd
    ICUConverter.999=Cp1252
    ICULocale.999=en_US
    ICUAlias.999=999
    SharedPath=.\shared
  32. Add the Address Map entries Instance Type SignBaseServer Instance Name * and Instance Type AttachManager Instance Name SignBase to this common section map
  33. Save the file element
  34. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type ServerManager, Instance Name *) for configuration parameters
    Name=Monitor1
    LogFile=.\logs\DB2-Monitor.log
    StatFile=.\logs\DB2-Stat.log
    Debug=N
  35. Save the file element. Notice that the Address Map for the Server Manager now shows “both”.
  36. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type AttachManager, Instance Name SignBase) for configuration parameters
    Program=attman5.exe
    Group=SignBase
    Port=2000
    ShowMode=0
  37. Save the file element. Notice that the Address Map for the SignBase Attach Manager now shows “both”.
  38. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type SignBaseServer, Instance Name *) for configuration parameters
    Program=sb1.exe
    Group=SignBase
    ShowMode=0
    MsgTypeList=AA,A8,A9,00,02,10,11,12,14,15,16,17,18,19,1A,1B,1C,1D,1E,1F
    SignSec=Yes
  39. Save the file element. Notice that the Address Map for the SignBaseServer now shows “both”.
  40. Apply the configuration file changes
  41. Using the topography editor, add a SignBase Server record to start 4 from 6 SignBase Server instances as configuration servers using the prefix “SB-Server-“ (right mouse click -> Add component)
  42. Save the changed topography
  43. Stop the Admin Client
  44. Stop and restart the Server Manager process
  45. Start the Admin Client and log on
  46. Edit any of the SrvMngr4.ini common sections
  47. Add an address map for Machine R44-905, Instance Type WorkflowRouter, Instance Name WFRouter
  48. Save the common section
  49. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type WorkflowRouter, Instance Name WFRouter) for configuration parameters
    Program=WFRouter.exe
    Group=Workflow
    ShowMode=0
    ConfigFile=WFRouter.ini 
    CRSRuleFile=crs.xml
    SignCheck=Yes
    CRSSchemaFile=crs.xsd
  50. Save the private section
  51. Add a WFRouter.ini private section (Machine R44-905, Instance Type WorkflowRouter, Instance Name WFRouter)
    LockTimeout=300
    PriorityBoostTimeout=86400
    PriorityBoostRefresh=86400
    SanityCheckRefresh=600
    CommitCount=1
    UsePriority=0
  52. Save the private section and apply the changes to the database
  53. Change to the CRS editor and create your rules graph
  54. When the graph is complete use “Save As” to save it AS SOMETHING OTHER THAN “crs.xml”. (This gives it the “active” alias of “crs.xml” we used above.) e.e DEMOWF.xml
  55. Using the topography editor, add a single Workflow-Router process with the prefix “WFRouter” (start 0 from 1).
  56. Save the topography changes
  57. Stop the Admin Client
  58. Stop and restart the Server Manager
  59. Start the Server Monitor GUI
  60. Observe the inactive WFRouter process (as we configured it) and then start it
  61. Stop the Server Monitor
  62. Start the Admin Client
  63. Edit any of the SrvMngr4.ini common sections
  64. Add an address map for Machine R44-905, Instance Type CRSServer, Instance Name *
  65. Save the common section
  66. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type CRSServer, Instance Name *) for configuration parameters
    Program=CRSSrv.exe
    Group=CRS ShowMode=0
    ConfigFile=CRS.ini
    CRSUseDbApi=1
    SignCheck=Yes
  67. Save the private section
  68. Add a CRS.ini private section (Machine R44-905, Instance Type CRSServer, Instance Name *)
    [Parameters]
    RuleFile=crs.xml
    CRSSchemaFile=crs.xsd
    WFServer=localhost
    CRSPort=2019
    RiskThreshold=0
    VipMultiplier=1
    [Constants]
    MinAmount=1000
    [BNO-001]
    [BNO-002]
  69. Save the private section and apply the changes to the database
  70. Using the topography editor, add CRSServer process with the prefix “CRS-” (start 0 from 1).
  71. Save the topography changes
  72. Stop the Admin Client
  73. Stop and restart the Server Manager
  74. Start the Server Monitor GUI
  75. Observe the inactive WFRouter process (as we configured it) and then start it
  76. Observe the inactive CRS-1 process (as we configured it) and then start it
  77. Stop the Server Monitor
  78. Start the Admin Client
  79. Edit any of the SrvMngr4.ini common sections
  80. Add the Address Map entries Instance Type SignCheckServer Instance Name * and Instance Type AttachManager Instance Name SignCheck to this common section map
  81. Save the common file element
  82. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type AttachManager, Instance Name SignCheck) for configuration parameters
    Program=attman5.exe
    Group=SignCheck
    Port=2001
    ShowMode=0
  83. Save the file element. Notice that the Address Map for the SignCheck Attach Manager now shows “both”.
  84. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type SignCheckServer, Instance Name *) for configuration parameters
    Program=sc1.exe
    Group=SignCheck
    ShowMode=0
    MsgTypeList=50,52,54,56,57,58,59,5A,5C,5E,60,62,63
    SignCheck=Yes
  85. Save the private section and apply the changes to the database. Notice that the Address Map for the SignCheckServer now shows “both”.
  86. Using the topography editor, add 4 SignCheckServer processes with the prefix “SC-Server-” (start 4 from 4).
  87. Change the topography entries for WFRouter and CRS Server to start both automatically
  88. Save the topography changes
  89. Stop the Admin Client
  90. Stop and restart the Server Manager
  91. Start the Server Monitor
  92. Observe all processes (except 2 SignBase Server processes) are running.
  93. Stop the Server Monitor
  94. Start the Admin Client
  95. Edit any of the SrvMngr4.ini common sections
  96. Add the Address Map entries Instance Type ASVServer Instance Name * and Instance Type AttachManager Instance Name Automat to this common section map
  97. Save the common file element
  98. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type AttachManager, Instance Name Automat) for configuration parameters
    Program=attman5.exe
    Group=Automat
    Port=2002
    ShowMode=0
  99. Save the file element. Notice that the Address Map for the Automat Attach Manager now shows “both”.
  100. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type ASVServer, Instance Name *) for configuration parameters
    Program=scs2.exe
    Group=Automat ShowMode=0
    SignCheck=Yes NoHistory=No
    MsgTypeList=8A,80,8C,82
    SCSnippetPrio=MP
    Sca2Ex=N
    Latin=1,7
  101. Save the private section and apply the changes to the database. Notice that the Address Map for the ASV Server now shows “both”.
  102. Using the topography editor, add 4 ASVServer processes with the prefix “ASV-Server-” (start 4 from 4).
  103. Save the topography changes
  104. Stop the Admin Client
  105. Stop and restart the Server Manager
  106. Start the Server Monitor
  107. Observe all processes (except 2 SignBase Server processes) are running.
  108. Stop the Server Monitor
  109. Start the Admin Client
  110. Add an Automat2.ini common section. (Machine R44-905, Instance Type *, Instance Name *) for configuration parameters
    [Common]
    WriteStat=Yes
    Interval=60
    NotVerified=Yes
    NotLatin=No
    RemoveInvalidVariants=Yes
    RemovePrefixedDate=No
    UseOnlyCleanSnippets=Yes
    DontCleanReference=No
    SepStepBeside=15
    SepStepUpon=15
    SepMinBorder=20
    FSXResizeImg=0
    NumFsxSplitsBeside=4
    NumFsxSplitsUpon=4
    MinPelsOrder=400
    MinPelsSignature=400
    MinPelsCleanedOrder=400
    MinPelsCleanedSignature=400
    BaseResolutionOrder=200
    BaseResolutionSignature=200
    MinResolution=150
    INICurrency=EUR
    MaxSimplicity=70
    FormTypeList=22, 24
    MaxAmount=-1
    Limit-1=200000: C1
    Limit-2=1000000: B5
    Limit-3=10000000: A5
    Limit-4=100000000: AA
    Limit22-1=200000: A5
    Limit22-2=1000000: A3
    Limit24-1=200000: A5
    Limit24-2=1000000: A3
    [BNO-001]
    MaxAmount=300000000
    BnoCurrency=USD
    Limit-1=200000: C1
    Limit-2=1000000: B5
    Limit-3=10000000: A5
    Limit-4=100000000: AA
    LimitAPIA-1=90000000: C5
    LimitAPIA-2=950000000: B5
  111. Save the common section.
  112. Add an Automat2.ini private section. (Machine R44-905, Instance Type *, Instance Name *) for configuration parameters
    [Automat] WriteStat=Yes
    SplitSingleSignerAccounts=FALSE
    UseDefaultFraud=No
    Register4Notification=Yes
    Port4Notification=2014
    Queue4Notification=11
    Wait4Notification=5
    TwinTestRating=D5
    UseRestInst=
    CheckCodes=
    GiroCodes=
    IntlCodes=
    AutoRuleVerification=1
  113. Save the file element. Notice that the Address Map for the Automat2.ini now shows “both”.
  114. Edit any of the SrvMngr4.ini common sections
  115. Add the Address Map entries Instance Type ASVCLIENT Instance Name * to this common section map
  116. Save the common file element
  117. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type ASVCLIENT, Instance Name *) for configuration parameters
    Program=automat2.exe ASV
    Group=ASV
    Host= Port=2002
    RemoteIni=automat2.ini
    ShowMode=0
    Timeout=30 Auto2Ex=N
  118. Save the private section and apply the changes to the database. Notice that the Address Map for the ASVCLIENT now shows “both”.
  119. Using the topography editor, add 3 ASVCLIENT processes with the prefix “Automat-” (start 3 from 3).
  120. Save the topography changes
  121. Stop the Admin Client
  122. Stop and restart the Server Manager
  123. Start the Server Monitor
  124. Observe all processes (except 2 SignBase Server processes) are running.
  125. Stop the Server Monitor
  126. Start the Admin Client
  127. Change the default Java Client configuration – bank name and change to customer model. Edit the private property element for Java Client / settings.properties
    Bank = Training Session
    AccountModel = 0
  128. Save the settings.properties client configuration
  129. Change the default Java Client configuration – enable SignCheck. Edit the private property element for Java Client / custom.properties
    SignCheck.Enabled = 1
  130. Save the custom.properties client configuration
  131. Save the client configuration and apply the changes to the database.
  132. Start the Java Client, observe title bar and menu structure
  133. Stop and restart the Admin Client
  134. Configure a Getter instance; SrvMngr4.ini - Edit any of the SrvMngr4.ini common sections
  135. Add the Address Map entries Machine R44-905 Instance Type Getter Instance Name * to this common section map
  136. Add the following line to the common section
    JavaDLL=c:\Java32\jdk1.8.0_60\jre\bin\server\jvm.dll
  137. Save the common file element
  138. Add a SrvMngr4.ini private section. (Machine R44-905, Instance Type Getter, Instance Name *) for configuration parameters
    Program=SrvMInitJava.exe
    MainClass=de.softpro.signplus.service.Getter
    ClassPath=.;SPCheckStock.jar;service.zip;service.jar;spclient.jar;softpro.jar;sputils.jar;tiff.zip;liveinfo.jar;XjLog-
    1.0.9.jar;slf4j-api-1.7.7.jar;logback-core-1.1.2.jar;logback-classic-
    1.1.2.jar;c:\IBM\SQLLIB\java\db2jcc.jar;c:\IBM\SQLLIB\java\db2jcc_license_cu.jar;
    ApplArgs=Getter $#USEde/softpro/signplus/service/DB=de/softpro/signplus/service/db2v9 Group=Getter
    JavaOpts= -Xms32m -Xmx256m Showmode=0
    TraceLevel=3
  139. Save the file element.
  140. Locate the sample service program properties files already present in the configuration database and edit each of the following private items to add a map for Machine R44-905, Instance Type Getter, Instance Name *
    1. database.properties
    2. databasesc.properties
    3. gsetfid.properties
    4. gsetvalues.properties
    5. ilsetvalues.properties
    6. getter.properties
    7. service.properties
  141. Edit the private properties item getter.properties and set the following parameters
    check.IRDCheck=0
    check.PADCheck=0
  142. Save the file element.
  143. Edit the private properties item service.properties and set the following parameters (Assums local DB2 type 4 connection is possible with localhost:51050/R44TRAIN) Getter.check.IRDCheck=0
    Getter.check.PADCheck=0 Getter.PADEngine=none
    Database.URL=jdbc:db2://localhost:51050/R44TRAIN
    Database.propValue1=signplus
    Database.propValue2=signplus
    DatabaseSC.URL=jdbc:db2://localhost:51050/R44TRAIN
    DatabaseSC.propValue1=signplus
    DatabaseSC.propValue2=signplus
    #DatabaseDWH.URL=jdbc:db2:FRAUD1DW
    #DatabaseDWH.propValue1=
    #DatabaseDWH.propValue2=
  144. Save the file element and apply the configuration changes.
  145. Using the topography editor, add 1 Getter process with the prefix “Getter-” (start 1 from 1).
  146. Save the topography changes
  147. Stop the Admin Client

Congratulation! You have finished the basic configuration. We suggest that you back up the above work and keep a copy of the initial configuration. Please go ahead and also configure your Putter, DFP, Accountloader, ....

Keywords: SignPlus, FraudOne, Configuration Service, Server, Srvmngr4