Re: [Dev] DAS minimum HA deployment in one node?

[Srinath Perera]

IMO  HA in same node does not make much sense.

--Srinath

On Tue, Apr 12, 2016 at 10:30 AM, Nirmal Fernando  wrote:

> Hi All,
>
> Is it possible to setup DAS minimum HA deployment in one node? AFAIS the
> requirement to create a symbolic link makes it impossible?
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 

Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
Site: http://home.apache.org/~hemapani/
Photos: http://www.flickr.com/photos/hemapani/
Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What are the features that enable federated authentication

[Ayesha Dissanayaka]

Thanks for the information Johann.

I will try this.

On Mon, Apr 18, 2016 at 11:15 PM, Johann Nallathamby 
wrote:

> Hi Ayehsa,
>
> [1] is the nested category for SSO. If you are installing directly from UI
> installing this category should do it.
>
> Otherwise if you are installing it through p2 plugin, according to [1] you
> need to install,
> 1. org.wso2.carbon.identity.application.authentication.framework.server
> 2. org.wso2.carbon.identity.application.mgt
>
> Along with this you may need to install identity.core.feautre,
> claim.mgt.feature, and there can be other features required when installing
> p2. If so it will fail installation and give you an error and you can find
> out. I am not sure if this can be  listed down in advance.
>
> [1]
> https://github.com/wso2/identity-framework/blob/master/features/categories/inbound-authentication/pom.xml
>
> On Mon, Apr 18, 2016 at 7:13 PM, Ayesha Dissanayaka 
> wrote:
>
>> Hi all,
>>
>> I am trying to enable managing Service Providers from GREG-5.1.0
>> management console to use Federated authentication for Store/Publisher.
>> Currently it seems GREG-5.1.0 does not have necessary features.
>>
>> Can someone point me which feature(s) need to be installed from [2] in
>> order to enable this.
>>
>> [1] https://docs.wso2.com/display/IS510/Federated+Authentication
>> [2] http://product-dist.wso2.com/p2/carbon/releases/wilkes/
>>
>> Thanks!
>> Ayesha
>> --
>> *Ayesha Dissanayaka*
>> Software Engineer,
>> WSO2, Inc : http://wso2.com
>> 
>> 20, Palmgrove Avenue, Colombo 3
>> E-Mail: aye...@wso2.com 
>>
>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What are the features that enable federated authentication

[Johann Nallathamby]

Hi Ayehsa,

[1] is the nested category for SSO. If you are installing directly from UI
installing this category should do it.

Otherwise if you are installing it through p2 plugin, according to [1] you
need to install,
1. org.wso2.carbon.identity.application.authentication.framework.server
2. org.wso2.carbon.identity.application.mgt

Along with this you may need to install identity.core.feautre,
claim.mgt.feature, and there can be other features required when installing
p2. If so it will fail installation and give you an error and you can find
out. I am not sure if this can be  listed down in advance.

[1]
https://github.com/wso2/identity-framework/blob/master/features/categories/inbound-authentication/pom.xml

On Mon, Apr 18, 2016 at 7:13 PM, Ayesha Dissanayaka  wrote:

> Hi all,
>
> I am trying to enable managing Service Providers from GREG-5.1.0
> management console to use Federated authentication for Store/Publisher.
> Currently it seems GREG-5.1.0 does not have necessary features.
>
> Can someone point me which feature(s) need to be installed from [2] in
> order to enable this.
>
> [1] https://docs.wso2.com/display/IS510/Federated+Authentication
> [2] http://product-dist.wso2.com/p2/carbon/releases/wilkes/
>
> Thanks!
> Ayesha
> --
> *Ayesha Dissanayaka*
> Software Engineer,
> WSO2, Inc : http://wso2.com
> 
> 20, Palmgrove Avenue, Colombo 3
> E-Mail: aye...@wso2.com 
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements

[Sohani Weerasinghe]

Hi Manuranga,

This is about datamapper in ESB and we are using JSON schema to define the
structure of the data. This is all about defining the JSON schema for
xml,json etc.

You can refer mails regarding datamapper to get more information

Thanks,
Sohani


Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Mon, Apr 18, 2016 at 9:08 PM, Manuranga Perera  wrote:

> btw, What is all this JSON/XML stuff you guys are doing. Just curious. Is
> there a mail I can read to get an overall idea?
>
> On Mon, Apr 18, 2016 at 2:32 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> As per the offline discussion we had, xsi:type can be supported in the
>> JSON schema as described below
>>
>> 123
>> ABC
>> 
>>
>> xsi:type can be added to a newly introduced json array called
>> "elementIdentifiers" and the value will be appended to to the field name in
>> the schema as shown below
>>
>> {
>> "$schema": "http://json-schema.org/draft-04/schema#;,
>> "title": "person",
>> "id": "http://wso2jsonschema.org;,
>> "type": "object",
>> "properties": {
>> "firstName": {
>> "id": "http://wso2jsonschema.org/firstName;,
>> "type": "string"
>> },
>> "*address,xsi:type=ipo:UKAddress"*: {
>>  "id": "
>> http://wso2jsonschema.org/phone;,
>> "type": "object",
>> "value":{
>> "type": "number"
>> },
>>
>> "properties": {
>> "city": {
>> "id": "http://wso2jsonschema.org/address/city;,
>> "type": "string"
>> }
>> },
>> "attributes": {
>> "postalcode": {
>> "id": "http://wso2jsonschema.org/address/postalcode;,
>> "type": "string"
>> }
>> }
>> }
>> },
>> *"elementIdentifiers": [{*
>> * "type": "xsi:type"*
>> * }]*
>> }
>>
>> @Nuwan : Feel free to add things we've discussed if I've missed anything
>>
>> Thanks,
>> Sohani
>>
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Mon, Apr 11, 2016 at 11:57 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Correction : This shouldn't add for the root level.
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Mon, Apr 11, 2016 at 11:32 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Thanks Viraj.

 I think this should be applied to the root level as well.

 {
 "$schema": "http://json-schema.org/draft-04/schema#;,
 "title": "person",
* "value"{*
 * "id": "http://wso2jsonschema.org
 ",*
 * "type": "object*
 *},*
 "properties": {
 "firstName": {
 "id": "http://wso2jsonschema.org/firstName;,
 "type": "string"
 },
 "phone": {
 "id": "http://wso2jsonschema.org/phone;,
 "type": "array",
 "items": [{
 *  “value”:{*
 *   "id":
 "http://wso2jsonschema.org/phone/phone
 ",*
 *   "type": "number"*
 *},*
 "attributes": {
 "primary": {
 "id": "http://wso2jsonschema.org/phone/primary;,
 "type": "boolean"
 }
 }
 }]
 }
 }
 }







 Sohani Weerasinghe
 Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe 
 wrote:

