[prev in list] [next in list] [prev in thread] [next in thread]
List: wsas-java-dev
Subject: [Dev] Transport Adaptor (Broker) In CEP
From: Mohanadarshan Vivekanandalingam <mohan () wso2 ! com>
Date: 2013-03-30 18:25:30
Message-ID: CAHf1eqTDhx8ZyMfwQP0DbSkwHpPFOOEgVmPiKd78z_9aUbMK_g () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi,
We have started the work of modifying the CEP server. As the first step we
have start re-writing the broker module of the CEP. In our next release we
are going to have Transport Adaptor module instead of broker module.
Transport Adaptor module going to do similar work as broker does. But
through the Transport adaptor module we can provide more user friendliness.
In the new architecture, same as broker module the core part will be handle
by the Transport Adaptor.
*Transport Adaptor Core*
- Transport Adaptor core contains the base methods to create
transportAdaptorDto and to handle transport adaptor configuration details.
- It exposes two services, 1) to register a transport adaptor 2) to get
the information about transport adaptors.
- It allows to write external transport adaptor component and register
it easily.
- Each and every transport adaptor types (broker types - jms, agent &
etc...) is written as individual module and registered with this transport
adaptor core.
Other important module which manages the transport adaptor is transport
adaptor manager. This module contains 3 sub components. There are core,
admin & UI, similar as old broker manager module.
But in the new module we have changed some old implementations.
*Transport Adaptor Manager Core*
- We have remove the registry related configurations of a transport
adaptor (broker). and all the transport adaptor information are stored as a
xml file like we are handing the bucket.
- We have also provided the hot deployment facility for transport
adaptor creation.
- All the transport adaptor information will store in the file system.
- It access the transport adaptor service and get the information
regarding the transport adaptors and their properties.
- It exposes a service to get the transport adaptor configuration and to
store the new transport adaptor configuration.
*Transport Adaptor Manager Admin*
- It act as an interface between the UI and core.
- It exposes an admin service to UI to get the information that needed
to create the UI and to store those information
This architecture will also provide the flexibility to integrated the CEP
with other products easily.
We are now moving forward to create the UI component for transport adaptor.
Hope our new design will provide more flexibility to work with CEP...
Any suggestions?
Thanks & Regards
Mohan
--
*V. Mohanadarshan*
*Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com *
*lean.enterprise.middleware.*
*
*
email: mohan@wso2.com
phone:(+94) 771117673
[Attachment #5 (text/html)]
<div><font face="tahoma, sans-serif">Hi,</font></div><div><font face="tahoma, \
sans-serif"><br></font></div><div><font face="tahoma, sans-serif">We have started the \
work of modifying the CEP server. As the first step we have start re-writing the \
broker module of the CEP. In our next release we are going to have Transport Adaptor \
module instead of broker module. Transport Adaptor module going to do similar work as \
broker does. But through the Transport adaptor module we can provide more user \
friendliness. </font></div> <div><font face="tahoma, \
sans-serif"><br></font></div><div><font face="tahoma, sans-serif">In the new \
architecture, same as broker module the core part will be handle by the Transport \
Adaptor.</font></div><div><font face="tahoma, sans-serif"><br> \
</font></div><div><font face="tahoma, sans-serif"><b>Transport Adaptor Core</b> \
</font></div><div><ul><li><font face="tahoma, sans-serif">Transport Adaptor core \
contains the base methods to create transportAdaptorDto and to handle transport \
adaptor configuration details.</font></li> <li><font face="tahoma, sans-serif">It \
exposes two services, 1) to register a transport adaptor 2) to get the information \
about transport adaptors.</font></li><li><font face="tahoma, sans-serif">It allows to \
write external transport adaptor component and register it easily.</font></li> \
<li><font face="tahoma, sans-serif">Each and every transport adaptor types (broker \
types - jms, agent & etc...) is written as individual module and registered with \
this transport adaptor core.</font></li></ul><div><font face="tahoma, \
sans-serif"><br> </font></div></div><div><font face="tahoma, sans-serif">Other \
important module which manages the transport adaptor is transport adaptor manager. \
This module contains 3 sub components. There are core, admin & UI, similar as old \
broker manager module.</font></div> <div><font face="tahoma, sans-serif">But in the \
new module we have changed some old implementations.</font></div><div><font \
face="tahoma, sans-serif"><br></font></div><div><b><font face="tahoma, \
sans-serif">Transport Adaptor Manager Core</font></b></div> <div><ul><li><font \
face="tahoma, sans-serif">We have remove the registry related configurations of a \
transport adaptor (broker). and all the transport adaptor information are stored as a \
xml file like we are handing the bucket. </font></li> <li><font face="tahoma, \
sans-serif">We have also provided the hot deployment facility for transport adaptor \
creation.</font></li><li><font face="tahoma, sans-serif">All the transport adaptor \
information will store in the file system.</font></li> <li><font face="tahoma, \
sans-serif">It access the transport adaptor service and get the information regarding \
the transport adaptors and their properties.</font></li><li><font face="tahoma, \
sans-serif">It exposes a service to get the transport adaptor configuration and to \
store the new transport adaptor configuration. </font></li> </ul></div><div><font \
face="tahoma, sans-serif"><br></font></div><div><b><font face="tahoma, \
sans-serif">Transport Adaptor Manager Admin</font></b></div><div><ul><li><span \
style="font-family:tahoma,sans-serif">It act as an interface between the UI and \
core.</span></li> <li><span style="font-family:tahoma,sans-serif">It exposes an admin \
service to UI to get the information that</span><span \
style="font-family:tahoma,sans-serif"> needed to create the UI and to store those \
information</span></li> </ul><div><font face="tahoma, \
sans-serif"><br></font></div></div><div><font face="tahoma, sans-serif">This \
architecture will also provide the flexibility to integrated the CEP with other \
products easily. </font></div><div> <font face="tahoma, sans-serif">We are now moving \
forward to create the UI component for transport adaptor. Hope our new design will \
provide more flexibility to work with CEP...</font></div><div><font face="tahoma, \
sans-serif">Any suggestions?</font></div> <div><font face="tahoma, \
sans-serif"><br></font></div><div><font face="tahoma, \
sans-serif"><br></font></div><div><font face="tahoma, \
sans-serif"><br></font></div><div><font face="tahoma, sans-serif">Thanks & \
Regards</font></div> <div><font face="tahoma, \
sans-serif">Mohan</font></div><div><font face="tahoma, sans-serif"> \
</font></div><div><font face="tahoma, sans-serif"> </font></div><font face="tahoma, \
sans-serif"><br clear="all"></font><div><font face="tahoma, sans-serif"><br> \
</font></div><font face="tahoma, sans-serif">-- <br></font><div dir="ltr"><font \
color="#444444" face="tahoma, sans-serif"><b \
style="background-color:rgb(255,255,255)">V. Mohanadarshan</b></font><div><div><font \
color="#444444" size="1" face="tahoma, sans-serif"><b \
style="background-color:rgb(255,255,255)">Software Engineer,</b></font></div> \
<div><font color="#444444" size="1" face="tahoma, sans-serif"><b \
style="background-color:rgb(255,255,255)">Data Technologies \
Team,</b></font></div><div><font color="#444444" size="1" face="tahoma, \
sans-serif"><b style="background-color:rgb(255,255,255)">WSO2, Inc. <a \
href="http://wso2.com" target="_blank">http://wso2.com</a> </b></font></div> \
<div><font color="#444444" size="1" face="tahoma, sans-serif"><b \
style="background-color:rgb(255,255,255)">lean.enterprise.middleware.</b></font></div></div><div><font \
color="#444444" face="tahoma, sans-serif"><b \
style="background-color:rgb(255,255,255)"><br> </b></font></div><div><font \
style="background-color:rgb(255,255,255)" color="#444444" size="1" face="tahoma, \
sans-serif">email: <a href="mailto:mohan@wso2.com" target="_blank">mohan@wso2.com</a> \
</font></div><div><font style="background-color:rgb(255,255,255)" color="#444444" \
size="1" face="tahoma, sans-serif">phone:(+94) 771117673</font></div> </div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic