RDBMS event publisher is used to publish events in map format to a RDBMS in two execution modes, which are insert and update-insert.
...
| Info | ||
|---|---|---|
After entering the above adapter properties, select the Message Format which you want to apply on the published events . Also, click Advanced to define custom output mappings based on the Message Format you selected. For more information on custom output mapping types, see Output Mapping Types .
|
You can also define the respective adapter properties of the event publisher based on the transport type within the <to> element of the event publisher configuration in the <PRODUCT_HOME>/repository/deployment/server/eventpublishers/ directory as follows.
...
Adapter Property | Description | Configuration file Property | Example | ||
|---|---|---|---|---|---|
| Data Source Name | Name of the datasource | datasource.name | WSO2_CARBON_DB | ||
| Table Name | Name of the table | table.name | sensordata | ||
| Execution Mode | Type of the execution mode. | execution.mode | insert/update or insert | ||
| Composite key columns | Attributes used for uniqueness checks for updates. Use commas to separate if you enter more than one attribute.
| update.keys | sensor-key,sensor-group |
Configuring advanced properties
Advanced properties are configured to select attributes with IDs different to those defined in the event stream to which the publisher is connected. When advanced properties are defined, they are considered the only attributes to be published and the original attributes in the connected event stream are not considered.
e.g., If the event stream to which the publisher is connected has an attribute named ID, but you want the publisher to include attributes of which the name is formatted as id, you can define id as an advanced property as shown below.
...
Related samples
For more information on rdbms event publisher type, see the following sample in WSO2 CEP Documentation.
...