This section explains how to prepare the data to be referenced from rules.
Prepare (create) event data to be used in checking the operation of rules.
Use an event data format that suits the event sender application to be used.
Example
This is an example of event data for the event sender sample program supplied with the samples of BDCEP.
/opt/FJSVcep/sample/sample1/event/CouponEvent.csv
"STR0001","CPN0001","30"
Prepare (create) a schema file and data files of the master data for the high-speed filter.
Refer to "9.2.3 Master Definition File" for information on the schema file and data files.
Example
Example of a schema file
"Kbn","Number","Code","Name","Value","Total","Comment"
Example of a data file
"01","1001","AAA","BlockA","1,000","1,000","Comment: Memo number 4023"
"02","1001","BBB","BlockB","","1,200","Comment: Memo number 4023"
"03","1002","CCC","BlockC","800","800","Comment: Memo number 4023"
If required, prepare (create) the data that is to be initially stored in the Terracotta cache to be referenced from complex event processing rules.
If an existing cache is to be used, this data need not be prepared (created).
Select a data format according to the specifications of the Terracotta application for update to be used.
Prepare (create) a relational database to be referenced from the complex event processing rule, and the data to be stored first. You need not prepare (create) data if using an existing relational database.
Create an RDB schema definition and storage data according to the specifications for the RDB commands to be used for storing data. Refer to the manual for the collaboration destination RDB for details.