D.5.4.1 BDF.xml Configuration Parameters

The following table describes the BD properties configurations mentioned in the <OFSAAI Installed Directory>/bdf/config/BDF.xml file.

Table D-19 BDF.xml File Configuration Parameters

Type Parameter Name Description Example
MISCELLANEOUS NumberOfThreads The number of worker threads used by some BD components 4
MISCELLANEOUS SequenceBatchSize The batch size when retrieving sequence IDs for new records 100000
MISCELLANEOUS SourceSystem he default value for source system when one is not provided MTS
MISCELLANEOUS Currency The default value for issuing currency when one is not provided USD
MISCELLANEOUS Separator The delimiter that separates fields in data file records. ~
DB: Parameters related to database access. DB.Connection.Driver The JDBC driver class name. oracle.jdbc.OracleDriver
DB: Parameters related to database access. DB.Timeout The number of seconds to wait before timing out on a database connection attempt. 10
DB: Parameters related to database access. DB.NumRetries The maximum number of times to attempt to connect to a database before failing. 5
DB: Parameters related to database access. DB.MaxNumberOfDeadlocks The maximum number of times a deadlock is encountered during a JDBC insert or update operation, before an error is generated. 10
Directory: Parameters used to define directory locations. Directory.Inbox The input directory where the Oracle client will write DIS files. Date subdirectories will be created in this directory where these files will be archived ../inbox
Directory: Parameters used to define directory locations. Directory.InternalData The directory where files generated by BD components will reside. This includes log files, error files, and any temporary processing files. ..
Log: Parameters used to configure the common logging module Log.Format Identifies the log formatting string. %d [%t] %p -

%m%n

Log: Parameters used to configure the common logging module Log.UseDefaultLog Specifies whether the system uses the default log file for a component. The default log file has the name of the component and resides in a date subdirectory of the logs directory (in YYYYMMDD format). true
Log: Parameters used to configure the common logging module Log.SysLogHostName The host name of syslog for messages sent to syslog. hostname
Log: Parameters used to configure the common logging module Log.SMTPHostName The host name of the SMTP server for messages that processing sends to an e-mail address. hostname
Log: Parameters used to configure the common logging module Log.MaxSize The maximum size (in MB) of a log file before the system creates a new log file. 2000MB
Log: Parameters used to configure the common logging module Log.MaxIndex If a log file exceeds Log.MaxSize, this will be the maximum number of additional log files that are created (Component.log.1, Component.log.2, etc). 10
Log: Parameters used to configure the common logging module Log.TRACE.Enabled Indicates that trace logging is not enabled; true indicates enabling of trace logging. false
Log: Parameters used to configure the common logging module Log.TRACE.Location Specifies additional locations to send TRACE log messages to, other than the default BD log file (logs/YYYYMMDD/Component.log). If the value is not provided, considers the default BD log location. false
Log: Parameters used to configure the common logging module Log.TRACE.Synchronous Specify whether logging for a particular level should be performed synchronously or asynchronously. false
Log: Parameters used to configure the common logging module Log.DIAGNOSTIC.Enabled DIAGNOSTIC logging is used to log database statements and will slow down performance. Make it true if needed. false
Log: Parameters used to configure the common logging module Log.DIAGNOSTIC.Location Additional locations to send DIAGNOSTIC log messages to, other than the default BD log file (logs/YYYYMMDD/Component.log).

If the value is not provided, considers the default BD log location.

