The table below lists the development assets of BDCEP. Development assets are broadly divided into definition information, data, and collaboration applications. Definition information is deployed in the CEP engine for execution. Each of the others is provided (deployed) in its corresponding server.
Development asset type | Development asset | Explanation | Deployment destination |
|---|---|---|---|
Definition information | Event type definition | Define the format of the events the input adapter is to receive. Also define the log storage area specification and whether or not complex event processing is to be used. The events the input adapter is to receive can be in XML or CSV format. | CEP engine |
Rule definition | Define high-speed filter processing rules and complex event processing rules. Describe these using filter rule language (IF-THEN format) and complex event processing rule language (SQL format), respectively. The processing results of complex event processing rules can be sent to an external application by SOAP communication, accumulated on disks by logging, and processed according to a user-developed Java class by the custom listener. | ||
Event type definition (filtered events) | Define this if the items that make up the events will vary according to factors such as join and extraction processing of high-speed filter processing. Filtered events will be in CSV format. | ||
Master definition | Create this if master referencing is to be performed in high-speed filter processing. This is the definition of the master data to be referenced. | ||
RDB reference definition | Create this if RDB collaboration is to be performed using complex event processing. Define RDB connection information. | ||
SOAP listener definition | Define the interface of the user-developed Web service to be used as the send destination when the processing results of complex event processing rules are to be sent to an external application using SOAP. | ||
Data | Event data | This is event data to be sent to the CEP Server to check the operation of definition information. | Event |
Master data | This is required separately if master referencing is to be performed in high-speed filter processing. Provide this in CSV file format on the CEP Server. | CEP | |
Terracotta (*1) | This is required separately if Terracotta collaboration is to be performed. Provide this on the collaborating Terracotta server. A Terracotta application for update is required separately in order to store or update the data in a Terracotta cache. | Terracotta | |
Relational database (RDB) | This must be considered if RDB collaboration is to be performed. Provide this on the collaborating RDB server. RDB commands or an RDB application is required for storing and updating data in a relational database. | RDB | |
Collaboration application | Event sender | This is an application that sends events to the CEP engine. To use SOAP for sending events, provide a SOAP client application. This is not required if events are to be sent directly to the CEP engine using an existing system as the event sender. If a new event sender application needs developing, it must be done according to the device to be used as the sender. The event sender sample program bundled with the product can be used in the operation testing of rule definitions. | Event |
User-developed | This Java class receives the output of complex event processing rules via the custom listener and processes it. It is deployed to the CEP Server and called from a CEP engine. | CEP | |
User-developed | This is a Web service (SOAP application) that receives and controls event data sent by the output adapter. Deploy this in the application server that collaborates with CEP Server. | Application server | |
Event log analysis | This is an application for analyzing event logs logged in a Hadoop system. Develop this using the Hadoop Java API. Deploy this in the Hadoop system and then execute it. | Hadoop | |
Terracotta | This is an application, separate from the complex event processing rules, for updating the cache contents such as by initially storing data in a Terracotta cache. This is not required if an existing Terracotta cache is to be used. | Terracotta server |
The following figure below shows the deployment destination of each development asset.
Figure 5.1 Deployment destinations of development assets
