Versions Compared

Old Version 22

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

C-App deployable artifacts and types

You can deploy all deployable artifacts, and also the stream definitions using Carbon apps (C-Apps). Given below is a list of deployable artifacts and the associated types.

ArtifactType
event receiversevent/receiver
event publishersevent/publisher
execution Plansplansevent/execution-plan
event streamevent/stream
Note
titleSpecific UI restrictions
If the above mentioned artifacts are being deployed using a C-App, you are restricted on editing or deleting them. Therefore, if you need to edit the C-App, you need to re-pack and re-deploy it.

Creating a C-App

Follow the steps below to create a C-App with the following structure.

Code Block
languagetext
├──artifacts.xml
├──WSO2EventReceiver_1.0.0
│       ├──artifact.xml
│       └──WSO2EventReceiver-1.0.0.xml
└──HighFrequentTweetsLogger_1.0.0
        ├──artifact.xml
        └──HighFrequentTweetsLogger-1.0.0.xml

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

    Code Block
    languagexml
    <?xml version="1.0" encoding="UTF-8"?><artifacts><artifacts>
    <artifact name="SampleC-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>

  2. Create separate directories in the top level of the 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 C-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. 

  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
    languagexml
    <?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 directory. 

  5. Create the the HighFrequentTweetsLogger-1.0.0.xml xml file, which is the actual event publisher file that you deploy in WSO2 CEP  inside the HighFrequentTweetsLogger_1.0.0.0 directory 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 C-App.

...