If the event sender application receives a response message indicating an error, take action according to the type of error.
Note that developers themselves must resolve error processing relating to ordinary socket communication (TCP/IP).
At the CEP Server, execute cepdispeng (with the -a option specified) to check if the CEP engine has started. If a socket adapter is being used, check the command results to see if the CEP engine listening on the specified TCP port has started.
If not started, use cepstarteng to start the CEP Server.
Check if the data format of the message sent from the event sender application conforms to the contents of "3.2 About Event Data". Also check if the send message specification method is compliant with the input adapter type.
If there is an error, reconfigure the event sender application.
At the CEP Server, execute cepdispeng (with the -i option specified) to check if the event type ID of the send message matches the event type definition (development asset ID) deployed to the CEP engine.
If there is an error, correct so that they match.
At the CEP Server, execute cepgetrsc (with eventtype and the -n option specified) to check if the event data format of the send message (CSV or XML) matches the event data format in the deployed event type definition.
If there is an error, correct so that they match.
Check if the encoding of the event data sent from the event sender application is the same as the specified character set.
If different, specify the same character set.
Refer to the syslogs or the engine logs at the CEP Server and check the detailed error information.
Refer to Messages for information on the appropriate action.
Refer to the syslogs or the engine logs at the CEP Server and check if the input adapter overload is temporary or permanent.
Refer to Messages for information on the appropriate action.
See
Refer to Chapter 8, "Command Reference" in the User's Guide for information on the cepdispeng, cepstarteng, and cepgetrsc commands.