> Ok.  For an xml like below, let's have the value field as follows
>
> 
>
>xyz
>
>071655339
>
>0112655333 
> 
>
> {
>
> "$schema": "http://json-schema.org/draft-04/schema#;,
>
> "title": "person",
>
> "id": "http://wso2jsonschema.org;,
>
> "type": "object",
>
> "properties": {
>
> "firstName": {
>
> "id": "http://wso2jsonschema.org/firstName;,
>
> "type": "string"
>
> },
>
> "phone": {
>
> "id": "http://wso2jsonschema.org/phone;,
>
> "type": "array",
>
> "items": [{
>
> * “value”:{*
>
> * "id": "http://wso2jsonschema.org/phone/phone
> ",*
>
> * "type": "number"*
>
> * },*
>
> "attributes": {
>
> "primary": {
>
> "id": "http://wso2jsonschema.org/phone/primary;,
>
> "type": "boolean"
>
> }
>
> }
>
> }]
>
> }
>
> }
>

Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements

[Manuranga Perera]

btw, What is all this JSON/XML stuff you guys are doing. Just curious. Is
there a mail I can read to get an overall idea?

On Mon, Apr 18, 2016 at 2:32 AM, Sohani Weerasinghe  wrote:

> Hi All,
>
> As per the offline discussion we had, xsi:type can be supported in the
> JSON schema as described below
>
> 123
> ABC
> 
>
> xsi:type can be added to a newly introduced json array called
> "elementIdentifiers" and the value will be appended to to the field name in
> the schema as shown below
>
> {
> "$schema": "http://json-schema.org/draft-04/schema#;,
> "title": "person",
> "id": "http://wso2jsonschema.org;,
> "type": "object",
> "properties": {
> "firstName": {
> "id": "http://wso2jsonschema.org/firstName;,
> "type": "string"
> },
> "*address,xsi:type=ipo:UKAddress"*: {
>  "id": "
> http://wso2jsonschema.org/phone;,
> "type": "object",
> "value":{
> "type": "number"
> },
>
> "properties": {
> "city": {
> "id": "http://wso2jsonschema.org/address/city;,
> "type": "string"
> }
> },
> "attributes": {
> "postalcode": {
> "id": "http://wso2jsonschema.org/address/postalcode;,
> "type": "string"
> }
> }
> }
> },
> *"elementIdentifiers": [{*
> * "type": "xsi:type"*
> * }]*
> }
>
> @Nuwan : Feel free to add things we've discussed if I've missed anything
>
> Thanks,
> Sohani
>
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Apr 11, 2016 at 11:57 AM, Sohani Weerasinghe 
> wrote:
>
>> Correction : This shouldn't add for the root level.
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Mon, Apr 11, 2016 at 11:32 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Thanks Viraj.
>>>
>>> I think this should be applied to the root level as well.
>>>
>>> {
>>> "$schema": "http://json-schema.org/draft-04/schema#;,
>>> "title": "person",
>>>* "value"{*
>>> * "id": "http://wso2jsonschema.org
>>> ",*
>>> * "type": "object*
>>> *},*
>>> "properties": {
>>> "firstName": {
>>> "id": "http://wso2jsonschema.org/firstName;,
>>> "type": "string"
>>> },
>>> "phone": {
>>> "id": "http://wso2jsonschema.org/phone;,
>>> "type": "array",
>>> "items": [{
>>> *  “value”:{*
>>> *   "id":
>>> "http://wso2jsonschema.org/phone/phone
>>> ",*
>>> *   "type": "number"*
>>> *},*
>>> "attributes": {
>>> "primary": {
>>> "id": "http://wso2jsonschema.org/phone/primary;,
>>> "type": "boolean"
>>> }
>>> }
>>> }]
>>> }
>>> }
>>> }
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe 
>>> wrote:
>>>
 Ok.  For an xml like below, let's have the value field as follows

 

xyz

071655339

0112655333 
 

 {

 "$schema": "http://json-schema.org/draft-04/schema#;,

 "title": "person",

 "id": "http://wso2jsonschema.org;,

 "type": "object",

 "properties": {

 "firstName": {

 "id": "http://wso2jsonschema.org/firstName;,

 "type": "string"

 },

 "phone": {

 "id": "http://wso2jsonschema.org/phone;,

 "type": "array",

 "items": [{

 * “value”:{*

 * "id": "http://wso2jsonschema.org/phone/phone
 ",*

 * "type": "number"*

 * },*

 "attributes": {

 "primary": {

 "id": "http://wso2jsonschema.org/phone/primary;,

 "type": "boolean"

 }

 }

 }]

 }

 }

 }



 Sohani Weerasinghe
 Software Engineer
 WSO2, Inc: http://wso2.com

 Mobile  : +94 716439774
 Blog :http://christinetechtips.blogspot.com/
 Twitter  : https://twitter.com/sohanichristine

 On Mon, Apr 11, 2016 at 11:05 AM, Nuwan Pallewela 
 wrote:

> Hi Sohani,
>
> +1 for the above approaches.
>
> We have to decide on how to represent non identical elements with same
> name. Viraj is working on it.
>
> Thanks,
> Nuwan
>
> On Mon, Apr 11, 2016 at 10:44 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi Viraj/Nuwan,
>>
>> Really appreciate your input on this
>>

[Dev] What are the features that enable federated authentication

[Ayesha Dissanayaka]

Hi all,

I am trying to enable managing Service Providers from GREG-5.1.0 management
console to use Federated authentication for Store/Publisher. Currently it
seems GREG-5.1.0 does not have necessary features.

Can someone point me which feature(s) need to be installed from [2] in
order to enable this.

[1] https://docs.wso2.com/display/IS510/Federated+Authentication
[2] http://product-dist.wso2.com/p2/carbon/releases/wilkes/

Thanks!
Ayesha
-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 API Manager Analytics 1.0.0 - Milestone 2 Released!

[Nirmal Fernando]

Please find the correct link
https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/wso2analytics-apim-1.0.0-SNAPSHOT.zip

On Mon, Apr 18, 2016 at 3:39 PM, Nirmal Fernando  wrote:

> Sorry Ushani, we'll reupload and let you know.
>
> On Mon, Apr 18, 2016 at 3:13 PM, Ushani Balasooriya 
> wrote:
>
>> Hi Nirmal,
>>
>> When I access the link [1] it gives me a 404 (Path
>> /org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
>> not found in local storage of repository "WSO2 snapshots" [id=snapshots]).
>> Can you please advice how to resolve it?
>>
>> [1]
>> http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
>>
>> Thanks,
>>
>> On Wed, Apr 13, 2016 at 6:00 PM, Nirmal Fernando  wrote:
>>
>>>
>>> *WSO2 API Manager Analytics 1.0.0 - Milestone 2 Released!*
>>>
>>> We are pleased to announce the milestone 2 release of WSO2 API Manager
>>> Analytics 1.0.0 [1] which is powered by WSO2 Data Analytics Server. In the
>>> second milestone release,
>>>
>>> * We are introducing alert dashboard, alert subscriptions and alert
>>> configuration features [2]
>>> * We are introducing log analytics to WSO2 API Manager [3] - Live log
>>> viewer, log analytics dashboard.
>>>
>>> Your feedback is highly appreciated to improve the future releases,
>>> please report any suggestions/issues at [4].
>>>
>>> [1]
>>> http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
>>>
>>> [2]
>>> https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/WSO2APIManagerAnalytics-Alerts.pdf
>>> (same is attached herewith)
>>>
>>> [3]
>>> https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/WSO2LogAnalyzerForAPIM.pdf
>>>  (same
>>> is attached herewith)
>>>
>>> [4] https://wso2.org/jira/browse/APIMANAGER
>>>
>>> --
>>>
>>> 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
>>>
>>>
>>
>>
>> --
>> *Ushani Balasooriya*
>> Senior Software Engineer - QA;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.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] [VOTE] Release WSO2 Governance Registry 5.2.0 RC 1

[Sameera Kannangara]

Hi all,

Canceling this vote due to issue[1] which we found in RC1 pack. Will fix
this issue and call for a RC2 ASAP.

Thanks and Regards,
G-Reg team.

[1] https://wso2.org/jira/browse/REGISTRY-3555

On Tue, Apr 12, 2016 at 3:52 PM, Thushara Ranawaka 
wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.2.0 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/browse/REGISTRY-3561?filter=13023
> Please download, test and vote. Please refer the release verification
> guide for detailed information on verifying this release.
>
> Source & binary distribution files:
> https://svn.wso2.org/repos/wso2/scratch/G-Reg/5.2.0/rc1/
>
> Maven staging repo:
> https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1001
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/tree/v5.2.0-rc1
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> Thanks and Regards
> G-Reg team
>
> --
> Thanks,
> Thushara Kasun Ranawaka
> Software Engineer
> WSO2 Inc.; 
> lean.enterprise.middleware
> Mobile : *+94 (0) 773438949 <%2B94%20%280%29%20773438949>*
> *thusha...@wso2.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sameera Kannangara*
Software Engineer
Platform TG; WSO2 Inc. http://wso2.com
Contact:
phone: +94719541577
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include carbon.yml and other config files in Carbon Core feature

[Niranjan Karunanandham]

Hi all,

I had a offline discussion with Sameera and KasunG with regard to this.
Please see the comments below based on the discussion:

On Mon, Apr 18, 2016 at 11:55 AM, Niranjan Karunanandham 
wrote:

> Hi all,
>
> Below is the current C5 source code structure:
>
> | -- archetypes
> | -- base
> | -- core
> | -- distribution (contains the conf files which are copied to the
> distribution via the bin.xml)
> | -- features
>
> | -- org.wso2.carbon.core.runtime.feature
> | -- org.wso2.carbon.core.server.feature
>
> | -- launcher
> | -- parent (parent pom)
> | -- tests
> | -- tools (Bundle Generator)
>
>
> Any particular reason as to why we have separate folder for each component
> such as launcher, tools, core and base? Can we move these to a folder
> called component since these are packed with the kernel and have the source
> code structure as below:
>
> | -- archetypes
> | -- components
>
> | -- base
> | -- core
> | -- launcher
> | -- tools (Bundle Generator)
>
> | -- distribution (contains the conf files which are copied to the
> distribution via the bin.xml)
> | -- features
>
> | -- org.wso2.carbon.core.runtime.feature
> | -- org.wso2.carbon.core.server.feature
>
> | -- parent (parent pom)
> | -- tests
>
> It was suggested to leave this as it is since changing it will not have
any impact.


> In-addition shall we bundle these components with a feature (either new
> say launcher feature or existing) and have its corresponding configuration
> files (including scripts like carbon.sh, if present) packed in the feature.
> In this case, we will not need to copy these config files via the bin.xml.
> In addition to this, other products will obtain these files when they
> install the feature without having to keep copy of this file in their
> distribution source code.
>
It was suggested to rename the org.wso2.carbon.core.server.feature to
org.wso2.carbon.kernel.feature and it will contain all the carbon kernel
features. The org.wso2.carbon.runtime.feature (instead of
org.wso2.carbon.core.runtime.feature) will contain all the runtime bundles
such as org.eclipse.equinox.simpleconfigurator, etc...

It was suggested that all the files in the distribution folder which are
packed using the bin.xml (assembly plugin), should be packed with
org.wso2.carbon.kernel.feature and when this feature is installed then it
will copy all those files to the location specified in the feature's p2.inf.


>
> WDYT?
>
> Regards,
> Nira
>
>
> On Mon, Apr 11, 2016 at 9:57 AM, Niranjan Karunanandham  > wrote:
>
>> Hi all,
>>
>> i have created a JIRA [1] for this. Along with the conf folder, shall we
>> include* bin folder* (in the distribution/carbon-home) as well into
>> org.wso2.carbon.core.server.feature? WDYT?
>>
>> [1] - https://wso2.org/jira/browse/CARBON-15851
>>
>> Regards,
>> Nira
>>
>> On Tue, Apr 5, 2016 at 3:45 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Apr 5, 2016 at 3:32 PM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Kishanthan,

 On Tue, Apr 5, 2016 at 3:23 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> +1
>
> Also by default, we need to have place holders for name, id and
> version properties rather than having hard coded values. The product team
> can then put their relevant values at build time. Let's add this also 
> along
> with this change.
>
 By default shall we have the above values as empty in the carbon.yml.
 If it is not defined pick it up from System properties (using the place
 holder carbon.name, carbon.id and carbon.version for name, id and
 version respectively). If both are not define then get the values from a
 Constant. WDYT?

>>>
>>> IMO, let's have it like this.
>>>
>>> id: ${server.key}
>>> name: ${server.name}
>>> version: ${server.version}
>>>
>>> If no value is set for this under system property or env property, we
>>> should use the default values which comes from the configuration bean. The
>>> product team can use their own values when building a product.
>>>
>>>

>
>
> On Tue, Apr 5, 2016 at 3:14 PM, Aruna Karunarathna 
> wrote:
>
>> On Fri, Apr 1, 2016 at 2:31 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> In Carbon 5, the carbon.yml, log4j2.xml and etc., are in the
>>> distribution folder and copied to the distribution pack via bin.xml. Why
>>> don't we add these configuration files to Carbon Server Feature
>>> (org.wso2.carbon.core.server.feature) which are copied to the packed 
>>> when
>>> the feature is installed. WDYT?
>>>
>>> +1. we should bring the configurations also when we install the core
>> feature.
>>
>> Regards,
>>> Nira
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: 

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Afkham Azeez]

Fixed.

On Mon, Apr 18, 2016 at 3:03 PM, Hasitha Aravinda  wrote:

> Hi Azeez,
>
> msf4j-core bundle exports a wrong version. This should be corrected as
> 1.1.0
>
> Export-Package: org.wso2.msf4j;version="*1.0.0*"
>
> Thanks,
> Hasitha.
>
> On Mon, Apr 18, 2016 at 1:18 PM, Hasitha Aravinda 
> wrote:
>
>> Thanks Azeez.
>>
>> Hasitha.
>>
>> On Mon, Apr 18, 2016 at 1:14 PM, Afkham Azeez  wrote:
>>
>>> Updated to 1.1.0-SNAPSHOT
>>>
>>> On Mon, Apr 18, 2016 at 1:13 PM, Afkham Azeez  wrote:
>>>
 Updates to 1.1.0-SNAPSHOT.

 On Mon, Apr 18, 2016 at 10:15 AM, Hasitha Aravinda 
 wrote:

> Hi Kernel team,
>
> This is happening due to an issue in msf4j 1.0.0 component and
> solution is to move latest msf4j version. But still msf4j master branch is
> set to 1.0.0-SNAPSHOT. Since MSF4J 1.0.0 is released, Jenkins is not
> publishing snapshot artifacts to nexus. Could you please fix this ?
>
> [1] - https://github.com/wso2/msf4j/tree/master
>
> Thanks,
> Hasitha.
>
> On Fri, Apr 8, 2016 at 5:35 PM, Hasitha Aravinda 
> wrote:
>
>> I have updated kernel version to 5.1.0-SNAPSHOT and now I am getting
>> following error. What could be the issue. ?
>>
>> [2016-04-08 17:24:26,865]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>> Startup component netty-transports-mgt from
>> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
>> state until Capability
>> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
>> from bundle(msf4j-core:1.0.0) is available
>> [2016-04-08 17:24:26,866]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>> Startup component netty-transports-mgt from
>> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
>> state until Capability
>> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
>> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>> [2016-04-08 17:24:26,866]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>> Startup component carbon-transport-mgt from
>> bundle(org.wso2.carbon.core:5.1.0.SNAPSHOT) will be in the pending state
>> until Capability
>> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
>> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>>
>>
>> Thanks,
>> Hasitha.
>>
>> On Thu, Apr 7, 2016 at 6:57 PM, Rasika Perera 
>> wrote:
>>
>>> Hi Himasha,
>>>
>>> This usually happens when MSF4J is waiting for its required
>>> capabilities. MSF4J has cardinality of AT_LEAST_ONE as required
>>> capabilities for the Carbon Transport. Which means server
>>> is waiting on the startup for at least one OSGi service implementing
>>> CarbonTransport.class interface[1]. As Aruna mentioned can you
>>> verify whether you are packing carbon transport.
>>>
>>> However one issue found on your pom file.
>>>
>>> 
>>> org.wso2.carbon.bpmn.rest.**,*
>>> version=${carbon.business-process.exp.pkg.version},
>>> 
>>>
>>> should be corrected as;
>>>
>>> 
>>> org.wso2.carbon.bpmn.rest.**;*
>>> version=${carbon.business-process.exp.pkg.version},
>>> 
>>>
>>> [1]
>>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74
>>>
>>> Thanks
>>> ~Rasika
>>>
>>>
>>> On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna 
>>> wrote:
>>>
 Have you guys added the carbon-transport-mgt?

 On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda 
 wrote:

> Hi Manu,
>
> were you able to solve this issue, I am getting the same error.
>
> Thanks,
> Hasitha.
>
> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera 
> wrote:
>
>> MSS product hangs when I deploy my service, but fat-jar mode
>> works.
>>
>> prints
>> Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.Interceptor
>>
>> how to proceed debugging?
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Hasitha Aravinda,

Re: [Dev] WSO2 API Manager Analytics 1.0.0 - Milestone 2 Released!

[Nirmal Fernando]

Sorry Ushani, we'll reupload and let you know.

On Mon, Apr 18, 2016 at 3:13 PM, Ushani Balasooriya  wrote:

> Hi Nirmal,
>
> When I access the link [1] it gives me a 404 (Path
> /org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
> not found in local storage of repository "WSO2 snapshots" [id=snapshots]).
> Can you please advice how to resolve it?
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
>
> Thanks,
>
> On Wed, Apr 13, 2016 at 6:00 PM, Nirmal Fernando  wrote:
>
>>
>> *WSO2 API Manager Analytics 1.0.0 - Milestone 2 Released!*
>>
>> We are pleased to announce the milestone 2 release of WSO2 API Manager
>> Analytics 1.0.0 [1] which is powered by WSO2 Data Analytics Server. In the
>> second milestone release,
>>
>> * We are introducing alert dashboard, alert subscriptions and alert
>> configuration features [2]
>> * We are introducing log analytics to WSO2 API Manager [3] - Live log
>> viewer, log analytics dashboard.
>>
>> Your feedback is highly appreciated to improve the future releases,
>> please report any suggestions/issues at [4].
>>
>> [1]
>> http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
>>
>> [2]
>> https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/WSO2APIManagerAnalytics-Alerts.pdf
>> (same is attached herewith)
>>
>> [3]
>> https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/WSO2LogAnalyzerForAPIM.pdf
>>  (same
>> is attached herewith)
>>
>> [4] https://wso2.org/jira/browse/APIMANAGER
>>
>> --
>>
>> 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
>>
>>
>
>
> --
> *Ushani Balasooriya*
> Senior Software Engineer - QA;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>


-- 

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] WSO2 API Manager Analytics 1.0.0 - Milestone 2 Released!

[Ushani Balasooriya]

Hi Nirmal,

When I access the link [1] it gives me a 404 (Path
/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
not found in local storage of repository "WSO2 snapshots" [id=snapshots]).
Can you please advice how to resolve it?

[1]
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip

Thanks,

On Wed, Apr 13, 2016 at 6:00 PM, Nirmal Fernando  wrote:

>
> *WSO2 API Manager Analytics 1.0.0 - Milestone 2 Released!*
>
> We are pleased to announce the milestone 2 release of WSO2 API Manager
> Analytics 1.0.0 [1] which is powered by WSO2 Data Analytics Server. In the
> second milestone release,
>
> * We are introducing alert dashboard, alert subscriptions and alert
> configuration features [2]
> * We are introducing log analytics to WSO2 API Manager [3] - Live log
> viewer, log analytics dashboard.
>
> Your feedback is highly appreciated to improve the future releases, please
> report any suggestions/issues at [4].
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/analytics/apim/wso2analytics-apim/1.0.0-SNAPSHOT/wso2analytics-apim-1.0.0-20160413.080447-2.zip
>
> [2]
> https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/WSO2APIManagerAnalytics-Alerts.pdf
> (same is attached herewith)
>
> [3]
> https://github.com/wso2/analytics-apim/releases/download/v1.0.0-m2/WSO2LogAnalyzerForAPIM.pdf
>  (same
> is attached herewith)
>
> [4] https://wso2.org/jira/browse/APIMANAGER
>
> --
>
> 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
>
>


-- 
*Ushani Balasooriya*
Senior Software Engineer - QA;
WSO2 Inc; http://www.wso2.com/.
Mobile; +94772636796
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Hasitha Aravinda]

Hi Azeez,

msf4j-core bundle exports a wrong version. This should be corrected as 1.1.0

Export-Package: org.wso2.msf4j;version="*1.0.0*"

Thanks,
Hasitha.

On Mon, Apr 18, 2016 at 1:18 PM, Hasitha Aravinda  wrote:

> Thanks Azeez.
>
> Hasitha.
>
> On Mon, Apr 18, 2016 at 1:14 PM, Afkham Azeez  wrote:
>
>> Updated to 1.1.0-SNAPSHOT
>>
>> On Mon, Apr 18, 2016 at 1:13 PM, Afkham Azeez  wrote:
>>
>>> Updates to 1.1.0-SNAPSHOT.
>>>
>>> On Mon, Apr 18, 2016 at 10:15 AM, Hasitha Aravinda 
>>> wrote:
>>>
 Hi Kernel team,

 This is happening due to an issue in msf4j 1.0.0 component and solution
 is to move latest msf4j version. But still msf4j master branch is set to
 1.0.0-SNAPSHOT. Since MSF4J 1.0.0 is released, Jenkins is not publishing
 snapshot artifacts to nexus. Could you please fix this ?

 [1] - https://github.com/wso2/msf4j/tree/master

 Thanks,
 Hasitha.

 On Fri, Apr 8, 2016 at 5:35 PM, Hasitha Aravinda 
 wrote:

> I have updated kernel version to 5.1.0-SNAPSHOT and now I am getting
> following error. What could be the issue. ?
>
> [2016-04-08 17:24:26,865]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
> Startup component netty-transports-mgt from
> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
> state until Capability
> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
> from bundle(msf4j-core:1.0.0) is available
> [2016-04-08 17:24:26,866]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
> Startup component netty-transports-mgt from
> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
> state until Capability
> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
> [2016-04-08 17:24:26,866]  WARN
> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
> Startup component carbon-transport-mgt from
> bundle(org.wso2.carbon.core:5.1.0.SNAPSHOT) will be in the pending state
> until Capability
> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>
>
> Thanks,
> Hasitha.
>
> On Thu, Apr 7, 2016 at 6:57 PM, Rasika Perera 
> wrote:
>
>> Hi Himasha,
>>
>> This usually happens when MSF4J is waiting for its required
>> capabilities. MSF4J has cardinality of AT_LEAST_ONE as required
>> capabilities for the Carbon Transport. Which means server is waiting
>> on the startup for at least one OSGi service implementing
>> CarbonTransport.class interface[1]. As Aruna mentioned can you
>> verify whether you are packing carbon transport.
>>
>> However one issue found on your pom file.
>>
>> 
>> org.wso2.carbon.bpmn.rest.**,*
>> version=${carbon.business-process.exp.pkg.version},
>> 
>>
>> should be corrected as;
>>
>> 
>> org.wso2.carbon.bpmn.rest.**;*
>> version=${carbon.business-process.exp.pkg.version},
>> 
>>
>> [1]
>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74
>>
>> Thanks
>> ~Rasika
>>
>>
>> On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Have you guys added the carbon-transport-mgt?
>>>
>>> On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda 
>>> wrote:
>>>
 Hi Manu,

 were you able to solve this issue, I am getting the same error.

 Thanks,
 Hasitha.

 On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera 
 wrote:

> MSS product hangs when I deploy my service, but fat-jar mode works.
>
> prints
> Waiting on pending capability registration. Capability:
> org.wso2.msf4j.Interceptor
>
> how to proceed debugging?
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 --
 Hasitha Aravinda,
 Senior Software Engineer,
 WSO2 Inc.
 Email: hasi...@wso2.com
 Mobile : +94 718 210 200

 ___
 Dev mailing list
 Dev@wso2.org
 

Re: [Dev] ESB Analytics - Verifying the common production use cases

[Supun Sethunga]

JIRA: https://wso2.org/jira/browse/ANLYESB-15

On Mon, Apr 18, 2016 at 2:24 PM, Srinath Perera  wrote:

