Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?

[Viraj Rajaguru]

Hi Iranga,

IIUC, requirement is to setting a global level setting with CAR files to
enable event statistics publishing. As per this document[1], we need to set
a property in synapse.properties file + relevant config changes in artifact
files to enable statistics publishing. With CAR files we are not modifying
config files such as synapse.properties. So how can we achieve this?

Thanks,
Viraj.

[1] -
https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics

On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri 
wrote:

>
>
> On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva  wrote:
>
>> +1 and it make sense to do it since we are having the
>> a separate analytics server for ESB.
>>
>> Iranga when you say global do you mean for a CAPP or for the complete
>> deployment? I think you are referring to the second option.
>>
>
> Global setting -Having it at complete deployment  , having it at the C-App
> level  would also be a useful option as well IMO
>
>>
>> On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri 
>> wrote:
>>
>>> Hi All,
>>>
>>> When creating a C-App to publish event statistics to ESB Analytics we
>>> have to enable event statistics for each configuration ( proxy service,
>>> API,) , would there be an option to set this at a global level?
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Iranga Muthuthanthri
>>> (M) -0777-255773
>>> Team Product Management
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> (M) -0777-255773
> Team Product Management
>
>


-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

I have finished the case insensitive user operations as well and i added
selenium test scripts for those implemented functions to my repo[1] except
delete function all the other functions with test script added to my repo[1]

[1] https://github.com/asanthamax/mongodbuserstore

Thanks,
Asantha

On Fri, Jun 17, 2016 at 2:28 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> sure i'll be look forward for the hangout
>
> Thanks,
> Asantha
>
> On Fri, Jun 17, 2016 at 2:22 AM, Tharindu Edirisinghe 
> wrote:
>
>> Hi Asantha,
>>
>> I will go through the docs and provide feedback soon. Let's have a
>> hangout session to discuss the pending issues.
>>
>> I'm available today 9.00 P.M IST for a google hangout.
>>
>> Thanks,
>> TharinduE
>>
>> On Fri, Jun 17, 2016 at 11:30 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I have prepared the user guide[1] and administrator guide[2] in google
>>> doc since all tasks are not finished yet i have only added the tasks i have
>>> already done and there is still the developer guide has to be prepare i
>>> will prepare it as sooner as well
>>>
>>> [1]
>>> https://docs.google.com/document/d/1fCLfZYsPOBkHMzRCGM3aexoBSplX3bKIRmONmFsgkBc/edit?usp=sharing
>>> [2]
>>> https://docs.google.com/document/d/1mdnmYruzQz5QSxAYwM1XVeJntJMFdxUsV5gord7LuPA/edit?usp=sharing
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Tue, Jun 14, 2016 at 1:55 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 sure i will prepare those documents sooner

 Thanks,
 Asantha

 On Mon, Jun 13, 2016 at 9:38 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Excellent work Asantha !
>
> Meanwhile you can prepare a document also adding the screenshots you
> have got. Basically we will need following documentation.
>
> 1. Developer Guide ( The architecture of the userstoremanager,
> diagrams of all the collections, how they are related to each other etc.)
>
> 2. Administrator Guide (How to guide a server administrator to setup a
> secondary userstore with mongodb)
>
> 3. User Guide (All the functionality of the userstoremanager, i.e each
> function in RemoteUserStoreManager with sample SOAP requests and 
> responses)
>
> We will need to look at the QA aspect of the project also.. but let's
> keep aside for the moment until we get all the functionality working.
>
> Thanks for all the hard work !
>
> Best Regards,
> Tharindu Edirisinghe
>
> On Tue, Jun 14, 2016 at 12:46 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> as you advice me i added soap ui screen shots of test result and
>> selenium script for implemented functions into my repository[1]
>>
>> [1] https://github.com/asanthamax/mongodbuserstore
>> Thanks,
>> Asantha
>>
>> On Mon, Jun 13, 2016 at 6:23 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> i updated my blog[1] with all the works i have done so far there i
>>> added all the methods and their use in MongoDBUserStoreManager ,
>>> hopes your feedback
>>> [1] http://asanthamax.blogspot.com/
>>> Thanks,
>>> Asantha
>>>
>>> On Sun, Jun 12, 2016 at 2:11 PM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 i have solved the login issue for registered users in my mongodb
 user store. after compare my implementation with JDBCUserStoreManager i
 realized that i would gone through the wrong path by implementing
 UserStoreManager so i changed it by extending AbstractUserStoreManager
 instead of UserStoreManager thereafter most of the issues i have faced
 being resolved now it can add new users,roles and assign users to roles
 ,roles to users can change user profile claim values and also 
 registered
 users can successfully logged into IS still the delete part has to be
 implemented and i will prepare a test scripts for my already 
 implemented
 working parts sooner and from implemented modules only issue i'm 
 facing at
 the moment is i can't decrypt the salted password of MongoDB server
 configuration in user store property xml file
 And also I need some advice from you to how i can improve the
 security of my query parameters in MongoDB
 i updated all my works in my repository[1]

 [1]https://github.com/asanthamax/mongodbuserstore

 Thanks,
 Asantha

 On Fri, Jun 10, 2016 at 12:51 PM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> sorry for the delay i have updated my blog today and i'm keep
