This section provides an overview of items included in the following definition information:
The table below provides an overview of event type definitions.
Item | Description |
---|---|
Development asset ID | Specify an ID that is unique in the deployment destination CEP engine. A development asset ID for the event type definition is used as an event stream name in complex event processing rules. |
Format | Specify the format of the event that is input to filter processing and complex event processing. Specify XML or CSV. Filtered events will only be in CSV format. |
CSV column information | Set this item if the event format is CSV. Define column names and type information. |
XML schema (*1) | Set this item if the event format is XML. Specify a schema (XML schema), which represents the event structure. |
Root element (*1) | Specify an event root element name if the event type is XML. This will be one of the XML schema defined elements. |
Use of logging | Specify whether to use Logging for received events that have not been processed by the high-speed filter in the input adapter. |
Log storage area (*1) | Specify a storage area if Logging is used in the input adapter. |
Use of complex event processing | Specify whether to use complex event processing. |
*1: There is no need to consider this if the definition information is "event type definition (filtered)". Refer to "5.4.6 Designing an Event Type Definition (Filtered)" for information on this definition.
The table below provides an overview of rule definitions.
Item | Description |
---|---|
Development asset ID | Specify an ID that is unique in the deployment destination CEP engine. |
Filter rule | Define high-speed filter rules. Multiple filter statements can be specified in a rule by specifying them consecutively. Use relevant development asset ID values in the following rule items:
|
Complex event processing rule | Define rules for complex event type processing (complex event processing rules). Multiple complex event processing statements can be defined in a rule by delimiting them using semicolons. Use relevant development asset ID values in the following rule items:
|
The table below provides an overview of master definitions.
Item | Description |
---|---|
Development asset ID | Specify an ID that is unique in the deployment destination CEP engine. |
Schema file | Specify a file in which data file item names are defined. |
Data file | Specify a directory path where data files are stored, or the data file path. If a directory is specified, all files stored in the specified directory excluding subdirectories are treated as the master data. Multiple data files can be specified and treated as single master data. |
Use of skip | Specify whether to skip the first line of a data file. |
The table below provides an overview of RDB reference definitions.
Item | Description |
---|---|
Development asset ID | Specify an ID that uniquely identifies the definition information. |
Database system name | Specify the name of the database system. (*1) |
Schema name | Specify the schema name of the database to be connected. (*1) |
JDBC driver class | Specify the class of the JDBC driver. (*2) |
Database URL | Specify the URL of the database to be connected. |
Access ID | Specify the name of the user who will connect to the relational database. |
Access password | Specify the password of the user who will connect to the relational database. |
Cache retention period | Specify the time period for holding the RDB reference results in the cache. |
Cache purge interval | Specify the time interval for flushing the cache of RDB reference results. |
*1: Required when referencing Symfoware with the native interface.
*2: Required when referencing Symfoware (Open Interface) or PostgreSQL.
The table below provides an overview of SOAP listener definitions.
Item | Description |
---|---|
Development asset ID | Specify an ID that is unique in the deployment destination CEP engine. |
Connection URL | Specify a connection URL of the user-developed Web service. |
Namespace | Specify a namespace of the message (SOAP body content) to be sent to the user-developed Web service. |
Namespace prefix | Specify a namespace prefix used in the message (SOAP body content) to be sent to the user-developed Web service. |
Root element | Specify a root element name of the message (SOAP body content) to be sent to the user-developed Web service. |