> Could you open a Jira ( blocker)? We need to figure out a solution for the
> project as well.
>
> --Srinath
>
>
>
> On Mon, Apr 18, 2016 at 12:17 PM, Supun Sethunga  wrote:
>
>> Hi Kasun,
>>
>> We ran several rounds of load tests for ESB analytics (covering few
>> scenarios with several proxy services, APIs, Sequences, etc). In the first
>> round, we ran the tests with a low TPS (around 10-15) to test and validate
>> the use cases, such as the counts, delays, drilling down to
>> mediator/sequence/message level, etc. These scenarios worked as expected.
>>
>> On the second round, we ran the same tests with a higher TPS (gradually
>> increasing). In the process, we identified a bottleneck at the DB level
>> under a high TPS (TPS of over 50, which is not that high), resulting the
>> stat generation to be slowed down with time. This occurs as DAS is both
>> reading and writing from/to the same table (row events) at the same time,
>> at a rapid rate, causing the IO operations to be slowed down (due to table
>> locks and etc.), and hence the summarizing process takes longer time, in
>> each iteration. (most of the consumed time for summarizing, around 80% is
>> taken for reading the raw data and store them as event-wise data in DB)
>> Therefore, we are currently doing an enhancement to improve performance,
>> by summarizing the data (summarize up to per-second info) on the fly with
>> siddhi and store it, rather than spark doing it as a batch operation. This
>> should eliminate roughly around 80% (above mentioned) of time taken to
>> read/write row data from DB.
>>
>> Will give an update after re-running the load test with this enhancement.
>>
>> Regards,
>> Supun
>>
>> On Mon, Apr 18, 2016 at 11:40 AM, Kasun Indrasiri  wrote:
>>
>>> Any updates on this?
>>>
>>> We must test the ESB analytics/ ESB 5 alpha release with the common
>>> production use cases + high load.
>>>
>>> On Mon, Mar 28, 2016 at 2:38 PM, Buddhima Wijeweera 
>>> wrote:
>>>
 Hi All,

 We are currently in the process of testing statistics & tracing for
 various scenarios.
 Initially we planned to cover on the areas we have identified for
 functionality testing.
 Then we planned to move on to common scenarios, and performance testing
 as well.

 Thank you,

 On Mon, Mar 28, 2016 at 2:34 PM, Srinath Perera 
 wrote:

> Please run ESB benchmark, get the events comes out of it to DAS, and
> use that for testing.
>
> --Srinath
>
> On Mon, Mar 28, 2016 at 10:02 AM, Kasun Indrasiri 
> wrote:
>
>> Hi Buddhima/VirajS,
>>
>> Once the end to end functionalities are implemented on the ESB
>> analytics side, can we start testing the current implementation for
>> production use cases of ESB. Basically we need to cover all the common
>> integration scenarios and stress test the implemented with high load too.
>>
>> Thanks,
>> Kasun
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> 
> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
> Site: http://home.apache.org/~hemapani/
> Photos: http://www.flickr.com/photos/hemapani/
> Phone: 0772360902
>



 --
 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

>>>
>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> *Supun Sethunga*
>> Software Engineer
>> WSO2, Inc.
>> http://wso2.com/
>> lean | enterprise | middleware
>> Mobile : +94 716546324
>>
>
>
>
> --
> 
> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
> Site: http://home.apache.org/~hemapani/
> Photos: http://www.flickr.com/photos/hemapani/
> Phone: 0772360902
>



-- 
*Supun Sethunga*
Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot generate P2 metadata: P2 publisher return code was 13

[Damith Wickramasinghe]

Thanks Niranjan.

Regards,
Damith.

On Mon, Apr 18, 2016 at 12:46 PM, Niranjan Karunanandham 
wrote:

