D.5.4.2 BD Datamap Configuration File

Oracle clients can modify the BDF.xml file under the bdf/config/custom folder to override default settings that the system provides.

You can also reapply any modifications in the current BDF.xml file to the newer BDF.xml file. Override any settings in BDF.xml by placing the modifications in BDF.xml under the bdf/config/custom folder. During installation, the following parameters are configured by the installer:
  • AccountTrustFromCustomer
  • DefaultJurisdiction
  • UseTaxidForUnrelatedPartyCode
  • BaseCountry
  • ProcessForeignFlag
  • ProcessBankToBank
  • ProcessTransactionXRefFlag
  • TrustedPairRiskReviewFlag

These parameters are stored in the <OFSAAI Installed Directory>/bdf/config/install/BDF.xml file.

The DefaultJurisdiction and BaseCountry parameters are defined in the InstallConfig.xml file during Silent Installation. Refer to the Installation Guide for more information.

The Installer sets the default value for other parameters as follows:

  • <Parameter name="AccountTrustFromCustomer" type="STRING" value="Y"/>
  • <Parameter name="DefaultJurisdiction" type="STRING" value="AMEA"/>
  • <Parameter name="UseTaxidForUnrelatedPartyCode" type="STRING" value="Y"/ >
  • <Parameter name="BaseCountry" type="STRING" value="US"/>
  • <Parameter name="ProcessForeignFlag" type="STRING" value="N"/>
  • <Parameter name="ProcessBankToBank" type="STRING" value="N"/>
  • <Parameter name="ProcessTransactionXRefFlag" type="STRING" value="Y"/>
  • <Parameter name="TrustedPairRiskReviewFlag" type="STRING" value="N"/>

To change the default value of these parameters, before running ingestion, go to <OFSAAI Installed Directory>/bdf/config/install/BDF.xml and change the value to 'Y' or 'N' as needed.

The following table describes the parameters defined in BDF.xml:

Table D-20 BD Datamap Configuration Parameters

Property Name Description Example
DB.Connection.Instance Database instance to connect to on the database servers. Typically, the instance name matches the database name portion of the DB.Connection.URL. D1O9L2
DB.Schema.MANTAS Schema name for the Oracle ATOMIC database schema. BD accesses the ATOMIC schema when allocating sequence IDs to ingested records. ATOMIC
DB.Schema.MARKET Schema name for the ATOMIC database schema. Data Management stores market data related records in the ATOMIC schema. ATOMIC
DB.Schema.BUSINESS Schema name for the ATOMIC database schema. Data Management stores business data related records in the ATOMIC schema. ATOMIC
DB.Schema.CONFIG Name of the configuration schema owner. REVELEUS
DB.Schema.CASE Name of the ATOMIC schema owner. ATOMIC
DB.Alg.Connection.User Database user for running Behavior Detection post- processing jobs. ATOMIC
DB.Alg.Connection.Password Password for the DB.Alg.Connection.User.
DB.Connection.URL Database URL for JDBC connections made by BD components. The content and format of this value is specific to the database vendor and the vendor database driver. jdbc:oracle:thin:@solitair e.mantas.com:1521:D1O9 L2

There are also configuration files for individual components that are delivered as part of the product as <OFSAAI Installed Directory>/bdf/config/<component>.xml

These can also be created in <OFSAAI Installed Directory>/bdf/config/custom/<component>.xml