The flow of the integration test tasks is as follows:
Send event data for testing to the CEP engine.
Execute the deployed event sender application or the event sender sample program supplied with the samples.
After sending the events, check the engine log to see if event sending is operating as expected.
Refer to "5.9.6 Event Sender Sample Program" for information on how to use an event sender sample program.
Example
Sending event data for testing
This is an example of sending the "/application/test.csv" data for testing, which is in CSV format, to a CEP engine (Cepengine) as event data with the event type "EVENT01".
$ /opt/FJSVcep/sample/sample1/bin/sendevent.sh EVENT01 /application/test.csv<ENTER>
Check whether any errors have been notified to the engine log of the high-speed filter, and correct the error based on the notified error content.
In addition to errors, also check whether any content on input events (those with logging enabled in the event type definition) was logged in the engine log, if logging with the "file" logging type is being used.
Check whether any errors have been output to the engine log of complex event processing, and correct the error based on the notified error content.
In addition to errors, also check the operation of the complex event processing rules by checking the engine log for any content output using the "@DebugLogListener" annotation described in a complex event processing statement.
If the conditions in the complex event processing rule with the "@DebugLogListener" annotation have a hit, the property value of the output event will be output to the log.
Also check whether any content output using the "@LoggingListener" annotation was logged in the engine log, if logging with the "file" logging type is being used.
Note
The following considerations relate to the operation results of complex event processing rules:
Once checking the operation results of the rules is complete, before deploying the rule definition in the production environment, edit it to delete the "@DebugLogListener" annotation from the rule definition.
To correct and replace a rule definition during testing, first stop the CEP engine, then redeploy the rule definition, and then restart the CEP engine.
When the CEP engine is stopped, any data that was in the windows generated by rules before it was stopped will disappear.
Example
Log output example of "DebugLogListener"
Below is an example of engine log output using the "@DebugLogListener" annotation, and will be the execution result of the following complex event processing statement:
Complex event processing statement to be used
@Name('EPL3')
@DebugLogListener
@LoggingListener(table='/EPL3', properties='areaID, couponID')
@SoapListener('LISTEN01')
select areaID, targetAge, storeID, couponID
from FilteredCouponEvent (storeID='STR0001') where cast(targetAge,int)>20;
Log output example of "DebugLogListener"
2012-07-15 14:21:11,854 [DEBUG] EPL3:length=1 ... 1.
EPL3[0] ... 2.
areaID :2222: String ... 3.
targetAge :30: String
storeID :STR0001: String
couponID :CPN0001: String
Explanation of output example:
This displays the number of records that are a hit from the SELECT statement condition. The value specified using the "@Name" annotation appears in the underlined part.
This displays the record index. The value specified using the "@Name" annotation appears in the underlined part.
This line onwards displays the properties, property values, and property types of the output event.
Information
Example of an engine log output by other output adapters
An engine log output by other output adapters can also be used as debug information because it shows whether listener calling succeeded.
Example of engine log output of the SOAP listener
If the conditions in the complex event processing statement associated with the "@SoapListener" annotation have a hit, the successful listener calling will be output to the engine log. (Please note that we added newlines in the example below for readability only - the actual output does not have a newline.)
2012-07-15 14:44:42,556 [DEBUG] id=LISTEN01 destination=http://xxx.xxx.xx.xxx/WebServWAR
/MyApp1Service methodName=root<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.
org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><ns:root xmlns:ns="http://webservic
e/"><ns:areaID>2222</ns:areaID><ns:targetAge>30</ns:targetAge><ns:storeID>STR0001</ns:st
oreID><ns:couponID>CPN0001</ns:couponID></ns:root></SOAP-ENV:Body></SOAP-ENV:Envelope>
Explanation of output example:
LISTEN01
This is the development asset ID of the SOAP listener definition that was used.
http://xxx.xxx.xx.xxx/WebServWAR/MyApp1Service
This is the connection URL. This will be the value specified in the "url" tag in the SOAP listener definition.
root
This is the root element name. This will be the value specified in the "method" tag in the SOAP listener definition.
From "root" onwards
This is the SOAP message that was sent.
Example of engine log output of the logging listener
If the conditions in the complex event processing statement associated with the "@LoggingListener" annotation have a hit, the successful logging will be output to the engine log.
2012-07-26 00:05:18,692 [DEBUG] Write Log message"2222","CPN0001"
If the engine log was used as the logging destination (by specifying "file" in "type" in the engine configuration file), the processing results of the complex event processing rules will also be output.
2012-07-26 00:05:18,692 [DEBUG] TableName:/EPL3; eventdata:"2222","CPN0001"
2012-07-26 00:05:18,692 [DEBUG] Write Log message"2222","CPN0001"
Perform this only if a user-developed Web service has been designed and developed.
Check the operation of a user-developed Web service based on information such as the logs it outputs.
If a setting to perform logging using Hadoop collaboration has been specified, check that an event log has been logged in the Hadoop system.
Perform this only if an event log analysis application has been designed and developed.
Use a recorded event log to check the operation of an event log analysis application.