Log: Parameters used to configure the common logging module Log.DIAGNOSTIC.Synchronou s Specify whether logging for a particular level should be performed synchronously or asynchronously. false
Log: Parameters used to configure the common logging module Log.NOTICE.Enabled Indicates enabling of notice logging; false indicates that notice logging is not enabled. true
Log: Parameters used to configure the common logging module Log.NOTICE.Location Specifies additional locations to send NOTICE log messages to, other than the default BD log file (logs/YYYYMMDD/ Component.log). If the value is not provided, considers the default BD log location.
Log: Parameters used to configure the common logging module Log.NOTICE.Synchronous Specify whether logging for a particular level should be performed synchronously or asynchronously. false
Log: Parameters used to configure the common logging module Log.WARN.Enabled Indicates enabling of warning logging; false indicates that warning logging is not enabled. true
Log: Parameters used to configure the common logging module Log.WARN.Location Specifies additional locations to send WARN log messages to, other than the default BD log file (logs/YYYYMMDD/Component.log).
Log: Parameters used to configure the common logging module Log.WARN.Synchronous Specify whether logging for a particular level should be performed synchronously or asynchronously. false
Log: Parameters used to configure the common logging module Log.FATAL.Enabled Indicates enabling of Fatal logging; false indicates that fatal logging is not enabled. true
Log: Parameters used to configure the common logging module Log.FATAL.Location Specifies additional locations to send FATAL log messages to, other than the default BD log file (logs/YYYYMMDD/Component.log).
Log: Parameters used to configure the common logging module Log.FATAL.Synchronous Specify whether logging for a particular level should be performed synchronously or asynchronously. false
Load: Parameters used to configure common Loading data Load.FullRefresh For DIS files defined as Overwrite, whether to fully replace FSDM tables with the contents of the DIS file (true) or to treat the DIS file as a delta (false) True
Load: Parameters used to configure common Loading data Load.BatchSize The batch size when loading data. 5000
Load: Parameters used to configure common Loading data Load.Direct Specifies whether to use direct path loading (TRUE) or conventional path loading (FALSE). false
Load: Parameters used to configure common Loading data Load.Unrecoverable Specifies whether a direct path load does not use redo logs (TRUE) or uses redo logs (FALSE). false
Load: Parameters used to configure common Loading data Load.Partitioned Specifies whether a direct path load uses the current date partition (TRUE) or any partition (FALSE). false
Load: Parameters used to configure common Loading data Load.SkipIndexes Specifies whether a direct path load skips index maintenance (TRUE) or maintains indexes (FALSE). If set to TRUE, rebuilding of indexes must occur after running the DataMap XML. false
Load: Parameters used to configure common Loading data Load.DoAnalyze Specifies whether to run a stored procedure to analyze a database table after loading data into it. true
Load: Parameters used to configure common Loading data Load.AnalyzeType Specifies the type of analyze statistics has to perform if DoAnalyze has a value of True. DLY_POST_L OAD
Load: Parameters used to configure common Loading data Load.LogRecordInterval Specifies how often to log a message saying how many records a particular thread has inserted/updated, 1000
Load: Parameters used to configure common Loading data Load.MaxErrorRate Specifies the percentage of invalid records to allow before exiting with an error. For example, a value of 10 allows 10 percent of records to be invalid before exiting with an error. A value of 0 allows no invalid records. A value of 100 allows all invalid records. 100
Load: Parameters used to configure common Loading data Load.RecordQueueSize Specifies the number of records the query reader thread will write to a database writer thread queue before waiting for the reader thread to catch up. Higher values will require more memory usage. 100
Load: Parameters used to configure common Loading data Load.SkipIndexesErrorCode Specifies a database error code that occurs in the log file when skipping index maintenance. 26025
Load: Parameters used to configure common Loading data Load.IndexParallelLevel Specifies the parallel level of an index rebuild (that is, number of concurrent threads for rebuilding an index). 1
Load: Parameters used to configure common Loading data Load.DataErrorCodes Specifies a comma-separated list of database error codes that indicate data level errors , such as data type and referential integrity. This results in rejection of records with a warning instead of a fatal failure.

1,1400,1401,14

07,1438,1722,1

840,1841,2291

,2359,1839,18

47,12899

Load: Parameters used to configure common Loading data Load.ParallelLevel Specifies the level of parallelization to apply when loading data from a set of source tables to a target table. 8
Load: Parameters used to configure common Loading data Load.WriteErrorFiles Whether to check a DIS file for errors before loading as an external table (true) or not (false) True
DIS: Parameters related to processing DIS files DIS.Source The mechanism used to load DIS data.

FILE: DIS files will be provided and will be loaded using SQL*Loader processes running on the application server.

FILE-EXT: DIS files will be provided and will be loaded using external tables with the DIS files accessed directly by the database.

FSDW: DIS data will be obtained from database tables in the FSDW.