> posting all the progress in their[1

Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?

[Chanaka Fernando]

Hi Viraj,

The configuration we have in the synapse.properties file is to globally
enable/disable the statistics/tracing for the server. By enabling that, we
prepare the server to publish events to DAS server. But, if you need to
publish real events, you need to enable them in individual artifacts
(proxy, api, sequence, etc). Iranga's suggestion is to provide a global
parameter to enable/disable them all at once (per CAPP or at global level).
This is a valid requirement which a particular user might have.

This will require a considerable effort to support in the current model and
we will not be able to support in the upcoming ESB 5.0.0 version.

@Iranga: Please create a public JIRA and we will fix this in a future
release.

Thanks,
Chanaka

On Wed, Jun 22, 2016 at 12:38 PM, Viraj Rajaguru  wrote:

> Hi Iranga,
>
> IIUC, requirement is to setting a global level setting with CAR files to
> enable event statistics publishing. As per this document[1], we need to set
> a property in synapse.properties file + relevant config changes in artifact
> files to enable statistics publishing. With CAR files we are not modifying
> config files such as synapse.properties. So how can we achieve this?
>
> Thanks,
> Viraj.
>
> [1] -
> https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics
>
> On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri 
> wrote:
>
>>
>>
>> On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva  wrote:
>>
>>> +1 and it make sense to do it since we are having the
>>> a separate analytics server for ESB.
>>>
>>> Iranga when you say global do you mean for a CAPP or for the complete
>>> deployment? I think you are referring to the second option.
>>>
>>
>> Global setting -Having it at complete deployment  , having it at the
>> C-App level  would also be a useful option as well IMO
>>
>>>
>>> On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri 
>>> wrote:
>>>
 Hi All,

 When creating a C-App to publish event statistics to ESB Analytics we
 have to enable event statistics for each configuration ( proxy service,
 API,) , would there be an option to set this at a global level?

 --
 Thanks & Regards

 Iranga Muthuthanthri
 (M) -0777-255773
 Team Product Management


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> Thanks & Regards
>>
>> Iranga Muthuthanthri
>> (M) -0777-255773
>> Team Product Management
>>
>>
>
>
> --
> Viraj Rajaguru
> Associate Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?

[Isuru Udana]

Hi,


On Wed, Jun 22, 2016 at 1:45 PM, Chanaka Fernando  wrote:

> Hi Viraj,
>
> The configuration we have in the synapse.properties file is to globally
> enable/disable the statistics/tracing for the server. By enabling that, we
> prepare the server to publish events to DAS server. But, if you need to
> publish real events, you need to enable them in individual artifacts
> (proxy, api, sequence, etc). Iranga's suggestion is to provide a global
> parameter to enable/disable them all at once (per CAPP or at global level).
> This is a valid requirement which a particular user might have.
>
> Enable/disable statistics per CAR from the tool is ok, but should we do
the global level controlling at the tool level ?
Enabling statics globally is a management task.
CARs are for packaging and deployable artifacts.
Using CARs to control global level parameters doesn't sound nice to me.


> This will require a considerable effort to support in the current model
> and we will not be able to support in the upcoming ESB 5.0.0 version.
>
> @Iranga: Please create a public JIRA and we will fix this in a future
> release.
>
> Thanks,
> Chanaka
>
> On Wed, Jun 22, 2016 at 12:38 PM, Viraj Rajaguru  wrote:
>
>> Hi Iranga,
>>
>> IIUC, requirement is to setting a global level setting with CAR files to
>> enable event statistics publishing. As per this document[1], we need to set
>> a property in synapse.properties file + relevant config changes in artifact
>> files to enable statistics publishing. With CAR files we are not modifying
>> config files such as synapse.properties. So how can we achieve this?
>>
>> Thanks,
>> Viraj.
>>
>> [1] -
>> https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics
>>
>> On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri 
>> wrote:
>>
>>>
>>>
>>> On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva  wrote:
>>>
 +1 and it make sense to do it since we are having the
 a separate analytics server for ESB.

 Iranga when you say global do you mean for a CAPP or for the complete
 deployment? I think you are referring to the second option.

>>>
>>> Global setting -Having it at complete deployment  , having it at the
>>> C-App level  would also be a useful option as well IMO
>>>

 On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri >>> > wrote:

> Hi All,
>
> When creating a C-App to publish event statistics to ESB Analytics we
> have to enable event statistics for each configuration ( proxy service,
> API,) , would there be an option to set this at a global level?
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> (M) -0777-255773
> Team Product Management
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 Best Regards,

 Malaka Silva
 Senior Tech Lead
 M: +94 777 219 791
 Tel : 94 11 214 5345
 Fax :94 11 2145300
 Skype : malaka.sampath.silva
 LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
 Blog : http://mrmalakasilva.blogspot.com/

 WSO2, Inc.
 lean . enterprise . middleware
 http://www.wso2.com/
 http://www.wso2.com/about/team/malaka-silva/
 
 https://store.wso2.com/store/

 Save a tree -Conserve nature & Save the world for your future. Print
 this email only if it is absolutely necessary.

>>>
>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Iranga Muthuthanthri
>>> (M) -0777-255773
>>> Team Product Management
>>>
>>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB Analytics for MT scenarios?

[Anjana Fernando]

Hi,

I've updated the thread "Cross Tenant Data Reading from Spark Queries in
DAS", where I've done the implementation on writing back to the tenant
space also from the super tenant space as well. This basically just
eliminates the current requirement of executing identical Spark scripts in
all the tenants, which would not be desirable performance wise, and now, we
can just use super tenant's single script to process all the tenant's data
and write back the results to their space. Of course, we've to now change
the current ESB analytics scripts to use this feature, but it shouldn't be
a big change. @Gihan/Supun, can we please check on this and get it done.

Cheers,
Anjana.

On Tue, Jun 21, 2016 at 12:35 PM, Anjana Fernando  wrote:

> Hi,
>
> Yeah, as Srinath mentioned, we do have MT support there, where each ESB
> analytics data/queryeis/dashboards would be fully isolated. This is the
> usual desirable mode, when different tenants deploy their own analytics
> scripts and all, and there is no connection at all with other tenants, and
> obviously there shouldn't be. But in our solutions like this, where we
> would deploy the exact same solution in each tenant, we can potentially
> optimize the scenario by, only doing the processing in one place. This is
> actually how APIM batch queries are written at the moment. Where they
> altogether stores all the tenant's data in super tenant space and process
> and put the summarized there itself. This model works, but then, if the
> tenant itself wants to do their own processing it doesn't have access to
> the data, that was suppose to be in his space. So a solution for this is
> done, which is explained in detail in the mail "Cross Tenant Data Reading
> from Spark Queries in DAS", where optionally the super tenant can read
> tenant's data which creates a single virtual table view which contains data
> from all the tenants. From this, you can read the data, do the processing
> and store it in a table in super tenant space. In this approach, you will
> still have to have the dashboard in the super tenant space, since the data
> resides in the super tenant space. I will be doing some experiments to see
> on the feasibility of storing back summarized data in tenant space soon.
>
> Even though we can get the batch scenario working efficiently, there would
> be a problem in the CEP side, which we now use heavily in the product
> analytics scenario processing. At the moment, there is no concept of having
> a single CEP execution plan for all the tenants. When data is published to
> receivers, they will be dispatched to their own streams and execution
> plans, so we will need to find an approach for this, to optimize the
> processing of the CEP side of things. Or else, I'm not sure, since these
> are in-memory processing constructs, if having copies of the same execution
> plans will actually be okay, compared to having a single one, since the
> traffic is anyway split between them.
>
> Cheers,
> Anjana.
>
> On Tue, Jun 21, 2016 at 9:35 AM, Srinath Perera 
> wrote:
>
>> We had a chat about this.
>>
>> This is supported, however, current implementation will run spark jobs
>> per each tenant. So it will have performance concerns with a large number
>> of tenants.
>>
>> Anjana, can you give the details and potential solutions? DAS team has
>> implemented the support for reading tenant data from super tenant so we can
>> run a one Spark Job for all tenants. But we will need to change the queries
>> and figure out how tenant dashboards can get access to results in super
>> tenant's space.
>>
>> Can we do a 5.1 addressing this?
>>
>> --Srinath
>>
>> On Tue, Jun 21, 2016 at 9:15 AM, Kasun Indrasiri  wrote:
>>
>>> Please note that this will be an essential feature for our integration
>>> cloud. So, we need to decide how should we proceed with this soon.
>>>
>>> On Fri, Jun 17, 2016 at 1:57 AM, Kasun Indrasiri  wrote:
>>>
 How about the $subject? I don't think there's no any limitation from
 the mediation engine side on collecting these stats. We need to have this
 for ESB 5.

 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> 
>>WSO2 Inc. http://wso2.com
>>Blog: http://srinathsview.blogspot.com/
>>Photos: http://www.flickr.com/photos/hemapani/ twitter:@srinath_perera
>>Site: http://people.apache.org/~hemapani/
>>
>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>



-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
__

Re: [Dev] ESB Analytics for MT scenarios?

[Anjana Fernando]

Hi,

On Wed, Jun 22, 2016 at 11:38 AM, Selvaratnam Uthaiyashankar <
shan...@wso2.com> wrote:

>
>
> On Tue, Jun 21, 2016 at 11:31 AM, Buddhima Wijeweera 
> wrote:
>
>> Hi,
>>
>> At the moment ESB can publish tenant-wise. I tried it with a latest ESB
>> and following are the steps need to follow:
>> 1. Enable statistics for global level.
>> 2. Add eventpublisher & eventstream files to tenant's deployment folder
>>
>
> Who has to deploy this? Tenant or Super tenant? how do we deploy this in
> cloud setup? Do we have UI for this?
>

Event stream can come from our CApp itself, the event publisher, the tenant
user has to deploy, and yes, it has an UI.


>
>
>
>
>
>> 3. Create a proxy (or API, inbound EP) and Enable Statistics.
>> 4. Send messages to proxy
>>
>> Depending on the tenant credentials in eventpublisher files(at point 2
>> above), statistics  get published to analytics-esb server. (for this
>> testing I published to super-tenant of analytics-esb).
>>
>
> Also, if point 2 above has to be done by the tenant, tenant will not know
> super tenant credentials to send events.
>

The tenant user should use a tenant user's credentials to send events, not
super tenant, since with our tenant isolation, the data should go to the
tenant's space.

Cheers,
Anjana.


>
>
>
>>
>> Thanks,
>>
>> On Tue, Jun 21, 2016 at 9:37 AM, Srinath Perera  wrote:
>>
>>> We had a chat about this.
>>>
>>> This is supported. However, current implementation will run spark jobs
>>> per each tenant. So it will have performance concerns with a large number
>>> of tenants.
>>>
>>> Anjana, can you give the details and potential solutions?
>>>
>>> Summary is that DAS team has implemented the support for reading tenant
>>> data from super tenant so we can run a one Spark Job for all tenants. But
>>> we will need to change the queries and figure out how tenant dashboards can
>>> get access to results in super tenant's space.
>>>
>>> Can we do a 5.1 addressing this?
>>>
>>> --Srinath
>>>
>>> On Tue, Jun 21, 2016 at 9:15 AM, Kasun Indrasiri  wrote:
>>>
 Please note that this will be an essential feature for our integration
 cloud. So, we need to decide how should we proceed with this soon.

 On Fri, Jun 17, 2016 at 1:57 AM, Kasun Indrasiri 
 wrote:

> How about the $subject? I don't think there's no any limitation from
> the mediation engine side on collecting these stats. We need to have this
> for ESB 5.
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>>
>>> --
>>> 
>>> Srinath Perera, Ph.D.
>>>http://people.apache.org/~hemapani/
>>>http://srinathsview.blogspot.com/
>>>
>>
>>
>>
>> --
>> Buddhima Wijeweera
>> Software Engineer; WSO2 Inc.; http://wso2.com ,
>>
>> Mobile: +94 71 427 9966
>> Email: buddh...@wso2.com
>> Blog:   https://buddhimawijeweera.wordpress.com
>> GitHub Profile: https://github.com/Buddhima
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> S.Uthaiyashankar
> VP Engineering
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
>
> Phone: +94 714897591
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?

[Chanaka Fernando]

Agreed with you Isuru.

Tool will only provide a short cut to enable disable stat/tracing per CAPP.
Basically, it will enable stat/tracing for each and every artifacts
(applicable).

Setting a global parameter should not be possible through a CAPP.

On Wed, Jun 22, 2016 at 1:54 PM, Isuru Udana  wrote:

> Hi,
>
>
> On Wed, Jun 22, 2016 at 1:45 PM, Chanaka Fernando 
> wrote:
>
>> Hi Viraj,
>>
>> The configuration we have in the synapse.properties file is to globally
>> enable/disable the statistics/tracing for the server. By enabling that, we
>> prepare the server to publish events to DAS server. But, if you need to
>> publish real events, you need to enable them in individual artifacts
>> (proxy, api, sequence, etc). Iranga's suggestion is to provide a global
>> parameter to enable/disable them all at once (per CAPP or at global level).
>> This is a valid requirement which a particular user might have.
>>
>> Enable/disable statistics per CAR from the tool is ok, but should we do
> the global level controlling at the tool level ?
> Enabling statics globally is a management task.
> CARs are for packaging and deployable artifacts.
> Using CARs to control global level parameters doesn't sound nice to me.
>
>
>> This will require a considerable effort to support in the current model
>> and we will not be able to support in the upcoming ESB 5.0.0 version.
>>
>> @Iranga: Please create a public JIRA and we will fix this in a future
>> release.
>>
>> Thanks,
>> Chanaka
>>
>> On Wed, Jun 22, 2016 at 12:38 PM, Viraj Rajaguru  wrote:
>>
>>> Hi Iranga,
>>>
>>> IIUC, requirement is to setting a global level setting with CAR files to
>>> enable event statistics publishing. As per this document[1], we need to set
>>> a property in synapse.properties file + relevant config changes in artifact
>>> files to enable statistics publishing. With CAR files we are not modifying
>>> config files such as synapse.properties. So how can we achieve this?
>>>
>>> Thanks,
>>> Viraj.
>>>
>>> [1] -
>>> https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics
>>>
>>> On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri 
>>> wrote:
>>>


 On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva  wrote:

> +1 and it make sense to do it since we are having the
> a separate analytics server for ESB.
>
> Iranga when you say global do you mean for a CAPP or for the complete
> deployment? I think you are referring to the second option.
>

 Global setting -Having it at complete deployment  , having it at the
 C-App level  would also be a useful option as well IMO

>
> On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri <
> ira...@wso2.com> wrote:
>
>> Hi All,
>>
>> When creating a C-App to publish event statistics to ESB Analytics we
>> have to enable event statistics for each configuration ( proxy service,
>> API,) , would there be an option to set this at a global level?
>>
>> --
>> Thanks & Regards
>>
>> Iranga Muthuthanthri
>> (M) -0777-255773
>> Team Product Management
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Tech Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> 
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print
> this email only if it is absolutely necessary.
>



 --
 Thanks & Regards

 Iranga Muthuthanthri
 (M) -0777-255773
 Team Product Management


>>>
>>>
>>> --
>>> Viraj Rajaguru
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>
>
> --
> *Isuru Udana*
> Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>



-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka

[Dev] ESB is not handling the invalid response type

[Shakila Sivagnanarajah]

Hi,

ESB is not handling the string response If the Content-Type is
application/json. Apparently this is the fault on API response. Please find
the wire log [1]. How can we handle this?

[1] - [2016-06-21 16:13:53,915]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,915] DEBUG - wire << "GET
/devices/smoke_co_alarms/VhVmm7HOhEcL5sSzblcDOMMSoJ03t2br/co_alarm_state?auth=c.fRDyCBmlbBmwvpmODrw7qMIuJkbwZAtROf53kM9cwHDPEYdasapWaV284w4GnSohzgMuzJM8HEt9Bex3ommjCCoKaFuXFxAX9ZMyb5ckwNDpYWAMepcvbTtm37PRy3vFvARFYhWxOAgvFEEh
HTTP/1.1[\r][\n]"
[2016-06-21 16:13:53,915]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,915] DEBUG - wire << "Accept-Charset: UTF-8[\r][\n]"
[2016-06-21 16:13:53,915]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,915] DEBUG - wire << "Content-Type:
application/json[\r][\n]"
[2016-06-21 16:13:53,915]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,915] DEBUG - wire << "Accept: text/html, image/gif,
image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
[2016-06-21 16:13:53,915]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,915] DEBUG - wire << "Host:
firebase-apiserver10-tah01-iad01.dapi.production.nest.com:9553[\r][\n]"
[2016-06-21 16:13:53,916]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,915] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-06-21 16:13:53,916]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,916] DEBUG - wire << "User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-21 16:13:53,916]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:53,916] DEBUG - wire << "[\r][\n]"
[2016-06-21 16:13:54,237]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,237] DEBUG - wire >> "HTTP/1.1 200 OK[\r][\n]"
[2016-06-21 16:13:54,237]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,237] DEBUG - wire >> "*Content-Type:
application/json; charset=UTF-8*[\r][\n]"
[2016-06-21 16:13:54,237]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,237] DEBUG - wire >> "Access-Control-Allow-Origin:
*[\r][\n]"
[2016-06-21 16:13:54,238]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,237] DEBUG - wire >> "Cache-Control: private,
no-cache, max-age=0[\r][\n]"
[2016-06-21 16:13:54,238]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,238] DEBUG - wire >> "Connection: close[\r][\n]"
[2016-06-21 16:13:54,238]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,238] DEBUG - wire >> "Content-Length: 4[\r][\n]"
[2016-06-21 16:13:54,238]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,238] DEBUG - wire >> "[\r][\n]"
[2016-06-21 16:13:54,238]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,238] DEBUG - wire >> "*"ok"*"
[2016-06-21 16:13:54,241]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,241] ERROR - JsonUtil #newJsonPayload. *Could not
save JSON payload. Invalid input stream found.* MessageID:
urn:uuid:84033421-f5c1-47a3-a3c7-9764c6cd087d
[2016-06-21 16:13:54,242]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 [2016-06-21 16:13:54,241] ERROR - DeferredMessageBuilder Error building
message
[2016-06-21 16:13:54,242]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
 org.apache.axis2.AxisFault: No JSON payload provided.
