Re: [Architecture] Implementing Latency Metrics Calculation Feature in GW

On Wed, Dec 16, 2015 at 12:38 PM, Isuru Ranawaka wrote: > > >- Data receiver needs to be Asynchronously collect the data without >blocking GW threads. > > What would be the approach we are planning to take here? Thanks > >- Latency Calculation Engine should be

Re: [Architecture] [MSS] Support lifecycle methods

Hi Isuru, In MetricsInterceptor, I can see multiple interceptors are collecting data but could not figure out how they are published to a central server. It it done by the metric manager? Would you mind explaining how this works?

Re: [Architecture] PPaaS Artifact Migration Tool

Hi All, This is the component architecture diagram of PPaaS Artifact Migration Tool. @ Chamila : Thank you for the suggestions and we will improve the tool as mentioned. ​ We highly appreciate your suggestions on this model. Thank you. On Fri, Dec 18, 2015 at 1:09 AM, Chamila De Alwis

[Architecture] WSO2 Carbon Kernel 5.0.0 Released !!!

*WSO2 Carbon Kernel 5.0.0 - Released !!!* We are pleased to announce the release of WSO2 Carbon Kernel 5.0.0. It is now available to download from here . The source and tag location for this release are available

Re: [Architecture] [BPMN] Implementing correlation support for BPMN Rest API

Hi Frank, Please find my comments inline. The process model you have drawn enables multiple receiving message events in parallel. According to the BPMN 2.0 spec this is not allowed for key-based correlation (i.e. the correlation mechanism similar to BPEL correlation sets); but it is allowed for

[Architecture] WebSockets support in ESB 4.10

Hi all, We are working on adding WebSockets support into ESB 4.10. For the default HTTP transport we won't be able to incorporate it as HTTPCore doesn't offer native WebSockets support. However, with the concept of inbound endpoints/connectors we will be able to implement it by leveraging Netty.

Re: [Architecture] WebSockets support in ESB 4.10

Yes Eranga. That's is a valid use case. AFAIR, we discuss about this use case with Kevin. @Kevin : WDYT? On Tue, Dec 22, 2015 at 12:03 PM, Eranga Perera wrote: > Hi, > > How can we facilitate broadcasting to a web socket channel. If there are > multiple subscribers to that

Re: [Architecture] Connector Improvements 2016

Hi Elilmatha & Ashalya, Can you list down the connectors we are planning to improve. We need minimum of 2 batches of 8-10 connectors to start next year. On Mon, Dec 14, 2015 at 5:50 PM, Malaka Silva wrote: > Hi Elilmatha, > > Connectors like GotoWebinar, Concur and Github

Re: [Architecture] WebSockets support in ESB 4.10

Hi all, Here are the main use cases we found with related to WebSockets support in 410. 1. Websocket client to Websocket endpoint via ESB 2. Websocket client to HTTP endpoint via ESB 3. HTTP client to Websocket endpoint via ESB In each of the main use cases we need to support following

Re: [Architecture] WebSockets support in ESB 4.10

Hi, How can we facilitate broadcasting to a web socket channel. If there are multiple subscribers to that channel can we discriminate what messages should go to each subscriber. I am thinking how a web socket chat application be implemented with ESB mediation sequences. Eranga. On Tue, Dec 22,

Re: [Architecture] [MSS] Support lifecycle methods

Hi Imesh, In Metrics, there are Reporters [1]. For example, DAS reporter [2] will publish metrics to a DAS server. Metrics Reporter will not publish an event for each invocation. The reporter will report periodically and we can configure that time interval. I hope this is clear. Thanks! [1]

Re: [Architecture] Implementing Latency Metrics Calculation Feature in GW

Hi IsuruR, As you said, please try to use Metrics feature. In Metrics, you can use a reporter [1] and it will periodically report metrics. [1] http://dropwizard.github.io/metrics/3.1.0/manual/core/#reporters On Tue, Dec 22, 2015 at 6:28 AM, Imesh Gunaratne wrote: > > > On Wed,

Re: [Architecture] WebSockets support in ESB 4.10

since the the images are not rendered properly I am attaching the google document [1] herewith [1] https://docs.google.com/document/d/1rPmJT-NVsPTC1SlUZUGw4gUQJjZ2R_K1rBIAY2a1dBc/edit Regards Kevin On Tue, Dec 22, 2015 at 11:12 AM, Kevin Ratnasekera wrote: > Hi all, > Here are

Re: [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Hi, I will look into that as well. Thanks, On Tue, Dec 8, 2015 at 11:35 AM, Malaka Silva wrote: > Hi, > > One of the main issues we had when automating the integration use cases is > accesstokens getting expired and need human interaction to continue the > service. > > From

Re: [Architecture] [Dev] [EMM200] Performance & Load Testing

One of the performance hits identified while analysing the JFR dumps taken out of EMM 2.0 set-ups is the time taken for token validation. The nature of the aforesaid token validation is that, a service stub is used to invoke an admin service deployed as part of EMM's Key Manager profile for token

Re: [Architecture] [Dev] [EMM200] Performance & Load Testing

Prabath, API Manager has the same setup and it uses a Thrift client for the same (in the place of using a stub for admin service) Can't we use the same Thrift server/client pattern?We had a similar situation in BAM data publisher. There also we used Thrift for performance reasons. Stubs are known

Re: [Architecture] [BPMN] Implementing correlation support for BPMN Rest API

The process model you have drawn enables multiple receiving message events in parallel. According to the BPMN 2.0 spec this is not allowed for key-based correlation (i.e. the correlation mechanism similar to BPEL correlation sets); but it is allowed for predicate based correlation (often used in