Page Comparison

Carbon applications (cApp) deployer is a specific feature of WSO2 CEP, which deploys WSO2 CEP-specific deployable artifacts using a single CAR file.

...

1. Create the top level artifacts.xml file of the cApp which defines the set of folders included in it as shown below. 

   Code Block
   language xml
   <?xml version="1.0" encoding="UTF-8"?><artifacts> <artifact name="SampleCApp" version="1.0.0" type="carbon/application"> <dependency artifact="WSO2EventReceiver" version="1.0.0" include="true" serverRole="ComplexEventProcessor"/> <dependency artifact="HighFrequentTweetsLogger" version="1.0.0" include="true" serverRole="ComplexEventProcessor"/> </artifact> </artifacts>

2. Create separate directories in the top level of the cApp for the two dependencies (WSO2EventReceiver_1.0.0 and HighFrequentTweetsLogger_1.0.0) defined in the artifacts.xml file. 

   Info
   You can have multiple dependencies as required with a directory for each of them in the same level as the artifacts.xml file in the cApp. Include the name and the version of the artifact in the name of the directory.

   Note
   Each dependency directory should contain an artifact.xml file.

3.  Create an artifact.xml file inside all dependency directories. For example, the artifact.xml file of the WSO2EventReceiver_1.0.0 dependency directory is as follows.

   Code Block
   language xml
   <?xml version="1.0" encoding="UTF-8"?> <artifact name="WSO2EventReceiver" version="1.0.0" type="event/receiver" serverRole="ComplexEventProcessor"> <file>WSO2EventReceiver-1.0.0.xml</file> </artifact>

4. Create the WSO2EventReceiver-1.0.0.xml file, which is the actual event receiver file that you deploy in WSO2 CEP inside the WSO2EventReceiver_1.0.0 directory0 directory. 

5. Create the HighFrequentTweetsLogger-1.0.0.xml file, which is the actual event publisher file that you deploy in WSO2 CEP inside the HighFrequentTweetsLogger_1.0.0 directory.

...