FILE
DIS: Parameters related to processing DIS files DIS.ArchiveFlag Whether DIS files will be archived to a date subdirectory (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.BufferSize The size in KB of the byte buffer used to read in DIS file records. 100
DIS: Parameters related to processing DIS files DIS.InputFileCharset The character set of the DIS files. Note that output data is always written in UTF8, this parameter just allows the DIS files to be in a different character set.
DIS: Parameters related to processing DIS files DIS.Default.Check.Requiremen t Whether to check for mandatory fields on DIS records (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.Default.Reject.Requiremen t Whether to reject DIS records for failing a mandatory field check (true) or to log a warning and attempt to load the record (false). True
DIS: Parameters related to processing DIS files DIS.Default.Check.Domain Whether to check that a DIS field has a valid domain value (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.Default.Reject.Domain Whether to reject DIS records that fail a domain check (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.Default.Check.Length Whether a DIS field should be checked for a valid length (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.Default.Reject.Length Whether to reject DIS records that fail a length check (true) or not (false) True
DIS: Parameters related to processing DIS files DIS.Default.Check.Threshold Whether a DIS field should be checked that it is within an acceptable threshold (i.e. greater than 0) (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.Default.Reject.Threshold Whether to reject DIS records that fail a threshold check (true) or not (false). True
DIS: Parameters related to processing DIS files DIS.Default.Check.Lookup Not currently supported. True
DIS: Parameters related to processing DIS files DIS.Default.Reject.Lookup - Not currently supported True
Parameters used by queries defined in the data maps MinimumGeographyRisk Defines what is considered High Risk For the Account Profile attributes related to High Risk Geography , such as Incoming High Risk Wire Count.

Processing compares this parameter using a strict greater-than operation.

0
Parameters used by queries defined in the data maps AccountInactivityInMonths Specifies the number of months that processing aggregated to determine whether an account is inactive. If the sum of trades and transactions over this number of months is <= 3, the account is considered inactive. This setting can impact the Escalation in Inactive Accounts scenario.

The default value is six months.

6
Parameters used by queries defined in the data maps TransactionsReversalLookbac kDays This parameter controls how many days of transactions to look across. Verify whether the new data contains reversals of prior transactions. 7
Parameters used by queries defined in the data maps LowPriceSecurityThreshold Defines Low Priced in the base currency for the Account Profile attributes named Low-Priced Equity Range # Opening Trade Count. Processing compares the value of this parameter to the Trade table's Last Execution Price-Base. 5000
Parameters used by queries defined in the data maps CommissionEquityPercentUp perLimit Defines the upper limit for Commission Versus Average Daily Equity Percentage in Account Profile Calculation. 5
Parameters used by queries defined in the data maps TurnOverRateUpperLimit Defines the upper limit for Total Turnover Rate in Account Profile Calculation. 5
Parameters used by queries defined in the data maps BankCodeListWithIA Defines the List of Financial Institution Identifier Types, these are type of unique identifiers which are used to represent the financial institutions.

This parameter also contains IA (Internal Account Identifier) to be used in datamaps and is mainly used in

Correspondent Bank related datamap derivations. Below are the list of examples

  • BIC: SWIFT Bank Identifier Code(BIC)
  • CHU: CHIPS Participant UserIdentifier
  • CO: CorporateIdentifier
  • CHP: CHIPS ParticipantIdentifier
  • FED: Federal Reserve Routing (ABA)Number
  • CU: CustomerIdentifier
  • GL: General LedgerAccount
  • l IA: Internal AccountIdentifier
BIC,FED,CHP, CHU, DTC,CDL,EPN, KID, CBI,CSN,OTF, BLZ,I BAN,ABLZ,B SB,CP AP, SDIC, HEBIC, BCHH, NSC, IFSC, IDIC, PNCC, RCBIC, UKDSC, Swiss BC, Swiss SIC,IA
Parameters used by queries defined in the data maps IdRiskWinLevel Defines the Risk level to calculate Effective Risks for internal parties (Account/ Customer).

For example: Account 1234 has an Effective Risk of 5, IdRiskWinLevel can be set by the client. If the party identifier effective risk is greater than the set IdRiskWinLevel, then the party identity risk wins compared to fuzzy matcher (Party Name Risk). If not, fuzzy matcher wins.

1
Parameters used by queries defined in the data maps InternalAccountCodeList Codes to define types of Internal Entities with client, for example:
  • IA: Internal AccountIdentifier
  • GL: General LedgerAccount
IA, GL
Parameters used by queries defined in the data maps ExternalEntityCodeList

Codes to define types of External Entities with client, for example:

  • XA: External AccountIdentifier
  • CO: CorporateIdentifier
  • DL: DriverLicense
  • IBAN: International Bank AccountNumber
XA,CC,CO,DL, GM, GP,LE,MC,ND, NR, PP,SS,TX,AR, OT,IB AN
Parameters used by queries defined in the data maps TrustedPairReviewReasonText 1 Defines the reason text1 for recommendation of canceling the Trusted Pair, due to increase in Risk of parties involved in trusted pair. Risk of <Party1> increased from <A> to <b>
Parameters used by queries defined in the data maps TrustedPairReviewReasonText 2 Defines the reason text2 for recommendation of canceling the Trusted Pair, due to increase in Risk of parties involved in trusted pair. Risk of <Party2> increased from <C> to <D>
Parameters used by queries defined in the data maps CorporateActionLookBackDay s This parameter determines the how many days trades to look back from the Corporate Effective Date. 7
Parameters used by queries defined in the data maps BankCodeList Defines the List of Financial Institution Identifier Types, these are type of unique identifiers which are used to represent the financial institutions excluding Internal Account (IA).

This parameter does not contain IA (Internal Account

Identifier) to be used in datamaps and is typically used to derive financial institutions. Below are the list of examples

  • l BIC: SWIFT Bank Identifier Code(BIC)
  • l CHU: CHIPS Participant UserIdentifier
  • l CO: CorporateIdentifier
  • l CHP: CHIPS ParticipantIdentifier
  • l FED: Federal Reserve Routing (ABA)Number
  • l CU: CustomerIdentifier
  • l GL: General LedgerAccount

BIC,FED,CHP, CHU, DTC,CDL,EPN, KID, CBI,CSN,OTF, BLZ,IBAN,ABLZ,B SB,CP AP, SDIC, HEBIC, BCHH, NSC, IFSC, IDIC, PNCC, RCBIC, UKDSC,Swiss BC, Swiss SIC

Parameters used by queries defined in the data maps DealNearTermMaturityDays Defines the maximum number of days between the End Date and Trade Date.

This helps to calculate Structured Deals Initiated w/ Near-Term Exp. In Customer Profile/ Institutional Account Profile.

7
Parameters used by queries defined in the data maps ProfitLossUpperLimit Helps determine how much a security must move by the end of the day to be considered a win or loss. If the security moves by less than a specified percentage, processing does not count it either way. If it moves by this percentage or more, it counts as a win or a loss, depending on whether the movement was beneficial to the account that made the trade. 5
Parameters used by queries defined in the data maps HouseholdTurnOverRateUppe rLimit Defines the upper limit for Total Turnover Rate in Household Profile Calculation. 10000
Parameters used by queries defined in the data maps HouseholdCommissionEquity PercentUpperLimit Defines the upper limit for Commission Versus Average Daily Equity Percentage in Account Profile Calculation. 10000
Parameters used by queries defined in the data maps OptionTradeAmountRange1 OptionTradeAmountRange2 OptionTradeAmountRange3 OptionTradeAmountRange4 OptionTradeAmountRange5 OptionTradeAmountRange6 Define the lower bound of each range for the Account Profile attributes named Options Range # Opening Trade Count.

Processing compares each parameter to the Trade table's Last Principal Amount- Base.

Each range is from the lower bound entered here to the lower bound of the next range.

Parameters used by queries defined in the data maps EquityTradeAmountRange1 EquityTradeAmountRange2 EquityTradeAmountRange3 EquityTradeAmountRange4 EquityTradeAmountRange5 EquityTradeAmountRange6 Define the lower bound of each range for the Account Profile attributes named Equity Range # Opening Trade Count.

Processing compares each parameter to the Trade table's Last Principal Amount- Base.

Each range is from the lower bound entered here to the lower bound of the next range.

Parameters used by queries defined in the data maps LowPricedEquityTradeAmountRange1 LowPricedEquityTradeAmountRange2 LowPricedEquityTradeAmountRange3 LowPricedEquityTradeAmountRange4 LowPricedEquityTradeAmountRange5 LowPricedEquityTradeAmountRange6 Define the lower bound of each range for the Account Profile attributes named Low-Priced Equity Range # Opening Trade Count. Processing compares each parameter to the Trade table's Last Principal Amount-Base.

Each range is from the lower bound entered here to the lower bound of the next range.

Parameters used by queries defined in the data maps MutualFundTradeAmountRange1 MutualFundTradeAmountRange2 MutualFundTradeAmountRange3 MutualFundTradeAmountRange4 MutualFundTradeAmountRange5 MutualFundTradeAmountRange6

Define the lower bound of each range for the Account Profile attributes named Mutual Fund Range # Opening Trade Count. Processing compares each parameter to the Trade table's Last Principal Amount-Base.

Each range is from the lower bound entered here to the lower bound of the next range.

Parameters used by queries defined in the data maps UnrelatedWhenOffsetAccount IsNull This parameter is used to assign unrelated party code as "J" in the BackOfficeTransaction table, If OFFST_ACCT_INTRL_ID is null and UnrelatedWhenOffsetAccountIsNull is "Y",

If OFFST_ACCT_INTRL_ID is null and UnrelatedWhenOffsetAccountIsNull is "N", then unrelated party code is NULL.

Y