This section explains how to deploy the definition information stored on the CEP Server, and how to undeploy definition information no longer required.
Execute cepdeployrsc to deploy the definition information on the CEP Server.
General user permissions can be used to execute this command.
If the CEP engine is not stopped, then you must stop it (refer to "6.1.6 Stopping the CEP Engine" for details).
Example
Deploying definition information
When deploying the following definition information (definition file) to 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)
+-- RDBREF01.xml ... RDB reference definition (development asset ID: RDBREF01)
+-- LISTENER01.xml ... SOAP listener definition (development asset ID: LISTENER01)
An example of command execution is shown below.
$ 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 rdb_ref -e CepEngine -f /application/RDBREF01.xml<ENTER>
(...)
$ cepdeployrsc listener -e CepEngine -f /application/LISTENER01.xml<ENTER>
(...)
Execute cepdispeng and cepgetrsc to check deployed definition information.
Execute cepdispeng with the -i option to list the definition information deployed in the CEP engine, and cepgetrsc to check details of the deployed definition information.
General user permissions can be used to execute these commands. The definition information can be checked regardless of whether the CEP engine is stopped or running.
Example
Listing the deployed definition information
When listing the definition information deployed to a CEP engine (CepEngine).
$ cepdispeng -i -e CepEngine<ENTER>
engineId :CepEngine
eventtype :EVENT01
rule :RULE01
master :MASTER01
rdb_ref :RDBREF01
listener :LISTENER01
Command cepdispeng executed successfully.
Listing details of the deployed definition information
When listing the details of an event type definition (EVENT01) deployed to a CEP engine (CepEngine).
$ cepgetrsc eventtype -e CepEngine -n EVENT01<ENTER>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<eventType xmlns="urn:xmlns-fujitsu-com:cspf:bdcep:v1" id="EVENT01">
<comment>Event type definition</comment>
<type>CSV</type>
<xmlSchema></xmlSchema>
<csvColumn>
<column name="memberID" type="string"/>
<column name="areaID" type="string"/>
<column name="status" type="string"/>
</csvColumn>
<root></root>
<useLogging>false</useLogging>
<loggingTableName></loggingTableName>
<useCep>true</useCep>
</eventType>
Command cepgetrsc executed successfully.
Note
If redirecting the command output of the detailed display (XML format), modify each item accordingly.
In addition to XML format data, the results of cepgetrsc also include output messages. If redirecting the command output to a file, delete unnecessary messages before using the results.
Execute cepdeployrsc with the -o option to update the deployed definition information.
General user permissions can be used to execute this command.
If the CEP engine is not stopped, then you must stop it (refer to "6.1.6 Stopping the CEP Engine" for details).
Refer to "6.1.5.5 Dynamically Changing Rule Definitions and Master Data" to update rule definitions or the master data while the CEP engine is running.
Example
Updating the deployed definition information
When updating an event type definition (EVENT01) of a CEP engine (CepEngine) with new details.
The path of the event type definition with the new details (development asset ID: EVENT01) is shown below.
/application/EVENT01_new.xmlAn example of command execution is shown below.
$ cepdeployrsc eventtype -o -e CepEngine -f /application/EVENT01_new.xml<ENTER>
Are you sure you want to deploy the event type definition?(default: y) [y,n,q]: <ENTER>
Command cepdeployrsc executed successfully.
Execute cepundeployrsc to undeploy definition information no longer required.
General user permissions can be used to execute this command. Release the definition information while the CEP engine is stopped.
Refer to "6.1.6 Stopping the CEP Engine" if the CEP engine needs to be stopped.
Example
Undeploying the definition information
When undeploying the following definition information deployed to a CEP engine (CepEngine).
Definition information type | Development asset ID |
|---|---|
Event type definition | EVENT01 |
Rule definition | RULE01 |
Master definition | MASTER01 |
RDB reference definition | RDBREF01 |
SOAP listener definition | LISTENER01 |
An example of command execution is shown below.
$ cepundeployrsc eventtype -e CepEngine -n EVENT01<ENTER>
Are you sure you want to undeploy the event type definition?(default: y) [y,n,q]: <ENTER>
Command cepundeployrsc eventtype executed successfully.
$ cepundeployrsc rule -e CepEngine -n RULE01<ENTER>
(...)
$ cepundeployrsc master -e CepEngine -n MASTER01<ENTER>
(...)
$ cepundeployrsc rdb_ref -e CepEngine -n RDBREF01<ENTER>
(...)
$ cepundeployrsc listener -e CepEngine -n LISTENER01<ENTER>
(...)