Re: [Architecture] Adding/Managing Sensor information on CDMF

On Wed, Sep 16, 2015 at 7:45 PM, Viraj Senevirathne wrote: > Hi all, > > In my experience I think it is important to identify each sensor in the > system separately if there are several of similar sensors exists. If each > sensor and device in the system can be distinguish separately it is very >

Re: [Architecture] [AppFactory][GSoC] CLI Tool for App Factory

All these proposals sound good to me. On Sep 15, 2015 10:08 PM, "Anuruddha Premalal" wrote: > Hi Dmitry, > > On Tue, Sep 15, 2015 at 2:27 AM, Dmitry Sotnikov wrote: > >> For App Cloud scenarios, should we have the executable available for >> download from Settings? Another alternative is to have

Re: [Architecture] ITERATE MEDIATOR

Thanks for your answer, those have been very useful, On Wed, Sep 16, 2015 at 1:24 PM, Colin Roy-Ehri wrote: > Hi John, > Inside the Iterate mediator, use a mediator, then use the > mediator in the OutSequence. For reference, please see this > iterate/aggregate sample (1) or the EIP guide here

Re: [Architecture] [ESB-Connector] EJB Connector

Hi Chanaka/Dushan, Thank you to add some ideas on this Thread. I’m Currently searching on implement new EJB Connector with Current EJB Mediator Functions and possibilities to add more features. So i will add your ideas also in the development. On Wed, Sep 16, 2015 at 10:27 PM, Dushan Abeyruwan wr

Re: [Architecture] ITERATE MEDIATOR