> Hi Damith,
>
> As mentioned in [1], this issue happens when the certificates are not
> trusted by the Oracle VM. A similar issue was mentioned in [2] and it was
> sorted.
>
> [1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=309059
> [2] - http://mail.wso2.org/mailarchive/dev/2014-November/039182.html
>
> Regards,
> Nira
>
>
> On Mon, Apr 18, 2016 at 10:30 AM, Damith Wickramasinghe 
> wrote:
>
>> Hi Lasantha,
>>
>> I have checked the log file. It does not have any information other than
>> the same thing mention in the above log One or more certificates rejected.
>> Cannot proceed with installation. After installing the Java again solved
>> the issue.
>>
>> Regards,
>> Damith.
>>
>>
>> On Mon, Apr 18, 2016 at 8:12 AM, Lasantha Fernando 
>> wrote:
>>
>>> Hi Damith,
>>>
>>> Were you able to get any more information from the log file mentioned in
>>> the above stack trace?
>>>
>>> log file location: /home/damith/.m2/repository/
>>> org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/
>>> configuration/1460895093502.log
>>>
>>> Can you post any error information in that log file as well?
>>>
>>> Thanks,
>>> Lasantha
>>>
>>> On 17 April 2016 at 22:47, Damith Wickramasinghe 
>>> wrote:
>>>
 Hi Mohan,

 Maven version is 3.0.5. and java is 1.7 .Following is the complete
 trace i got.

  Command line:
 /bin/sh -c cd
 /home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen
 && /usr/lib/jvm/java-7-oracle/jre/bin/java -jar
 /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
 -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
 file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
 -artifactRepository
 file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
 -installIU carbon.product.id -profileProperties
 org.eclipse.update.install.features=true -profile worker -bundlepool
 file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components
 -shared
 file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/p2
 -destination
 file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/worker
 -p2.os linux -p2.ws gtk -p2.arch x86 -roaming
 Installing carbon.product.id 4.4.3.
 Installation failed.
 One or more certificates rejected. Cannot proceed with installation.
 Application failed, log file location:
 /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460895093502.log

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 CEP - Parent . SUCCESS
 [0.972s]
 [INFO] WSO2 CEP - Style Parent ... SUCCESS
 [0.040s]
 [INFO] WSO2 CEP - Styles . SUCCESS
 [1.216s]
 [INFO] WSO2 Stratos CEP - Styles . SUCCESS
 [0.185s]
 [INFO] WSO2 CEP - Samples Parent . SUCCESS
 [0.023s]
 [INFO] WSO2 CEP - Samples Producers .. SUCCESS
 [0.046s]
 [INFO] WSO2 CEP - Producer - WSO2 Event Client ... SUCCESS
 [8.591s]
 [INFO] WSO2 CEP - Publisher - HTTP Client  SUCCESS
 [0.336s]
 [INFO] WSO2 CEP - Publisher - JMS Client . SUCCESS
 [2.722s]
 [INFO] WSO2 CEP - Publisher - MQTT Client  SUCCESS
 [0.171s]
 [INFO] WSO2 CEP - Publisher - Kafka Client ... SUCCESS
 [11.891s]
 [INFO] WSO2 CEP - Publisher - SOAP Client  SUCCESS
 [0.551s]
 [INFO] WSO2 CEP - Producer - Websocket Publisher . SUCCESS
 [4.295s]
 [INFO] WSO2 CEP - Producer - Performance Test  SUCCESS
 [0.475s]
 [INFO] WSO2 CEP - Publisher - HTTP Performance Client  SUCCESS
 [0.166s]
 [INFO] WSO2 CEP - Publisher - Kafka Producer . SUCCESS
 [0.174s]
 [INFO] WSO2 CEP - Publisher - JMS Performance Client . SUCCESS
 [0.150s]
 [INFO] WSO2 CEP - Sample Consumers ... SUCCESS
 [0.035s]
 [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS
 [1.061s]
 [INFO] WSO2 CEP - Consumer - JMS Consumer  SUCCESS
 [0.145s]
 [INFO] WSO2 CEP - Consumer - MQTT Consumer ... SUCCESS
 [0.103s]
 [INFO] 

Re: [Dev] ESB Analytics - Verifying the common production use cases

[Srinath Perera]

Could you open a Jira ( blocker)? We need to figure out a solution for the
project as well.

--Srinath



On Mon, Apr 18, 2016 at 12:17 PM, Supun Sethunga  wrote:

> Hi Kasun,
>
> We ran several rounds of load tests for ESB analytics (covering few
> scenarios with several proxy services, APIs, Sequences, etc). In the first
> round, we ran the tests with a low TPS (around 10-15) to test and validate
> the use cases, such as the counts, delays, drilling down to
> mediator/sequence/message level, etc. These scenarios worked as expected.
>
> On the second round, we ran the same tests with a higher TPS (gradually
> increasing). In the process, we identified a bottleneck at the DB level
> under a high TPS (TPS of over 50, which is not that high), resulting the
> stat generation to be slowed down with time. This occurs as DAS is both
> reading and writing from/to the same table (row events) at the same time,
> at a rapid rate, causing the IO operations to be slowed down (due to table
> locks and etc.), and hence the summarizing process takes longer time, in
> each iteration. (most of the consumed time for summarizing, around 80% is
> taken for reading the raw data and store them as event-wise data in DB)
> Therefore, we are currently doing an enhancement to improve performance,
> by summarizing the data (summarize up to per-second info) on the fly with
> siddhi and store it, rather than spark doing it as a batch operation. This
> should eliminate roughly around 80% (above mentioned) of time taken to
> read/write row data from DB.
>
> Will give an update after re-running the load test with this enhancement.
>
> Regards,
> Supun
>
> On Mon, Apr 18, 2016 at 11:40 AM, Kasun Indrasiri  wrote:
>
>> Any updates on this?
>>
>> We must test the ESB analytics/ ESB 5 alpha release with the common
>> production use cases + high load.
>>
>> On Mon, Mar 28, 2016 at 2:38 PM, Buddhima Wijeweera 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are currently in the process of testing statistics & tracing for
>>> various scenarios.
>>> Initially we planned to cover on the areas we have identified for
>>> functionality testing.
>>> Then we planned to move on to common scenarios, and performance testing
>>> as well.
>>>
>>> Thank you,
>>>
>>> On Mon, Mar 28, 2016 at 2:34 PM, Srinath Perera 
>>> wrote:
>>>
 Please run ESB benchmark, get the events comes out of it to DAS, and
 use that for testing.

 --Srinath

 On Mon, Mar 28, 2016 at 10:02 AM, Kasun Indrasiri 
 wrote:

> Hi Buddhima/VirajS,
>
> Once the end to end functionalities are implemented on the ESB
> analytics side, can we start testing the current implementation for
> production use cases of ESB. Basically we need to cover all the common
> integration scenarios and stress test the implemented with high load too.
>
> Thanks,
> Kasun
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



 --
 
 Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
 Site: http://home.apache.org/~hemapani/
 Photos: http://www.flickr.com/photos/hemapani/
 Phone: 0772360902

>>>
>>>
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> *Supun Sethunga*
> Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
>



-- 

Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
Site: http://home.apache.org/~hemapani/
Photos: http://www.flickr.com/photos/hemapani/
Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Hasitha Aravinda]

Thanks Azeez.

Hasitha.

On Mon, Apr 18, 2016 at 1:14 PM, Afkham Azeez  wrote:

> Updated to 1.1.0-SNAPSHOT
>
> On Mon, Apr 18, 2016 at 1:13 PM, Afkham Azeez  wrote:
>
>> Updates to 1.1.0-SNAPSHOT.
>>
>> On Mon, Apr 18, 2016 at 10:15 AM, Hasitha Aravinda 
>> wrote:
>>
>>> Hi Kernel team,
>>>
>>> This is happening due to an issue in msf4j 1.0.0 component and solution
>>> is to move latest msf4j version. But still msf4j master branch is set to
>>> 1.0.0-SNAPSHOT. Since MSF4J 1.0.0 is released, Jenkins is not publishing
>>> snapshot artifacts to nexus. Could you please fix this ?
>>>
>>> [1] - https://github.com/wso2/msf4j/tree/master
>>>
>>> Thanks,
>>> Hasitha.
>>>
>>> On Fri, Apr 8, 2016 at 5:35 PM, Hasitha Aravinda 
>>> wrote:
>>>
 I have updated kernel version to 5.1.0-SNAPSHOT and now I am getting
 following error. What could be the issue. ?

 [2016-04-08 17:24:26,865]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
 Startup component netty-transports-mgt from
 bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
 state until Capability
 org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
 from bundle(msf4j-core:1.0.0) is available
 [2016-04-08 17:24:26,866]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
 Startup component netty-transports-mgt from
 bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
 state until Capability
 org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
 from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
 [2016-04-08 17:24:26,866]  WARN
 {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
 Startup component carbon-transport-mgt from
 bundle(org.wso2.carbon.core:5.1.0.SNAPSHOT) will be in the pending state
 until Capability
 org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
 from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available


 Thanks,
 Hasitha.

 On Thu, Apr 7, 2016 at 6:57 PM, Rasika Perera  wrote:

> Hi Himasha,
>
> This usually happens when MSF4J is waiting for its required
> capabilities. MSF4J has cardinality of AT_LEAST_ONE as required
> capabilities for the Carbon Transport. Which means server is waiting
> on the startup for at least one OSGi service implementing
> CarbonTransport.class interface[1]. As Aruna mentioned can you verify
> whether you are packing carbon transport.
>
> However one issue found on your pom file.
>
> 
> org.wso2.carbon.bpmn.rest.**,*
> version=${carbon.business-process.exp.pkg.version},
> 
>
> should be corrected as;
>
> 
> org.wso2.carbon.bpmn.rest.**;*
> version=${carbon.business-process.exp.pkg.version},
> 
>
> [1]
> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74
>
> Thanks
> ~Rasika
>
>
> On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna 
> wrote:
>
>> Have you guys added the carbon-transport-mgt?
>>
>> On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda 
>> wrote:
>>
>>> Hi Manu,
>>>
>>> were you able to solve this issue, I am getting the same error.
>>>
>>> Thanks,
>>> Hasitha.
>>>
>>> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera 
>>> wrote:
>>>
 MSS product hangs when I deploy my service, but fat-jar mode works.

 prints
 Waiting on pending capability registration. Capability:
 org.wso2.msf4j.Interceptor

 how to proceed debugging?
 --
 With regards,
 *Manu*ranga Perera.

 phone : 071 7 70 20 50
 mail : m...@wso2.com

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


>>>
>>>
>>> --
>>> --
>>> Hasitha Aravinda,
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>> Email: hasi...@wso2.com
>>> Mobile : +94 718 210 200
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>> ___

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Afkham Azeez]

Updated to 1.1.0-SNAPSHOT

On Mon, Apr 18, 2016 at 1:13 PM, Afkham Azeez  wrote:

> Updates to 1.1.0-SNAPSHOT.
>
> On Mon, Apr 18, 2016 at 10:15 AM, Hasitha Aravinda 
> wrote:
>
>> Hi Kernel team,
>>
>> This is happening due to an issue in msf4j 1.0.0 component and solution
>> is to move latest msf4j version. But still msf4j master branch is set to
>> 1.0.0-SNAPSHOT. Since MSF4J 1.0.0 is released, Jenkins is not publishing
>> snapshot artifacts to nexus. Could you please fix this ?
>>
>> [1] - https://github.com/wso2/msf4j/tree/master
>>
>> Thanks,
>> Hasitha.
>>
>> On Fri, Apr 8, 2016 at 5:35 PM, Hasitha Aravinda 
>> wrote:
>>
>>> I have updated kernel version to 5.1.0-SNAPSHOT and now I am getting
>>> following error. What could be the issue. ?
>>>
>>> [2016-04-08 17:24:26,865]  WARN
>>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>>> Startup component netty-transports-mgt from
>>> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
>>> state until Capability
>>> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
>>> from bundle(msf4j-core:1.0.0) is available
>>> [2016-04-08 17:24:26,866]  WARN
>>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>>> Startup component netty-transports-mgt from
>>> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
>>> state until Capability
>>> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
>>> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>>> [2016-04-08 17:24:26,866]  WARN
>>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>>> Startup component carbon-transport-mgt from
>>> bundle(org.wso2.carbon.core:5.1.0.SNAPSHOT) will be in the pending state
>>> until Capability
>>> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
>>> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>>>
>>>
>>> Thanks,
>>> Hasitha.
>>>
>>> On Thu, Apr 7, 2016 at 6:57 PM, Rasika Perera  wrote:
>>>
 Hi Himasha,

 This usually happens when MSF4J is waiting for its required
 capabilities. MSF4J has cardinality of AT_LEAST_ONE as required
 capabilities for the Carbon Transport. Which means server is waiting
 on the startup for at least one OSGi service implementing
 CarbonTransport.class interface[1]. As Aruna mentioned can you verify
 whether you are packing carbon transport.

 However one issue found on your pom file.

 
 org.wso2.carbon.bpmn.rest.**,*
 version=${carbon.business-process.exp.pkg.version},
 

 should be corrected as;

 
 org.wso2.carbon.bpmn.rest.**;*
 version=${carbon.business-process.exp.pkg.version},
 

 [1]
 https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74

 Thanks
 ~Rasika


 On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna 
 wrote:

> Have you guys added the carbon-transport-mgt?
>
> On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda 
> wrote:
>
>> Hi Manu,
>>
>> were you able to solve this issue, I am getting the same error.
>>
>> Thanks,
>> Hasitha.
>>
>> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera 
>> wrote:
>>
>>> MSS product hangs when I deploy my service, but fat-jar mode works.
>>>
>>> prints
>>> Waiting on pending capability registration. Capability:
>>> org.wso2.msf4j.Interceptor
>>>
>>> how to proceed debugging?
>>> --
>>> With regards,
>>> *Manu*ranga Perera.
>>>
>>> phone : 071 7 70 20 50
>>> mail : m...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 With Regards,

 *Rasika Perera*
 Software Engineer
 M: +94 71 680 9060 E: rasi...@wso2.com
 LinkedIn: 

Re: [Dev] product-mss hangs after deploying a (faulty) service

[Afkham Azeez]

Updates to 1.1.0-SNAPSHOT.

On Mon, Apr 18, 2016 at 10:15 AM, Hasitha Aravinda  wrote:

> Hi Kernel team,
>
> This is happening due to an issue in msf4j 1.0.0 component and solution is
> to move latest msf4j version. But still msf4j master branch is set to
> 1.0.0-SNAPSHOT. Since MSF4J 1.0.0 is released, Jenkins is not publishing
> snapshot artifacts to nexus. Could you please fix this ?
>
> [1] - https://github.com/wso2/msf4j/tree/master
>
> Thanks,
> Hasitha.
>
> On Fri, Apr 8, 2016 at 5:35 PM, Hasitha Aravinda  wrote:
>
>> I have updated kernel version to 5.1.0-SNAPSHOT and now I am getting
>> following error. What could be the issue. ?
>>
>> [2016-04-08 17:24:26,865]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>> Startup component netty-transports-mgt from
>> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
>> state until Capability
>> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
>> from bundle(msf4j-core:1.0.0) is available
>> [2016-04-08 17:24:26,866]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>> Startup component netty-transports-mgt from
>> bundle(org.wso2.carbon.transport.http.netty:1.0.0) will be in the pending
>> state until Capability
>> org.wso2.carbon.transport.http.netty.listener.CarbonNettyServerInitializer
>> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>> [2016-04-08 17:24:26,866]  WARN
>> {org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver} -
>> Startup component carbon-transport-mgt from
>> bundle(org.wso2.carbon.core:5.1.0.SNAPSHOT) will be in the pending state
>> until Capability
>> org.wso2.carbon.transport.http.netty.internal.NettyTransportServiceComponent
>> from bundle(org.wso2.carbon.transport.http.netty:1.0.0) is available
>>
>>
>> Thanks,
>> Hasitha.
>>
>> On Thu, Apr 7, 2016 at 6:57 PM, Rasika Perera  wrote:
>>
>>> Hi Himasha,
>>>
>>> This usually happens when MSF4J is waiting for its required
>>> capabilities. MSF4J has cardinality of AT_LEAST_ONE as required
>>> capabilities for the Carbon Transport. Which means server is waiting on
>>> the startup for at least one OSGi service implementing
>>> CarbonTransport.class interface[1]. As Aruna mentioned can you verify
>>> whether you are packing carbon transport.
>>>
>>> However one issue found on your pom file.
>>>
>>> 
>>> org.wso2.carbon.bpmn.rest.**,*
>>> version=${carbon.business-process.exp.pkg.version},
>>> 
>>>
>>> should be corrected as;
>>>
>>> 
>>> org.wso2.carbon.bpmn.rest.**;*
>>> version=${carbon.business-process.exp.pkg.version},
>>> 
>>>
>>> [1]
>>> https://github.com/wso2/msf4j/blob/master/core/src/main/java/org/wso2/msf4j/internal/MicroservicesServerSC.java#L74
>>>
>>> Thanks
>>> ~Rasika
>>>
>>>
>>> On Thu, Apr 7, 2016 at 2:47 PM, Aruna Karunarathna 
>>> wrote:
>>>
 Have you guys added the carbon-transport-mgt?

 On Thu, Apr 7, 2016 at 1:57 PM, Hasitha Aravinda 
 wrote:

> Hi Manu,
>
> were you able to solve this issue, I am getting the same error.
>
> Thanks,
> Hasitha.
>
> On Wed, Feb 10, 2016 at 1:42 PM, Manuranga Perera 
> wrote:
>
>> MSS product hangs when I deploy my service, but fat-jar mode works.
>>
>> prints
>> Waiting on pending capability registration. Capability:
>> org.wso2.msf4j.Interceptor
>>
>> how to proceed debugging?
>> --
>> With regards,
>> *Manu*ranga Perera.
>>
>> phone : 071 7 70 20 50
>> mail : m...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Hasitha Aravinda,
> Senior Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Aruna Sujith Karunarathna *
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com | Web: www.wso2.com


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


>>>
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> M: +94 71 680 9060 E: rasi...@wso2.com
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Senior Software Engineer,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>
>
>
> --
> --
> 

Re: [Dev] Handling Kubernetes Specific Configurations in Puppet/Hiera

[Imesh Gunaratne]

On Tue, Apr 12, 2016 at 11:48 PM, Chamila De Alwis 
wrote:

> Hi,
>
> To continue the earlier concern to copy all the files inside
> `repository/components/lib` folder without specifying their filenames in
> the Hiera YAML, I think that would cause problems when multiple profiles
> and platforms are provisioned. For example we don't need Kubernetes
> Membership Scheme JAR file for a non-clustered setup, but we can't delete
> that from Puppet either, because it has to support provisioning for
> container image run on Kubernetes as well.
>

Yes it make sense, we would need to specifically mention the file list in
each platform/profile!

Thanks

>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Tue, Apr 12, 2016 at 11:40 PM, Chamila De Alwis 
> wrote:
>
>>
>> On Tue, Apr 12, 2016 at 11:01 PM, Imesh Gunaratne  wrote:
>>
>>> Looks good! Regarding the "iaas" folder, shall we rename it to default
>>> and remove the files under product/profile/?
>>>
>>
>> +1.
>>
>> I renamed this to `default`. `default` platform will contain all the
>> common data that will be overriden in other platforms. Now the
>> Hiera hierarchy looks like the following.
>>
>> [image: Inline image 1]
>>
>> Data such as pack filename will not have to be duplicated in all the
>> platforms, as it will  be found when the lookup reaches
>> `"wso2/%{::product_name}/%{::product_version}/default/%{::product_profile}"`
>> or `"wso2/%{::product_name}/%{::product_version}/default/default"` level.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>


-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.io
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to exchange a SAML2 bearer token with OAuth2 token

[Gonzalo Valencia]

As far as I remember you need to split the headers in the curl command:
curl -k -d 
"grant_type=urn:ietf:params:oauth:grant-type:saml2-bearer=[...]=PRODUCTION" 
-H "Authorization: Basic 
VWhXczlIN2xPaTlOMGJZM1pfdUswVW41OU93YTpKcTdMNFdzZHg5SER3TGx3TnVERVkxdVl4UUFh" 
-H "Content-Type: application/x-www-form-urlencoded" 
https://localhost:8243/token


El 18/04/2016 a las 4:22, Geesara Prathap escribió:

Hi All,

As an example, I enabled SSO in Dashboard Server and registered the 
portal app with the Identity Server by creating a service provider. So 
I was able to get SAML bearer assertion in SAML response. Then created 
an application in API Manager and  combined the consumer key and 
consumer secret keys as consumer-key:consumer-secret then encoded the 
combined string using base64. After that filtered out SAML bearer 
assertion from SAML response and encoded into base64-URL.


SAML  bearer assertion

IssueInstant="2016-04-17T15:31:00.991Z" Version="2.0" 
xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion">Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity">localhostxmlns:ds="http://www.w3.org/2000/09/xmldsig#;>Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>URI="#iddkjncialbbnlpfjhmkjhebojbpkhfppjglhfga">Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>fk3OExA6WC93w7o7ckZudmP4N3Q=UJyh3pYatemvZVMnLM0CZKb3HWWeCGD2AXJtY+zme4cQXNVtzi+ugHW0dHz+ZbpUykPFdCspYA1K1g/15x4yEH2MY6zPACvqVcfxEgqcrlDVTUSTeKtr+8+4zoYBtJb0usSEui+22vpzlEv3f++7eVAFwWLDODS0QPChpF39hxs7s1l+9zBR4rciSh5hQW5n/Ww56dgS1pzn4DY+slIdBCme7fSRozVEhiihotqEZ+Oa7CSvSZzPycDLEFXfeJDmRp+JD1vE9KIoygHtOr3BFL9H1RIXm+3rO7128XChPL2ZP1zfwBfwmGzRb7mC2iPXw3TTV9pcl9HzQJLFtiyywnFcN0kAbkY0N3mJQgARDbCKf4v2zG7x4MqXroPYAishe3bStkwgkO63xGiMI4XhaQCMGCcQB6TDVpvd7bb9zyYPyXMrqBLMQg4X6jZTOgpRfEUyQEItquEjvjRyV0yPgO9ULBUK5qhmZYOVn5ef7c8kk/ceh4diVoOFdyuYdw7KmLw3RjFgxMzbm8QOyfwhn0f75wiDt7ctokpRSwf3PBkIP7al6cEs3d6aHM9N94NY5ZGSHij+fV5dRZieZMv3zkYcEj90o8eRJk8nDgO5zpo40k/mbfWnAkpEwXdGyMFnK6CWW6oPGbY0qnoLPio4gytdEW+DBIdK+lTFbyzhafM=MIIFkzCCA3sCBAKkVfcwDQYJKoZIhvcNAQEFBQAwgY0xCzAJBgNVBAYTAlNMMRAwDgYDVQQIEwdXZXN0ZXJuMRAwDgYDVQQHEwdDb2xvbWJvMQ0wCwYDVQQKEwRXU08yMRQwEgYDVQQLEwtFbmdpbmVlcmluZzESMBAGA1UEAxMJbG9jYWxob3N0MSEwHwYJKoZIhvcNAQkBFhJpb3RzZXJ2ZXJAd3NvMi5jb20wHhcNMTUxMjE3MTMxMTA0WhcNMTcxMjE2MTMxMTA0WjCBjTELMAkGA1UEBhMCU0wxEDAOBgNVBAgTB1dlc3Rlcm4xEDAOBgNVBAcTB0NvbG9tYm8xDTALBgNVBAoTBFdTTzIxFDASBgNVBAsTC0VuZ2luZWVyaW5nMRIwEAYDVQQDEwlsb2NhbGhvc3QxITAfBgkqhkiG9w0BCQEWEmlvdHNlcnZlckB3c28yLmNvbTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBALkiGVQ9tZOKIi/gD/toV+enq+neqOBGYQ8Fq/ABOWnK2QpGWm81+Rets5GbQ6W//D8C5TOBGqK7z+LAgdmILr1XLkvrXWoan0GPdDJ1wpc2/6XDZvM5f7Y8cmRqVPJv7AF+ImgF9dqv97gYCiujy+nNHd5Nk/60pco2LBV5SyLqqrzKXEnSGrS4zoYWpPeJ9YrXPEkW7A6AxTQK0yU9Ej4TktgafbTueythrLomKiZJj4wPxm2lA2lAZscDdws9NWrI5z/LUVLbUMxrY10Nig1liX5b1mrUk5bb1d2tqwkPrpRILKoOBJtI674SQS3GziiUiCJGIO/EGGRn1AJsC/SvnnEez3WKY/DgJ6102MWK/yWtY8NYHUX2anwMBS7UpT5A4BXdsfBz3R+iPF99FxdAGGsS4GQuuPocZaycLqoPCxpTSSxBsKMUcKpn3yaiQRd6uDuiTNt7odDOQj0Tno7uokh/HILgbzvj9EExDOsdwLVvqYmUHBPeLmiICWXfi4kyH/twPOZtV9eVnfWYx5Kwg+2Y4fIb3q4ABr0hzxaMYHQo6NOukSH1BcdAWiQIXbSFFaTZD8p6OfiZpHcQ59HT/Z8GBlCFL2xkYJFmOhXI/Cu+xrcwqEIInv7d8w3eiNQ7MneomEptLbBk9+kMsP0ubo34oOGHR9qk3Lj580c/AgMBAAEwDQYJKoZIhvcNAQEFBQADggIBADw70g2/wrgzrAM8OXBlthGbCEaXZpKwq9IJN0qu+/l+PNwF7csQhj+qW+zMrWaH1DGWJroaei1+NFFrj/pvp61rF/ZeTPGVJd7puCq++SevqIrzKyAEBtwtpXmcFhBpV/FrQAv3ODOJ3bN2wSRPZHUvARTBB3RaUI06g1jCaBzjDEGoMfSxdr5/Ty2WxTI9u9RlIs3Q52AiOmROtLPiEQZQIqfNO3cxCEWojHxPqVEZA/kQYy+rryj4H0zzSrj7QFlQhsMDw5j8bv9AcvTEGmwp29avsgnceDWinI6lwtd8zqh0ZW9QJdH0BRNCM/EkTlTUHeEg04/sOgOrlWcvEfVxDqNEtbUzU9UFxl0lkQkuRn1UdxZlvhWaFnel5iRC9b7OZvi2mkVujLyxEWlJB1tuyMLQxu6PfabBVODP5V8/+uyiiK/gwrB5rYl8RHxGoznJnI1Y3HVzKlA849CrMBaY5vnhE03cNja7QroPzLmmuXBLk2LbI1lu5nJAqKpBUPMI/IU3pF4Q7VTD2ZANI+ktGgGlM8AK4OJHWOhj8W289pWTHVjG8syPLTsaYkhgLjzZl/g9cUwn/96NJNvzd3dkT+7VgE+BJOLofq25CjZcN1M7MhWdl3vbWNj9vzL0+FCnwca8UecfvFS39PIekIvqbtP+Gw8NiYOUGIllZ0JHFormat="urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress">admin@carbon.superMethod="urn:oasis:names:tc:SAML:2.0:cm:bearer">InResponseTo="ghmnopmcckmfdgkbncdbfaddoablkleedohalfib" 
NotOnOrAfter="2016-04-17T15:36:00.991Z" 
Recipient="https://localhost:9443/portal/acs"/>Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">InResponseTo="ghmnopmcckmfdgkbncdbfaddoablkleedohalfib" 
NotOnOrAfter="2016-04-17T15:36:00.991Z" 
Recipient="https://localhost:9443/oauth2/token"/>NotBefore="2016-04-17T15:31:00.991Z" 
NotOnOrAfter="2016-04-17T15:36:00.991Z">portalhttps://localhost:9443/oauth2/tokencarbonServerAuthnInstant="2016-04-17T15:31:00.992Z" 
SessionIndex="2211a42e-d554-4e94-a59a-5269b920a3e7">urn:oasis:names:tc:SAML:2.0:ac:classes:Password



To exchange the SAML2 bearer token for an OAuth2.0 access token, this 
is the command I used.


curl -k -d 

Re: [Dev] Cannot generate P2 metadata: P2 publisher return code was 13

[Niranjan Karunanandham]

Hi Damith,

As mentioned in [1], this issue happens when the certificates are not
trusted by the Oracle VM. A similar issue was mentioned in [2] and it was
sorted.

[1] - https://bugs.eclipse.org/bugs/show_bug.cgi?id=309059
[2] - http://mail.wso2.org/mailarchive/dev/2014-November/039182.html

Regards,
Nira


On Mon, Apr 18, 2016 at 10:30 AM, Damith Wickramasinghe 
wrote:

> Hi Lasantha,
>
> I have checked the log file. It does not have any information other than
> the same thing mention in the above log One or more certificates rejected.
> Cannot proceed with installation. After installing the Java again solved
> the issue.
>
> Regards,
> Damith.
>
>
> On Mon, Apr 18, 2016 at 8:12 AM, Lasantha Fernando 
> wrote:
>
>> Hi Damith,
>>
>> Were you able to get any more information from the log file mentioned in
>> the above stack trace?
>>
>> log file location: /home/damith/.m2/repository/
>> org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/
>> configuration/1460895093502.log
>>
>> Can you post any error information in that log file as well?
>>
>> Thanks,
>> Lasantha
>>
>> On 17 April 2016 at 22:47, Damith Wickramasinghe 
>> wrote:
>>
>>> Hi Mohan,
>>>
>>> Maven version is 3.0.5. and java is 1.7 .Following is the complete trace
>>> i got.
>>>
>>>  Command line:
>>> /bin/sh -c cd
>>> /home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen
>>> && /usr/lib/jvm/java-7-oracle/jre/bin/java -jar
>>> /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/plugins/org.eclipse.equinox.launcher_1.2.0.v20110725-1610.jar
>>> -nosplash -application org.eclipse.equinox.p2.director -metadataRepository
>>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
>>> -artifactRepository
>>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/p2-repo
>>> -installIU carbon.product.id -profileProperties
>>> org.eclipse.update.install.features=true -profile worker -bundlepool
>>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components
>>> -shared
>>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/p2
>>> -destination
>>> file:/home/damith/java/wso2-repos/latestCep/product-cep/modules/p2-profile-gen/target/wso2carbon-core-4.4.3/repository/components/worker
>>> -p2.os linux -p2.ws gtk -p2.arch x86 -roaming
>>> Installing carbon.product.id 4.4.3.
>>> Installation failed.
>>> One or more certificates rejected. Cannot proceed with installation.
>>> Application failed, log file location:
>>> /home/damith/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1460895093502.log
>>>
>>> [INFO]
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] WSO2 CEP - Parent . SUCCESS
>>> [0.972s]
>>> [INFO] WSO2 CEP - Style Parent ... SUCCESS
>>> [0.040s]
>>> [INFO] WSO2 CEP - Styles . SUCCESS
>>> [1.216s]
>>> [INFO] WSO2 Stratos CEP - Styles . SUCCESS
>>> [0.185s]
>>> [INFO] WSO2 CEP - Samples Parent . SUCCESS
>>> [0.023s]
>>> [INFO] WSO2 CEP - Samples Producers .. SUCCESS
>>> [0.046s]
>>> [INFO] WSO2 CEP - Producer - WSO2 Event Client ... SUCCESS
>>> [8.591s]
>>> [INFO] WSO2 CEP - Publisher - HTTP Client  SUCCESS
>>> [0.336s]
>>> [INFO] WSO2 CEP - Publisher - JMS Client . SUCCESS
>>> [2.722s]
>>> [INFO] WSO2 CEP - Publisher - MQTT Client  SUCCESS
>>> [0.171s]
>>> [INFO] WSO2 CEP - Publisher - Kafka Client ... SUCCESS
>>> [11.891s]
>>> [INFO] WSO2 CEP - Publisher - SOAP Client  SUCCESS
>>> [0.551s]
>>> [INFO] WSO2 CEP - Producer - Websocket Publisher . SUCCESS
>>> [4.295s]
>>> [INFO] WSO2 CEP - Producer - Performance Test  SUCCESS
>>> [0.475s]
>>> [INFO] WSO2 CEP - Publisher - HTTP Performance Client  SUCCESS
>>> [0.166s]
>>> [INFO] WSO2 CEP - Publisher - Kafka Producer . SUCCESS
>>> [0.174s]
>>> [INFO] WSO2 CEP - Publisher - JMS Performance Client . SUCCESS
>>> [0.150s]
>>> [INFO] WSO2 CEP - Sample Consumers ... SUCCESS
>>> [0.035s]
>>> [INFO] WSO2 CEP - Consumer - WSO2 Event Server ... SUCCESS
>>> [1.061s]
>>> [INFO] WSO2 CEP - Consumer - JMS Consumer  SUCCESS
>>> [0.145s]
>>> [INFO] WSO2 CEP - Consumer - MQTT Consumer ... SUCCESS
>>> [0.103s]
>>> [INFO] WSO2 CEP - Consumer - Axis2 Log Service ... SUCCESS
>>> [0.090s]
>>> [INFO] WSO2 CEP - Consumer - Generic Log Service . SUCCESS
>>> [1.271s]
>>> [INFO] WSO2 CEP - Consumer - Dashboard Service ... SUCCESS
>>> [0.117s]
>>> [INFO] 

