Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

On Wed, Nov 13, 2013 at 10:53 AM, Subash Chaturanga wrote: > > On Tue, Nov 12, 2013 at 8:19 PM, Sriskandarajah Suhothayan > wrote: > >> Just a suggestion. I would like this gadget gen tool to take a template >> gadget and a conf file as the input, ask to enter the UI options based on >> the conf

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

Hi all, As Ashansa has pointed out rather than connecting to the databases directly and retrieving data the rest apis supported by different entities can be used. For example the issue tracker has its own api. The registry supports this also. WDYT? Thanks GayanD Gayan Dhanuska Software Engineer

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

On Tue, Nov 12, 2013 at 8:19 PM, Sriskandarajah Suhothayan wrote: > Just a suggestion. I would like this gadget gen tool to take a template > gadget and a conf file as the input, ask to enter the UI options based on > the conf and generate the gadget based on the template gadget file. > Whereby we

Re: [Architecture] [AppFactory] Non Buildable artifact deploy directly from appfactory to S2-Git

Hi ashansa, It is just remove artifact from s2-git , like same as buildable artifact in current impl that checkout it, remove and push. then it will be undeployed by stratos. thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * * * email: **

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

Hi all, I couldn't participate due to unavoidable circumstances. We would be needing the following in appfactory. 1) Multi tenancy support from UES.. 2) Store need to work for multi tenancy 3) Tenant dashboard should be a customizable 4) Role based gadgets (so only that role can use it) Thanks.

Re: [Architecture] [AppFactory] Non Buildable artifact deploy directly from appfactory to S2-Git

The demote statement is bit unclear for me, hope we are not going to undeploy the artifact :) On Wed, Nov 13, 2013 at 9:12 AM, Dimuthu Leelarathne wrote: > > > Hi, > > On Tue, Nov 12, 2013 at 2:49 PM, Harsha Thirimanna wrote: > >> Hi, >> >> We have few artifact type that shouldn't want to build

Re: [Architecture] [AppFactory] Non Buildable artifact deploy directly from appfactory to S2-Git

Hi, On Tue, Nov 12, 2013 at 2:49 PM, Harsha Thirimanna wrote: > Hi, > > We have few artifact type that shouldn't want to build like Jaggery, PHP. > So customer will not accept to start separate build server without having > such a requirement. Because of that we thought to handle this deployment

Re: [Architecture] [AppFactory] Non Buildable artifact deploy directly from appfactory to S2-Git

Hi, We have another approach to do this. We can copy the repository as it is from repository-git to s2-git from server to server without doing check out to local folder it appfactory. When promote that, we can do the same thing. But when we demote it, we have to check out the artifact from s2-git

Re: [Architecture] CEP timing with varying window sizes

Hi Daya, What is the query you used? Could you try this monitoring the size of the queue (should add a log to show size of the queue for every 100k message or so)? Can we test with non-blocking queue? Another explanation to drop is that there are too much events in the window at 1.5M TPS. But we

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

Just a suggestion. I would like this gadget gen tool to take a template gadget and a conf file as the input, ask to enter the UI options based on the conf and generate the gadget based on the template gadget file. Whereby we can support many types of gadgets. This is impingement because in the curr

[Architecture] [Jaggery] [Test] Test framework for jaggery

Hi, Still we do not have jaggery test framework even though there are considerable jaggery applications were developed. It is not easy maintain those jaggery applications/APIs steady without testing frame work. Now onward we will starting $subject as it is important for jaggery as well as there

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

Hi All, So this whole discussion started with us publishing all data (irrespective of whether we have it stored or not) whenever an action happened in AppFactory. We can categorize these actions as 1. Those actions where data is stored within AppFactory and where the datasource will not change 2.

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

I meant write some proper gadget but using db of our issue tracker. So if we move to some other issue tracker , then we have to rewrite retrieval part to that api to show the gadgets. We don't want to generalize our gadget or extension that much by evaluation most common issue tracker right now. B

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

Hi Dhanushka, No need to rewrite the whole gadget. Just changing the datasource and the query is enough. Then there is no point of having issue related gadgets in the dashboard at all when we are using appfac issue tracker and internal databases. Thanks. GayanD Gayan Dhanuska Software Engineer h

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

Hi Gayan, Rather than directly reading from the db, it would be good to use the REST API to get the required data. ( If we do not have the required API implementation we may have to look into that first ) On Tue, Nov 12, 2013 at 5:07 PM, Danushka Fernando wrote: > But if we do this way then whe

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

But if we do this way then when we go for jira or any other issue tracker we need to rewrite the whole gadget. This question was ones raised by Manjula if you remember. IMO we shouldn't do things like that. When we plug a new system writing an extensions is ok. But changing a code isn't ok for me.

Re: [Architecture] [AppFactory] Non Buildable artifact deploy directly from appfactory to S2-Git

Hi Harsha, It would be good to disconnect the app types which should not be buildable from the build server since it is a valid scenario that people do not want to have a build server if they need only some application types which does not need to be built. But there are few concerns regarding thi

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

Hi Gayan, Yes it is. We have done only few features in issue tracker for the basic appfactory only. Most of the time we would have to implement to the JIRA, or some other issue tracker later. Better to develop for our issue tracker first, if it is not big workaround. thanks *Harsha Thirimanna*

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

