Re: [Architecture] Improving BAM toolbox deployment

[Maninda Edirisooriya]

Hi all,

After the discussion about BAM tooling we has come to a solution. Similar
to the other archive deployment, we are going to make the artifacts
deployed from the toolbox, read-only. Then every artifact editing should be
done with Developer Studio. This will remove the unnecessary complexity of
deployment and delegate the main artifact creation / edition capability to
dev-studio.


*Maninda Edirisooriya*
Software Engineer

*WSO2, Inc.*lean.enterprise.middleware.

*Blog* : http://maninda.blogspot.com/
*Phone* : +94 777603226


On Wed, Jan 29, 2014 at 1:02 PM, Srinath Perera  wrote:

> I have scheduled a chat for next monday
>
>
> On Wed, Jan 29, 2014 at 11:54 AM, Maninda Edirisooriya 
> wrote:
>
>> Although there is no proper Dev-studio story for BAM it will be possible.
>> There is no theoretical restriction we found. But the problem is editing
>> each artifact separately in the deployed setup and propagating changes to
>> other nodes with Dep-Sync. There are several problems. It is difficult to
>> explain everything here. Will talk offline and reply back.
>>
>>
>> *Maninda Edirisooriya*
>> Software Engineer
>>
>> *WSO2, Inc. *lean.enterprise.middleware.
>>
>> *Blog* : http://maninda.blogspot.com/
>> *Phone* : +94 777603226
>>
>>
>> On Tue, Jan 28, 2014 at 11:27 PM, Paul Fremantle  wrote:
>>
>>> I think we also need to be able to edit the different aspects (stream,
>>> analyzer, dashboard) independently. If there is versioned deployment of
>>> each aspect then we could update say the dashboard without the analyzers or
>>> vice-versa.
>>>
>>> Paul
>>>
>>>
>>> On 28 January 2014 17:08, Isabelle Mauny  wrote:
>>>

 On Tue, Jan 28, 2014 at 1:20 PM, Paul Fremantle  wrote:

> 1. Every artifact deployed from the toolbox should be editable from
> the UI.
>
> i) Streams will be edited from the new UI that is going to be
> implemented.
> ii) Hive scripts can already be edited from the UI
> iii) Dashboards will be editable with the UES jaggery editor.


 Maninda,

 Those editors need to go in Dev Studio - We need the Create/Update
 toolbox support there. You can either create a template for a new toolbox,
 or import and edit an existing toolbox. This is inline with what we agreed
 to in SL couple weeks ago.

 Thanks.
 --
 Isabelle Mauny

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Paul Fremantle
>>> CTO and Co-Founder, WSO2
>>> OASIS WS-RX TC Co-chair, Apache Member
>>>
>>> UK: +44 207 096 0336
>>> US: +1 646 595 7614
>>>
>>> blog: http://pzf.fremantle.org
>>> twitter.com/pzfreo
>>> p...@wso2.com
>>>
>>> wso2.com Lean Enterprise Middleware
>>>
>>> Disclaimer: This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may have
>>> received this communication in error, please reply to the sender indicating
>>> that fact and delete the copy you received and in addition, you should not
>>> print, copy, retransmit, disseminate, or otherwise use the information
>>> contained in this communication. Internet communications cannot be
>>> guaranteed to be timely, secure, error or virus-free. The sender does not
>>> accept liability for any errors or omissions.
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> 
> Srinath Perera, Ph.D.
>http://people.apache.org/~hemapani/
>http://srinathsview.blogspot.com/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Going further with Repository API/SPI

[Senaka Fernando]

Hi Shazni,

You should return a new Embedded Registry instance per call. The whole
point of having lazy loading inside the Embedded Registry is to get rid of
the expensiveness, :).

Regards,
Senaka.


On Fri, Feb 7, 2014 at 6:36 AM, Shazni Nazeer  wrote:

