Carbon applications (cAppCarbon applications (C-App) deployer is a specific feature of WSO2 CEP, which deploys WSO2 CEP-specific deployable artifacts using a single CAR file.
Table of Contents maxLevel 3
...
C-App deployable artifacts and types
You can deploy all deployable artifacts, and also the stream definitions using Carbon apps (cAppsC-Apps). Given below is a list of deployable artifacts and the associated types.
Artifact | Type |
---|---|
event receivers | event/receiver |
event publishers | event/publisher |
execution Plansplans | event/execution-plan |
event stream | event/stream |
Note | ||
---|---|---|
| ||
If the above mentioned artifacts are being deployed using a cAppC-App, you are restricted on editing or deleting them. Therefore, if you need to edit the cAppC-App, you need to re-pack and re-deploy it. |
Creating a
...
C-App
Follow the steps below to create a cApp C-App with the following structure.
Code Block | ||
---|---|---|
| ||
├──artifacts.xml ├──WSO2EventReceiver_1.0.0 │ ├──artifact.xml │ └──WSO2EventReceiver-1.0.0.xml └──HighFrequentTweetsLogger_1.0.0 ├──artifact.xml └──HighFrequentTweetsLogger-1.0.0.xml |
Create the top level
artifacts.xml
file of the cApp C-App which defines the set of folders included in it as shown below.Code Block language xml <?xml version="1.0" encoding="UTF-8"?><artifacts><artifacts> <artifact name="SampleCAppSampleC-App" 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>
Create separate directories in the top level of the cApp C-App for the two dependencies (WSO2EventReceiver_1.0.0 and HighFrequentTweetsLogger0 and HighFrequentTweetsLogger_1.0.0) defined 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 cAppC-App. 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.
Create an
artifact.xml
file inside all dependency directories. For example, theartifact.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>
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.00 directory.Create the the
HighFrequentTweetsLogger-1.0.0.xml
file, which is the actual event publisher file that you deploy in WSO2 CEP inside theHighFrequentTweetsLogger_1.0.
0 directory0
directory.
Info |
---|
You can also create a C-App using the WSO2 Developer Studio. For more information, see Creating an Analytics Project. |
Deploying a
...
C-App
Follow the steps below to deploy a cAppC-App.
- Log in to WSO2 CEP management console using admin/admin credentials.
- Click Main, and then click Add in the Carbon Applications menu.
- Click Choose File as shown below.
- Select the CAR file you need to upload as shown below.
- Click Upload.
Click Main , and then click List in the Carbon Applications menu. You see the file added to the list of deployed CAR files as shown below.
Info If there is a deployment failure, the faulty Carbon applications and the deployment error will be displayed in the UI.
Undeploying a
...
C-App
Follow the steps below to undeploy a cAppC-App.
- Log in to WSO2 CEP management console using admin/admin credentials.
- Click Main , and then click List in the Carbon Applications menu.
- Click the corresponding Delete link of the relevant Carbon application, which you want to delete as shown below.