cepdispeng - CEP engine information display
cepdispeng [-i] [-a | -e engineName]
This command displays the basic information or the operation status of a CEP engine.
This option is used to display the basic information of a CEP engine.
If this option is not specified, the operation status of the CEP engine will be displayed.
The table below explains the items displayed:
Item name | Content | Displayed? |
|---|---|---|
engineId | CEP engine name | Yes |
eventtype | Development asset ID of the deployed event type definition | Conditional |
rule | Development asset ID of the deployed rule definition | Conditional |
master | Development asset ID of the deployed master definition | Conditional |
listener | Development asset ID of the deployed SOAP listener definition | Conditional |
Yes: Always displayed
Conditional: Displayed if the development asset has been deployed
Point
If two or more development assets of the same definition are deployed, they are displayed in multiple lines.
Item name | Content | Displayed? |
|---|---|---|
engineId | CEP engine name. | Yes |
port | Port number for socket communication (socket adapter port). | Conditional (*1) |
socket | Number of simultaneous connections in socket communication. | Conditional (*1) |
status_filter | Status of the CEP engine (high-speed filter). RUN: Running normally STARTING: Starting STOP: Stopped STOPPING: Stopping ABNORMAL: Abnormal | Yes |
status_cep | Status of the CEP engine (complex event processing). RUN: Running normally STARTING: Starting STOP: Stopped STOPPING: Stopping ABNORMAL: Abnormal | Yes |
inEvent_filter | Number of input events for the CEP engine (high-speed filter). Indicates the number of events input to the high-speed filter. Displays a cumulative value from when the CEP engine started. | Conditional (*2) |
inEvent_cep | Number of input events for the CEP engine (complex event processing). Indicates the number of events input to complex event processing. Displays a cumulative value from when the CEP engine started. | Conditional (*3) |
outEvent_filter | Number of output events for the CEP engine (high-speed filter). Indicates the number of events sent to complex event processing. Displays a cumulative value from when the CEP engine started. | Conditional (*2) |
outEvent_cep | Number of output events for the CEP engine (complex event processing). Indicates the number of events sent to a user-developed Web service. Displays a cumulative value from when the CEP engine started. | Conditional (*3) |
logging_filter | Number of loggings for the CEP engine (high-speed filter). | Conditional (*2) |
logging_cep | Number of loggings for the CEP engine (complex event processing). | Conditional (*3) |
heap_filter | Java heap usage and area size for the CEP engine (high-speed filter). Displayed in the following format: Java heap usage (bytes)/area size (bytes) | Conditional (*2) |
heap_cep | Java heap usage and area size for the CEP engine (complex event processing). Displayed in the following format: Java heap usage (bytes)/area size (bytes) | Conditional (*3) |
useMemory_filter | Memory usage of CEP engine (high-speed filter) processes (kilobytes). | Conditional (*2) |
useMemory_cep | Memory usage of CEP engine (complex event processing) processes (kilobytes). | Conditional (*3) |
countRule_filter | Number of rules applied to the CEP engine (high-speed filter). | Conditional (*2) |
countRule_cep | Number of rules applied to the CEP engine (complex event processing). | Conditional (*3) |
countListener | Number of applied listeners. Indicates the number of SOAP listener definitions applied to the CEP engine (complex event processing). | Conditional (*3) |
Yes: Always displayed
Conditional: Displayed in the following cases:
*1: If socket communication is being used (if a socket adapter is being used by the CEP engine)
*2: If the CEP engine (high-speed filter) is running normally (if status_filter is "RUN")
*3: If the CEP engine (complex event processing) is running normally (if status_cep is "RUN")
This option is used to display information on all configured CEP engines.
Specify the name of the CEP engine for which information is to be displayed.
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 display will fail.
The following status codes are returned:
Normal end
Abnormal end
Example
Example of output at normal end
When the operation statuses of all configured CEP engines are displayed:
$ cepdispeng -a <ENTER>
engineId :CepEngine1
port :9600
socket :1
status_filter :RUN
status_cep :RUN
inEvent_filter :100
inEvent_cep :100
outEvent_filter :100
outEvent_cep :100
logging_filter :100
logging_cep :100
heap_filter :98,725,088 / 532,545,536
heap_cep :98,725,088 / 532,545,536
useMemory_filter :823,493,339
useMemory_cep :823,493,339
countRule_filter :1
countRule_cep :1
countListener :1
engineId :CepEngine2
port :9601
status_filter :STOP
status_cep :STOP
Command cepdispeng executed successfully.
When the basic information of a CEP engine (CepEngine1) is displayed:
$ cepdispeng -i -e CepEngine1 <ENTER>
engineId :CepEngine1
eventtype :EVENT_01
rule :RULE_01
master :MASTER_01
listener :LISTEN_01
listener :LISTEN_02
Command cepdispeng executed successfully.
