If the table to which you want to map already exists in the target database, then you can map event fields to the table’s columns.
In the Mapper, select an event type from the list on the left.
Click Select Table and select an existing table in your target database.
In each event field’s row, specify the name of a column in the target table to which to replicate data.
To do so, click in the Enter column name field and start typing. A menu of column names in the target table that contain the text that you typed is displayed for your selection.
After you map or discard an event field, a Clear button appears at the end of that row which enables you to unmap that field. The field changes to unmapped (red) again.
Repeat this procedure for each event field.
The mapping of a specific event type can be considered complete after all its non-metadata fields are either Mapped or Discarded and the dot next to the event type in the left hand pane has turned green.
You can leave some of the event fields unmapped, if Alooma’s Mapper's configuration for handling unmapped event fields is set to Flexible or Auto-mapped mode. If Alooma is set to Strict mode, then unmapped event fields cause an event to be sent to the Restream queue (and not replicated into the target database).
Click Apply to apply these changes to Alooma. Data that is already in the target database is not affected by mapping changes.
Before clicking Apply, you can cancel the current mapping definitions by clicking Discard.
After making mapping changes, we recommend monitoring the Alooma Notification pane and the Restream queue in order to see whether Alooma has detected any issues that require handling because of the new mapping.