[Architecture] [EMM] EMM 2.0.0 Dashboard Use-cases

Hi All, Following are some obvious use-cases for the dashboard view of EMM 2.0.0. (Also considering our previous release of EMM 1.1.0 - see below) ​ ​ Captured Use-cases : [1] Stats on Devices Total Count Count By Platform (Android / iOS / Windows) Count By Ownership Type (COPE /

Re: [Architecture] [Architecture ]OpenWeatherMap Connector for WSO2 ESB

Hi Thulasika, There won't be any unit tests but integration tests. Usually it'll take more than 1 day to do integration tests. Please change according and talk to your mentor. On Mon, Aug 3, 2015 at 3:48 PM, Thulasika Vijayanathan thulas...@wso2.com wrote: Hi All, I have attached my

Re: [Architecture] [BPS] BPMN data publisher for DAS

Does BPEL engine has analytics support? does the stream definitions are the same as what BPEL engine uses? Does process execution generate any events other than start and end? Can we capture those also? For generating charts, use https://github.com/wso2/VizGrammar. Talk to Dunith for more info.

Re: [Architecture] [BPS] BPMN data publisher for DAS

We decided to collect all information once the data publisher is enabled. instead of allowing user to select options, That way, we can implement the charts as required. Regards Nandika On Tue, Aug 4, 2015 at 9:28 AM, Srinath Perera srin...@wso2.com wrote: Does BPEL engine has analytics

Re: [Architecture] [AF] ESB Apptype Resources section

Hi all, The registry resources may contain sensitive data that we do not need to expose to anyone who is having a download link or access to source code. Can we further list down set of resources we are concerned here? IMO, we need to securely transfer the car file from jenkins and provide a

Re: [Architecture] [BPS] BPMN data publisher for DAS

Does process execution generate any events other than start and end? Can we capture those also? We are capturing process level as well as task level events. We can capture generic events for processes (i.e. process start time, end time, initiator) and tasks (i.e. task creation time, claim

Re: [Architecture] [Architecture ]OpenWeatherMap Connector for WSO2 ESB

Hi All, I have attached my milestone plan in[1]. [1]. https://docs.google.com/a/wso2.com/spreadsheets/d/1Cig8kM6JHqDg25D6x0bYJl65rXt4cv9kdbWwg6R9m1Q/edit?usp=sharing Thanks, Thulasika. On Mon, Aug 3, 2015 at 12:16 PM, Thulasika Vijayanathan thulas...@wso2.com wrote: Hi All, I have

Re: [Architecture] [APIM] Removing Subscription when an API retired

+1 if its temporary outage then that should be blocked. Deprecate and retire means they will never come back. So we may clean all data associated with given API. Lets make sure we remove all data including subscriptions, resources, scopes etc Thanks, sanjeewa. On Mon, Aug 3, 2015 at 3:44 PM,

Re: [Architecture] [AF] Adding CAR application type to App Factory

After revisiting the architecture, we changed having three different Resources CAR files to one CAR file. And in the UI we will let other users to upload a CAR file for other stages. Reason for this change is that in AF we don't allow to commit, build, deploy after the promotion. But QAs/DevOps

[Architecture] [APIM] Removing Subscription when an API retired

Hi All, I'm working on JiRA [1] When we try to delete a retired API from API Publisher, if that API has subscriptions, APIM won't allow to delete that API. As a solution, APIM can remove those subscription when retiring the API. But, If a API owner temporarly retired the API and later in some

Re: [Architecture] [APIM] Removing Subscription when an API retired

We should get confirmation before he retires to make sure he knows what he's doing. I don't think retiring an API temporarily is a valid scenario. Retiring means he's removing it from the runtime totally. So if there are existing users, they'll get service outages. He also has options to Block

Re: [Architecture] Deploying an ESB Connector with a cApp?

Hi Kasun/Malaka, Once we import a connector into DevS, it will be stored in a shared location for all the ESB projects in workplace. We can use the connectors in this shared location while creating CAPP. Please note that these connectors will not be uploaded to the SVN or Git while uploading

[Architecture] Fwd: [Architecture ]OpenWeatherMap Connector for WSO2 ESB

Hi All, I have planned to develop $subject as described below. Introduction OpenWeatherMap API used to access current weather data for any location on Earth including over 200,000 cities.Current weather is frequently updated based on global models and data from more than 40,000 weather stations.

Re: [Architecture] Deploying an ESB Connector with a cApp?

Hi Viraj, thx for the details explanation. AFAIK currently we provide import connectors from store directly or local file location? However we can't go ahead with the solution 2 due to the following reasons. 1. Some users build there own set of connectors and it may not be available in

Re: [Architecture] [Dev] [GSoC-2015] Proposal2 : Siddhi Editor for WSO2 CEP

Hi Suho, As per the discussion last time , I have implemented the context aware auto-completion feature with regular expression based approach. Currently this supports - Syntax completions : For stream,table, function definition statements and query statements appropriately -

Re: [Architecture] [Dev] [GSoC-2015] Proposal2 : Siddhi Editor for WSO2 CEP

Sure, we'll have a chat on this next Wednesday Suho On Mon, Aug 3, 2015 at 1:50 PM, Tharindu Munasinghe munasinghethari...@gmail.com wrote: Hi Suho, As per the discussion last time , I have implemented the context aware auto-completion feature with regular expression based approach.

Re: [Architecture] Deploying an ESB Connector with a cApp?

Hi Malaka, As we discussed offline, considering the difficulties and limitations of deploying connectors as Maven artifacts into public repo, we will introduce a new project type for connectors in DevS. Users have to create a connector project and add connectors into it. Then these connectors can

[Architecture] [AF] ESB Apptype Resources section

Hi All Currently in AF we have four kind of resources/runtime configs. 1. Databases 2. Data Sources 3. APIs 4. Registry Resources But for ESB Apptype only Registry Resources will be valid. So in the UI we need to show only registry resources for the application.

Re: [Architecture] [APIM] Removing Subscription when an API retired

I don't think we should be removing resources and scopes. Because we're not deleting the API here but only retiring it. If the publisher wants to bring it back online he can do so but he would have lost all subscriptions by then, which is fine IMO. Thanks, NuwanD. On Mon, Aug 3, 2015 at 4:31 PM,

Re: [Architecture] Implement File Connector for zip file for WSO2 ESB

Hi For the record , please refer [1] [1] https://wso2.org/jira/browse/ESBCONNECT-52 Cheers, Dushan On Mon, Aug 3, 2015 at 1:10 AM, Gayan Gunarathne gay...@wso2.com wrote: On Sun, Aug 2, 2015 at 9:03 PM, Dushan Abeyruwan dus...@wso2.com wrote: Hi Malaka, [Adding Gayan G] I guess

Re: [Architecture] [APIM] Removing Subscription when an API retired

Retired means it never come back right. So what is the purpose of maintaining some additional data. Context and version can be maintain to avoid another API creation with same name context. IMO other than that we do not need anything. Thanks, sanjeewa. On Mon, Aug 3, 2015 at 6:46 PM, Nuwan Dias

Re: [Architecture] [APIM] Removing Subscription when an API retired

Well, we can't really say can we? There might be a use case where someone decides to bring it back online. Besides, someone might want to create a new version by copying a retired API. Therefore I don't think its right to partially delete information of the API just because we're retiring it.