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

8.9 cepstarteng

Name

cepstarteng - CEP engine start


Format
cepstarteng [-e engineName]

Function description

This command starts a CEP engine.


Arguments
-e engineName

Specify the name of the CEP engine to be started.

If only one CEP engine has been configured, this option can be omitted.

If this option is omitted, and if there are two or more configured CEP engines, an error message will be output and the start will fail.


End status

The following status codes are returned:

0

Normal end

8

Abnormal end


Note

  • Before this command is executed, cepdeployrsc must be used to deploy at least one event type definition. If an event type definition has not been deployed, an error message will be output when the CEP engine is started, and the start will fail.

  • This command monitors the start of the CEP engine until it has completed, and the command ends normally if it can confirm that the start has completed.

  • If this command is not completed within 180 seconds, force the CEP engine to stop. If the forced stop is then completed within 180 seconds, a message is output stating that the startup processing has timed out and that this command has ended abnormally. If the forced stop is not completed within 180 seconds, a message is output stating that the forced stop has failed and that this command has ended abnormally.

Example

Example of output at normal end

When a CEP engine (CepEngine1) is started:

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

Example of output at abnormal end

When an attempt is made to start a CEP engine that does not exist:

$ cepstarteng -e CepEngine2 <ENTER>
An incorrect value was entered. Reason=(The engine does not exist.)
Command cepstarteng execution failed.

The following information will be added to the error message in this example:

Reason

Cause of the error (reason for the failure to start the CEP engine)