[2016-06-21 16:13:54,242]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -   at
org.apache.synapse.commons.json.JsonStreamBuilder.processDocument(JsonStreamBuilder.java:52)
[2016-06-21 16:13:54,242]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -   at
org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:138)
[2016-06-21 16:13:54,242]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -   at
org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
[2016-06-21 16:13:54,242]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -   at
org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
[2016-06-21 16:13:54,243]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -   at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:72)
[2016-06-21 16:13:

[Dev] [APIM 2.0] Revoked access and revoked refresh tokens returning with http response header

[Kavitha Subramaniyam]

Hi team,

I observed that both revoked access and revoked refresh tokens were
returning in http response header [3].
setup : IS as KM
 - apim 2.0.0 17th nightly build
 - IS 5.2.0 19th build
 - Token encryption enabled

Could you please confirm that this behavior is not resolved purposely in
apim 2.0.0 due to the reasons discussed in mail thread [1], or it has been
solved?
Find an identity jira was raised for IS issue [2]

[1] Revoked Access Token and Revoked Refresh Token returned back in token
revoke endpoint response

[2] https://wso2.org/jira/browse/IDENTITY-4112

[3]

[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << HTTP/1.1 200
OK
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
AuthorizedUser: WSO2.ORG/admin@carbon.super
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
Cache-Control: no-store
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Date: Wed, 22
Jun 2016 08:39:00 GMT
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Pragma:
no-cache
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
RevokedRefreshToken:
h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Content-Type:
text/html
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 <<
Content-Length: 0
[2016-06-22 14:09:00,745] DEBUG - headers http-outgoing-10 << Server: WSO2
Carbon Server
[2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 << HTTP/1.1 200
OK
[2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
RevokedAccessToken: 030415a3-7b8a-39e7-b154-28cec1aeaf89
[2016-06-22 14:09:00,747] DEBUG - headers http-incoming-13 <<
AuthorizedUser: WSO2.ORG/admin@carbon.super
[2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
RevokedRefreshToken:
h56lM3zcJNCBbPHJfGnbQpUcI/ocp6CzGaE+r53nYDM021ItoJP4T/tN8fYGkQq6vvke4PwfkMQEt1zP7HNHJwgynI6Ch86C1tNCthxsG2CKsthHvjsGXvOzktURrNUGxJboj+U/r9arQc/mEt/J0skFQm1R76IC9Zlgh/5irBU=
[2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Content-Type:
text/html
[2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Pragma:
no-cache
[2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
Cache-Control: no-store
[2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 << Date: Wed, 22
Jun 2016 08:39:00 GMT
[2016-06-22 14:09:00,748] DEBUG - headers http-incoming-13 <<
Transfer-Encoding: chunked





Thanks,

-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Kerberos communication fails with java server to C# client

[Hasanthi Purnima Dissanayake]

Hi All,
The name-formats used in GSS-API are somewhat different than the
name-formats used in SSPI.  So the C# client could not identify the   SPN,
as the SPN name of the Java server is not windows compatible. After
providing the SPN name without realm when creating the client credentials
in C# client side the above problem solved.

Thanks Fara and Shazni for the suggestions and all the help. :)

Hasanthi Dissanayake

Software Engineer | WSO2

E: hasan...@wso2.com
M :0718407133| http://wso2.com 

On Tue, Jun 21, 2016 at 4:36 PM, Farasath Ahamed  wrote:

> Hi Hasanthi,
>
>
> On Tue, Jun 21, 2016 at 3:01 PM, Hasanthi Purnima Dissanayake <
> hasan...@wso2.com> wrote:
>
>> Hi Fara/Shazni,
>>
>> Thanks for the feedback. Here I'm using a sample standalone Java server
>> and C# client which communicates through a socket. And I'm using the fully
>> qualified name as you suggested.
>>
>> As this error comes when validating the server token the the issue should
>> be with the SPN of java server. Following is the code snippet which I'm
>> using generate the server token.
>>
>> GSSName serviceName =
>> manager.createName("wso2@IS.LOCAL", GSSName.NT_USER_NAME);
>>
>
> You seem to be using the service account here. Can you try using the
> Service Principal name under which you registered the java sever (that will
> be something like HTTP/server.is.local@IS.LOCAL) instead. As Shazni has
> pointed out use the SPN name along with realm at all places. I faced a
> similar situation during implementing IWA using Kerberos, and giving the
> SPN name along with the domain did the trick for me.
>
>
>
>> GSSCredential serviceCredentials =
>> manager.createCredential(serviceName,
>> GSSCredential.INDEFINITE_LIFETIME, spnegoOid,
>> GSSCredential.ACCEPT_ONLY);
>> GSSContext context =
>> manager.createContext(serviceCredentials);
>> serverToken = context.acceptSecContext(serviceTicket,
>> 0, serviceTicket.length);
>>
>> Here IS.LOCAL is the realm name and wso2 is the account name. When
>> executing this I got a value for 'serverToken' and the exception occurs
>> when the client uses this 'serverToken' to validate.
>>
>> Thanks,
>>
>> Hasanthi Dissanayake
>>
>> Software Engineer | WSO2
>>
>> E: hasan...@wso2.com
>> M :0718407133| http://wso2.com 
>>
>> On Tue, Jun 21, 2016 at 2:32 PM, Shazni Nazir  wrote:
>>
>>> HI Hasanthi,
>>>
>>> I've one question. What's this Java Server? Is it a standalone server
>>> you have custom written or is it a WSO2 server?
>>>
>>> When it comes to Kerberos related work for SOAP, we faced a couple of
>>> issues with related to service principal (SPN) name. In that discrepancies
>>> were noticed when using service principal name without a realm. For
>>> example, if the service principal name is, esb/localhost and the realm is
>>> WSO2.ORG, you have to specify the SPN as a fully qualified name; like
>>> esb/localh...@wso2.org. I'm not sure whether your issue is related to
>>> this. Maybe you can check if that's the case.
>>>
>>> Shazni Nazeer
>>> Mob : +94 37331
>>> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>>> Blog : http://shazninazeer.blogspot.com
>>>
>>> On Tue, Jun 21, 2016 at 2:20 PM, Farasath Ahamed 
>>> wrote:
>>>
 Hi Hasanthi,

 Assuming that you are using an AD as the Kerberos Server, Have you
 registered a Service Principal for both the C# client and Java Server in
 the AD?

 You can do this using the setspn.exe. Also, when you registering the
 SPN register all possible value that principal can take.
 For eg: Let's say the hostname of your java server is *server.is.local*,
 you can do

 setspn -A HTTP/server.is.local 
 setspn -A HTTP/server 

 to add your java server as a service principal in the Kerberos Server.
 You can do the same for the C# client as well. Can you check whether you
 have already registered the Service Principals by listing them out using
 commands specified in [1]

 [1]
 https://blogs.msdn.microsoft.com/psssql/2009/02/13/searching-for-duplicate-spns-got-a-little-easier/

 Thanks,

 Farasath Ahamed
 Software Engineer,
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware


 Email: farasa...@wso2.com
 Mobile: +94777603866
 Blog: blog.farazath.com
 Twitter: @farazath619 

 On Tue, Jun 21, 2016 at 2:03 PM, Hasanthi Purnima Dissanayake <
 hasan...@wso2.com> wrote:

> Hi I'm implementing Kerberos communication between java (GSSAPI) to
> C#(SSPI).
>
> The KDC is an Active Directory. When it comes to Java client vs Java
> server and C# client vs C# Server, for both the scenarios this works fine.
>
> When using Java client - server the process happens as below and it
> works fine:
> * Client uses JAAS and creates T

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

I have handled the exceptions and pushed the changes to my repository [1].
Please have a look



[1] https://github.com/osuran/azure-membership-scheme

thanks,

On Wed, Jun 22, 2016 at 11:42 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you very much for the feedback.
> I updated the snapshot dependency with a released version. Also I made it
> use Jackson to parse the API responses using bean classes. And I properly
> formatted the code as well. Exceptions handling is still on the way.
> Sure will have a code review this week.
>
>
> On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> I went through the code at [1] briefly. Some general comments:
>>
>>- The code is not properly formatted
>>- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If
>>you do not have a specific reason to do so, its better to use a released
>>version.
>>- To parse the responses from the rest API, you are directly
>>manipulating JSON objects. Have a look at the Kubernetes Membership 
>> Scheme.
>>Its using Jackson to parse the API responses using bean classes. This 
>> would
>>be much easier than directly interacting with JSON structures. Or else, 
>> you
>>can use Netflix Feign as a REST API client [2], in which the amount of 
>> code
>>you have to write is very less.
>>- System.exit(1) is used in few places to handle error scenarios,
>>which is wrong. Please use a proper Exception for the purpose
>>
>> Noted that you have updated the README file, which is great. Lets have a
>> code review this week to go through the functional aspects at a more fine
>> grained level.
>>
>> [1]. https://github.com/osuran/azure-membership-scheme.git
>>
>> [2]. https://github.com/Netflix/feign
>>
>> On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> That's great, will do the demo at 3 o'clock in the evening today.
>>> thanks
>>>
>>> On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
>>> wrote:
>>>


 On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake 
 wrote:

> Hi Mentors,
>
> Thank you for the update.
> Yes I can demonstrate it anytime today.
>
 Great! Shall we have a hangout at 3.00 PM? The main purpose would be to
 demonstrate the membership scheme functionality with a carbon cluster
 deployed in Azure.

>
>
> thanks
>
> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Would you be able to demonstrate the functionality of the membership
>> scheme today?
>>
>> Also, please keep an eye on the timeline for the project [1], as the
>> midterm evaluations will be starting on 20th.
>>
>> [1]. https://developers.google.com/open-source/gsoc/timeline
>>
>> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne 
>> wrote:
>>
>>>
>>>
>>> On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi Mentors,

 As we discussed at the very beginning, next in line is to see how
 each of the following can be setup on Azure using native features:

- Auto healing
- Autoscaling
- Dynamic load balancing
- Centralized logging
- Monitoring
- Metering

 For auto healing, we can implement it in both VM level and
 application level. In VM level, we can poll for VM statuses and check 
 if a
 given VM is down or not. And then we can up them if they have gone 
 down,
 using api calls. for application level of course we will have to run a
 shell script to determine the status of a given application and will 
 have
 to up it accordingly. I'm looking forward to hear from you regarding 
 this.

>>>
>>> ​No, auto healing and autoscaling should be handled by Azure. We
>>> might not need to write code to handle that.
>>>
>>> Thanks​
>>>
>>>

 thanks,

 On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Isuru,
>
> Can you please tell me when you would be free to have a hangout to
> do a code review and discuss next project goals?
>
> Thanks,
>
> On Saturday, June 11, 2016, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you very much.
>> Yes there was a misconfiguration in registry mounts and now it
>> works properly.
>> Okay will have a code review next week.
>>
>>
>> On Fri, Jun 10, 2016 at 9:45 AM, Isuru Haththotuwa <
>> isu...@wso2.com> wrote:
>>
>>> Hi Osura,
>>>
>>> This is great progress! This shows that a clust

Re: [Dev] ESB Analytics for MT scenarios?

[Isabelle Mauny]

Great! So that's for Spark.. You mentioned CEP as a big issue as well. Any
hope to fix in CEP too ??

-
*Isabelle Mauny*
VP, Product Strategy - WSO2, Inc. - http://wso2.com/
email: isabe...@wso2.com - mobile (Spain) : +34 616050684 - mobile (Sri
Lanka) +94 (0)774777663
Landline:  +1 (650) 745 4499  (USA)  or +94 (11) 214 534 (Sri Lanka)
Extension : 7302

On Wed, Jun 22, 2016 at 11:50 AM, Srinath Perera  wrote:

> Perfect!!
>
> On Wed, Jun 22, 2016 at 1:58 PM, Anjana Fernando  wrote:
>
>> Hi,
>>
>> I've updated the thread "Cross Tenant Data Reading from Spark Queries in
>> DAS", where I've done the implementation on writing back to the tenant
>> space also from the super tenant space as well. This basically just
>> eliminates the current requirement of executing identical Spark scripts in
>> all the tenants, which would not be desirable performance wise, and now, we
>> can just use super tenant's single script to process all the tenant's data
>> and write back the results to their space. Of course, we've to now change
>> the current ESB analytics scripts to use this feature, but it shouldn't be
>> a big change. @Gihan/Supun, can we please check on this and get it done.
>>
>> Cheers,
>> Anjana.
>>
>> On Tue, Jun 21, 2016 at 12:35 PM, Anjana Fernando 
>> wrote:
>>
>>> Hi,
>>>
>>> Yeah, as Srinath mentioned, we do have MT support there, where each ESB
>>> analytics data/queryeis/dashboards would be fully isolated. This is the
>>> usual desirable mode, when different tenants deploy their own analytics
>>> scripts and all, and there is no connection at all with other tenants, and
>>> obviously there shouldn't be. But in our solutions like this, where we
>>> would deploy the exact same solution in each tenant, we can potentially
>>> optimize the scenario by, only doing the processing in one place. This is
>>> actually how APIM batch queries are written at the moment. Where they
>>> altogether stores all the tenant's data in super tenant space and process
>>> and put the summarized there itself. This model works, but then, if the
>>> tenant itself wants to do their own processing it doesn't have access to
>>> the data, that was suppose to be in his space. So a solution for this is
>>> done, which is explained in detail in the mail "Cross Tenant Data Reading
>>> from Spark Queries in DAS", where optionally the super tenant can read
>>> tenant's data which creates a single virtual table view which contains data
>>> from all the tenants. From this, you can read the data, do the processing
>>> and store it in a table in super tenant space. In this approach, you will
>>> still have to have the dashboard in the super tenant space, since the data
>>> resides in the super tenant space. I will be doing some experiments to see
>>> on the feasibility of storing back summarized data in tenant space soon.
>>>
>>> Even though we can get the batch scenario working efficiently, there
>>> would be a problem in the CEP side, which we now use heavily in the product
>>> analytics scenario processing. At the moment, there is no concept of having
>>> a single CEP execution plan for all the tenants. When data is published to
>>> receivers, they will be dispatched to their own streams and execution
>>> plans, so we will need to find an approach for this, to optimize the
>>> processing of the CEP side of things. Or else, I'm not sure, since these
>>> are in-memory processing constructs, if having copies of the same execution
>>> plans will actually be okay, compared to having a single one, since the
>>> traffic is anyway split between them.
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Tue, Jun 21, 2016 at 9:35 AM, Srinath Perera 
>>> wrote:
>>>
 We had a chat about this.

 This is supported, however, current implementation will run spark jobs
 per each tenant. So it will have performance concerns with a large number
 of tenants.

 Anjana, can you give the details and potential solutions? DAS team has
 implemented the support for reading tenant data from super tenant so we can
 run a one Spark Job for all tenants. But we will need to change the queries
 and figure out how tenant dashboards can get access to results in super
 tenant's space.

 Can we do a 5.1 addressing this?

 --Srinath

 On Tue, Jun 21, 2016 at 9:15 AM, Kasun Indrasiri 
 wrote:

> Please note that this will be an essential feature for our integration
> cloud. So, we need to decide how should we proceed with this soon.
>
> On Fri, Jun 17, 2016 at 1:57 AM, Kasun Indrasiri 
> wrote:
>
>> How about the $subject? I don't think there's no any limitation from
>> the mediation engine side on collecting these stats. We need to have this
>> for ESB 5.
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>

[Dev] Request to upgrade the carbon-identity version in carbon-store and product-es

[Megala Uthayakumar]

Hi All,

We are working on a DS and ES integration in which we have a use case when
a user changes some configuration in a gadget configuration file, we need
to unzip the gadget zip file and change the relevant file and zip it again
and send it to the DS side.

Since unzip and zip functionality are not currently available in Jaggery,
we have implemented those in jaggery level and it will be included in
Jaggery 0.12.6. But Jaggery 0.12.6 requires carbon-identity version 5.1.0,
But carbon-store still uses the carbon-identity version 5.0.8. So is it
possible to upgrade the carbon-identity version to newer one in both
 carbon-store and product-es?

Thanks.

Regards,
Megala

-- 
Megala Uthayakumar

Software Engineer
Mobile : 0779967122
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request to upgrade the carbon-identity version in carbon-store and product-es

[Megala Uthayakumar]

+Chandana

On Wed, Jun 22, 2016 at 3:33 PM, Megala Uthayakumar  wrote:

> Hi All,
>
> We are working on a DS and ES integration in which we have a use case when
> a user changes some configuration in a gadget configuration file, we need
> to unzip the gadget zip file and change the relevant file and zip it again
> and send it to the DS side.
>
> Since unzip and zip functionality are not currently available in Jaggery,
> we have implemented those in jaggery level and it will be included in
> Jaggery 0.12.6. But Jaggery 0.12.6 requires carbon-identity version 5.1.0,
> But carbon-store still uses the carbon-identity version 5.0.8. So is it
> possible to upgrade the carbon-identity version to newer one in both
>  carbon-store and product-es?
>
> Thanks.
>
> Regards,
> Megala
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>



-- 
Megala Uthayakumar

Software Engineer
Mobile : 0779967122
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB Analytics for MT scenarios?

[Anjana Fernando]

Hi,

On Wed, Jun 22, 2016 at 3:25 PM, Isabelle Mauny  wrote:

> Great! So that's for Spark.. You mentioned CEP as a big issue as well. Any
> hope to fix in CEP too ??
>

As per Suho's reply in this thread, it wouldn't be an issue, it just
consumed a little bit of extra memory, but performance wise, there
shouldn't be a problem.

Cheers,
Anjana.


>
>
> -
> *Isabelle Mauny*
> VP, Product Strategy - WSO2, Inc. - http://wso2.com/
> email: isabe...@wso2.com - mobile (Spain) : +34 616050684 - mobile (Sri
> Lanka) +94 (0)774777663
> Landline:  +1 (650) 745 4499  (USA)  or +94 (11) 214 534 (Sri Lanka)
> Extension : 7302
>
> On Wed, Jun 22, 2016 at 11:50 AM, Srinath Perera 
> wrote:
>
>> Perfect!!
>>
>> On Wed, Jun 22, 2016 at 1:58 PM, Anjana Fernando  wrote:
>>
>>> Hi,
>>>
>>> I've updated the thread "Cross Tenant Data Reading from Spark Queries in
>>> DAS", where I've done the implementation on writing back to the tenant
>>> space also from the super tenant space as well. This basically just
>>> eliminates the current requirement of executing identical Spark scripts in
>>> all the tenants, which would not be desirable performance wise, and now, we
>>> can just use super tenant's single script to process all the tenant's data
>>> and write back the results to their space. Of course, we've to now change
>>> the current ESB analytics scripts to use this feature, but it shouldn't be
>>> a big change. @Gihan/Supun, can we please check on this and get it done.
>>>
>>> Cheers,
>>> Anjana.
>>>
>>> On Tue, Jun 21, 2016 at 12:35 PM, Anjana Fernando 
>>> wrote:
>>>
 Hi,

 Yeah, as Srinath mentioned, we do have MT support there, where each ESB
 analytics data/queryeis/dashboards would be fully isolated. This is the
 usual desirable mode, when different tenants deploy their own analytics
 scripts and all, and there is no connection at all with other tenants, and
 obviously there shouldn't be. But in our solutions like this, where we
 would deploy the exact same solution in each tenant, we can potentially
 optimize the scenario by, only doing the processing in one place. This is
 actually how APIM batch queries are written at the moment. Where they
 altogether stores all the tenant's data in super tenant space and process
 and put the summarized there itself. This model works, but then, if the
 tenant itself wants to do their own processing it doesn't have access to
 the data, that was suppose to be in his space. So a solution for this is
 done, which is explained in detail in the mail "Cross Tenant Data Reading
 from Spark Queries in DAS", where optionally the super tenant can read
 tenant's data which creates a single virtual table view which contains data
 from all the tenants. From this, you can read the data, do the processing
 and store it in a table in super tenant space. In this approach, you will
 still have to have the dashboard in the super tenant space, since the data
 resides in the super tenant space. I will be doing some experiments to see
 on the feasibility of storing back summarized data in tenant space soon.

 Even though we can get the batch scenario working efficiently, there
 would be a problem in the CEP side, which we now use heavily in the product
 analytics scenario processing. At the moment, there is no concept of having
 a single CEP execution plan for all the tenants. When data is published to
 receivers, they will be dispatched to their own streams and execution
 plans, so we will need to find an approach for this, to optimize the
 processing of the CEP side of things. Or else, I'm not sure, since these
 are in-memory processing constructs, if having copies of the same execution
 plans will actually be okay, compared to having a single one, since the
 traffic is anyway split between them.

 Cheers,
 Anjana.

 On Tue, Jun 21, 2016 at 9:35 AM, Srinath Perera 
 wrote:

> We had a chat about this.
>
> This is supported, however, current implementation will run spark jobs
> per each tenant. So it will have performance concerns with a large number
> of tenants.
>
> Anjana, can you give the details and potential solutions? DAS team has
> implemented the support for reading tenant data from super tenant so we 
> can
> run a one Spark Job for all tenants. But we will need to change the 
> queries
> and figure out how tenant dashboards can get access to results in super
> tenant's space.
>
> Can we do a 5.1 addressing this?
>
> --Srinath
>
> On Tue, Jun 21, 2016 at 9:15 AM, Kasun Indrasiri 
> wrote:
>
>> Please note that this will be an essential feature for our
>> integration cloud. So, we need to decide how should we proceed with this
>> soon.
>>
>> On Fri, Jun 1

Re: [Dev] Request to upgrade the carbon-identity version in carbon-store and product-es

[Chandana Napagoda]

Hi Megala,

SameeraM found an issue in IS side while upgrading the Jaggery version. I
hope SameeraM has more insight about that.

Regards,
Chandana

On Wed, Jun 22, 2016 at 3:35 PM, Megala Uthayakumar  wrote:

> +Chandana
>
> On Wed, Jun 22, 2016 at 3:33 PM, Megala Uthayakumar 
> wrote:
>
>> Hi All,
>>
>> We are working on a DS and ES integration in which we have a use case
>> when a user changes some configuration in a gadget configuration file, we
>> need to unzip the gadget zip file and change the relevant file and zip it
>> again and send it to the DS side.
>>
>> Since unzip and zip functionality are not currently available in Jaggery,
>> we have implemented those in jaggery level and it will be included in
>> Jaggery 0.12.6. But Jaggery 0.12.6 requires carbon-identity version 5.1.0,
>> But carbon-store still uses the carbon-identity version 5.0.8. So is it
>> possible to upgrade the carbon-identity version to newer one in both
>>  carbon-store and product-es?
>>
>> Thanks.
>>
>> Regards,
>> Megala
>>
>> --
>> Megala Uthayakumar
>>
>> Software Engineer
>> Mobile : 0779967122
>>
>
>
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>



-- 
*Chandana Napagoda*
Senior Software Engineer
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299*

*Blog  :http://cnapagoda.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB is not handling the invalid response type

[Hariprasath Thanarajah]

Hi All,

I got the same error when I try with billiving connector create client
operation. You can find the wire log[1]

[1]

[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Action: urn:createClient[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Accept-Charset: UTF-8[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Content-Type: application/json;
charset=UTF-8[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Accept: text/html, image/gif,
image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Content-Length: 26[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Host: www.billiving.com:443
[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-06-22 15:35:02,794]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,794] DEBUG - wire << "User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-06-22 15:35:02,795]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,795] DEBUG - wire << "[\r][\n]"
[2016-06-22 15:35:02,795]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:02,795] DEBUG - wire << "{"Email":"1...@gmail.com"}"
[2016-06-22 15:35:03,476]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,476] DEBUG - wire >> "HTTP/1.1 400 Bad Request[\r][\n]"
[2016-06-22 15:35:03,476]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,476] DEBUG - wire >> "Cache-Control: no-cache[\r][\n]"
[2016-06-22 15:35:03,476]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,476] DEBUG - wire >> "Pragma: no-cache[\r][\n]"
[2016-06-22 15:35:03,476]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,476] DEBUG - wire >> "Content-Length: 110[\r][\n]"
[2016-06-22 15:35:03,476]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,476] DEBUG - wire >> "Content-Type: application/json;
charset=utf-8[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,476] DEBUG - wire >> "Expires: -1[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "Server:
Microsoft-IIS/8.0[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "X-AspNet-Version:
4.0.30319[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "X-Powered-By: ASP.NET[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "Set-Cookie:
ARRAffinity=87810450b90c9a83023a6768742c17e54dbf87a7a858516e54cad2c06cbddacf;Path=/;Domain=www.billiving.com:443
[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "Date: Wed, 22 Jun 2016 10:05:02
GMT[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "[\r][\n]"
[2016-06-22 15:35:03,477]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,477] DEBUG - wire >> "*"Your current plan is limited
to 5 clients. Please visit our account upgrade page to explore available
plans."*"
[2016-06-22 15:35:03,485]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,485] *ERROR - JsonUtil #newJsonPayload. Could not save
JSON payload. Invalid input stream found.* MessageID:
urn:uuid:687c4ba7-71e0-4ce8-8600-d2f474509ae4
[2016-06-22 15:35:03,488]  INFO
{org.wso2.carbon.automation.core.utils.coreutils.InputStreamHandler} -
[2016-06-22 15:35:03,487] ERROR - DeferredMessageBuilder Error building
message
[2016-06-22 15:35:03,488]  INFO
{org.wso2.carbon.automation.core.utils.

[Dev] Siddhi Query : group by results

[Aneela Safdar]

Hi all,
  I am having a trouble in digesting results of my group by query. My source 
stream named intermediateStream has data ts   uid   
  id_resp_h
2016-05-08 08:59  CLuCgz3HHzG7LpLwH9172.30.26.119
2016-05-08 09:00  C3WnnK3TgUf2cSzxVa172.30.26.127 
2016-05-08 09:00  C3WnnK3TgUf2cSzxff172.30.26.119
SIDDHI query is from intermediateStream
select ts, count(ts) as ssh_logins
group by ts
insert into SSHOutStream;
I am expecting output to be likets ssh_logins
2016-05-08 08:59   1
2016-05-08 09:00   2  
But instead it returns ts ssh_logins
2016-05-08 08:59   1
2016-05-08 09:00   1
2016-05-08 09:00   2
Any suggestions?  Regards, Aneela Safdar___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Siddhi Query : group by results

[Charini Nanayakkara]

Hi Aneela,

The siddhi query you have specified processes each and every incoming
event. Since processing is done in real time, when the first event for
ts= 2016-05-08
09:00 arrives it gives count = 1 (due to no events with ts = 2016-05-08
09:00 having arrived earlier). When second event with ts = 2016-05-08 09:00
comes, we get count as 2 since an event with same ts arrived earlier as
well.

Best Regards,
Charini

On Wed, Jun 22, 2016 at 4:40 PM, Aneela Safdar  wrote:

> Hi all,
>
> I am having a trouble in digesting results of my group by query. My source
> stream named intermediateStream has data
>
>  ts   uid id_resp_h
> 2016-05-08 08:59  CLuCgz3HHzG7LpLwH9172.30.26.119
> 2016-05-08 09:00  C3WnnK3TgUf2cSzxVa172.30.26.127
> 2016-05-08 09:00  C3WnnK3TgUf2cSzxff172.30.26.119
>
> SIDDHI query is
>
> from intermediateStream
> select ts, count(ts) as ssh_logins
> group by ts
> insert into SSHOutStream;
>
> I am expecting output to be like
>
> ts ssh_logins
> 2016-05-08 08:59   1
> 2016-05-08 09:00   2
>
> But instead it returns
>
> ts ssh_logins
> 2016-05-08 08:59   1
> 2016-05-08 09:00   1
> 2016-05-08 09:00   2
>
> Any suggestions?
>
> Regards, Aneela Safdar
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Charini Vimansha Nanayakkara
Software Engineer at WSO2
Mobile: 0714126293
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?

[Iranga Muthuthanthri]

Created JIRA https://wso2.org/jira/browse/DEVTOOLESB-448


On Wed, Jun 22, 2016 at 2:15 PM, Chanaka Fernando  wrote:

> Agreed with you Isuru.
>
> Tool will only provide a short cut to enable disable stat/tracing per
> CAPP. Basically, it will enable stat/tracing for each and every artifacts
> (applicable).
>
> Setting a global parameter should not be possible through a CAPP.
>
> On Wed, Jun 22, 2016 at 1:54 PM, Isuru Udana  wrote:
>
>> Hi,
>>
>>
>> On Wed, Jun 22, 2016 at 1:45 PM, Chanaka Fernando 
>> wrote:
>>
>>> Hi Viraj,
>>>
>>> The configuration we have in the synapse.properties file is to globally
>>> enable/disable the statistics/tracing for the server. By enabling that, we
>>> prepare the server to publish events to DAS server. But, if you need to
>>> publish real events, you need to enable them in individual artifacts
>>> (proxy, api, sequence, etc). Iranga's suggestion is to provide a global
>>> parameter to enable/disable them all at once (per CAPP or at global level).
>>> This is a valid requirement which a particular user might have.
>>>
>>> Enable/disable statistics per CAR from the tool is ok, but should we do
>> the global level controlling at the tool level ?
>> Enabling statics globally is a management task.
>> CARs are for packaging and deployable artifacts.
>> Using CARs to control global level parameters doesn't sound nice to me.
>>
>>
>>> This will require a considerable effort to support in the current model
>>> and we will not be able to support in the upcoming ESB 5.0.0 version.
>>>
>>> @Iranga: Please create a public JIRA and we will fix this in a future
>>> release.
>>>
>>> Thanks,
>>> Chanaka
>>>
>>> On Wed, Jun 22, 2016 at 12:38 PM, Viraj Rajaguru  wrote:
>>>
 Hi Iranga,

 IIUC, requirement is to setting a global level setting with CAR files
 to enable event statistics publishing. As per this document[1], we need to
 set a property in synapse.properties file + relevant config changes in
 artifact files to enable statistics publishing. With CAR files we are not
 modifying config files such as synapse.properties. So how can we achieve
 this?

 Thanks,
 Viraj.

 [1] -
 https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics

 On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri >>> > wrote:

>
>
> On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva 
> wrote:
>
>> +1 and it make sense to do it since we are having the
>> a separate analytics server for ESB.
>>
>> Iranga when you say global do you mean for a CAPP or for the complete
>> deployment? I think you are referring to the second option.
>>
>
> Global setting -Having it at complete deployment  , having it at the
> C-App level  would also be a useful option as well IMO
>
>>
>> On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri <
>> ira...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> When creating a C-App to publish event statistics to ESB Analytics
>>> we have to enable event statistics for each configuration ( proxy 
>>> service,
>>> API,) , would there be an option to set this at a global level?
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Iranga Muthuthanthri
>>> (M) -0777-255773
>>> Team Product Management
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> 
>> https://store.wso2.com/store/
>>
>> Save a tree -Conserve nature & Save the world for your future. Print
>> this email only if it is absolutely necessary.
>>
>
>
>
> --
> Thanks & Regards
>
> Iranga Muthuthanthri
> (M) -0777-255773
> Team Product Management
>
>


 --
 Viraj Rajaguru
 Associate Technical Lead
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068




>>>
>>>
>>> --
>>> Thank you and Best Regards,
>>> Chanaka Fernando
>>> Senior Technical Lead
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 773337238
>>> Blog : http://soatutorials.blogspot.com
>>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>>> Twitter:https://twitter.com/chanakaudaya
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email

Re: [Dev] APIM 2.0.0-SNAPSHOT Nightly build - 17/06/2016

[Nirmal Fernando]

When you do perf test on analytics, please make sure to add the following
properties to my.cnf file of your MySQL server. Change the values
appropriately.


innodb_buffer_pool_instances = 4

innodb_use_native_aio = false

innodb_flush_method = O_DIRECT

innodb_write_io_threads = 10

innodb_read_io_threads = 10

#innodb_additional_mem_pool_size = 20M

*innodb_buffer_pool_size = 2G*

innodb_log_files_in_group = 2

innodb_log_buffer_size = 10M

innodb_log_file_size = 200M

innodb_flush_log_at_trx_commit = 2

innodb_lock_wait_timeout = 50

innodb_file_per_table=1

#innodb_compression_algorithm=2

#innodb_compression_punch_hole = 1

#innodb_compression_level = 4

innodb_file_format=barracuda

innodb_file_format_max=barracuda

On Wed, Jun 22, 2016 at 11:57 AM, Fazlan Nazeem  wrote:

> Hi Shavantha,
>
> Noted. We will remove the stat dbscripts from the pack, so that there will
> be less confusion.
>
> On Wed, Jun 22, 2016 at 11:45 AM, Shavantha Weerasinghe <
> shavan...@wso2.com> wrote:
>
>> Hi All
>>
>> The  scripts related to the stat db for the analytic server for which
>> until the 17th June release we had to manually source the script. However,
>> upon manually sourcing we came across[1]. We were lated updated that the
>> script will be sourced when -Dsetup is run and manual sourcing is not
>> necessary.
>>
>> We were unable to find any details on the read-me file as well
>>
>> Appreciate if this type changes can be communicated with the release pack
>> in future to avoid delays in setup
>>
>> [1]https://wso2.org/jira/browse/ANLYAPIM-71
>>
>> regards,
>> Shavantha Weerasinghe
>> Senior Software Engineer QA
>> WSO2, Inc.
>> lean.enterprise.middleware.
>> http://wso2.com
>> http://wso2.org
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>>
>>
>> On Fri, Jun 17, 2016 at 10:20 PM, Nirmal Fernando 
>> wrote:
>>
>>> Please find the API-M analytics pack
>>> https://wso2.org/jenkins/job/analytics-apim/173/org.wso2.analytics.apim$wso2analytics-apim/artifact/org.wso2.analytics.apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-SNAPSHOT.zip
>>>
>>> On Fri, Jun 17, 2016 at 10:07 PM, Bhathiya Jayasekara >> > wrote:
>>>

 Hi all,

 Please find today's nightly builds.

 APIM 2.0.0 SNAPSHOT[1], P2 repo[2] and IS 5.2.0 SNAPSHOT[3].

 [1]
 https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/wso2am-2.0.0-SNAPSHOT-17-06-2016.zip
 [2]
 https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/p2-repos/17-06-2016/p2-repo.zip
 [3]
 http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/is/wso2is/5.2.0-SNAPSHOT/wso2is-5.2.0-20160617.023441-125.zip

 Thanks,

 --
 *Bhathiya Jayasekara*
 *Senior Software Engineer,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <%2B94715478185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>



-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Siddhi Query : group by results

[Ashen Weerathunga]

Hi Aneela,

As Charini mentioned above this is the expected output as for your query. There
will be an output for each and every incoming event since you haven't
included any window for your intermediateStream. But you can get your
expected output by adding a batch window[1] to your query. As an example if
you knew the event count you can simply add a lengthBatch[2] window as
below,

from intermediateStream#window.lengthBatch(3)
select ts, count(ts) as ssh_logins
group by ts
insert into SSHOutStream;

Then it will hold events as a batch of 3 events and return an output as below,

ts ssh_logins
2016-05-08 08:59   1
2016-05-08 09:00   2

Similarly you can use other windows such as timeBatch, cron etc. as for
your requirment.

[1]https://docs.wso2.com/display/CEP410/SiddhiQL+Guide+3.0#SiddhiQLGuide3.0-InbuiltWindows
[2]https://docs.wso2.com/display/CEP410/Inbuilt+Windows#InbuiltWindows-lengthBatch


Best regards,
Ashen


On Wed, Jun 22, 2016 at 5:00 PM, Charini Nanayakkara 
wrote:

> Hi Aneela,
>
> The siddhi query you have specified processes each and every incoming
> event. Since processing is done in real time, when the first event for ts= 
> 2016-05-08
> 09:00 arrives it gives count = 1 (due to no events with ts = 2016-05-08
> 09:00 having arrived earlier). When second event with ts = 2016-05-08
> 09:00 comes, we get count as 2 since an event with same ts arrived earlier
> as well.
>
> Best Regards,
> Charini
>
> On Wed, Jun 22, 2016 at 4:40 PM, Aneela Safdar 
> wrote:
>
>> Hi all,
>>
>> I am having a trouble in digesting results of my group by query. My
>> source stream named intermediateStream has data
>>
>>  ts   uid id_resp_h
>> 2016-05-08 08:59  CLuCgz3HHzG7LpLwH9172.30.26.119
>> 2016-05-08 09:00  C3WnnK3TgUf2cSzxVa172.30.26.127
>> 2016-05-08 09:00  C3WnnK3TgUf2cSzxff172.30.26.119
>>
>> SIDDHI query is
>>
>> from intermediateStream
>> select ts, count(ts) as ssh_logins
>> group by ts
>> insert into SSHOutStream;
>>
>> I am expecting output to be like
>>
>> ts ssh_logins
>> 2016-05-08 08:59   1
>> 2016-05-08 09:00   2
>>
>> But instead it returns
>>
>> ts ssh_logins
>> 2016-05-08 08:59   1
>> 2016-05-08 09:00   1
>> 2016-05-08 09:00   2
>>
>> Any suggestions?
>>
>> Regards, Aneela Safdar
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Charini Vimansha Nanayakkara
> Software Engineer at WSO2
> Mobile: 0714126293
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: +94 716042995 <94716042995>
LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request to upgrade the carbon-identity version in carbon-store and product-es

[Sameera Medagammaddegedara]

Hi Chandana and Megala,

*Note:* Adding Pulasthi and Hasintha

There is a small issue with upgrading to 5.1.0.It is caused when the
HostName element is commented out in the carbon.xml (which is the case in
ES and G-Reg).The issue occurs when attempting to validate the Home Realm
Id [1]. The root cause is the hostname been resolved to NULL here[2]. As a
work around for local testing we can set the HostName in the carbon.xml to
localhost. The IS team will be including the fix in the next
identity-framework release.

*Reference*
[1]
https://github.com/wso2/carbon-identity-framework/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/listener/IdPMgtValidationListener.java#L124
[2]
https://github.com/wso2/carbon-identity-framework/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/internal/IdPManagementServiceComponent.java#L340

On Wed, Jun 22, 2016 at 3:45 PM, Chandana Napagoda 
wrote:

> Hi Megala,
>
> SameeraM found an issue in IS side while upgrading the Jaggery version. I
> hope SameeraM has more insight about that.
>
> Regards,
> Chandana
>
> On Wed, Jun 22, 2016 at 3:35 PM, Megala Uthayakumar 
> wrote:
>
>> +Chandana
>>
>> On Wed, Jun 22, 2016 at 3:33 PM, Megala Uthayakumar 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are working on a DS and ES integration in which we have a use case
>>> when a user changes some configuration in a gadget configuration file, we
>>> need to unzip the gadget zip file and change the relevant file and zip it
>>> again and send it to the DS side.
>>>
>>> Since unzip and zip functionality are not currently available in
>>> Jaggery, we have implemented those in jaggery level and it will be included
>>> in Jaggery 0.12.6. But Jaggery 0.12.6 requires carbon-identity version
>>> 5.1.0, But carbon-store still uses the carbon-identity version 5.0.8. So is
>>> it possible to upgrade the carbon-identity version to newer one in both
>>>  carbon-store and product-es?
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Megala
>>>
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122
>>>
>>
>>
>>
>> --
>> Megala Uthayakumar
>>
>> Software Engineer
>> Mobile : 0779967122
>>
>
>
>
> --
> *Chandana Napagoda*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com *
>
>


-- 
Sameera Medagammaddegedara
Software Engineer

Contact:
Email: samee...@wso2.com
Mobile: + 94 077 255 3005
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request to upgrade the carbon-identity version in carbon-store and product-es

[Sameera Medagammaddegedara]

Hi,

I have created a JIRA to track this issue:
https://wso2.org/jira/browse/CIDENTITY-15

Please note that I have severity to Blocker as it breaks Out of the Box SSO
functionality in the ES.

Thank You,
Sameera

On Wed, Jun 22, 2016 at 6:01 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> Hi Chandana and Megala,
>
> *Note:* Adding Pulasthi and Hasintha
>
> There is a small issue with upgrading to 5.1.0.It is caused when the
> HostName element is commented out in the carbon.xml (which is the case in
> ES and G-Reg).The issue occurs when attempting to validate the Home Realm
> Id [1]. The root cause is the hostname been resolved to NULL here[2]. As a
> work around for local testing we can set the HostName in the carbon.xml to
> localhost. The IS team will be including the fix in the next
> identity-framework release.
>
> *Reference*
> [1]
> https://github.com/wso2/carbon-identity-framework/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/listener/IdPMgtValidationListener.java#L124
> [2]
> https://github.com/wso2/carbon-identity-framework/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/internal/IdPManagementServiceComponent.java#L340
>
> On Wed, Jun 22, 2016 at 3:45 PM, Chandana Napagoda 
> wrote:
>
>> Hi Megala,
>>
>> SameeraM found an issue in IS side while upgrading the Jaggery version. I
>> hope SameeraM has more insight about that.
>>
>> Regards,
>> Chandana
>>
>> On Wed, Jun 22, 2016 at 3:35 PM, Megala Uthayakumar 
>> wrote:
>>
>>> +Chandana
>>>
>>> On Wed, Jun 22, 2016 at 3:33 PM, Megala Uthayakumar 
>>> wrote:
>>>
 Hi All,

 We are working on a DS and ES integration in which we have a use case
 when a user changes some configuration in a gadget configuration file, we
 need to unzip the gadget zip file and change the relevant file and zip it
 again and send it to the DS side.

 Since unzip and zip functionality are not currently available in
 Jaggery, we have implemented those in jaggery level and it will be included
 in Jaggery 0.12.6. But Jaggery 0.12.6 requires carbon-identity version
 5.1.0, But carbon-store still uses the carbon-identity version 5.0.8. So is
 it possible to upgrade the carbon-identity version to newer one in both
  carbon-store and product-es?

 Thanks.

 Regards,
 Megala

 --
 Megala Uthayakumar

 Software Engineer
 Mobile : 0779967122

>>>
>>>
>>>
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122
>>>
>>
>>
>>
>> --
>> *Chandana Napagoda*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com *
>>
>>
>
>
> --
> Sameera Medagammaddegedara
> Software Engineer
>
> Contact:
> Email: samee...@wso2.com
> Mobile: + 94 077 255 3005
>



-- 
Sameera Medagammaddegedara
Software Engineer

Contact:
Email: samee...@wso2.com
Mobile: + 94 077 255 3005
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

following is the summary of operations i have implemented up to now and yet
to implement

1. Add new MongoDB User Store - done both case sensitive and intensensitive
2. Add new users to MongoDB user store - done both case sensitive and
intensensitive
3. Add new roles to MongoDB user store - done both case sensitive and
intensensitive
4. Search users and roles - done both case sensitive and intensensitive
5. Assign roles to mongodb user store users - done both case sensitive and
intensensitive
6. Assign users to mongodb user store roles - done both case sensitive and
intensensitive
7. Edit claim values of user profiles  - done both case sensitive and
intensensitive
for those implemented user operations i have added selenium scripts also to
my repo[1] and also i have prepared user guide[2] and administrator
guide[3] also and also i have updated my blog[4] with all my tasks what i
have done and following are the tasks yet to complete

1. implement delete operations
2. implement new profiles adding
3. check for injections possibilities and improve the security of all the
functions
4. prepare full test scripts for all the functions
5. prepare developer guide and database architecture diagrams

expect your feedback

[1]  https://github.com/asanthamax/mongodbuserstore
[2]
https://docs.google.com/document/d/1mdnmYruzQz5QSxAYwM1XVeJntJMFdxUsV5gord7LuPA/edit?usp=sharing
[3]
https://docs.google.com/document/d/1fCLfZYsPOBkHMzRCGM3aexoBSplX3bKIRmONmFsgkBc/edit?usp=sharing
[4]  http://asanthamax.blogspot.com

Thanks,
Asantha

On Wed, Jun 22, 2016 at 12:29 AM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> I have finished the case insensitive user operations as well and i added
> selenium test scripts for those implemented functions to my repo[1] except
> delete function all the other functions with test script added to my repo[1]
>
> [1] https://github.com/asanthamax/mongodbuserstore
>
> Thanks,
> Asantha
>
> On Fri, Jun 17, 2016 at 2:28 AM, Asantha Thilina  > wrote:
>
>> Hi Tharindu,
>>
>> sure i'll be look forward for the hangout
>>
>> Thanks,
>> Asantha
>>
>> On Fri, Jun 17, 2016 at 2:22 AM, Tharindu Edirisinghe > > wrote:
>>
>>> Hi Asantha,
>>>
>>> I will go through the docs and provide feedback soon. Let's have a
>>> hangout session to discuss the pending issues.
>>>
>>> I'm available today 9.00 P.M IST for a google hangout.
>>>
>>> Thanks,
>>> TharinduE
>>>
>>> On Fri, Jun 17, 2016 at 11:30 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 I have prepared the user guide[1] and administrator guide[2] in google
 doc since all tasks are not finished yet i have only added the tasks i have
 already done and there is still the developer guide has to be prepare i
 will prepare it as sooner as well

 [1]
 https://docs.google.com/document/d/1fCLfZYsPOBkHMzRCGM3aexoBSplX3bKIRmONmFsgkBc/edit?usp=sharing
 [2]
 https://docs.google.com/document/d/1mdnmYruzQz5QSxAYwM1XVeJntJMFdxUsV5gord7LuPA/edit?usp=sharing

 Thanks,
 Asantha

 On Tue, Jun 14, 2016 at 1:55 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> sure i will prepare those documents sooner
>
> Thanks,
> Asantha
>
> On Mon, Jun 13, 2016 at 9:38 PM, Tharindu Edirisinghe <
> tharin...@wso2.com> wrote:
>
>> Excellent work Asantha !
>>
>> Meanwhile you can prepare a document also adding the screenshots you
>> have got. Basically we will need following documentation.
>>
>> 1. Developer Guide ( The architecture of the userstoremanager,
>> diagrams of all the collections, how they are related to each other etc.)
>>
>> 2. Administrator Guide (How to guide a server administrator to setup
>> a secondary userstore with mongodb)
>>
>> 3. User Guide (All the functionality of the userstoremanager, i.e
>> each function in RemoteUserStoreManager with sample SOAP requests and
>> responses)
>>
>> We will need to look at the QA aspect of the project also.. but let's
>> keep aside for the moment until we get all the functionality working.
>>
>> Thanks for all the hard work !
>>
>> Best Regards,
>> Tharindu Edirisinghe
>>
>> On Tue, Jun 14, 2016 at 12:46 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> as you advice me i added soap ui screen shots of test result and
>>> selenium script for implemented functions into my repository[1]
>>>
>>> [1] https://github.com/asanthamax/mongodbuserstore
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Jun 13, 2016 at 6:23 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi Tharindu,

 i updated my blog[1] with all the works i have done so far there i
 added all the methods and their use in MongoDBUserStoreManager ,
 hopes your feedback
 [1] 

Re: [Dev] [Carbon Netty ] Default value for "executor.workerpool.size"

[Isuru Udana]

Hi Sagara,

Yes, we are working on setting sensible default values from the code, which
will be available in next transport release.

Thanks.

On Wed, Jun 22, 2016 at 10:36 PM, Sagara Gunathunga  wrote:

>
> It seems there is no default value available for
>  "executor.workerpool.size" setting, when explicitly not set  transport
> fail with NPE, can we have a sensible default value here ?
>
> Thanks !
> --
> Sagara Gunathunga
>
> Architect; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 
*Isuru Udana*
Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Carbon Netty ] Default value for "executor.workerpool.size"

[Sagara Gunathunga]

It seems there is no default value available for
 "executor.workerpool.size" setting, when explicitly not set  transport
fail with NPE, can we have a sensible default value here ?

Thanks !
-- 
Sagara Gunathunga

Architect; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon Netty ] Default value for "executor.workerpool.size"

[Sagara Gunathunga]

On Wed, Jun 22, 2016 at 10:38 PM, Isuru Udana  wrote:

> Hi Sagara,
>
> Yes, we are working on setting sensible default values from the code,
> which will be available in next transport release.
>

Great ! Please let us know once you update the SNAPSHOTs so that we can
remove some unwanted code from MSF4J code.

Thanks !

>
> Thanks.
>
> On Wed, Jun 22, 2016 at 10:36 PM, Sagara Gunathunga 
> wrote:
>
>>
>> It seems there is no default value available for
>>  "executor.workerpool.size" setting, when explicitly not set  transport
>> fail with NPE, can we have a sensible default value here ?
>>
>> Thanks !
>> --
>> Sagara Gunathunga
>>
>> Architect; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>
>
> --
> *Isuru Udana*
> Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>



-- 
Sagara Gunathunga

Architect; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Tharindu Edirisinghe]

Good work Asantha... Meanwhile let's look at getting your research work
published as well. I will provide feedback for the work so far in couple of
days time. I have also completed the Mid Review based on your current work
where you are already ahead of schedule.

Regards,
TharinduE

On Wed, Jun 22, 2016 at 9:41 PM, Asantha Thilina 
wrote:

> Hi Tharindu,
>
> following is the summary of operations i have implemented up to now and
> yet to implement
>
> 1. Add new MongoDB User Store - done both case sensitive and intensensitive
> 2. Add new users to MongoDB user store - done both case sensitive and
> intensensitive
> 3. Add new roles to MongoDB user store - done both case sensitive and
> intensensitive
> 4. Search users and roles - done both case sensitive and intensensitive
> 5. Assign roles to mongodb user store users - done both case sensitive and
> intensensitive
> 6. Assign users to mongodb user store roles - done both case sensitive and
> intensensitive
> 7. Edit claim values of user profiles  - done both case sensitive and
> intensensitive
> for those implemented user operations i have added selenium scripts also
> to my repo[1] and also i have prepared user guide[2] and administrator
> guide[3] also and also i have updated my blog[4] with all my tasks what i
> have done and following are the tasks yet to complete
>
> 1. implement delete operations
> 2. implement new profiles adding
> 3. check for injections possibilities and improve the security of all the
> functions
> 4. prepare full test scripts for all the functions
> 5. prepare developer guide and database architecture diagrams
>
> expect your feedback
>
> [1]  https://github.com/asanthamax/mongodbuserstore
> [2]
> https://docs.google.com/document/d/1mdnmYruzQz5QSxAYwM1XVeJntJMFdxUsV5gord7LuPA/edit?usp=sharing
> [3]
> https://docs.google.com/document/d/1fCLfZYsPOBkHMzRCGM3aexoBSplX3bKIRmONmFsgkBc/edit?usp=sharing
> [4]  http://asanthamax.blogspot.com
>
> Thanks,
> Asantha
>
> On Wed, Jun 22, 2016 at 12:29 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> I have finished the case insensitive user operations as well and i added
>> selenium test scripts for those implemented functions to my repo[1] except
>> delete function all the other functions with test script added to my repo[1]
>>
>> [1] https://github.com/asanthamax/mongodbuserstore
>>
>> Thanks,
>> Asantha
>>
>> On Fri, Jun 17, 2016 at 2:28 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> sure i'll be look forward for the hangout
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Fri, Jun 17, 2016 at 2:22 AM, Tharindu Edirisinghe <
>>> tharin...@wso2.com> wrote:
>>>
 Hi Asantha,

 I will go through the docs and provide feedback soon. Let's have a
 hangout session to discuss the pending issues.

 I'm available today 9.00 P.M IST for a google hangout.

 Thanks,
 TharinduE

 On Fri, Jun 17, 2016 at 11:30 AM, Asantha Thilina <
 asanthathil...@gmail.com> wrote:

> Hi Tharindu,
>
> I have prepared the user guide[1] and administrator guide[2] in google
> doc since all tasks are not finished yet i have only added the tasks i 
> have
> already done and there is still the developer guide has to be prepare i
> will prepare it as sooner as well
>
> [1]
> https://docs.google.com/document/d/1fCLfZYsPOBkHMzRCGM3aexoBSplX3bKIRmONmFsgkBc/edit?usp=sharing
> [2]
> https://docs.google.com/document/d/1mdnmYruzQz5QSxAYwM1XVeJntJMFdxUsV5gord7LuPA/edit?usp=sharing
>
> Thanks,
> Asantha
>
> On Tue, Jun 14, 2016 at 1:55 AM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> sure i will prepare those documents sooner
>>
>> Thanks,
>> Asantha
>>
>> On Mon, Jun 13, 2016 at 9:38 PM, Tharindu Edirisinghe <
>> tharin...@wso2.com> wrote:
>>
>>> Excellent work Asantha !
>>>
>>> Meanwhile you can prepare a document also adding the screenshots you
>>> have got. Basically we will need following documentation.
>>>
>>> 1. Developer Guide ( The architecture of the userstoremanager,
>>> diagrams of all the collections, how they are related to each other 
>>> etc.)
>>>
>>> 2. Administrator Guide (How to guide a server administrator to setup
>>> a secondary userstore with mongodb)
>>>
>>> 3. User Guide (All the functionality of the userstoremanager, i.e
>>> each function in RemoteUserStoreManager with sample SOAP requests and
>>> responses)
>>>
>>> We will need to look at the QA aspect of the project also.. but
>>> let's keep aside for the moment until we get all the functionality 
>>> working.
>>>
>>> Thanks for all the hard work !
>>>
>>> Best Regards,
>>> Tharindu Edirisinghe
>>>
>>> On Tue, Jun 14, 2016 at 12:46 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>

[Dev] [DEV][APPM] Rest API support for Mobile App Installation/Download options

[Thilini Shanika]

Hi all,

We have few concerns regarding mobile app installing REST API support in
APPM.

In the new JAX-RS Rest API model, we have provided following API to install
a mobile application via MDM.

/api/appm/store/v1.1/apps/download

Apart from that, below app installation options have to be supported by new
REST APIs.

   - In App Manager, there is an option to enabling app binary direct
   download ( config in app-manager.xml). Once direct
   download is enabled, authorized and subscribed users should be able to
   download the app binaries directly without having MDM integrated. This
   particular requirement is not satisfied by currently available REST APIs.
   - Subscribed users should be able to obtain one-time download link for
   enterprise andrioid app binaries and generated plist config link for
   enterprise ios apps, so that the link can be shared via email, SMS etc.


As per the discussion we had with the team, below are the alterations and
additions to current API model in order to fulfill above requirements.

   1. Adding new API to make mobile app subscriptions/download. This
   particular install won't have any interaction with MDM and it is dedicated
   to make subscription and return app url for users. This API will return
   generated one-time download link for enterprise android apps and one-time
   download link included plist config link for enterprise IOS apps. For
   mobile webapps and public android/IOS, this will return the app url.
   2. In 1.2.0 Beta release, we already have a mobile binary retrieving
   API. That API has to be deprecated or removed, since we have a one-time
   download API.
   3. Renaming the currently available API path (/api/appm/store/v1.1/apps/
   download) in order to indicate the actual purpose of it.


Your suggestions and comments are highly appreciated.

Thanks
Thilini

-- 
Thilini Shanika
Senior Software Engineer
WSO2, Inc.; http://wso2.com
20, Palmgrove Avenue, Colombo 3

E-mail: tgtshan...@gmail.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Docker images layered composition

[Isuru Haththotuwa]

Hi Akila,

On Tue, Jun 21, 2016 at 6:54 PM, Akila Ravihansa Perera 
wrote:

> Hi Isuru,
>
> One drawback of not having a wso2base is that in a restricted environment
> where Internet connectivity is not available, a private build server will
> not be able to build the images using Puppet provisioning if there are any
> additional packages to be installed. But if there was a wso2base image,
> those packages could have been installed to that and manually loaded into
> the build server as a one time task.
>
Yes this is true. However, still there is a possibility of this occurring
even at a base image building time, isn't it?

>
> Thanks.
>
I'm not against having a base image for the WSO2 Docker images. But, IMHO
the advantages should be significant for doing so. AFAIU there is no
significant advantage of doing so currently. But, this is my take only.
Therefore lets get the input from the community on this matter.

@Imesh: WDYT?


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Request to upgrade the carbon-identity version in carbon-store and product-es

[Megala Uthayakumar]

Hi Chandana and Sameera,

Thanks for the quick responses. For the testing purposes we will try the
work around mentioned by Sameera.

Thanks.

Regards,
Megala

On Wed, Jun 22, 2016 at 6:45 PM, Sameera Medagammaddegedara <
samee...@wso2.com> wrote:

> Hi,
>
> I have created a JIRA to track this issue:
> https://wso2.org/jira/browse/CIDENTITY-15
>
> Please note that I have severity to Blocker as it breaks Out of the Box
> SSO functionality in the ES.
>
> Thank You,
> Sameera
>
> On Wed, Jun 22, 2016 at 6:01 PM, Sameera Medagammaddegedara <
> samee...@wso2.com> wrote:
>
>> Hi Chandana and Megala,
>>
>> *Note:* Adding Pulasthi and Hasintha
>>
>> There is a small issue with upgrading to 5.1.0.It is caused when the
>> HostName element is commented out in the carbon.xml (which is the case in
>> ES and G-Reg).The issue occurs when attempting to validate the Home Realm
>> Id [1]. The root cause is the hostname been resolved to NULL here[2]. As a
>> work around for local testing we can set the HostName in the carbon.xml to
>> localhost. The IS team will be including the fix in the next
>> identity-framework release.
>>
>> *Reference*
>> [1]
>> https://github.com/wso2/carbon-identity-framework/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/listener/IdPMgtValidationListener.java#L124
>> [2]
>> https://github.com/wso2/carbon-identity-framework/blob/master/components/idp-mgt/org.wso2.carbon.idp.mgt/src/main/java/org/wso2/carbon/idp/mgt/internal/IdPManagementServiceComponent.java#L340
>>
>> On Wed, Jun 22, 2016 at 3:45 PM, Chandana Napagoda 
>> wrote:
>>
>>> Hi Megala,
>>>
>>> SameeraM found an issue in IS side while upgrading the Jaggery version.
>>> I hope SameeraM has more insight about that.
>>>
>>> Regards,
>>> Chandana
>>>
>>> On Wed, Jun 22, 2016 at 3:35 PM, Megala Uthayakumar 
>>> wrote:
>>>
 +Chandana

 On Wed, Jun 22, 2016 at 3:33 PM, Megala Uthayakumar 
 wrote:

> Hi All,
>
> We are working on a DS and ES integration in which we have a use case
> when a user changes some configuration in a gadget configuration file, we
> need to unzip the gadget zip file and change the relevant file and zip it
> again and send it to the DS side.
>
> Since unzip and zip functionality are not currently available in
> Jaggery, we have implemented those in jaggery level and it will be 
> included
> in Jaggery 0.12.6. But Jaggery 0.12.6 requires carbon-identity version
> 5.1.0, But carbon-store still uses the carbon-identity version 5.0.8. So 
> is
> it possible to upgrade the carbon-identity version to newer one in both
>  carbon-store and product-es?
>
> Thanks.
>
> Regards,
> Megala
>
> --
> Megala Uthayakumar
>
> Software Engineer
> Mobile : 0779967122
>



 --
 Megala Uthayakumar

 Software Engineer
 Mobile : 0779967122

>>>
>>>
>>>
>>> --
>>> *Chandana Napagoda*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.org
>>>
>>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>>> <%2B94718169299>*
>>>
>>> *Blog  :http://cnapagoda.blogspot.com
>>> *
>>>
>>>
>>
>>
>> --
>> Sameera Medagammaddegedara
>> Software Engineer
>>
>> Contact:
>> Email: samee...@wso2.com
>> Mobile: + 94 077 255 3005
>>
>
>
>
> --
> Sameera Medagammaddegedara
> Software Engineer
>
> Contact:
> Email: samee...@wso2.com
> Mobile: + 94 077 255 3005
>



-- 
Megala Uthayakumar

Software Engineer
Mobile : 0779967122
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][IS] User Store error while doing GREG performance testing in clustered setup

[Dilini Gunatilake]

Hi All,

I have also faced a similar issue[1] to the issue mentioned by Danesh in
[2] above when we are doing a long running test for ES 210. Were you able
to find a root cause for this issue?

[1] https://wso2.org/jira/browse/STORE-1352

Thanks.

Regards,
Dilini

On Wed, Jun 1, 2016 at 6:04 PM, Kasun Bandara  wrote:

> Hi Thushara,
>
> Seems like the root cause of the issue originates from the below
> stack-trace.
>
> *JDBCAuthorizationManager.java:1378)*
> * at
> org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.isUserAuthorized(JDBCAuthorizationManager.java:168)*
>
> As you said in the offline discussion this occurs when the number of
> concurrent users increase from 80 to 100 right?. I think if you can debug
> the *isUserAuthorized() *method in *JDBCAuthorizationManager *class*, *you
> can the trace out the exact reason behind this concurrency issue*.*
> (debug it in both the occasions : 80 Users and 100 Users)
>
> Thanks,
> Kasun.
>
> On Wed, Jun 1, 2016 at 11:18 AM, Thushara Ranawaka 
> wrote:
>
>> Hi Everyone,
>>
>> This is continuously reproducible for 100 concurrent users in a single
>> node G-Reg setup.
>> Any idea of why this is happen.
>>
>> TID: [-1234] [] [2016-05-30 13:12:07,771] ERROR
>> {org.wso2.carbon.user.core.common.AbstractUserStoreManager} -  Error
>> occurred while accessing Java Security Manager Privilege Block
>> {org.wso2.carbon.user.core.common.AbstractUserStoreManager}
>> TID: [-1234] [] [2016-05-30 13:13:00,324] ERROR
>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager} -  Error
>> occurred while accessing Java Security Manager Privilege Block
>> {org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager}
>> TID: [-1234] [] [2016-05-30 13:13:03,183] ERROR {rxt-permissions} -
>>  org.mozilla.javascript.WrappedException: Wrapped
>> org.wso2.carbon.user.core.UserStoreException: Error occurred while
>> accessing Java Security Manager Privilege Block (eval code#1(eval)#86)
>> at
>> org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1754)
>> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:148)
>> at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:225)
>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0._c_anonymous_52(/scripts/permissions/permissions.js:594)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0.call(/scripts/permissions/permissions.js)
>> at
>> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0._c_anonymous_53(/scripts/permissions/permissions.js:637)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0.call(/scripts/permissions/permissions.js)
>> at
>> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0._c_anonymous_54(/scripts/permissions/permissions.js:658)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0.call(/scripts/permissions/permissions.js)
>> at
>> org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:63)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0._c_anonymous_60(/scripts/permissions/permissions.js:751)
>> at
>> org.jaggeryjs.rhino..scripts.permissions.c0.call(/scripts/permissions/permissions.js)
>> at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:52)
>> at
>> org.jaggeryjs.rhino.store.modules.c5._c_anonymous_8(/store/modules/page-decorators.js:200)
>> at
>> org.jaggeryjs.rhino.store.modules.c5.call(/store/modules/page-decorators.js)
>> at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1473)
>>
>>
>>
>>
>> Caused by: org.wso2.carbon.user.core.UserStoreException: Error occurred
>> while accessing Java Security Manager Privilege Block
>> at
>> org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.callSecure(JDBCAuthorizationManager.java:1378)
>> at
>> org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.isUserAuthorized(JDBCAuthorizationManager.java:168)
>> at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source)
>>
>> Thanks,
>> Thushara.
>>
>> On Thu, Mar 31, 2016 at 9:27 AM, Danesh Kuruppu  wrote:
>>
>>> Hi all,
>>>
>>> I am currently doing GREG performance testing in clustered setup. It is
>>> a two nodes cluster fronted with nginx and we have enabled sticky sessions.
>>> We have JDBC user store (mysql DB) shared with both nodes.
>>>
>>> User store exception[1][2] occurred while performing asset crud
>>> operation in publisher for 20+ concurrent users.
>>>
>>> Any idea of why this is happen.
>>> Thanks
>>> Danesh
>>>
>>> [1]
>>> Caused by: org.wso2.carbon.user.core.UserStoreException: Error occurred
>>> while accessing Java Security Manager Privilege Block
>>> at
>>> org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.callSecure(JDBCAuthorizationManager.java:1378)
>>> at
>>> org.wso2.carbon.user.core.authorization.JDBCAuthorizationMan

