Top
Interstage Big Data Complex Event Processing Server V1.0.0 User's Guide
Interstage

5.7.3 Starting

Start the deployed user-developed Web service and the CEP engine in which definition information has been deployed.

Also check syntax errors along with starting the CEP engine.

The procedure for the starting tasks is as follows:

  1. Checking the Status of a User-developed Web Service

  2. Starting the CEP Engine

  3. Checking for Syntax Errors in Filter Rules

  4. Checking for Syntax Errors in Complex Event Processing Rules

5.7.3.1 Checking the Status of a User-developed Web Service

If the application server in which a user-developed Web service has been deployed is not running, start the server. After starting the server, check that the deployed user-developed Web service has the status of receiving requests from outside.

Refer to the application server manuals for information on how to start the application server and how to check the status of the Web service.

5.7.3.2 Starting the CEP Engine

After deployment, use cepstarteng to start the CEP engine. Start the CEP engine in which definition information has been deployed. Refer to "8.9 cepstarteng" for details.

Example

Example of executing cepstarteng

$ cepstarteng -e CepEngine<ENTER>
Command cepstarteng executed successfully.

5.7.3.3 Checking for Syntax Errors in Filter Rules

If the filter rules in the rule definition contain syntax errors, the CEP engine start will fail. If this happens, the cause of the error will be notified to the engine log of the high-speed filter. Correct the syntax error based on the notified error content.

Redeploy the corrected rule definition in the CEP engine. Refer to "6.1.4.3 Updating Deployed Definition Information" for information on redeploying. After redeploying, repeat the operations from "5.7.3.2 Starting the CEP Engine".

5.7.3.4 Checking for Syntax Errors in Complex Event Processing Rules

If the complex event processing statements in the rule definition contain syntax errors, the CEP engine start will fail with a "cep20201e" error.

If this happens, the cause of the error will be notified to the engine log of complex event processing using the error message in the "cep20201e" ERRORINFO parameter.

Below is an example of an error message in the ERRORINFO parameter. Correct the syntax error based on this content.

Incorrect syntax near xxxxxxxx at line X column Y

xxxxxxxx: Keyword near the abnormality

X: Number of lines from the beginning of the complex event processing statement in which the error occurred

Y: Number of characters from the beginning of the line of the complex event processing statement in which the error occurred

Redeploy the corrected rule definition in the CEP engine. Refer to "6.1.4.3 Updating Deployed Definition Information" for information on redeploying. After redeploying, repeat the operations from "5.7.3.2 Starting the CEP Engine".

Note

Depending on the content of the error message, the location of the error (line and column information) may not be displayed.

Example

Log output example of a syntax error in a complex event processing statement

Target complex event processing statement

@Name('EPL3')
@DebugLogListener

select * from
FilteredCouponEvent (storeID='STR0001') wherer cast(targetAge,int)>20;

Log output (please note that we added newlines in the example below (lines 1 to 6) for readability only - the actual output does not have a newline.)

2012-07-15 13:51:18,843 [ERROR] CSPF_CEP: ERROR: cep20201e: EPL module file access 
failure. EngineId=CepEngine, FILE=/etc/opt/FJSVcep/resources/CepEngine/rules/SampleRule.
epl, ERRORINFO=com.espertech.esper.client.deploy.DeploymentActionException: Compilation
failed in module url '/etc/opt/FJSVcep/resources/CepEngine/rules/SampleRule.epl' in
expression '@Name('EPL3')@DebugLogListenerselect * from Filt...(115 chars)' : Incorrect
syntax near 'cast' (a reserved keyword) at line 3 column 61, please check the from
clause [@Name('EPL3')
@DebugLogListener

select * from FilteredCouponEvent
(storeID='STR0001') wherer cast(targetAge,int)>20]

Explanation of log output:

  • ERRORINFO=...

    Error information will be output following this ERRORINFO parameter.

  • Compilation failed...

    This is a broad error classification. "Compilation failed" or "Deployment failed" will be output.

  • SampleRule

    This is the development asset ID of the rule definition in which the error occurred.

  • Incorrect syntax...

    This is the error message. It indicates that there is a syntax error near "cast" in line 3, column 61 from the beginning of complex event processing statement in which the error occurred.

  • @Name('EPL3')...

    This is the complex event processing statement in which the error occurred. In this example, the "wherer" before "cast" should actually be "where", and the extra "r" has caused a syntax error.