Re: [Dev] ESB Analytics - Verifying the common production use cases

[Supun Sethunga]

Hi Kasun,

We ran several rounds of load tests for ESB analytics (covering few
scenarios with several proxy services, APIs, Sequences, etc). In the first
round, we ran the tests with a low TPS (around 10-15) to test and validate
the use cases, such as the counts, delays, drilling down to
mediator/sequence/message level, etc. These scenarios worked as expected.

On the second round, we ran the same tests with a higher TPS (gradually
increasing). In the process, we identified a bottleneck at the DB level
under a high TPS (TPS of over 50, which is not that high), resulting the
stat generation to be slowed down with time. This occurs as DAS is both
reading and writing from/to the same table (row events) at the same time,
at a rapid rate, causing the IO operations to be slowed down (due to table
locks and etc.), and hence the summarizing process takes longer time, in
each iteration. (most of the consumed time for summarizing, around 80% is
taken for reading the raw data and store them as event-wise data in DB)
Therefore, we are currently doing an enhancement to improve performance, by
summarizing the data (summarize up to per-second info) on the fly with
siddhi and store it, rather than spark doing it as a batch operation. This
should eliminate roughly around 80% (above mentioned) of time taken to
read/write row data from DB.

Will give an update after re-running the load test with this enhancement.