Hi John, Inside the Iterate mediator, use a mediator, then use the mediator in the OutSequence. For reference, please see this iterate/aggregate sample (1) or the EIP guide here (2). In the EIP example, a clone mediator is used instead of iterate, but the aggregate functions in the same way. (

Re: [Architecture] ITERATE MEDIATOR

Hi John, You can use a property to count the number of iterations and invoke the next service once all iterations are finished. For example, -- -call service--- Thanks, On Wed, Sep 16, 2015 at

Re: [Architecture] ITERATE MEDIATOR

Colin, thanks for your answer, actually I am using the iterate mediator, the problem is that I want to receive the original message, iterate over all the items calling the service for each one and finally call another service onlye once, but the service is invoked many times. this is what I have n

Re: [Architecture] ITERATE MEDIATOR

Hi John Q, The aggregate mediator is used for exactly this purpose (1). (1) https://docs.wso2.com/display/ESB481/Aggregate+Mediator Thanks, Colin Roy-Ehri Software Engineer *WSO2, Inc. : wso2.com * *Mobile* : 812-219-6517 On Wed, Sep 16, 2015 at 12:56 PM, John Q wrot

Re: [Architecture] [ESB-Connector] EJB Connector

Hi I guess there are many improvements to be made if you writing connector, and would certainly looking forward to see new design rather what we currently have in EJB mediator [1] (it seems original doc is corrupted) Existing problems - EJB mediator binds with Bean mediator when we need to

[Architecture] ITERATE MEDIATOR

Hello, I´m beginner and I need some help with the ESB. This is my situation: I will receive a message with many items, I need to iterate the items list and call a service for creating each item. At the end of all of the calls, I need to call another service to notify the end of items creation. h

Re: [Architecture] [ESB-Connector] EJB Connector

Hi Rajjaz, Well, if you see any issue with the EJB mediator, please report them and help us to improve the existing mediator. It is not required to repeat the functionality of the EJB mediator in the new connector which you are going to develop. Could you elaborate on a use case for this EJB conne

Re: [Architecture] [APIM] Hard Throttling limit for APIs

For displaying at Publisher, throttling limits have to persisted on a DB in some format (either in the registry artifact, in the swagger definition or in AM_API table). But at the runtime, values will be picked from the synapse definition. Plan is to enforce the hard limit on a particular version

Re: [Architecture] [APIM] Hard Throttling limit for APIs

On Wed, Sep 16, 2015 at 5:08 PM, Sanjeewa Malalgoda wrote: > Yes what you said have value actually. > But wont it make things complicated? For the initial implementation we may > go with configuration per API/Endpoint. > May be later we need to implement something to have multiple back end > serv

Re: [Architecture] [APIM] Hard Throttling limit for APIs

Yes what you said have value actually. But wont it make things complicated? For the initial implementation we may go with configuration per API/Endpoint. May be later we need to implement something to have multiple back end services for same API(endpoint per resource). And at that point we need to

Re: [Architecture] Adding/Managing Sensor information on CDMF

Hi all, In my experience I think it is important to identify each sensor in the system separately if there are several of similar sensors exists. If each sensor and device in the system can be distinguish separately it is very easy to integrate any system. For example: Think about a behavior anal

Re: [Architecture] Adding/Managing Sensor information on CDMF

@Dulitha and @ Sachith I see both your comments ends with the same question whether we need to have event stream definition for each sensor type or do we need to maintain a separate event stream for each sensor type on a device type ?. eg: stream definition: Use Case 1 : org.wso2.devices.temperat

Re: [Architecture] [DAS] Modifying the migration tool to use Hector replacing CQL

Great. I think we can re-use this effort for purging and archiving tool as well. On Wed, Sep 16, 2015 at 2:03 PM, Sachith Withana wrote: > Yes. We are shipping the tool with DAS. > > On Wed, Sep 16, 2015 at 1:52 PM, Malith Dhanushka wrote: > >> I mean are we shipping this with DAS as a default

Re: [Architecture] [APIM] Hard Throttling limit for APIs

On Wed, Sep 16, 2015 at 1:42 PM, Amila De Silva wrote: > > On Wed, Sep 9, 2015 at 11:47 AM, Sanjeewa Malalgoda > wrote: > >> I also believe we should use existing handler without writing new one. >> >> And regarding registry decoupling, publisher may be able to push API to >> gateway as we do no

[Architecture] [ESB-Connector] EJB Connector

Hi All, I have planned to Implement EJB Connector for WSO2 ESB. Currently, EJB mediator supports EJB3 Stateless Session Beans and Stateful Session Beans. Since EJB mediator have some isues EJB Connector will include the Functionality of EJB mediator which calls an external Enterprise JavaBean (EJB

Re: [Architecture] [ESB-Connector] EJB Connector

On Wed, Sep 16, 2015 at 2:04 PM, Rajjaz Mohammed wrote: > Hi All, > I have planned to Implement EJB Connector for WSO2 ESB. Currently, EJB > mediator supports EJB3 Stateless Session Beans and Stateful Session Beans. > Since EJB mediator have some isues EJB Connector will include the > Functionali

Re: [Architecture] [DAS] Modifying the migration tool to use Hector replacing CQL

Yes. We are shipping the tool with DAS. On Wed, Sep 16, 2015 at 1:52 PM, Malith Dhanushka wrote: > I mean are we shipping this with DAS as a default tool? > > On Wed, Sep 16, 2015 at 1:43 PM, Sachith Withana wrote: > >> @Malith >> What do you mean as a generic tool? >> >> @Ramith >> I think tha

Re: [Architecture] [DAS] Modifying the migration tool to use Hector replacing CQL

I mean are we shipping this with DAS as a default tool? On Wed, Sep 16, 2015 at 1:43 PM, Sachith Withana wrote: > @Malith > What do you mean as a generic tool? > > @Ramith > I think that only works with Cassandra 2.0 onwards (If I'm not mistaken) > and BAM uses Cassandra 1.x versions. That was t

Re: [Architecture] [APIM] Hard Throttling limit for APIs

On Wed, Sep 16, 2015 at 1:42 PM, Amila De Silva wrote: > > On Wed, Sep 9, 2015 at 11:47 AM, Sanjeewa Malalgoda > wrote: > >> I also believe we should use existing handler without writing new one. >> >> And regarding registry decoupling, publisher may be able to push API to >> gateway as we do no

Re: [Architecture] IBM MQ Inbound/Connector for WSO2 ESB

Hi, I suggest to start with 7.5 version. A lot of customers are using this version and they are late in upgrading because of licensing price. In the end, everything can be tested against latest version. Thank you, -- Gabriel Popa | WSO2 Partner > On Sep 16, 2015, at 9:20 AM, Kirish

Re: [Architecture] [DAS] Modifying the migration tool to use Hector replacing CQL

@Malith What do you mean as a generic tool? @Ramith I think that only works with Cassandra 2.0 onwards (If I'm not mistaken) and BAM uses Cassandra 1.x versions. That was the initial issue. On Wed, Sep 16, 2015 at 1:18 PM, Ramith Jayasinghe wrote: > so, > > http://docs.datastax.com/en/drivers/j

Re: [Architecture] IBM MQ Inbound/Connector for WSO2 ESB

Hi Krishanthy, IBM MQ V8.0.0 is the latest stable release. As Chanaka suggested better to go with the latest. Thanks. On Wed, Sep 16, 2015 at 12:02 PM, Chanaka Fernando wrote: > Hi Krishanthy, > > It is always better to work with the latest stable release. My suggestion > is to go with V8.X if

Re: [Architecture] [APIM] Hard Throttling limit for APIs

On Wed, Sep 9, 2015 at 11:47 AM, Sanjeewa Malalgoda wrote: > I also believe we should use existing handler without writing new one. > > And regarding registry decoupling, publisher may be able to push API to > gateway as we do now. > And just before we call rest API admin service we may call regi

Re: [Architecture] [DAS] Modifying the migration tool to use Hector replacing CQL

so, http://docs.datastax.com/en/drivers/java/2.0/com/datastax/driver/core/ResultSet.html#fetchMoreResults() doesn't work for you? On Wed, Sep 16, 2015 at 12:22 PM, Malith Dhanushka wrote: > Hi Sachith, > > +1 for using Hector and this will be a handy utility tool for DAS as well. > Because any