> Hi Senaka and all,
>
> I've been able to introduce lazy loading on EmbeddedRegistry as I stated
> above. Further as the next step I removed AXIOM dependency on XML parsing
> and used DOM instead and tested the change.
>
> I think what remains is getting rid of UserRegistry and other deprecated
> classes. As the next step I'm going to remove UserRegistry, hence UserRealm
> from UserStore.
>
> Now in this process I need to clarify few things.
>
> Are we going to have only the EmbeddedRegistry in the code?
>
> It's recommended to have only one EmbeddedRegistry in general for all
> operations per application (there are exceptions when the application needs
> to connect to different data sources). So if we are going to have only the
> EmbeddedRegistry, every time a registry instance is requested, are we going
> to return a new Embeddedregistry, which is going to be expensive?
>
> I hope the answer is No. In that case, we need to have a wrapper Registry
> for EmbeddedRegistry and use it to keep the information like the 'chroot'
> and tenantId.
>
> WDYT?
>
> regards,
>
> Shazni Nazeer
>
> Senior Software Engineer
>
> Mob : +94 715 440 607
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
>
> On Thu, Feb 6, 2014 at 10:57 AM, Shazni Nazeer  wrote:
>
>> Hi Senaka,
>>
>> Yes, the current code is in GitHub. You can clone the current code at
>> https://github.com/shazni/Repository.git
>>
>> I'll go through the staged process that you are suggesting. I can
>> introduce lazy loading into EmbeddedRegistry. The reason I told
>> GhostRegistry is dependant on UserRegistry was that, AFAIU, GhostRegistry
>> does lazy loading only on UserRegistry, but not on EmbeddedRegistry in the
>> C4 code. It doesn't lazy load EmbeddedRegistry. EmbeddedRegistry get loaded
>> initially with EmbeddedRegistryService. But IMO, even that needs to be lazy
>> loaded and I'll do what you are suggesting.
>>
>> And then, we are in the last stage of removing AXIOM (by introducing DOM)
>> and then UserRegistry and finally all the other deprecated code. These
>> three tasks will be done step by step, but it will certainly affect the
>> platform and IMO is ok because we are in the last step. I'll try to be
>> online at the said time to have a chat on this.
>>
>> regards,
>>
>> Shazni Nazeer
>>
>> Senior Software Engineer
>>
>> Mob : +94 715 440 607
>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>> Blog : http://shazninazeer.blogspot.com
>>
>>
>> On Wed, Feb 5, 2014 at 11:30 PM, Senaka Fernando  wrote:
>>
>>> Hi Shazni,
>>>
>>> Please do this in a staged process. As of now, is the code you worked on
>>> so far in GitHub? Also, after that's done, you can remove the axiom
>>> dependency, and integrate ghost registry into embedded registry without
>>> removing user registry. Basically, write a new ghost registry logic inside
>>> the embedded registry and validate the lazy loading logic, and convert the
>>> existing ghost registry class to simply a wrapper that invokes the user
>>> registry. This way, you would move the logic to the right level without
>>> impacting the existing functionality. Did you get what I mean? If you want
>>> to clarify further over skype/g-talk, I'm online between 10.30-11.30am LKT.
>>>
>>> Thanks,
>>> Senaka.
>>>
>>>
>>> On Wed, Feb 5, 2014 at 12:07 PM, Shazni Nazeer  wrote:
>>>
 Hi Senaka,

 Hoping you are reading the mail.

 I've currently removed RemoteRegistry and integrated CacheBackRegistry
 with EmbeddeRegistry. And at this state I ran the integration test cases
 and it passes with similar figures as I shared earlier.

 What remains to do is follows,

- Removing the AXIOM dependency and using DOM to parse the
configuration.
- Removing the UserRegistry
- Integrating GhostRegistry (This is dependant on UserRegistry, so
have to do with UserRegistry removal)
- Removing the marked deprecated things like Comments, Tags.

 I think from this point onwards the platform is going to be completely
 broken, as it's highly dependant on these. I'll keep a copy of the code of
 the current status and thought of moving forward in doing the above 4 step.

 WDYT???

 Shazni Nazeer

 Senior Software Engineer

 Mob : +94 715 440 607
 LinkedIn : http://lk.linkedin.com/in/shazninazeer
 Blog : http://shazninazeer.blogspot.com

