How do I map Batch Processor input data to a Rulebase entity?

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

When using csv data, by default, the name of a csv file will be mapped to an entity with the same name if one exists; for example, if there is a csv data file called child.csv and the rulebase has an entity with the public name child then rows in the child.csv will be treated as child entity instance. You can explicitly map an csv file or database table to a rulebase entity by specifying a mapping.

Use the xml element <entity> in the configuration file, to specify a mapping with the following attributes:

Entity attribute defines the rulebase entity public name.
Table attribute defines the csv or database table.
Primary-key attribute defines the unique primary key for each entity. This is needed if any relationships will be mapped for this entity.

There are also two optional attributes which are as follows:

Output-table attribute is used to identify an alternate table into which the output attributes of the entity are to be inserted, when writing to a database.
Primary-key-type attribute specifies whether the source table has a text or integer primary key. If not provided, an integer key is assumed.

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