Regards,
Supun

On Mon, Apr 18, 2016 at 11:40 AM, Kasun Indrasiri  wrote:

> Any updates on this?
>
> We must test the ESB analytics/ ESB 5 alpha release with the common
> production use cases + high load.
>
> On Mon, Mar 28, 2016 at 2:38 PM, Buddhima Wijeweera 
> wrote:
>
>> Hi All,
>>
>> We are currently in the process of testing statistics & tracing for
>> various scenarios.
>> Initially we planned to cover on the areas we have identified for
>> functionality testing.
>> Then we planned to move on to common scenarios, and performance testing
>> as well.
>>
>> Thank you,
>>
>> On Mon, Mar 28, 2016 at 2:34 PM, Srinath Perera  wrote:
>>
>>> Please run ESB benchmark, get the events comes out of it to DAS, and use
>>> that for testing.
>>>
>>> --Srinath
>>>
>>> On Mon, Mar 28, 2016 at 10:02 AM, Kasun Indrasiri 
>>> wrote:
>>>
 Hi Buddhima/VirajS,

 Once the end to end functionalities are implemented on the ESB
 analytics side, can we start testing the current implementation for
 production use cases of ESB. Basically we need to cover all the common
 integration scenarios and stress test the implemented with high load too.

 Thanks,
 Kasun

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

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

>>>
>>>
>>>
>>> --
>>> 
>>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
>>> Site: http://home.apache.org/~hemapani/
>>> Photos: http://www.flickr.com/photos/hemapani/
>>> Phone: 0772360902
>>>
>>
>>
>>
>> --
>> 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
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
*Supun Sethunga*
Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements

[Sohani Weerasinghe]

Hi All,

As per the offline discussion we had, xsi:type can be supported in the JSON
schema as described below

123
ABC


xsi:type can be added to a newly introduced json array called
"elementIdentifiers" and the value will be appended to to the field name in
the schema as shown below

{
"$schema": "http://json-schema.org/draft-04/schema#;,
"title": "person",
"id": "http://wso2jsonschema.org;,
"type": "object",
"properties": {
"firstName": {
"id": "http://wso2jsonschema.org/firstName;,
"type": "string"
},
"*address,xsi:type=ipo:UKAddress"*: {
 "id": "
http://wso2jsonschema.org/phone;,
"type": "object",
"value":{
"type": "number"
},

"properties": {
"city": {
"id": "http://wso2jsonschema.org/address/city;,
"type": "string"
}
},
"attributes": {
"postalcode": {
"id": "http://wso2jsonschema.org/address/postalcode;,
"type": "string"
}
}
}
},
*"elementIdentifiers": [{*
* "type": "xsi:type"*
* }]*
}

@Nuwan : Feel free to add things we've discussed if I've missed anything

Thanks,
Sohani


Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine

On Mon, Apr 11, 2016 at 11:57 AM, Sohani Weerasinghe 
wrote:

