Store the developed definition information in the CEP Server, and then use cepdeployrsc to deploy the definition information. Refer to "6.1.4.1 Deploying Definition Information" for information on how to deploy definition information.
Below is an example of deploying definition information.
Example
Example of deploying definition information
This is an example of command execution when the following definition information (definition file) is deployed in a CEP engine (CepEngine):
/application
+-- EVENT01.xml ... Event type definition (development asset ID: EVENT01)
+-- RULE01.xml ... Rule definition (development asset ID: RULE01)
+-- MASTER01.xml ... Master definition (development asset ID: MASTER01)
+-- LISTENER01.xml ... SOAP listener definition (development asset ID: LISTENER01)
The example of command execution is as follows:
$ cepdeployrsc eventtype -e CepEngine -f /application/EVENT01.xml<ENTER>
Are you sure you want to deploy the event type definition?(default: y) [y,n,q]:<ENTER>
Command cepdeployrsc executed successfully.
$ cepdeployrsc rule -e CepEngine -f /application/RULE01.xml<ENTER>
(...)
$ cepdeployrsc master -e CepEngine -f /application/MASTER01.xml<ENTER>
(...)
$ cepdeployrsc listener -e CepEngine -f /application/LISTENER01.xml<ENTER>
(...)