Re: [Dev] carbon-datasources: Supporting Database Properties

[Isuru Perera]

Hi,

This regarding CDATASRCS-2 . I
guess that won't be fixed soon. But as I mentioned, this issue is a blocker
for Metrics release. Since we need to release Metrics soon (by next week),
I'll release the Metrics with datasources import range "[1.0.0, 2.0.0)"

I hope this issue will be fixed in a Minor release. I also hope the
datasource properties will be supported using the same configuration
elements used in C4. See:
https://github.com/wso2/carbon-metrics/blob/v1.2.1/features/carbon-metrics/org.wso2.carbon.metrics.server.feature/src/main/resources/conf/metrics-datasources.xml#L144-L146

Please let me know the plan to support datasource properties in C5.

Thanks!

Best Regards,

On Thu, Jun 2, 2016 at 12:25 PM, Isuru Perera  wrote:

> Hi,
>
> This is regarding [1]. Supporting database properties is required for
> Carbon Metrics.
>
> It will be a blocker when someone wants to use Carbon Metrics with Oracle
> database.
>
> Can we get it fixed soon?
>
> Thanks!
>
> Best Regards,
>
> [1] https://wso2.org/jira/browse/CDATASOURC-2
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

[Osura Rathnayake]

Hi Mentors,

Please arrange a hangout for the code review of membership scheme at any
time which is convenient for you.