> Correction : This shouldn't add for the root level.
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Mon, Apr 11, 2016 at 11:32 AM, Sohani Weerasinghe 
> wrote:
>
>> Thanks Viraj.
>>
>> I think this should be applied to the root level as well.
>>
>> {
>> "$schema": "http://json-schema.org/draft-04/schema#;,
>> "title": "person",
>>* "value"{*
>> * "id": "http://wso2jsonschema.org
>> ",*
>> * "type": "object*
>> *},*
>> "properties": {
>> "firstName": {
>> "id": "http://wso2jsonschema.org/firstName;,
>> "type": "string"
>> },
>> "phone": {
>> "id": "http://wso2jsonschema.org/phone;,
>> "type": "array",
>> "items": [{
>> *  “value”:{*
>> *   "id":
>> "http://wso2jsonschema.org/phone/phone
>> ",*
>> *   "type": "number"*
>> *},*
>> "attributes": {
>> "primary": {
>> "id": "http://wso2jsonschema.org/phone/primary;,
>> "type": "boolean"
>> }
>> }
>> }]
>> }
>> }
>> }
>>
>>
>>
>>
>>
>>
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Ok.  For an xml like below, let's have the value field as follows
>>>
>>> 
>>>
>>>xyz
>>>
>>>071655339
>>>
>>>0112655333 
>>> 
>>>
>>> {
>>>
>>> "$schema": "http://json-schema.org/draft-04/schema#;,
>>>
>>> "title": "person",
>>>
>>> "id": "http://wso2jsonschema.org;,
>>>
>>> "type": "object",
>>>
>>> "properties": {
>>>
>>> "firstName": {
>>>
>>> "id": "http://wso2jsonschema.org/firstName;,
>>>
>>> "type": "string"
>>>
>>> },
>>>
>>> "phone": {
>>>
>>> "id": "http://wso2jsonschema.org/phone;,
>>>
>>> "type": "array",
>>>
>>> "items": [{
>>>
>>> * “value”:{*
>>>
>>> * "id": "http://wso2jsonschema.org/phone/phone
>>> ",*
>>>
>>> * "type": "number"*
>>>
>>> * },*
>>>
>>> "attributes": {
>>>
>>> "primary": {
>>>
>>> "id": "http://wso2jsonschema.org/phone/primary;,
>>>
>>> "type": "boolean"
>>>
>>> }
>>>
>>> }
>>>
>>> }]
>>>
>>> }
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Mon, Apr 11, 2016 at 11:05 AM, Nuwan Pallewela 
>>> wrote:
>>>
 Hi Sohani,

 +1 for the above approaches.

 We have to decide on how to represent non identical elements with same
 name. Viraj is working on it.

 Thanks,
 Nuwan

 On Mon, Apr 11, 2016 at 10:44 AM, Sohani Weerasinghe 
 wrote:

> Hi Viraj/Nuwan,
>
> Really appreciate your input on this
>
> Thanks,
> Sohani
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Tue, Apr 5, 2016 at 12:06 PM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> This is regarding clarifying the $subject.
>>
>> If we consider an xml as below, we are 

Re: [Dev] Fwd: [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' & 'No-Encryption' states via Device Info

[Dilshan Edirisuriya]

Checked the doc and didnt come across such features in the doc. Will check
more.

Regards,

Dilshan

On Fri, Apr 15, 2016 at 6:32 AM, Dilan Udara Ariyaratne 
wrote:

> Hi Dilshan / Inosh,
>
> Any update from iOS side?
>
> Thanks,
> Dilan.
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Fri, Apr 8, 2016 at 10:41 AM, Hasunie Adikari  wrote:
>
>> Hi Dilan,
>>
>> Passcode state and encryption state can be retrieved from windows device
>> also.We have already taken those information while applying passcode
>> related policies to the device.
>>
>> On Thu, Apr 7, 2016 at 6:31 PM, Kasun Dananjaya Delgolla > > wrote:
>>
>>> Hi Dilan,
>>>
>>> It's possible on android. We can simply check it via device policy
>>> manager and attach it to device info payload. Also it should be possible on
>>> iOS. But we will have to check on Windows. @Hasunie - Any input on this?
>>>
>>> Thanks
>>> On Apr 7, 2016 6:27 PM, "Dilan Udara Ariyaratne" 
>>> wrote:
>>>
 Adding KasunD, Milan, InoshP, Dilshan and Hasunie to the thread...

 *Dilan U. Ariyaratne*
 Software Engineer
 WSO2 Inc. 
 Mobile: +94766405580 <%2B94766405580>
 lean . enterprise . middleware


 -- Forwarded message --
 From: Dilan Udara Ariyaratne 
 Date: Thu, Apr 7, 2016 at 6:23 PM
 Subject: [Dev] [EMM 2.1.0] [Device Analytics] Obtaining 'No-Passcode' &
 'No-Encryption' states via Device Info
 To: WSO2 Developers' List 


 Hi Folks,

 Is there currently any possibility of retrieving the following states
 via device-info capturing task of EMM for all mobile platforms, i.e.
 Android, iOS and Windows ?

 [1] No-Passcode state - This could carry the value of either true or
 false and express whether the device is currently having a passcode or not
 [2] No-Encryption state - This could also carry the value of either
 true or false and express whether the device data is currently encrypted or
 not

 If we can obtain these data, there lies the possibility of showing
 related analytics (See Following Figure) on Device Dashboard page for EMM
 administrators
 which is currently considered as a useful requirement.




 Thanks.

 *Dilan U. Ariyaratne*
 Software Engineer
 WSO2 Inc. 
 Mobile: +94766405580 <%2B94766405580>
 lean . enterprise . middleware



>>
>>
>> --
>> *Hasunie Adikari*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>> blog http://hasuniea.blogspot.com
>> Mobile:+94715139495
>>
>
>


-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2
Mob: + 94 777878905
http://wso2.com/
https://www.linkedin.com/profile/view?id=50486426
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Include carbon.yml and other config files in Carbon Core feature

[Niranjan Karunanandham]

Hi all,

Below is the current C5 source code structure:

| -- archetypes
| -- base
| -- core
| -- distribution (contains the conf files which are copied to the
distribution via the bin.xml)
| -- features

| -- org.wso2.carbon.core.runtime.feature
| -- org.wso2.carbon.core.server.feature

| -- launcher
| -- parent (parent pom)
| -- tests
| -- tools (Bundle Generator)


Any particular reason as to why we have separate folder for each component
such as launcher, tools, core and base? Can we move these to a folder
called component since these are packed with the kernel and have the source
code structure as below:

| -- archetypes
| -- components

| -- base
| -- core
| -- launcher
| -- tools (Bundle Generator)

| -- distribution (contains the conf files which are copied to the
distribution via the bin.xml)
| -- features

| -- org.wso2.carbon.core.runtime.feature
| -- org.wso2.carbon.core.server.feature

| -- parent (parent pom)
| -- tests


In-addition shall we bundle these components with a feature (either new say
launcher feature or existing) and have its corresponding configuration
files (including scripts like carbon.sh, if present) packed in the feature.
In this case, we will not need to copy these config files via the bin.xml.
In addition to this, other products will obtain these files when they
install the feature without having to keep copy of this file in their
distribution source code.

WDYT?

Regards,
Nira


On Mon, Apr 11, 2016 at 9:57 AM, Niranjan Karunanandham 
wrote:

> Hi all,
>
> i have created a JIRA [1] for this. Along with the conf folder, shall we
> include* bin folder* (in the distribution/carbon-home) as well into
> org.wso2.carbon.core.server.feature? WDYT?
>
> [1] - https://wso2.org/jira/browse/CARBON-15851
>
> Regards,
> Nira
>
> On Tue, Apr 5, 2016 at 3:45 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>> On Tue, Apr 5, 2016 at 3:32 PM, Niranjan Karunanandham > > wrote:
>>
>>> Hi Kishanthan,
>>>
>>> On Tue, Apr 5, 2016 at 3:23 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 +1

 Also by default, we need to have place holders for name, id and version
 properties rather than having hard coded values. The product team can then
 put their relevant values at build time. Let's add this also along with
 this change.

>>> By default shall we have the above values as empty in the carbon.yml. If
>>> it is not defined pick it up from System properties (using the place holder
>>> carbon.name, carbon.id and carbon.version for name, id and version
>>> respectively). If both are not define then get the values from a Constant.
>>> WDYT?
>>>
>>
>> IMO, let's have it like this.
>>
>> id: ${server.key}
>> name: ${server.name}
>> version: ${server.version}
>>
>> If no value is set for this under system property or env property, we
>> should use the default values which comes from the configuration bean. The
>> product team can use their own values when building a product.
>>
>>
>>>


 On Tue, Apr 5, 2016 at 3:14 PM, Aruna Karunarathna 
 wrote:

> On Fri, Apr 1, 2016 at 2:31 PM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> In Carbon 5, the carbon.yml, log4j2.xml and etc., are in the
>> distribution folder and copied to the distribution pack via bin.xml. Why
>> don't we add these configuration files to Carbon Server Feature
>> (org.wso2.carbon.core.server.feature) which are copied to the packed when
>> the feature is installed. WDYT?
>>
>> +1. we should bring the configurations also when we install the core
> feature.
>
> Regards,
>> Nira
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



 --
 *Kishanthan Thangarajah*
 Associate Technical Lead,
 Platform Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com
 *
 Twitter - *http://twitter.com/kishanthan
 *

>>>
>>>
>>> Regards,
>>> Nira
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>
>>
>>
>> --
>> *Kishanthan Thangarajah*
>> Associate Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - 

Re: [Dev] ESB Analytics - Verifying the common production use cases

[Kasun Indrasiri]

Any updates on this?

We must test the ESB analytics/ ESB 5 alpha release with the common
production use cases + high load.

On Mon, Mar 28, 2016 at 2:38 PM, Buddhima Wijeweera 
wrote:

> Hi All,
>
> We are currently in the process of testing statistics & tracing for
> various scenarios.
> Initially we planned to cover on the areas we have identified for
> functionality testing.
> Then we planned to move on to common scenarios, and performance testing as
> well.
>
> Thank you,
>
> On Mon, Mar 28, 2016 at 2:34 PM, Srinath Perera  wrote:
>
>> Please run ESB benchmark, get the events comes out of it to DAS, and use
>> that for testing.
>>
>> --Srinath
>>
>> On Mon, Mar 28, 2016 at 10:02 AM, Kasun Indrasiri  wrote:
>>
>>> Hi Buddhima/VirajS,
>>>
>>> Once the end to end functionalities are implemented on the ESB analytics
>>> side, can we start testing the current implementation for production use
>>> cases of ESB. Basically we need to cover all the common integration
>>> scenarios and stress test the implemented with high load too.
>>>
>>> Thanks,
>>> Kasun
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>> 
>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
>> Site: http://home.apache.org/~hemapani/
>> Photos: http://www.flickr.com/photos/hemapani/
>> Phone: 0772360902
>>
>
>
>
> --
> 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
>



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

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev