This section explains the definition files (development assets) for using the various CEP service features.
There are four kinds of development assets, as shown below, and each has an identifier known as a development asset ID, which must be unique per definition type.
cepdeployrsc deploys a development asset to a CEP engine, and cepundeployrsc undeploys a development asset.
Definition type | Definition overview | Used by feature | Mandatory/ | |||
|---|---|---|---|---|---|---|
Input adapter | High-speed filter | Complex event processing | Output adapter | |||
Defines the data structure of the input event data. Also sets Logging in the input adapter. | Used | Used | Used | (*1) | ||
Describes high-speed filter rules and complex event processing rules. | Used | Used | Used | (*2) | ||
Sets the master data used by the High-speed Filter. | Used | (*3) | ||||
Sets the send destination information when SOAP communication is to be used to notify user-developed Web service events. | Used | (*4) | ||||
*1: At least one development asset must be deployed.
*2: Deploy if the high-speed filter or complex event processing is to be used.
*3: Deploy if master data is to be referenced in the high-speed filter.
*4: Deploy if the SOAP listener is to be used in the output adapter.
Point
Each definition file is a text file in XML format (except for master data).
The items to be set are specified as XML element and attribute values.
The character encoding for each definition file is UTF-8.