thanks,

On Wed, Jun 22, 2016 at 3:21 PM, Osura Rathnayake 
wrote:

> Hi Mentors,
>
> I have handled the exceptions and pushed the changes to my repository [1].
> Please have a look
>
>
>
> [1] https://github.com/osuran/azure-membership-scheme
>
> thanks,
>
> On Wed, Jun 22, 2016 at 11:42 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you very much for the feedback.
>> I updated the snapshot dependency with a released version. Also I made it
>> use Jackson to parse the API responses using bean classes. And I
>> properly formatted the code as well. Exceptions handling is still on the
>> way.
>> Sure will have a code review this week.
>>
>>
>> On Tue, Jun 21, 2016 at 10:18 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> I went through the code at [1] briefly. Some general comments:
>>>
>>>- The code is not properly formatted
>>>- The code has a SNAPSHOT dependency for org.wso2.carbon.utils. If
>>>you do not have a specific reason to do so, its better to use a released
>>>version.
>>>- To parse the responses from the rest API, you are directly
>>>manipulating JSON objects. Have a look at the Kubernetes Membership 
>>> Scheme.
>>>Its using Jackson to parse the API responses using bean classes. This 
>>> would
>>>be much easier than directly interacting with JSON structures. Or else, 
>>> you
>>>can use Netflix Feign as a REST API client [2], in which the amount of 
>>> code
>>>you have to write is very less.
>>>- System.exit(1) is used in few places to handle error scenarios,
>>>which is wrong. Please use a proper Exception for the purpose
>>>
>>> Noted that you have updated the README file, which is great. Lets have a
>>> code review this week to go through the functional aspects at a more fine
>>> grained level.
>>>
>>> [1]. https://github.com/osuran/azure-membership-scheme.git
>>>
>>> [2]. https://github.com/Netflix/feign
>>>
>>> On Thu, Jun 16, 2016 at 11:23 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Isuru,

 That's great, will do the demo at 3 o'clock in the evening today.
 thanks

 On Thu, Jun 16, 2016 at 11:21 AM, Isuru Haththotuwa 
 wrote:

>
>
> On Thu, Jun 16, 2016 at 11:10 AM, Osura Rathnayake  > wrote:
>
>> Hi Mentors,
>>
>> Thank you for the update.
>> Yes I can demonstrate it anytime today.
>>
> Great! Shall we have a hangout at 3.00 PM? The main purpose would be
> to demonstrate the membership scheme functionality with a carbon cluster
> deployed in Azure.
>
>>
>>
>> thanks
>>
>> On Thu, Jun 16, 2016 at 10:11 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Would you be able to demonstrate the functionality of the membership
>>> scheme today?
>>>
>>> Also, please keep an eye on the timeline for the project [1], as the
>>> midterm evaluations will be starting on 20th.
>>>
>>> [1]. https://developers.google.com/open-source/gsoc/timeline
>>>
>>> On Thu, Jun 16, 2016 at 6:46 AM, Imesh Gunaratne 
>>> wrote:
>>>


 On Wed, Jun 15, 2016 at 2:46 PM, Osura Rathnayake <
 osura...@gmail.com> wrote:

> Hi Mentors,
>
> As we discussed at the very beginning, next in line is to see how
> each of the following can be setup on Azure using native features:
>
>- Auto healing
>- Autoscaling
>- Dynamic load balancing
>- Centralized logging
>- Monitoring
>- Metering
>
> For auto healing, we can implement it in both VM level and
> application level. In VM level, we can poll for VM statuses and check 
> if a
> given VM is down or not. And then we can up them if they have gone 
> down,
> using api calls. for application level of course we will have to run a
> shell script to determine the status of a given application and will 
> have
> to up it accordingly. I'm looking forward to hear from you regarding 
> this.
>

 ​No, auto healing and autoscaling should be handled by Azure. We
 might not need to write code to handle that.

 Thanks​


>
> thanks,
>
> On Mon, Jun 13, 2016 at 10:53 AM, Osura Rathnayake <
> osura...@gmail.com> wrote:
>
>> Hi Isuru,
>>
>> Can you please tell me when you would be free to have a hangout
>> to do a code review and discuss next project goals?
>>
>> Thanks,
>>
>> On Saturday, June 11, 2016, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you very much.
>>> Yes there wa

[Dev] Possibility of wrong super tenant id used in api manager when publishing data to DAS

[Amila Maha Arachchi]

APIM Team,

I see following logs in DAS receiver. I have only the API gateway
publishing data to DAS.

TID: [-1234] [] [2016-06-22 23:46:11,295]  INFO
{org.wso2.carbon.databridge.core.DataBridge} -  user bamuser connected
{org.wso2.carbon.databridge.core.DataBridge}

TID: [-1] [] [2016-06-22 23:46:11,313]  INFO
{org.wso2.carbon.databridge.core.DataBridge} -  user bamuser connected
{org.wso2.carbon.databridge.core.DataBridge}

TID: [-1234] [] [2016-06-22 23:46:11,383]  INFO
{org.wso2.carbon.databridge.core.DataBridge} -  user bamuser connected
{org.wso2.carbon.databridge.core.DataBridge}
Above highlighted log section hints me that there can be some code which
sets a wrong ST ID. Better to have a look.
-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting error JsonUtil #writeAsJson. Payload could not be written as JSON with ESB 5.0.0 - BETA

[Chanaka Fernando]

This issue is fixed with following commit and will be available with the
next build.

[1]
https://github.com/wso2/wso2-synapse/commit/2776abf03789d7d9b7ee8fbe0f1c8c294ad7aa71

On Tue, Jun 7, 2016 at 1:43 PM, Kesavan Yogarajah  wrote:

> Please find the template [1] , proxy [2] configurations and sample request
> [3].
>
> [1] -
>
> 
> 
> http://ws.apache.org/ns/synapse";>
> 
> 
>  expression="$func:paymentMethodId"/>
> 
> 
> 
> uri-template="{uri.var.zuora.apiUrl}/{uri.var.zuora.apiVersion}/payment-methods/{uri.var.zuora.paymentMethodId}"/>
> 
> 
> 
> 
>
>
> [2] -
>
> 
> http://ws.apache.org/ns/synapse";
>name="z"
>transports="http,https"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
>  
>   expression="json-eval($.apiAccessKeyId)"/>
>   expression="json-eval($.apiSecretAccessKey)"/>
>   expression="json-eval($.paymentMethodId)"/>
>  
> {$ctx:apiUrl}
> {$ctx:apiVersion}
> {$ctx:apiAccessKeyId}
>
> {$ctx:apiSecretAccessKey}
>  
>  
> {$ctx:paymentMethodId}
>  
>  
>   
>
>
> 
>
> [3] -
> {
>   "apiUrl": "https://apisandbox-api.zuora.com/rest";,
>   "apiVersion": "v1",
>   "apiAccessKeyId": "a...@sample.com",
>   "apiSecretAccessKey": "zuorapwd"
> }
>
> Thanks
>
> Kesavan Yogarajah
> Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
> On Tue, Jun 7, 2016 at 1:16 PM, Malaka Silva  wrote:
>
>> Please share the synapse configs you are using?
>>
>> On Tue, Jun 7, 2016 at 12:33 PM, Kesavan Yogarajah 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am checking Zuora connector with ESB 5.0.0 - BETA.I am getting error
>>> [1] when the API response with 403 comes with no body.But this works fine
>>> with ESB -4.9.0 [2]. Is this an expected behavior?
>>>
>>> [1]
>>>
>>> [2016-06-07 11:43:43,212] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "DELETE /rest/v1/payment-methods/ HTTP/1.1[\r][\n]"
>>> [2016-06-07 11:43:43,213] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Authorization: Basic aXXX==[\r][\n]"
>>> [2016-06-07 11:43:43,213] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
>>> [2016-06-07 11:43:43,214] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Action: urn:deletePayments[\r][\n]"
>>> [2016-06-07 11:43:43,214] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Accept: */*[\r][\n]"
>>> [2016-06-07 11:43:43,214] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Cache-Control: no-cache[\r][\n]"
>>> [2016-06-07 11:43:43,215] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Postman-Token: b618abc9-99ca-9540-3332-b6302bb01e10[\r][\n]"
>>> [2016-06-07 11:43:43,215] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Accept-Encoding: gzip, deflate[\r][\n]"
>>> [2016-06-07 11:43:43,215] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Accept-Language: en-US,en;q=0.8[\r][\n]"
>>> [2016-06-07 11:43:43,215] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Content-Type: application/json[\r][\n]"
>>> [2016-06-07 11:43:43,215] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Host: apisandbox-api.zuora.com[\r][\n]"
>>> [2016-06-07 11:43:43,216] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "Connection: Keep-Alive[\r][\n]"
>>> [2016-06-07 11:43:43,216] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "User-Agent: Synapse-PT-HttpComponents-NIO[\r][\n]"
>>> [2016-06-07 11:43:43,216] DEBUG - wire HTTPS-Sender I/O dispatcher-1 <<
>>> "[\r][\n]"
>>> [2016-06-07 11:43:43,639] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "HTTP/1.1 403 Forbidden[\r][\n]"
>>> [2016-06-07 11:43:43,640] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Server: Zuora App[\r][\n]"
>>> [2016-06-07 11:43:43,640] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Access-Control-Allow-Credentials: true[\r][\n]"
>>> [2016-06-07 11:43:43,641] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Access-Control-Allow-Origin:
>>> chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop[\r][\n]"
>>> [2016-06-07 11:43:43,641] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Content-Length: 0[\r][\n]"
>>> [2016-06-07 11:43:43,641] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Expires: Tue, 07 Jun 2016 06:13:43 GMT[\r][\n]"
>>> [2016-06-07 11:43:43,641] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Cache-Control: max-age=0, no-cache, no-store[\r][\n]"
>>> [2016-06-07 11:43:43,642] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Pragma: no-cache[\r][\n]"
>>> [2016-06-07 11:43:43,642] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Date: Tue, 07 Jun 2016 06:13:43 GMT[\r][\n]"
>>> [2016-06-07 11:43:43,642] DEBUG - wire HTTPS-Sender I/O dispatcher-1 >>
>>> "Connection: keep-alive[\r][\n]"
>>> [2016-06-07 11:43