How do I map Batch Processor input data to a rulebase relationship?

When using csv data, if a column in a table exists which has the public name of relationship for that entity, then that column will be mapped as a relationship. If a csv file matches the public name of a many-to-many relationship then, the data in that table will be treated as a many to many relationship.

See the description of column headings used for relationships in Zero-configuration conventions for csv input for a detailed explanation of how one-to-many relationships are identified in csv input.

You can use data mapping to explicitly identify a column or table to be used as a relationship.

For a one-to-many relationship, the relationship mapping should be placed in the entity which has the foreign key, this is usually the entity on the "to-many" side of the relationship.

For a many-to-many relationship, the relationship mapping can be placed in either (or both) entities.

Use the xml element <relationship> to specify a mapping for a one-to-many relationship, with the following attributes:

name attribute - defines relationship public name.
source-entity attribute - defines the source entity for the relationship.
foreign-key attribute - defines the column in which the foreign-key for the source entity is stored. This field must be a integer field which references a primary key in the source entity table (or csv file).

A many-to-many relationship is specified in a separate table and should contain rows which are source and target keys for the many-to-many relationship. This type of relationship is also specified by using the <relationship> element with the following attributes:

name attribute - defines relationship public name.
source-entity attribute - defines the source entity for the relationship.
rel-source attribute - specifies the table where the relationship rows are specified.
source-key attribute - specified the column with the foreign key reference to the source entity.
target-key attribute - specifies the column with the foreign key reference to the target entity.

For more information, see Data mapping in the XML configuration file. See also Zero-configuration conventions for csv input for more information on the default mapping of csv data.