>>>
>>>
>>>
>>> --
>>>
>>>
>>> *[image: http://wso2.com]  Senaka Fernando*
>>> Senior Technical Lead; WSO2 Inc.; http://wso2.com
>>>
>>>
>>>
>>> * Member; Apache Software Foundation; http://apache.org
>>> E-mail: senaka AT wso2.com 

Re: [Architecture] Going further with Repository API/SPI

[Shazni Nazeer]

Hi Senaka and all,

I've been able to introduce lazy loading on EmbeddedRegistry as I stated
above. Further as the next step I removed AXIOM dependency on XML parsing
and used DOM instead and tested the change.

I think what remains is getting rid of UserRegistry and other deprecated
classes. As the next step I'm going to remove UserRegistry, hence UserRealm
from UserStore.

Now in this process I need to clarify few things.

Are we going to have only the EmbeddedRegistry in the code?

It's recommended to have only one EmbeddedRegistry in general for all
operations per application (there are exceptions when the application needs
to connect to different data sources). So if we are going to have only the
EmbeddedRegistry, every time a registry instance is requested, are we going
to return a new Embeddedregistry, which is going to be expensive?

I hope the answer is No. In that case, we need to have a wrapper Registry
for EmbeddedRegistry and use it to keep the information like the 'chroot'
and tenantId.

WDYT?

regards,

Shazni Nazeer

Senior Software Engineer

Mob : +94 715 440 607
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com


On Thu, Feb 6, 2014 at 10:57 AM, Shazni Nazeer  wrote:

> Hi Senaka,
>
> Yes, the current code is in GitHub. You can clone the current code at
> https://github.com/shazni/Repository.git
>
> I'll go through the staged process that you are suggesting. I can
> introduce lazy loading into EmbeddedRegistry. The reason I told
> GhostRegistry is dependant on UserRegistry was that, AFAIU, GhostRegistry
> does lazy loading only on UserRegistry, but not on EmbeddedRegistry in the
> C4 code. It doesn't lazy load EmbeddedRegistry. EmbeddedRegistry get loaded
> initially with EmbeddedRegistryService. But IMO, even that needs to be lazy
> loaded and I'll do what you are suggesting.
>
> And then, we are in the last stage of removing AXIOM (by introducing DOM)
> and then UserRegistry and finally all the other deprecated code. These
> three tasks will be done step by step, but it will certainly affect the
> platform and IMO is ok because we are in the last step. I'll try to be
> online at the said time to have a chat on this.
>
> regards,
>
> Shazni Nazeer
>
> Senior Software Engineer
>
> Mob : +94 715 440 607
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
> Blog : http://shazninazeer.blogspot.com
>
>
> On Wed, Feb 5, 2014 at 11:30 PM, Senaka Fernando  wrote:
>
>> Hi Shazni,
>>
>> Please do this in a staged process. As of now, is the code you worked on
>> so far in GitHub? Also, after that's done, you can remove the axiom
>> dependency, and integrate ghost registry into embedded registry without
>> removing user registry. Basically, write a new ghost registry logic inside
>> the embedded registry and validate the lazy loading logic, and convert the
>> existing ghost registry class to simply a wrapper that invokes the user
>> registry. This way, you would move the logic to the right level without
>> impacting the existing functionality. Did you get what I mean? If you want
>> to clarify further over skype/g-talk, I'm online between 10.30-11.30am LKT.
>>
>> Thanks,
>> Senaka.
>>
>>
>> On Wed, Feb 5, 2014 at 12:07 PM, Shazni Nazeer  wrote:
>>
>>> Hi Senaka,
>>>
>>> Hoping you are reading the mail.
>>>
>>> I've currently removed RemoteRegistry and integrated CacheBackRegistry
>>> with EmbeddeRegistry. And at this state I ran the integration test cases
>>> and it passes with similar figures as I shared earlier.
>>>
>>> What remains to do is follows,
>>>
>>>- Removing the AXIOM dependency and using DOM to parse the
>>>configuration.
>>>- Removing the UserRegistry
>>>- Integrating GhostRegistry (This is dependant on UserRegistry, so
>>>have to do with UserRegistry removal)
>>>- Removing the marked deprecated things like Comments, Tags.
>>>
>>> I think from this point onwards the platform is going to be completely
>>> broken, as it's highly dependant on these. I'll keep a copy of the code of
>>> the current status and thought of moving forward in doing the above 4 step.
>>>
>>> WDYT???
>>>
>>> Shazni Nazeer
>>>
>>> Senior Software Engineer
>>>
>>> Mob : +94 715 440 607
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>> Blog : http://shazninazeer.blogspot.com
>>>
>>
>>
>>
>> --
>>
>>
>> *[image: http://wso2.com]  Senaka Fernando*
>> Senior Technical Lead; WSO2 Inc.; http://wso2.com
>>
>>
>>
>> * Member; Apache Software Foundation; http://apache.org
>> E-mail: senaka AT wso2.com **P: +1
>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*;
>>
>>
>> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In:
>> http://linkedin.com/in/senakafernando
>> *Lean . Enterprise . Middleware
>>
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Updated Invitation: EMM to IoT @ Fri 2014-02-07 13:30 - 14:20 (az...@wso2.com)

[Afkham Azeez]

I am cancelling this event because Srinath & Sanjiva cannot make it today.
We definitely need them to attend this since this is the very first
brainstorming session, and we should establish the vision.

Azeez


On Thu, Feb 6, 2014 at 7:51 PM, az...@wso2.com  wrote:

> This event has been changed.
> more details 
> >>
> EMM to IoT
> *Changed: *1. Please join my meeting, Feb 7, 2014 at 8:00 AM GMT.
> https://www4.gotomeeting.com/join/927250255
>
> 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or,
> call in using your telephone.
>
> United Arab Emirates (toll-free): 800 044 40444
> Argentina (toll-free): 0 800 444 2385
> Austria: +43 (0) 7 2088 0716
> Austria (toll-free): 0 800 080061
> Australia: +61 2 8355 1038
> Australia (toll-free): 1 800 191 358
> Belgium: +32 (0) 28 08 4372
> Belgium (toll-free): 0 800 81388
> Bulgaria (toll-free): 00800 120 4413
> Bahrain (toll-free): 800 81 305
> Brazil (toll-free): 0 800 047 4909
> Belarus (toll-free): 8 820 0011 0331
> Canada: +1 (647) 497-9380
> Canada (toll-free): 1 877 777 3281
> Switzerland: +41 (0) 435 0026 89
> Switzerland (toll-free): 0 800 000 452
> China (toll-free): 4008 866154
> Czech Republic (toll-free): 800 500453
> Germany: +49 (0) 811 8899 6934
> Germany (toll-free): 0 800 723 5274
> Denmark: +45 (0) 69 91 84 58
> Denmark (toll-free): 8025 0919
> Spain: +34 931 76 1534
> Spain (toll-free): 800 900 593
> Finland: +358 (0) 931 58 1773
> Finland (toll-free): 0 800 94473
> France: +33 (0) 170 950 590
> France (toll-free): 0 805 541 052
> United Kingdom: +44 20 7151 1817
> United Kingdom (toll-free): 0 808 168 0209
> Hong Kong SAR China (toll-free): 30774812
> Hungary (toll-free): (06) 80 986 259
> Indonesia (toll-free): 001 803 020 2563
> Ireland: +353 (0) 15 133 006
> Ireland (toll-free): 1 800 818 263
> Israel (toll-free): 1 809 388 020
> India (toll-free): 000 800 100 8227
> Iceland (toll-free): 800 9993
> Italy: +39 0 699 26 68 65
> Italy (toll-free): 800 792289
> Japan (toll-free): 0 120 242 200
> South Korea (toll-free): 0806180880
> Luxembourg (toll-free): 800 81016
> Mexico (toll-free): 01 800 123 8367
> Malaysia (toll-free): 1 800 81 6860
> Netherlands: +31 (0) 208 080 759
> Netherlands (toll-free): 0 800 020 0178
> Norway: +47 21 04 30 59
> Norway (toll-free): 800 69 055
> New Zealand: +64 (0) 9 974 9579
> New Zealand (toll-free): 0 800 47 0051
> Panama (toll-free): 001 800 507 2789
> Peru (toll-free): 0 800 55253
> Philippines (toll-free): 1 800 1110 1565
> Poland (toll-free): 00 800 3211434
> Portugal (toll-free): 800 180 139
> Russia (toll-free): 8 800 100 6914
> Saudi Arabia (toll-free): 800 844 3636
> Sweden: +46 (0) 852 500 691
> Sweden (toll-free): 020 794 545
> Singapore (toll-free): 800 101 3000
> Thailand (toll-free): 001 800 852 2442
> Turkey (toll-free): 00 800 4488 29001
> Taiwan (toll-free): 0 800 666 846
> Ukraine (toll-free): 0 800 50 4691
> United States: +1 (626) 521-0017
> United States (toll-free): 1 877 309 2070
> Uruguay (toll-free): 000 405 4459
> South Africa (toll-free): 0 800 988 836
> Access Code: 927-250-255
> Audio PIN: Shown after joining the meeting
>
> Meeting ID: 927-250-255
>
> GoToMeeting(R)
> Online Meetings Made Easy(R)
>
> Not at your computer? Click the link to join this meeting from your
> iPhone(R), iPad(R) or Android(R) device via the GoToMeeting app.
>
> *When*
> Fri 2014-02-07 13:30 - 14:20 Colombo
> *Where*
> LK 5th Floor Meeting Room - Garage 
> (map
> )
> *Calendar*
> az...@wso2.com
> *Who*
>  *
> Afkham Azeez - organizer
> *
> Lance Douglas
> *
> Shanmugarajah Sinnathamby
> *
> Paul Fremantle
> *
> architecture@wso2.org
> *
> Srinath Perera
> *
> Sanjiva Weerawarana
> *
> Sumedha Rubasinghe
>
> Going?   *Yes
> 
> - Maybe
> 
> - No
> *
> more options 
> >>

Re: [Architecture] [C5] Clustering SPI

[Sameera Jayasoma]

Kishanthan and I chatted over the possible designs of the Clustering SPI
implementations and how to make it easy to plug in new clustering
implementations using the provided SPI.

Carbon clustering module allows its consumers (Component developers) to
work with a cluster of products. I.e sending messages to cluster, to get
notified about new member additions or removals etc. Clustering module uses
a cluster communication engine underneath to support all these features. By
default it uses Hazelcast [1], but we have designed this module such that
any cluster communication engine can be plugged in.

According to the existing design, whenever you are plugging in a new
cluster communication engine you have to read the cluster.xml and
initialize the ClusterConfiguration and register yourself as a
ClusteringAgent. This means that every implementation has to write
boiler-plate code perform above actions and alsoCarbon Clustering module
has no control over selecting and initializing the correct implementation.

To overcome this problem we change existing design. Now Carbon clustering
module is responsible for discovering the correct implementation.
Clustering implementations just need to register themselves as OSGi
services. During the server startup, Carbon clustering engine will populate
the ClusterConfiguration and the ClusterContext and initialize the correct
clustering implementation by passing the ClusterContext.

*ClusterConfiguration* - Holds all the static properties defined in the
cluster.xml
*ClusterContext* - Holds all the dynamic information such as members in the
cluster, membership listeners implementations etc. ClusterContext has a
reference to the ClusterConfiguration as well.


Thanks,
Sameera.

[1] http://www.hazelcast.org


On Sun, Jan 19, 2014 at 11:40 AM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:

> Clustering SPI provides the ability to plug-in different clustering
> implementation to carbon. By default, carbon will ship hazel-cast based
> clustering impl. There will be a separate file (cluster.xml) for cluster
> configuration.
>
> The SPI will contain the following main interfaces.
>
> *ClusteringAgent* - is responsible for initializing and managing this
> node in the cluster.
> *MembershipScheme* - a representation of a membership scheme such as
> "multicast" or "well-known address (wka) used in the cluster.
>
> A high-level view can be as follows
>
> [image: Inline image 1]
>
> When the cluster agent is successfully initialized, it will also register
> the Cluster Service (being discussed at "[C5] Clustering API"). The
> Cluster Service will use the clustering agent underneath at implementation
> level for its required operations. Based on previous experiences, we have
> defined the following methods for clustering agent and membership scheme
> for now. Based on the final outcome of this discussion, they may get
> changed.
>
> *ClusteringAgent*
>
> /**
>  * Initialize the agent which will initialize this node, and join the
> cluster
>  */
> void *init*() throws ClusteringFault;
>
> /**
>  * Shutdown the agent which will remove this node from cluster
>  */
> void *shutdown*() throws ClusteringFault;
>
> /**
>  * Set carbon configuration context to this agent to be used in the
> clustering impl
>  */
> void *setConfigurationContext*(CarbonConfigurationContext
> configurationContext);
>
> /**
>  * Get the list of static members
>  */
> List *getStaticMembers*();
>
> /**
>  * Get the number of members alive.
>  */
> int *getAliveMemberCount*();
>
> /**
>  * Send a message to all members in the cluster
>  */
> List *sendMessage*(ClusterMessage msg, boolean
> isSync)
> throws ClusteringFault;
>
> /**
>  * Send a message to a set of specific members in the cluster
>  */
> List *sendMessage*(ClusterMessage msg,
> List members, boolean isSync)
> throws ClusteringFault;
>
>
> *MembershipScheme*
>
> void *init*() throws ClusteringFault;
>
> void *joinGroup*() throws ClusteringFault;
>
>
> Thoughts?
>
> Thanks,
> Kishanthan.
> --
>  *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com *
> Twitter - *http://twitter.com/kishanthan *
>



-- 
Sameera Jayasoma,
Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

Lean . Enterprise . Middleware
<>___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Canceled Event: EMM to IoT @ Fri 2014-02-07 13:30 - 14:20 (az...@wso2.com)

[az...@wso2.com]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VEVENT
DTSTART:20140207T08Z
DTEND:20140207T085000Z
DTSTAMP:20140207T041843Z
ORGANIZER;CN=Afkham Azeez:mailto:az...@wso2.com
UID:52sin551nu54novkogb9cdb...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=La
 nce Douglas;X-NUM-GUESTS=0:mailto:la...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=Sh
 anmugarajah Sinnathamby;X-NUM-GUESTS=0:mailto:s...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=Pa
 ul Fremantle;X-NUM-GUESTS=0:mailto:p...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=Afkham
  Azeez;X-NUM-GUESTS=0:mailto:az...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ar
 chitect...@wso2.org;X-NUM-GUESTS=0:mailto:architecture@wso2.org
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=LK 5
 th Floor Meeting Room - Garage;X-NUM-GUESTS=0:mailto:wso2.com_2d34313836353
 13232393...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=Sr
 inath Perera;X-NUM-GUESTS=0;X-RESPONSE-COMMENT="Have a talk at just before.
  I will try to come over. \n\nThere is a Fedality meeting overlapping. ":ma
 ilto:srin...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=Sa
 njiva Weerawarana;X-NUM-GUESTS=0:mailto:sanj...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=Su
 medha Rubasinghe;X-NUM-GUESTS=0:mailto:sume...@wso2.com
CREATED:20140206T053545Z
DESCRIPTION:1.  Please join my meeting\, Feb 7\, 2014 at 8:00 AM GMT.\nhttp
 s://www4.gotomeeting.com/join/927250255\n\n2.  Use your microphone and spea
 kers (VoIP) - a headset is recommended. Or\, call in using your telephone.\
 n\nUnited Arab Emirates (toll-free): 800 044 40444\nArgentina (toll-free): 
 0 800 444 2385\nAustria: +43 (0) 7 2088 0716\nAustria (toll-free): 0 800 08
 0061\nAustralia: +61 2 8355 1038\nAustralia (toll-free): 1 800 191 358\nBel
 gium: +32 (0) 28 08 4372\nBelgium (toll-free): 0 800 81388\nBulgaria (toll-
 free): 00800 120 4413\nBahrain (toll-free): 800 81 305\nBrazil (toll-free):
  0 800 047 4909\nBelarus (toll-free): 8 820 0011 0331\nCanada: +1 (647) 497
 -9380\nCanada (toll-free): 1 877 777 3281\nSwitzerland: +41 (0) 435 0026 89
 \nSwitzerland (toll-free): 0 800 000 452\nChina (toll-free): 4008 866154\nC
 zech Republic (toll-free): 800 500453\nGermany: +49 (0) 811 8899 6934\nGerm
 any (toll-free): 0 800 723 5274\nDenmark: +45 (0) 69 91 84 58\nDenmark (tol
 l-free): 8025 0919\nSpain: +34 931 76 1534\nSpain (toll-free): 800 900 593\
 nFinland: +358 (0) 931 58 1773\nFinland (toll-free): 0 800 94473\nFrance: +
 33 (0) 170 950 590\nFrance (toll-free): 0 805 541 052\nUnited Kingdom: +44 
 20 7151 1817\nUnited Kingdom (toll-free): 0 808 168 0209\nHong Kong SAR Chi
 na (toll-free): 30774812\nHungary (toll-free): (06) 80 986 259\nIndonesia (
 toll-free): 001 803 020 2563\nIreland: +353 (0) 15 133 006\nIreland (toll-f
 ree): 1 800 818 263\nIsrael (toll-free): 1 809 388 020\nIndia (toll-free): 
 000 800 100 8227\nIceland (toll-free): 800 9993\nItaly: +39 0 699 26 68 65\
 nItaly (toll-free): 800 792289\nJapan (toll-free): 0 120 242 200\nSouth Kor
 ea (toll-free): 0806180880\nLuxembourg (toll-free): 800 81016\nMexico (toll
 -free): 01 800 123 8367\nMalaysia (toll-free): 1 800 81 6860\nNetherlands: 
 +31 (0) 208 080 759\nNetherlands (toll-free): 0 800 020 0178\nNorway: +47 2
 1 04 30 59\nNorway (toll-free): 800 69 055\nNew Zealand: +64 (0) 9 974 9579
 \nNew Zealand (toll-free): 0 800 47 0051\nPanama (toll-free): 001 800 507 2
 789\nPeru (toll-free): 0 800 55253\nPhilippines (toll-free): 1 800 1110 156
 5\nPoland (toll-free): 00 800 3211434\nPortugal (toll-free): 800 180 139\nR
 ussia (toll-free): 8 800 100 6914\nSaudi Arabia (toll-free): 800 844 3636\n
 Sweden: +46 (0) 852 500 691\nSweden (toll-free): 020 794 545\nSingapore (to
 ll-free): 800 101 3000\nThailand (toll-free): 001 800 852 2442\nTurkey (tol
 l-free): 00 800 4488 29001\nTaiwan (toll-free): 0 800 666 846\nUkraine (tol
 l-free): 0 800 50 4691\nUnited States: +1 (626) 521-0017\nUnited States (to
 ll-free): 1 877 309 2070\nUruguay (toll-free): 000 405 4459\nSouth Africa (
 toll-free): 0 800 988 836\nAccess Code: 927-250-255\nAudio PIN: Shown after
  joining the meeting\n\nMeeting ID: 927-250-255\n\nGoToMeeting®\nOnline Mee
 tings Made Easy®\n\nNot at your computer? Click the link to join this meeti
 ng from your iPhone®\, iPad® or Android® device via the GoToMeeting app.
LAST-MODIFIED:20140207T041843Z
LOCATION:LK 5th Floor Meeting Room - Garage
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:EMM to IoT
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/c

[Architecture] Updated Invitation: EMM to IoT @ Fri 2014-02-07 13:30 - 14:20 (az...@wso2.com)

[az...@wso2.com]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20140207T08Z
DTEND:20140207T085000Z
DTSTAMP:20140206T142124Z
ORGANIZER;CN=Afkham Azeez:mailto:az...@wso2.com
UID:52sin551nu54novkogb9cdb...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Lance Douglas;X-NUM-GUESTS=0:mailto:la...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Shanmugarajah Sinnathamby;X-NUM-GUESTS=0:mailto:s...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Paul Fremantle;X-NUM-GUESTS=0:mailto:p...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Afkham Azeez;X-NUM-GUESTS=0:mailto:az...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=architecture@wso2.org;X-NUM-GUESTS=0:mailto:architecture@wso2.org
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE;C
 N=LK 5th Floor Meeting Room - Garage;X-NUM-GUESTS=0:mailto:wso2.com_2d34313
 83635313232393...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Srinath Perera;X-NUM-GUESTS=0:mailto:srin...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sanjiva Weerawarana;X-NUM-GUESTS=0:mailto:sanj...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Sumedha Rubasinghe;X-NUM-GUESTS=0:mailto:sume...@wso2.com
CREATED:20140206T053545Z
DESCRIPTION:1.  Please join my meeting\, Feb 7\, 2014 at 8:00 AM GMT.\nhttp
 s://www4.gotomeeting.com/join/927250255\n\n2.  Use your microphone and spea
 kers (VoIP) - a headset is recommended. Or\, call in using your telephone.\
 n\nUnited Arab Emirates (toll-free): 800 044 40444\nArgentina (toll-free): 
 0 800 444 2385\nAustria: +43 (0) 7 2088 0716\nAustria (toll-free): 0 800 08
 0061\nAustralia: +61 2 8355 1038\nAustralia (toll-free): 1 800 191 358\nBel
 gium: +32 (0) 28 08 4372\nBelgium (toll-free): 0 800 81388\nBulgaria (toll-
 free): 00800 120 4413\nBahrain (toll-free): 800 81 305\nBrazil (toll-free):
  0 800 047 4909\nBelarus (toll-free): 8 820 0011 0331\nCanada: +1 (647) 497
 -9380\nCanada (toll-free): 1 877 777 3281\nSwitzerland: +41 (0) 435 0026 89
 \nSwitzerland (toll-free): 0 800 000 452\nChina (toll-free): 4008 866154\nC
 zech Republic (toll-free): 800 500453\nGermany: +49 (0) 811 8899 6934\nGerm
 any (toll-free): 0 800 723 5274\nDenmark: +45 (0) 69 91 84 58\nDenmark (tol
 l-free): 8025 0919\nSpain: +34 931 76 1534\nSpain (toll-free): 800 900 593\
 nFinland: +358 (0) 931 58 1773\nFinland (toll-free): 0 800 94473\nFrance: +
 33 (0) 170 950 590\nFrance (toll-free): 0 805 541 052\nUnited Kingdom: +44 
 20 7151 1817\nUnited Kingdom (toll-free): 0 808 168 0209\nHong Kong SAR Chi
 na (toll-free): 30774812\nHungary (toll-free): (06) 80 986 259\nIndonesia (
 toll-free): 001 803 020 2563\nIreland: +353 (0) 15 133 006\nIreland (toll-f
 ree): 1 800 818 263\nIsrael (toll-free): 1 809 388 020\nIndia (toll-free): 
 000 800 100 8227\nIceland (toll-free): 800 9993\nItaly: +39 0 699 26 68 65\
 nItaly (toll-free): 800 792289\nJapan (toll-free): 0 120 242 200\nSouth Kor
 ea (toll-free): 0806180880\nLuxembourg (toll-free): 800 81016\nMexico (toll
 -free): 01 800 123 8367\nMalaysia (toll-free): 1 800 81 6860\nNetherlands: 
 +31 (0) 208 080 759\nNetherlands (toll-free): 0 800 020 0178\nNorway: +47 2
 1 04 30 59\nNorway (toll-free): 800 69 055\nNew Zealand: +64 (0) 9 974 9579
 \nNew Zealand (toll-free): 0 800 47 0051\nPanama (toll-free): 001 800 507 2
 789\nPeru (toll-free): 0 800 55253\nPhilippines (toll-free): 1 800 1110 156
 5\nPoland (toll-free): 00 800 3211434\nPortugal (toll-free): 800 180 139\nR
 ussia (toll-free): 8 800 100 6914\nSaudi Arabia (toll-free): 800 844 3636\n
 Sweden: +46 (0) 852 500 691\nSweden (toll-free): 020 794 545\nSingapore (to
 ll-free): 800 101 3000\nThailand (toll-free): 001 800 852 2442\nTurkey (tol
 l-free): 00 800 4488 29001\nTaiwan (toll-free): 0 800 666 846\nUkraine (tol
 l-free): 0 800 50 4691\nUnited States: +1 (626) 521-0017\nUnited States (to
 ll-free): 1 877 309 2070\nUruguay (toll-free): 000 405 4459\nSouth Africa (
 toll-free): 0 800 988 836\nAccess Code: 927-250-255\nAudio PIN: Shown after
  joining the meeting\n\nMeeting ID: 927-250-255\n\nGoToMeeting®\nOnline Mee
 tings Made Easy®\n\nNot at your computer? Click the link to join this meeti
 ng from your iPhone®\, iPad® or Android® device via the GoToMeeting app.\nV
 iew your event at http://www.google.com/calendar/event?action=VIEW&eid=NTJz
 aW41NTFudTU0bm92a29nYjljZGJ2djQgYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&tok=MTQjYXplZX
 pAd3NvMi5jb203NmIzMmQ3YzY5MjNlNjIyNTdhYWI1YmQ0NjA1MjQ3MGQ2YzMyNjNm&ctz=Asia
 /Colombo&hl=en.
LAST-MODIFIED:20140206T142123Z
LOCATION:LK 5th Floor Meeting Room - Garage
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:E

[Architecture] Updated Invitation: EMM to IoT @ Fri 2014-02-07 13:30 - 14:20 (az...@wso2.com)

[az...@wso2.com]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20140207T08Z
DTEND:20140207T085000Z
DTSTAMP:20140206T131004Z
ORGANIZER;CN=Afkham Azeez:mailto:az...@wso2.com
UID:52sin551nu54novkogb9cdb...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Lance Douglas;X-NUM-GUESTS=0:mailto:la...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Shanmugarajah Sinnathamby;X-NUM-GUESTS=0:mailto:s...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Paul Fremantle;X-NUM-GUESTS=0:mailto:p...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Afkham Azeez;X-NUM-GUESTS=0:mailto:az...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=architecture@wso2.org;X-NUM-GUESTS=0:mailto:architecture@wso2.org
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE;CN=LK 5th Floor Meeting Room - Garage;X-NUM-GUESTS=0:mailto:wso2.com_2d3
 431383635313232393...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Srinath Perera;X-NUM-GUESTS=0:mailto:srin...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sanjiva Weerawarana;X-NUM-GUESTS=0:mailto:sanj...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sumedha Rubasinghe;X-NUM-GUESTS=0:mailto:sume...@wso2.com
CREATED:20140206T053545Z
DESCRIPTION:View your event at http://www.google.com/calendar/event?action=
 VIEW&eid=NTJzaW41NTFudTU0bm92a29nYjljZGJ2djQgYXJjaGl0ZWN0dXJlQHdzbzIub3Jn&t
 ok=MTQjYXplZXpAd3NvMi5jb203NmIzMmQ3YzY5MjNlNjIyNTdhYWI1YmQ0NjA1MjQ3MGQ2YzMy
 NjNm&ctz=Asia/Colombo&hl=en.
LAST-MODIFIED:20140206T131004Z
LOCATION:LK 5th Floor Meeting Room - Garage
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:EMM to IoT
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Extending workflow integration in API Manager

[Amila De Silva]

Hi,

In the previous API Manager release we incorporated workflows for the
following operations;

1. User Signup.

2. Application Creation.

3. Creating subscriptions.

As a part of the API Manager 2.0.0 release, we are planning to integrate
workflows for other useful business operations. These are the areas we have
identified currently;

 1. Token Generation - As of now, after creating an application,
application owner can Generate a Production or Sandbox access token (or
both) for an application. What actually happens at this point is the
application getting registered as an OAuth application of either type. With
this feature, a workflow will be executed when registering the application,
so it'll be after an admin user confirms, the application will be able to
obtain Production (or Sandbox) keys. Using this feature administrators can
allow users\developers to create Sandbox keys to continue
development\testing , but defer generating Production keys until the
testing is done.

2. Adding/Updating Comments - Currently users can post comments about the
APIs and these will be displayed in the store without any moderation. With
this feature, comments can be moderated before they are displayed.

Appreciate your suggestions on these.

Further we'd like to identify any additional useful operations we can
integrate workflows for.

-- 
*Amila De Silva*

*Software Engineer*
WSO2 Inc.
mobile :(+94) 775119302
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Embedded cassandra server in MB leads to problems in evaluations with load testing

[Shammi Jayasinghe]

Hi All,

As all you may know, WSO2 Message Broker is tightly coupled with apache
cassandra and we install cassandra server feature to the product when
making the pack and ship MB with embedded cassandra.

Once a user downloads and starts the pack with out any configuration
change, MB uses this embedded cassandra for functioning and it is more than
enough for functionality verification.

How ever, we could observe that, many new users trying to do load testing
with this embedded cassandra with millions of messages and it is a known
fact that MB can not handle that much load with embedded cassandra and it
is essential to configure MB to run with an external cassandra server for
load testing as in documentation[1] with tuned paramaters[2].

If a user , test the MB for load with embedded cassandra, it will raise
problems and it makes a bad first impression on MB products. So, we would
like to have a solution to overcome this and could some one give us an idea
to overcome this problem.

[1]
http://docs.wso2.org/display/MB210/Standalone+Deployment+on++External+Cassandra+Server
[2]http://docs.wso2.org/display/MB210/Cassandra+Tuned+Up+Configurations


Thanks
Shammi
-- 
Best Regards,

*  Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture