Consider which method to use to send events to the CEP engine.
Here, consideration must be given to which communication method to use for the input events and which application to use to send the events, according to that communication method.
Communication method for input events
Consider which communication method to use when the CEP engine is receiving events, according to the characteristics of the input events.
If an existing system that is to be used as the event issuer has an event sending feature, check which communication methods the existing system can use.
With BDCEP, the following three communication methods can be selected:
SOAP
HTTP
Socket
Select a communication method according to the characteristics of the system or device that is to be used as the event sender, and the desired processing performance. Characteristics of each communication method are described below.
Communication method | Characteristic |
|---|---|
SOAP | A generic communication protocol. This method allows sending XML or CSV event data to the CEP engine as SOAP messages. WSDL can be used to define an interface and an event sender application can be developed using the existing Web service development tool. |
HTTP | A generic communication protocol. This method allows sending XML or CSV event data to the CEP engine connected via HTTP without modification. There is no unnecessary header information so that the communication load can be less than that of SOAP. This means that this method is not only more suitable for sending large amounts of event data but also enables sending event data from devices supporting the REST communication. |
Socket | A communication protocol unique to BDCEP, which is used for TCP/IP socket communication. This method allows simultaneously sending multiple XML or CSV event data. There is no HTTP header so the communication load can be less than that of HTTP, making this method most suitable for sending large amounts of event data. |
Event sender application
Consider which system or application to use to send events to the CEP Server.
There are two types of event sender applications: systems that send events during normal business operation and those that send events at any time during rule testing. For the latter, consider using the event sender sample program supplied with BDCEP, if the volumes of event data are small. Refer to "5.11.6 Event Sender Sample Program" for details.
If the system issuing the events can send the events using a communication method supported by BDCEP, check that the CEP engine can receive events using that feature.
If the event issuer has no event sending feature, or if it does not support a communication method of the BDCEP input adapter, consider developing an application to send events to the CEP Server (event sender application).
The design and development of an event sender application must be carried out according to the specifications of the server or device that is to be used as the event sender. Refer to Chapter 3, "Input Adapter Reference" in the Developer's Reference for detailed specifications on each communication method and for information on the sample event sender application.
