#
# G2.INI
#



[SQL]
   CONNECTION=db2://G2USER:G2PASSWD@{Database}
   LAST_TOUCH_WAIT=10
   AUTO_UNTOUCH=1

[PIPELINE]
   CONCURRENCY=1
   INIT_BUFFER_SIZE=16384   
   SUPPORTPATH={DataFolder}
   ENABLE_SECURE_STORE=1
   SECURE_STORE_LIB=gsk8iccs_64
   SECURE_STORE_URL=pkcs11://token/?slotID=0
   SECURE_STORE_PIN=

   XLIT_RULE1=arabicTransRule.ibm 
   XLIT_RULE2=chineseTransRule.ibm 
   XLIT_RULE3=cyrillicTransRule.ibm 
   XLIT_RULE4=greekTransRule.ibm 
   XLIT_RULE5=hindiTransRule.ibm 
   XLIT_RULE6=japaneseTransRule.ibm 
   XLIT_RULE7=koreanTransRule.ibm 
   XLIT_RULE8=chineseONTransRule.ibm 
   XLIT_RULE9=cyrillicONTransRule.ibm 
   XLIT_RULE10=hindiONTransRule.ibm 
   XLIT_RULE11=japaneseONTransRule.ibm 
   XLIT_RULE12=koreanONTransRule.ibm 
   XLIT_RULE13=anyTransRule.ibm


[SALT]
  NAME={salt_name}
  CHECKSUM={salt_checksum}

[LOGGING]
   LOG_OBS=1


#################################################
#  About G2.INI
#################################################
#
#  This INI file is automatically built and
#  placed here when the repository is created
#  the first time. If this repository is
#  deleted and recreated all changes will be
#  lost.
#
#  The G2.INI template is typically located near
#  the EXE programs in a directory like this
#  .\ext\bin\pasw.entityanalytics\templates.
# 
#################################################
#  [GNR]
#  SUPPORTPATH=<path name>
#################################################
#
#  DO NOT CHANGE THIS SETTING
#
#  This is the path to locate the Global Name
#  Recognition (GNR) configuration data
#  directory. Typically this directory is
#  located near the EXE programs, for example:
#  .\ext\bin\pasw.entityanalytics\data.
#################################################
#
#  [ER]
#  SUPPORTPATH=<path name>
#################################################
#
#  DO NOT CHANGE THIS SETTING
# 
#  This is the path to locate the Entity
#  Analytics configuration data directory.
#  Typically this directory is located near the
#  EXE programs, for example: 
#  .\ext\bin\pasw.entityanalytics\data.
#
#################################################
#  [SQL]
#  CONNECTION=solid://<user>:<pwd>@tcp <port>
#################################################
#
#  DO NOT CHANGE THIS SETTING
# 
#  This is the database (solidDB) CONNECTION
#  string. The user name of 'G2USER' and
#  password of 'G2PASSWD' are replaced at time
#  the CONNECTION is made based on user input.
#  The port is assigned when the system is
#  initially setup. A typical configuration may
#  look like this:
#  CONNECTION=solid://G2USER:G2PASSWD@tcp 1321.
# 
# Enable/disable the secure store feature. 0=disabled / 1=enabled
 # The default is 0.
 #ENABLE_SECURE_STORE=1

 # The base name of the PKCS #11 implementation library in use. This
 # product also ships with a software-only PKCS #11 implementation
 # that will use a file as storage for its security token. The library
 # name for this software-only implementation is gsk8iccs_64 (gsk8iccs
 # on 32-bit systems).
 #SECURE_STORE_LIB=gsk8iccs_64

 # URL that specifies which security token should be used for the
 # secure store (out of multiple possible security tokens that could
 # be known to the implementation library). The basic URL format is as
 # follows:
 #
 #  pkcs11://token/?slotID=<integer>&tokenLabel=<string>
 #
 # At least one of slotID or tokenLabel must be specified. If both
 # are specified, then the specified security token must have both
 # the specified slot ID number and token label string.  Specifying
 # token label is usually preferred since it is easier to be sure the
 # correct token is being used as the secure store (even if it changes
 # slots due to a PKCS #11 configuration change).
 #SECURE_STORE_URL=pkcs11://token/?slotID=0

 # This can be left blank (the default value) unless you wish to
 # specify your own User PIN for the PKCS #11 security token. Other
 # possible values are "prompt" to have G2 prompt for the User PIN
 # every time it starts; a string beginning with "pin:" followed
 # by an encrypted User PIN string (see the documentation for the
 # ssadm utility on how to obtain this encrypted string); a string
 # beginning with "file:" followed by a path to an encrypted PIN file
 # (as can be optionally created by the ssadm utility's -ssinit mode).
 #SECURE_STORE_PIN=

 # Specifies the name of a system mutex/semaphore to be used in synchronizing
 # secure store operations when there are multiple simultaneous users of
 # the secure store's PKCS#11 security token (only needed in unusual cases).
 # This is not normally required.
 # This name must be a string of ASCII alphanumeric characters, with
 # underscores allowed.
 # The default value is G2_PKCS11_Mutex
 #SECURE_STORE_MUTEX_NAME=G2_PKCS11_Mutex

 # Specifies how long the secure store should wait to acquire the system mutex.
 # The time is specified in milliseconds, but should be at least
 # 5 seconds (5000). Specifying zero means the mutex is not used.
 # The default value is 0 (mutex not used)
 #SECURE_STORE_MUTEX_TIMEOUT=0



 # G2 Transliteration culture files, up to 256 transliteration files can be
 # specified.  If specified, file(s) must be present in
 # [PIPELINE] SUPPORTPATH location.
 # Valid values: file name
 # Default setting:
 # XLIT_RULE1=arabicTransRule.ibm
 # XLIT_RULE2=cyrillicTransRule.ibm
 # XLIT_RULE3=greekTransRule.ibm
 # XLIT_RULE4=japaneseTransRule.ibm
 # XLIT_RULE5=koreanTransRule.ibm
 # XLIT_RULE6=chineseTransRule.ibm
 # XLIT_RULE7=anyTransRule.ibm
 # ...
 # ...
 # ...
 # XLIT_RULE256=

 # Specifies a default Native Script to use while transliterating text
 # If no script is provided via the input UMF record, this default is used
 # Valid value: ANY/CHINESE/JAPANESE
 # Default setting: ANY
 # NATIVE_SCRIPT=ANY

###############################################################################
# Anonymization salt settings
# A salt value is a large securely generated random number that is used
# during the anonymization process to increase security of sensitive data.
###############################################################################
#[SALT]

 # This is the name/label of the salt you want to use from the secure store
 # Once the secure store is properly setup, you can use the following command
 # to create a new salt inside the secure store:
 # saltadm -c g2.ini -new -name <chosen name of new salt>
 # Valid values: alphanumeric string
 # Default setting: None - must be specified
 #NAME=<chosen name of new salt>

 # This is the checksum of the salt you want to use from the secure store
 # Once the secure store is properly setup, you can use the following command
 # to create a new salt inside the secure store:
 # saltadm -c g2.ini -new -name <chosen name of new salt>
 # The above command will display a "finger-print" checksum for the new salt
 # that should be used here.  Alternatively, you can display the checksum for
 # any salt in the secure store using the following command:
 # saltadm -c g2.ini -checksum -name <name of salt>
 # Valid values: Base64 string
 # Default setting: None - must be specified
 #CHECKSUM=<checksum of salt specified with [SALT] NAME>
#################################################
#  End of Comments
#################################################


