The following sections describe the database-config.xml file in your project's src/main/resources/ folder:


For most deployments, the only section of the database-config.xml file you need to edit is the FIN_LINK <dataTableSchema>, which specifies the name of your raw data source table. This will allow you to pass your unique transaction IDs to Influent.

<dataTableSchema key="FIN_LINK">
        <table key="FIN_LINK" memberKey="aml.transactions"/>
To specify the name of your raw data source table
  1. Edit the FIN_LINK table <memberKey> to pass in the correct table name.
  2. See Mapping Fields to Property Descriptors for information on mapping your transaction ID column to the property descriptor (ID) required by Influent.

Custom Details

The database-config.xml also allows you to:

  • Adjust table and columns you altered to correspond with your database administration standards
  • Pass in additional entity or transaction details specific to your deployment

NOTE: All of the capitalized <key> values for the columns and tables in the following schemas are required by Influent:

To adjust for any of the required columns you altered
  • Edit the corresponding <memberKey> and/or <memberType> attributes, where:
    Property Description
    memberKey Column named that should be mapped to the corresponding key
    memberType Type of data stored in the corresponding column:
    • string
    • float
    • integer
    • date
    • double
    • boolean
    • hex (binary/raw referred to locally in hex without the 0x prefix)
To adjust for any of the required tables you altered
  • Edit the corresponding <memberKey> attribute, where:
    Property Description
    memberKey Table named that should be mapped to the corresponding key
To add new schemas, tables or columns
  • Follow the steps in the preceding sections and give each new dataTableSchema, column and table a unique key value. This value serves as an identifier that can be used by Influent.

Multi-Type Configurations

For deployments that have multiple account types (e.g., the Kiva application supports lender, borrower and partner entities), the FIN_ENTITY schema requires unique tables for each type.

    <table key="FIN_ENTITY">
        <memberOf typeKey="loan" memberKey="dbo.FinEntityLoan"/>
        <memberOf typeKey="lender" memberKey="dbo.FinEntityLender"/>
        <memberOf typeKey="partner" memberKey="dbo.FinEntityPartner"/>

List the individual FIN_ENTITY tables as <memberOf> elements, where:

Property Description
typeKey Type of entities stored in the table
memberKey Name of the table in which the entities are stored