This will be for the people who are going to use the appfactory issue tracker. Otherwise we can only accommodate at the request of the customer only. This raises another important question. What would be the future of appfactory issue tracker? Thanks. GayanD Gayan Dhanuska Software Engineer http:

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

On Tue, Nov 12, 2013 at 4:03 PM, Lasantha Fernando wrote: > Hi Tanya, > > > On 12 November 2013 15:50, Isabelle Mauny wrote: > >> Sure - These are static dashboards. But a user must be able to create >> their own dashboards , on top on the ones we are delivering by default. In >> this case, they

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

On Tue, Nov 12, 2013 at 3:50 PM, Isabelle Mauny wrote: > Sure - These are static dashboards. But a user must be able to create > their own dashboards , on top on the ones we are delivering by default. In > this case, they would create their own toolbox , leveraging the gadgetgen > tool you discus

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

Hi Tanya, On 12 November 2013 15:50, Isabelle Mauny wrote: > Sure - These are static dashboards. But a user must be able to create > their own dashboards , on top on the ones we are delivering by default. In > this case, they would create their own toolbox , leveraging the gadgetgen > tool you

[Architecture] Updated Invitation: ES Publisher Code Review @ Wed Nov 13, 2013 2pm - 3pm (samee...@wso2.com)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20131113T083000Z DTEND:20131113T093000Z DTSTAMP:20131112T103233Z ORGANIZER;CN=samee...@wso2.com:mailto:samee...@wso2.com UID:e5329fdrho9quttnedrjh2l...@google.com ATT

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

Sure - These are static dashboards. But a user must be able to create their own dashboards , on top on the ones we are delivering by default. In this case, they would create their own toolbox , leveraging the gadgetgen tool you discussed right? Thanks. -- Isabelle Mauny Director, Product Ma

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

On Tue, Nov 12, 2013 at 3:24 PM, Isabelle Mauny wrote: > For APIM, we need consumer dashboards as well. > Isabelle, Consumer dashboards are static dashboards that we can ship with APIM. Right ? IS there a need for consumers to go ahead and create dashboards themselves containing their preferred

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

@Gayand : In the first discussion we had about issue tracker we considered versioning. Please contact Punnadi/Manisha/Ramith. And If you are going to take this database what happens if we change the IssueTracker itself. We need to rewrite this gadget. So for the stuff that stored outside AF we shou

Re: [Architecture] [Appfactory] Use of existing appfactory data sources for dashboards instead of publishing everything to BAM

Hi all, In the current issue tracker db we are not capturing an issue's lifecycle stage. But there is a gadget called "Issues by stage". Hence that information is needed. Shall we add a new column to the ISSUE table in the Issue tracker db? Thanks. GayanD Gayan Dhanuska Software Engineer http://

Re: [Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

For APIM, we need consumer dashboards as well. Isabelle. __ Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ On Nov 12, 2013, at 10:52 AM, Tanya Madurapperuma wrote: > Hi all, > > Following is the meeting notes of the

[Architecture] [Meeting Notes] UES integration with BAM / CEP / APIM

Hi all, Following is the meeting notes of the $Subject. Participants : Anjana, Gokul, Mohan, Lasantha, SameeraP, Shiro, Lalaji, Joe, Chan, Gillian (over the phone), UES team BAM = 1. Some tool simialar to Gadget gen tool will developed in UES side and there will be a url from carbon cons

Re: [Architecture] Integrating Enterprise Store With API Manager

Hi Sumedha, All three things are not yet supported, but we can have them for APIM migration, will create jira items in the store side. Regards, /Nuwan On Tue, Nov 12, 2013 at 2:01 PM, Sumedha Rubasinghe wrote: > Nuwan, > I was going through some of the TODO items for API Manager & came across

Re: [Architecture] Upgrading jdbc pool version

Hi Manoj, Please apply the attached patch for kernel patch0002 Thanks On Tue, Nov 12, 2013 at 2:11 PM, Chanika Geeganage wrote: > Hi, > > > On Tue, Nov 12, 2013 at 1:03 AM, Jackie Wheeler wrote: > >> Will this change be in Carbon 5? I'd like to add a note in the About This >> Release page of

[Architecture] [AppFactory] Non Buildable artifact deploy directly from appfactory to S2-Git

Hi, We have few artifact type that shouldn't want to build like Jaggery, PHP. So customer will not accept to start separate build server without having such a requirement. Because of that we thought to handle this deployment from appfactoy. Just checkout the repository to appfactory local folder

Re: [Architecture] Upgrading jdbc pool version

Hi, On Tue, Nov 12, 2013 at 1:03 AM, Jackie Wheeler wrote: > Will this change be in Carbon 5? I'd like to add a note in the About This > Release page of the appropriate product docs. > > Yes this will be there in the Carbon 5 and I'm going to add this in the kernel patch0002 too. > > On Mon,

Re: [Architecture] Integrating Enterprise Store With API Manager

Nuwan, I was going through some of the TODO items for API Manager & came across following. 1. Tenant specific store themes. Configurable via UI (internal : RM1407) 2. Password recovery for store (internal: AM -> RM1330, IS -> RM686) 3. Multiple dashboard UIs under several links How much of suppor