Batch export to a database

A sample properties file, named RDMBatchExportClient.properties, is provided with the InfoSphere® MDM Reference Data Management Hub installation. The options in this file are used to specify parameters for running the batch export when you export to a database.

The general format of the options in this properties file is:
		option = value
The following options apply when you export to a database:
db_driver
JDBC-specific driver, which must be copied to the batch export folder. If it is not provided with batch export, contact your database administrator.

For example: db_driver = com.ibm.db2.jcc.DB2Driver

db_url
URL of the database server instance where the exported information is stored in format host:port.

For example: db_url = jdbc:db2://myserver:50000/

db_user
User to authenticate in the database server where the exported information is stored.

For example: db_user = admin

db_password
Password to authenticate in the database server where the exported information is stored.

For example: db_password = pass

db_dbname:
Database destination name for exported data.

For example: db_name = exportdb

db_schema
Database destination schema name for exported data. Must be in uppercase letters.

For example: db_schema = EXPORTDB

db_maps_tbl:
Database destination table name for exported data.

For example: db_maps_tbl = dataexporttable

db_boolean_type:
Since DB2 does not support a native Boolean data type, this property specifies how to handle Boolean types from two available options, CHAR and INTEGERS.

For example: db_boolean_type = CHAR

When CHAR is specified, false values are stored in the database as F and true values are stored as T.

When INT is specified, false values are stored in the database as 0 and true values are stored as 1.

db_mapping_columns = value/pathToValue
Database column configuration for mapping export in format.

value | pathToValue- (destinationcolumnname)

Mapping level properties (prefix map)

Mapping level properties are exported using the following syntax: 
prefix.mappingPropertyName(database destination column name)
Valid properties are:
  • SourceSetID
  • SourceSetName
  • SourceVersion
  • TargetSetID
  • TargetSetName
  • TargetVersion
  • MappingState
  • MappingVersion
  • MappingName
  • MappingDataTypeID - This property is mandatory to export.
  • MappingDataTypeName
  • EffectiveDate
  • ExpiryDate
  • Owners
  • Description
  • Comments

Example:

map.MappingID(MAPID) exports the MappingID field to the database column "MAPID"

map.SourceSetID(SETID) exports the SourceSetID field to the database column "SETID"

Value mapping properties (prefix valueMap)

Value mapping level properties are exported using the following syntax: 
prefix.valueMappingPropertyName(database destination column name)
Valid properties are:
valueMappingID
This property is mandatory to export.
Source properties
valueMap.dot _separated_path_to_value.Property_to_export(destinationcolumnname) where dot_separated_path is formed by related referenced sets and Property_to_export options are code or name.

For example: valueMap.source.city.state.country.continent.planet.name(PLANETNAME)

This example exports the planet description, for example "EARTH", into database column "PLANET".
Note: The full path must be specified. The path is composed of all related set names. For example, the following sets are related: city set > state set > country set > continent set > planet set.
Target properties
valueMap.dot _separated_path_to_value.Property_to_export(destinationcolumnname) where dot_separated_path is formed by related referenced sets and Property_to_export options are code or name.

For example: valueMap.target.city.state.country.code(COUNTRY)

This example exports country code (for example "US") into database column "COUNTRY".
Note: The full path must be specified. The path is composed of all related set names. For example, the following sets are related: city set > state set > country set.
Custom properties
valueMap.custom_property_name

The custom property name is case-sensitive.

For example: valueMap.anualIncome(ANUALINC)

This property exports the value for custom property anualIncome into database column "ANUALINC".

effectiveDate
For example: valueMap.effectiveDate(VALEFFDT)

This example exports the value mapping effective date into database column "VALEFFDT".

expirationDate
For example: valueMap.expirationDate (VALEXPDT)

This example exports the value mapping expiration date into database column "VALEXPDT".

For example: 
db_mapping_columns = map.MappingID(MAPPINGID),map.SourceSetID(SRCSETID,
map.SourceSetName(SRCSETNAME),map.SourceVersion(SRCSETVER),
map.TargetSetID(TARSETID),map.TargetSetName(TARSETNAME),
map.TargetVersion(TARSETVER),map.MappingState(MAPSTATE),
map.MappingVersion(MAPVER),map.MappingName(MAPNAME),
map.MappingDataTypeID(MAPDT),map.MappingDataTypeName(MAPDTNAME),
map.EffectiveDate(EFFDT),map.ExpiryDate(EXPDT),map.Owners(OWNERS),
map.Description(MAPDESCR),map.Comments(COMMENTS),
valueMap.valueMappingID(VALMAPPINGID),
valueMap.source.people.code(PEOPLECODE),
valueMap.source.people.nationality.code(NATIONALITYCODE),
valueMap.target.city.code(CITYCODE),
valueMap.target.city.name(CITYNAME),
valueMap.target.city.state.code(STATECODE),
valueMap.target.city.state.country.code(COUNTRYCODE),
valueMap.target.city.state.country.continent.planet.code(PLANETCODE)
,valueMap.effectiveDate(VALEFFDT),
valueMap.expirationDate(VALEXPDT),
valueMap.Income(INCOME),valueMap.Birth(BIRTH),
valueMap.Single(SINGLE),
valueMap.facebook(FACEBOOK)

Last updated: 22 Mar 2017