8.11 cepstopeng

Name: cepstopeng - CEP engine stop

Format

cepstopeng [-e engineName]

Function description: This command stops a CEP engine.

Arguments

-e engineName

Specify the name of the CEP engine to be stopped.

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 stop will fail.

End status

The following status codes are returned:

0: Normal end

8: Abnormal end

Note

This command monitors the stop of the CEP engine until it has completed, and the command ends normally if it can confirm that the stop has completed.
If the stop has not completed within a predetermined time (within 180 seconds), an error message will be output and the stop will fail with a timeout.

Example

Example of output at normal end

When a CEP engine (CepEngine1) is stopped:

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

Example of output at abnormal end

When stop processing has not completed within a predetermined time (when a timeout has occurred):

$ cepstopeng -e CepEngine2 <ENTER>
ERROR: cep30203e: Failed to stop Collection Engine. EngineId=(CepEngine2) JobId=(CepEngine2
-cepjobnet-20120710130118-CepEngine2) Reason=(A timeout occurred.(localhost_FRT))
Command cepstopeng execution failed.

Please note that we added a newline in the example above (line 2) for readability only - the actual message does not have a newline.

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

EngineId: Name of the CEP engine to be stopped

JobId

The Job ID, in the following format:

CEPengineName-cepjobnet-yyyyMMddHHmmss(time of CEP engine start)-CEPengineName

Reason: Error details (reason for the failure to stop the CEP engine)