Re: [Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

[Gayan Gunarathne]

I think we need to consider other Databases (Oracle,PostgreSQL etc) also.

Default[1] set up also we have hard corded to the h2 database. Better if we
support the other set of databases here also.Based on the database we used
we can set the appropriate DB driver with hiera.

[1]
https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/default.yaml#L101

Thanks,
Gayan

On Sat, Apr 23, 2016 at 8:25 AM, Imesh Gunaratne  wrote:

> Hi Devs,
>
> How do we manage $subject in Puppet provisioning for Kubernetes?
>
> I can see that in API-M we have defined MySQL connector JAR [1] and data
> sources but not in others. We have also hard coded MySQL host IP [2] in
> API-M profile yaml files.
>
> [1]
> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/api-key-manager.yaml#L36
> [2]
> https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/api-key-manager.yaml#L48
>
> Thanks
>
> --
> *Imesh Gunaratne*
> Senior Technical Lead
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: http://imesh.io TW: @imesh
> Lean . Enterprise . Middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Dockerfiles] Managing Data Sources & JDBC Driver in Distributed Deployments

[Imesh Gunaratne]

Hi Devs,

How do we manage $subject in Puppet provisioning for Kubernetes?

I can see that in API-M we have defined MySQL connector JAR [1] and data
sources but not in others. We have also hard coded MySQL host IP [2] in
API-M profile yaml files.

[1]
https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/api-key-manager.yaml#L36
[2]
https://github.com/wso2/puppet-modules/blob/master/hieradata/dev/wso2/wso2am/1.10.0/kubernetes/api-key-manager.yaml#L48

Thanks

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

Re: [Dev] [ESB] API/Proxy to consult LDAP through ESB

[Willian Antunes]

Chanaka, thank you very much for your tip!

I have an issue during the execution time and I believe that the connector
maybe has a problem with its parameters for ldap.init
.
During the execution of this component an error is gotten by the fault flow:

[2016-04-22 18:08:24,089] INFO - LogMediator To: /SampleContextLdapContext,
MessageID: urn:uuid:bd9a9e05-84eb-48d9-8cef-6eff06b6f64d, Direction:
request, DEUPAU = An error has been gotten, messageFaultError = Error
occured in the mediation of the class mediator, messageFaultCode = 0,
messageFaultException = , messageFaultDetail =
org.apache.synapse.SynapseException: Error occured in the mediation of the
class mediator at
org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:82)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.template.TemplateMediator.mediate(TemplateMediator.java:97)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:129)
at
org.apache.synapse.mediators.template.InvokeMediator.mediate(InvokeMediator.java:78)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.rest.Resource.process(Resource.java:297) at
org.apache.synapse.rest.API.process(API.java:378) at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:65)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
at
org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
at
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:363)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
java.lang.Thread.run(Unknown Source) Caused by:
java.lang.NullPointerException at java.util.Hashtable.put(Unknown Source) *
at
org.wso2.carbon.connector.ldap.Authenticate.connect(Authenticate.java:55)*
at
org.wso2.carbon.connector.core.AbstractConnector.mediate(AbstractConnector.java:32)
at
org.apache.synapse.mediators.ext.ClassMediator.mediate(ClassMediator.java:78)
... 22 more





asd

It seems that I missed some parameter. Look at line 55 in the GitHub

and
now on a part of my XML:

http://ws.apache.org/ns/synapse;>
  

  


  
  
<*providerUrl*>ldap://192.168.2.10:389/
<*securityPrincipal*>aqlbras\willian
<*securityCredentials*>SamplePassword
  

When I don't configure *providerUrl *the error occurs at line 54, it means
that the name parameter is correct for this tag but it's incorrect for
securityPrincipal tag (you can see in GitHub

to
make sure).

Have you ever tested it or I am missing something?

Thank you for your attention again!

On Thu, Apr 21, 2016 at 10:55 PM, Chanaka Fernando 
wrote:

> Hi William,
>
> You don't need do such hard things.
>
> 1. Create a REST API in WSO2 ESB to accept the request payload with your
> preferred path. You can refer [1] for REST support in ESB.
>
> 2. Use the LDAP connector available in WSO2 connector store at [2] to
> communicate with your LDAP.
>
> That's all you need to do. No custom code, No WSO2 AS involvement.
>
> [1]
> http://wso2.com/library/articles/2013/12/restful-integration-with-wso2-esb/
>
> [2]
> https://store.wso2.com/store/assets/esbconnector/6e86496f-431e-43e2-bded-caedd10c4cb9
>
> Cheers,
> Chanaka
>
> On Fri, Apr 22, 2016 at 5:14 AM, Willian Antunes <
> willian.lima.antu...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I'm used to work with Apache Camel and I'm new with WSO2 solutions. I
>> have the following requirement:
>>
>> *- Create a rest web service which receives an username and password.*

Re: [Dev] P2 profile fails in MDM

[Niranjan Karunanandham]

Hi Lakshman,

AFAIU, this is because of the import range defined in for axiom in
carbon-commons and is fixed in carbon-commons version 4.4.9 and 4.5.1 [1].
The carbon-commons version defined in carbon identity is 4.4.8. Can you
manually try upgrading it to 4.4.9 / 4.5.1, build it locally and testing
it.

Btw it advice-able to upgrade to a released version of the carbon-identity
since SNAPSHOT version can change after it is released and this can cause
your build to break.


[1] : Mail Subject: [Kernel 4.4.4 release] Releasing downstream projects of
wso2-axiom

Regards,
Nira

On Fri, Apr 22, 2016 at 11:37 PM, Lakshman Udayakantha 
wrote:

> Hi,
>
> When version upgrading in MDM, I got below error,
>
> Installing org.wso2.carbon.core.common.feature.group 4.4.5.
> Installation failed.
> Cannot complete the install because one or more required items could not
> be found.
>  Software being installed: Identity OAuth Common Feature 5.0.9.SNAPSHOT
> (org.wso2.carbon.identity.oauth.common.feature.group 5.0.9.SNAPSHOT)
>  Missing requirement: org.wso2.carbon.tenant.common 4.4.7
> (org.wso2.carbon.tenant.common 4.4.7) requires 'package
> org.apache.axiom.om [1.2.11.wso2v6,1.3.0)' but it could not be found
>  Missing requirement: org.wso2.carbon.tenant.common 4.4.8
> (org.wso2.carbon.tenant.common 4.4.8) requires 'package
> org.apache.axiom.om [1.2.11.wso2v6,1.3.0)' but it could not be found
>  Cannot satisfy dependency:
>   From: WSO2 Carbon - Identity Core 5.0.9.SNAPSHOT
> (org.wso2.carbon.identity.core 5.0.9.SNAPSHOT)
>   To: package org.wso2.carbon.stratos.common.beans [4.4.0,5.0.0)
>  Cannot satisfy dependency:
>   From: Identity Core Server Feature 5.0.9.SNAPSHOT
> (org.wso2.carbon.identity.core.server.feature.group 5.0.9.SNAPSHOT)
>   To: org.wso2.carbon.identity.core [5.0.9.SNAPSHOT]
>  Cannot satisfy dependency:
>   From: Identity OAuth Common Feature 5.0.9.SNAPSHOT
> (org.wso2.carbon.identity.oauth.common.feature.group 5.0.9.SNAPSHOT)
>   To: org.wso2.carbon.identity.core.server.feature.group
> [5.0.9.SNAPSHOT,6.0.0)
>
> Anyway I have checked the axiom version in p2-repo folder of generated
> target folder of p2 profile gen module and it was 1.2.11.wso2v10 which is
> indeed between [1.2.11.wso2v6,1.3.0) range. then why is this error message?
>
> Thanks
>
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0714388124*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*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

[Dev] P2 profile fails in MDM

[Lakshman Udayakantha]

Hi,

When version upgrading in MDM, I got below error,

Installing org.wso2.carbon.core.common.feature.group 4.4.5.
Installation failed.
Cannot complete the install because one or more required items could not be
found.
 Software being installed: Identity OAuth Common Feature 5.0.9.SNAPSHOT
(org.wso2.carbon.identity.oauth.common.feature.group 5.0.9.SNAPSHOT)
 Missing requirement: org.wso2.carbon.tenant.common 4.4.7
(org.wso2.carbon.tenant.common 4.4.7) requires 'package org.apache.axiom.om
[1.2.11.wso2v6,1.3.0)' but it could not be found
 Missing requirement: org.wso2.carbon.tenant.common 4.4.8
(org.wso2.carbon.tenant.common 4.4.8) requires 'package org.apache.axiom.om
[1.2.11.wso2v6,1.3.0)' but it could not be found
 Cannot satisfy dependency:
  From: WSO2 Carbon - Identity Core 5.0.9.SNAPSHOT
(org.wso2.carbon.identity.core 5.0.9.SNAPSHOT)
  To: package org.wso2.carbon.stratos.common.beans [4.4.0,5.0.0)
 Cannot satisfy dependency:
  From: Identity Core Server Feature 5.0.9.SNAPSHOT
(org.wso2.carbon.identity.core.server.feature.group 5.0.9.SNAPSHOT)
  To: org.wso2.carbon.identity.core [5.0.9.SNAPSHOT]
 Cannot satisfy dependency:
  From: Identity OAuth Common Feature 5.0.9.SNAPSHOT
(org.wso2.carbon.identity.oauth.common.feature.group 5.0.9.SNAPSHOT)
  To: org.wso2.carbon.identity.core.server.feature.group
[5.0.9.SNAPSHOT,6.0.0)

Anyway I have checked the axiom version in p2-repo folder of generated
target folder of p2 profile gen module and it was 1.2.11.wso2v10 which is
indeed between [1.2.11.wso2v6,1.3.0) range. then why is this error message?

Thanks


-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0714388124*
___
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 2

[Chandana Napagoda]

Hi Devs,

Thanks for testing and verifying the WSO2 Governance Registry 5.2.0 RC2. We
are closing this vote now. This vote has passed with 7 +1s and 0 -1s.
Therefore, we are proceeding with the WSO2 Governance Registry 5.2.0
release.

7 +1s
0 -1s

Thank you and Regards,
ES/G-Reg Team

On Fri, Apr 22, 2016 at 7:20 PM, Malintha Fernando 
wrote:

> Hi All,
>
> Tested following scenarios for G-Reg 5.2.0 RC2 pack.
>
> Lifecycle traversal on IE 11
> Mounting the registry DB with mySQL.
> Connection restoration when DB connection lost
> Tenant anonymous diff view
> Tenant anonymous view for new RXT types
>
> [+] stable
>
> Regards,
> Malintha
>
> On Fri, Apr 22, 2016 at 7:15 PM, Prasanna Dangalla 
> wrote:
>
>> Hi All,
>>
>> Tested following scenarios
>>
>>
>>- Getting Unbounded table valued in rest API get requests
>>- Uploading WSDLs
>>- Dependency graph for uploaded WSDLs
>>- Adding tags to a asset
>>- Adding notes to an asset
>>- Creating custom RXTs
>>- Promoting lifecycles
>>
>>
>> [+] stable
>>
>> Thanks
>> Prasana
>>
>>
>> On Fri, Apr 22, 2016 at 5:25 PM, Rajith Roshan  wrote:
>>
>>> Hi All,
>>> I tested following basic operation on  config and governance paths
>>> mounted to a MYSQL database.
>>>
>>>- Upload wsdls(single and batch upload)
>>>- Upload wadls(single and batch upload)
>>>- RXT hot deployment.
>>>- Categorization and tag based filtering
>>>- RXT field regex validation at the publisher.
>>>
>>> [+] stable
>>>
>>> Thank you
>>> Rajith
>>>
>>> On Fri, Apr 22, 2016 at 5:10 PM, Chandana Napagoda 
>>> wrote:
>>>
 Hi All,

 Tested following scenarios with mounted setup

 - Store and Publisher notification
 - Tenant notification Store/Publisher
 - Publisher Lifecycle Management
 - Multiple Lifecycles
 - OR and AND search within a same field.

 Regards,
 Chandana


 On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka  wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>
> Maven staging repo:
> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
> *
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>
> [+] 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
>
>


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

 *Email  :  chand...@wso2.com **Mobile :
 +94718169299 <%2B94718169299>*

 *Blog  :http://cnapagoda.blogspot.com
 *


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


>>>
>>>
>>> --
>>> Rajith Roshan
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Prasanna Dangalla
>> Software Engineer, WSO2, Inc.; http://wso2.com/
>> lean.enterprise.middleware
>>
>> cell: +94 777 55 80 30 | +94 718 11 27 51
>> twitter: @prasa77
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Fernando
> Software Engineer
> WSO2 Inc. | http://wso2.com
> Mobile : +94 718874922
> Blog : http://blog.malintha.org
>
> Lean . Enterprise . Middleware
>
>
>
>
>
>
>


-- 
*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] [VOTE] Release WSO2 Governance Registry 5.2.0 RC 2

[Malintha Fernando]

Hi All,

Tested following scenarios for G-Reg 5.2.0 RC2 pack.

Lifecycle traversal on IE 11
Mounting the registry DB with mySQL.
Connection restoration when DB connection lost
Tenant anonymous diff view
Tenant anonymous view for new RXT types

[+] stable

Regards,
Malintha

On Fri, Apr 22, 2016 at 7:15 PM, Prasanna Dangalla 
wrote:

> Hi All,
>
> Tested following scenarios
>
>
>- Getting Unbounded table valued in rest API get requests
>- Uploading WSDLs
>- Dependency graph for uploaded WSDLs
>- Adding tags to a asset
>- Adding notes to an asset
>- Creating custom RXTs
>- Promoting lifecycles
>
>
> [+] stable
>
> Thanks
> Prasana
>
>
> On Fri, Apr 22, 2016 at 5:25 PM, Rajith Roshan  wrote:
>
>> Hi All,
>> I tested following basic operation on  config and governance paths
>> mounted to a MYSQL database.
>>
>>- Upload wsdls(single and batch upload)
>>- Upload wadls(single and batch upload)
>>- RXT hot deployment.
>>- Categorization and tag based filtering
>>- RXT field regex validation at the publisher.
>>
>> [+] stable
>>
>> Thank you
>> Rajith
>>
>> On Fri, Apr 22, 2016 at 5:10 PM, Chandana Napagoda 
>> wrote:
>>
>>> Hi All,
>>>
>>> Tested following scenarios with mounted setup
>>>
>>> - Store and Publisher notification
>>> - Tenant notification Store/Publisher
>>> - Publisher Lifecycle Management
>>> - Multiple Lifecycles
>>> - OR and AND search within a same field.
>>>
>>> Regards,
>>> Chandana
>>>
>>>
>>> On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
>>> wrote:
>>>
 Hi Devs,

 WSO2 Governance Registry 5.2.0 RC2 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/rc2/

 Maven staging repo:
 *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
 *

 The tag to be voted upon:
 https://github.com/wso2/product-greg/tree/v5.2.0-rc2

 [+] 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


>>>
>>>
>>> --
>>> *Chandana Napagoda*
>>> Senior Software Engineer
>>> WSO2 Inc. - http://wso2.org
>>>
>>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>>> <%2B94718169299>*
>>>
>>> *Blog  :http://cnapagoda.blogspot.com
>>> *
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Rajith Roshan
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prasanna Dangalla
> Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> cell: +94 777 55 80 30 | +94 718 11 27 51
> twitter: @prasa77
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Malintha Fernando
Software Engineer
WSO2 Inc. | http://wso2.com
Mobile : +94 718874922
Blog : http://blog.malintha.org

Lean . Enterprise . Middleware
___
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 2

[Prasanna Dangalla]

Hi All,

Tested following scenarios


   - Getting Unbounded table valued in rest API get requests
   - Uploading WSDLs
   - Dependency graph for uploaded WSDLs
   - Adding tags to a asset
   - Adding notes to an asset
   - Creating custom RXTs
   - Promoting lifecycles


[+] stable

Thanks
Prasana


On Fri, Apr 22, 2016 at 5:25 PM, Rajith Roshan  wrote:

> Hi All,
> I tested following basic operation on  config and governance paths mounted
> to a MYSQL database.
>
>- Upload wsdls(single and batch upload)
>- Upload wadls(single and batch upload)
>- RXT hot deployment.
>- Categorization and tag based filtering
>- RXT field regex validation at the publisher.
>
> [+] stable
>
> Thank you
> Rajith
>
> On Fri, Apr 22, 2016 at 5:10 PM, Chandana Napagoda 
> wrote:
>
>> Hi All,
>>
>> Tested following scenarios with mounted setup
>>
>> - Store and Publisher notification
>> - Tenant notification Store/Publisher
>> - Publisher Lifecycle Management
>> - Multiple Lifecycles
>> - OR and AND search within a same field.
>>
>> Regards,
>> Chandana
>>
>>
>> On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>>>
>>> Maven staging repo:
>>> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
>>> *
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>>>
>>> [+] 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
>>>
>>>
>>
>>
>> --
>> *Chandana Napagoda*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Prasanna Dangalla
Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware

cell: +94 777 55 80 30 | +94 718 11 27 51
twitter: @prasa77
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Cloud] Custom Applications on AppCloud

[Nishadi Kirielle]

HI All,
The above feature has been developed in this PR.[1]

Thanks
[1]. https://github.com/wso2/app-cloud/pull/288

On Mon, Apr 18, 2016 at 8:39 AM, Nishadi Kirielle  wrote:

> Hi,
> With the implemented feature we can input the above docker image url with
> the ports that should be exposed (http port and https port). Then the
> procedure is to pull the docker image and push it to the docker registry.
> Then it will follow the standard procedure in to deploy it in AppCloud.
>
> Thanks
> Nishadi
>
> On Tue, Apr 12, 2016 at 8:18 PM, Kasun De Silva  wrote:
>
>> Hi Nishadi,
>>
>> As for now this feature is expected to be exposed only to internal users
>>> by updating the configuration file.
>>
>>
>> How did we do this? what is the config file used ?
>>
>> Can you provide some example how can we use this feature. Say I have an
>> image "kasun/af_tomcat" how can I deploy this in AppCloud using this
>> feature?
>>
>> Thanks,
>> Kasun
>>
>
>
>
> --
> *Nishadi Kirielle*
> *Software Engineering Intern*
> Mobile : +94 (0) 714722148
> Blog : http://nishadikirielle.blogspot.com/
> nish...@wso2.com
>



-- 
*Nishadi Kirielle*
*Software Engineering Intern*
Mobile : +94 (0) 714722148
Blog : http://nishadikirielle.blogspot.com/
nish...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [App Cloud] Search By Tag feature in App Cloud

[Nishadi Kirielle]

Hi all,
The above feature has been developed with this PR[1].

Thanks
[1]. https://github.com/wso2/app-cloud/pull/282

On Tue, Apr 12, 2016 at 8:27 AM, Nishadi Kirielle  wrote:

> Hi All,
> Currently, I'm focusing on implementing the functionality to search
> applications by the provided tag in application listing index page. In
> implementing that functionality I'm planning to use the same search box
> used to search applications by their name to be used but the search phrase
> will begin with the 'tag' keyword. For example;
>  'tag:tomcat'
>
> Really appreciate your suggestions in proceeding with this.
>
> Thanks
> --
> *Nishadi Kirielle*
> *Software Engineering Intern*
> Mobile : +94 (0) 714722148
> Blog : http://nishadikirielle.blogspot.com/
> nish...@wso2.com
>



-- 
*Nishadi Kirielle*
*Software Engineering Intern*
Mobile : +94 (0) 714722148
Blog : http://nishadikirielle.blogspot.com/
nish...@wso2.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 2

[Rajith Roshan]

Hi All,
I tested following basic operation on  config and governance paths mounted
to a MYSQL database.

   - Upload wsdls(single and batch upload)
   - Upload wadls(single and batch upload)
   - RXT hot deployment.
   - Categorization and tag based filtering
   - RXT field regex validation at the publisher.

[+] stable

Thank you
Rajith

On Fri, Apr 22, 2016 at 5:10 PM, Chandana Napagoda 
wrote:

> Hi All,
>
> Tested following scenarios with mounted setup
>
> - Store and Publisher notification
> - Tenant notification Store/Publisher
> - Publisher Lifecycle Management
> - Multiple Lifecycles
> - OR and AND search within a same field.
>
> Regards,
> Chandana
>
>
> On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>>
>> Maven staging repo:
>> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
>> *
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>>
>> [+] 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
>>
>>
>
>
> --
> *Chandana Napagoda*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
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 2

[Chandana Napagoda]

Hi All,

Tested following scenarios with mounted setup

- Store and Publisher notification
- Tenant notification Store/Publisher
- Publisher Lifecycle Management
- Multiple Lifecycles
- OR and AND search within a same field.

Regards,
Chandana


On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>
> Maven staging repo:
> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
> *
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>
> [+] 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
>
>


-- 
*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] [VOTE] Release WSO2 Governance Registry 5.2.0 RC 2

[Denuwanthi De Silva]

Hi all,

I tested the below aspects for G-reg 5.2.0 RC2 pack:

-Tested the migration from 5.1.0 to 5.2.0 using the new migration client.
-Tested both database and data migrations
-Tested migration in both in ubuntu and windows environments using mysql as
the database.
-Mounting of registry db, identity db in both ubuntu and windows.

[+] stable

Thanks,

On Fri, Apr 22, 2016 at 4:38 PM, Lahiru J Ekanayake 
wrote:

> Hi All,
>
> I tested following scenarios with G-Reg 5.2.0  RC2 pack
>
> Search History - Store .
> When having multiple lifecycles in asset, publisher will auto select last
> upadted lifecycle .
> Custom RXT lifecycle promote and demote , lifecycle history .
> Login page client side validation.
> Register new user with having @ mark in username - store user registration
> page.
> Consistent alert messages.
> Lifecycle promote demote notifications .
>
> [+] stable
>
> Thanks!
>
> On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>>
>> Maven staging repo:
>> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
>> *
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>>
>> [+] 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
>>
>>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Denuwanthi De Silva
Software Engineer;
WSO2 Inc.; http://wso2.com,
Email: denuwan...@wso2.com
Blog: https://denuwanthi.wordpress.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 2

[Sameera Kannangara]

Hi all,

I tested following scenarios,

Getting started guide in Windows environment.
WADL GAR upload in windows environment.
Notification support in windows environment.
Lifecycle operations in windows environment.

[+] Stable.

Thank you,
SameeraK.



On Fri, Apr 22, 2016 at 4:38 PM, Lahiru J Ekanayake 
wrote:

> Hi All,
>
> I tested following scenarios with G-Reg 5.2.0  RC2 pack
>
> Search History - Store .
> When having multiple lifecycles in asset, publisher will auto select last
> upadted lifecycle .
> Custom RXT lifecycle promote and demote , lifecycle history .
> Login page client side validation.
> Register new user with having @ mark in username - store user registration
> page.
> Consistent alert messages.
> Lifecycle promote demote notifications .
>
> [+] stable
>
> Thanks!
>
> On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>>
>> Maven staging repo:
>> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
>> *
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>>
>> [+] 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
>>
>>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> 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] [VOTE] Release WSO2 Governance Registry 5.2.0 RC 2

[Lahiru J Ekanayake]

Hi All,

I tested following scenarios with G-Reg 5.2.0  RC2 pack

Search History - Store .
When having multiple lifecycles in asset, publisher will auto select last
upadted lifecycle .
Custom RXT lifecycle promote and demote , lifecycle history .
Login page client side validation.
Register new user with having @ mark in username - store user registration
page.
Consistent alert messages.
Lifecycle promote demote notifications .

[+] stable

Thanks!

On Tue, Apr 19, 2016 at 10:14 PM, Thushara Ranawaka 
wrote:

> Hi Devs,
>
> WSO2 Governance Registry 5.2.0 RC2 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/rc2/
>
> Maven staging repo:
> *https://maven.wso2.org/nexus/content/repositories/orgwso2greg-1002/
> *
>
> The tag to be voted upon:
> https://github.com/wso2/product-greg/tree/v5.2.0-rc2
>
> [+] 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
>
>


-- 



*Lahiru J Ekanayake**Software Engineer*
Mobile : +94 (0) 77 8812629 / +94(0) 778509547
Email : lahi...@wso2.com
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Commented Test Cases in API-M Master

[Bhathiya Jayasekara]

Hi Saneth,

Thanks, I'll merge it after running the test locally.

Regards,
Bhathiya

On Fri, Apr 22, 2016 at 3:38 PM, Saneth Dharmakeerthi 
wrote:

> Hi APIM Team,
>
> Above fix for TA-974 was submitted via pull request [1] on Jun 11, 2015,
> It is still on open stage.
>
> [1] https://github.com/wso2/product-apim/pull/224/files
>
>
> Thanks and Best Regards,
>
> Saneth Dharmakeerthi
> Senior Software Engineer
> WSO2, Inc.
> Mobile: +94772325511
>
> On Fri, Apr 22, 2016 at 3:33 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi Yasassri
>>
>> Thanks for pointing out. Will have a look.
>>
>> Regards,
>> Bhathiya
>>
>> On Fri, Apr 22, 2016 at 3:30 PM, Yasassri Ratnayake 
>> wrote:
>>
>>> Hi API-M Team,
>>>
>>> When we are mapping Automation tests against test cases in test-link we
>>> observed the $subject. Although some Tests are commented by pointing to
>>> JIRAs, the corresponding JIRAs are fixed.
>>>
>>> For instance [1
>>> ]
>>> is commented due to [2 ] but it
>>> has being resolved last year. I see around 15 test cases commented in the
>>> Master. Can you guys look into this and enable the tests that can be enabled
>>>
>>> [1] -
>>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/resources/testng.xml#L32
>>> [2] - https://wso2.org/jira/browse/TA-974
>>>
>>> With Regards,
>>> --
>>> Yasassri Ratnayake
>>> Software Engineer - QA
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>> *Mobile : +94715933168 <%2B94715933168>*
>>> *Blogs : http://yasassriratnayake.blogspot.com
>>> *
>>> *http://wso2logs.blogspot.com *
>>>
>>
>>
>>
>> --
>> *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
>> *
>>
>
>


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

*Phone: +94715478185*
*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

Re: [Dev] Commented Test Cases in API-M Master

[Saneth Dharmakeerthi]

Hi APIM Team,

Above fix for TA-974 was submitted via pull request [1] on Jun 11, 2015, It
is still on open stage.

[1] https://github.com/wso2/product-apim/pull/224/files


Thanks and Best Regards,

Saneth Dharmakeerthi
Senior Software Engineer
WSO2, Inc.
Mobile: +94772325511

On Fri, Apr 22, 2016 at 3:33 PM, Bhathiya Jayasekara 
wrote:

> Hi Yasassri
>
> Thanks for pointing out. Will have a look.
>
> Regards,
> Bhathiya
>
> On Fri, Apr 22, 2016 at 3:30 PM, Yasassri Ratnayake 
> wrote:
>
>> Hi API-M Team,
>>
>> When we are mapping Automation tests against test cases in test-link we
>> observed the $subject. Although some Tests are commented by pointing to
>> JIRAs, the corresponding JIRAs are fixed.
>>
>> For instance [1
>> ]
>> is commented due to [2 ] but it has
>> being resolved last year. I see around 15 test cases commented in the
>> Master. Can you guys look into this and enable the tests that can be enabled
>>
>> [1] -
>> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/resources/testng.xml#L32
>> [2] - https://wso2.org/jira/browse/TA-974
>>
>> With Regards,
>> --
>> Yasassri Ratnayake
>> Software Engineer - QA
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>> *Mobile : +94715933168 <%2B94715933168>*
>> *Blogs : http://yasassriratnayake.blogspot.com
>> *
>> *http://wso2logs.blogspot.com *
>>
>
>
>
> --
> *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

Re: [Dev] Commented Test Cases in API-M Master

[Bhathiya Jayasekara]

Hi Yasassri

Thanks for pointing out. Will have a look.

Regards,
Bhathiya

On Fri, Apr 22, 2016 at 3:30 PM, Yasassri Ratnayake 
wrote:

> Hi API-M Team,
>
> When we are mapping Automation tests against test cases in test-link we
> observed the $subject. Although some Tests are commented by pointing to
> JIRAs, the corresponding JIRAs are fixed.
>
> For instance [1
> ]
> is commented due to [2 ] but it has
> being resolved last year. I see around 15 test cases commented in the
> Master. Can you guys look into this and enable the tests that can be enabled
>
> [1] -
> https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/resources/testng.xml#L32
> [2] - https://wso2.org/jira/browse/TA-974
>
> With Regards,
> --
> Yasassri Ratnayake
> Software Engineer - QA
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
> *Mobile : +94715933168 <%2B94715933168>*
> *Blogs : http://yasassriratnayake.blogspot.com
> *
> *http://wso2logs.blogspot.com *
>



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

*Phone: +94715478185*
*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

[Dev] Commented Test Cases in API-M Master

[Yasassri Ratnayake]

Hi API-M Team,

When we are mapping Automation tests against test cases in test-link we
observed the $subject. Although some Tests are commented by pointing to
JIRAs, the corresponding JIRAs are fixed.

For instance [1
]
is commented due to [2 ] but it has
being resolved last year. I see around 15 test cases commented in the
Master. Can you guys look into this and enable the tests that can be enabled

[1] -
https://github.com/wso2/product-apim/blob/master/modules/integration/tests-integration/tests-backend/src/test/resources/testng.xml#L32
[2] - https://wso2.org/jira/browse/TA-974

With Regards,
-- 
Yasassri Ratnayake
Software Engineer - QA
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
*Mobile : +94715933168*
*Blogs : http://yasassriratnayake.blogspot.com
*
*http://wso2logs.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Analytics] Removing FACET from Indexing data types

[Gimantha Bandara]

Hi Isuru,

In Spark, we use "-sp" to denote score parameters and it also denotes that
the specific parameter will be indexed. Thats because, we can make score
parameter from indexed fields only. Same applies to facets, If so we use
"-f" to denote facets, we shouldn't use "-i", since facets will anyway be
indexed.

On Fri, Apr 22, 2016 at 10:00 AM, Gimantha Bandara 
wrote:

> Hi Isuru,
>
> Older FACET keyword is also supported. Yes, we are planing to add -f to
> denote facet attribute.
>
> @Anjana/Niranda WDYT?
>
>
> On Friday, April 22, 2016, Isuru Wijesinghe  wrote:
>
>> Hi Gimantha,
>>
>> How can we denote a given field in any data type as a facet in
>> *spark-sql.* Lets say as an example I have a field called
>> processDefinitionId (string data-type) and I need to define it as a facet
>> as well (see below example).
>>
>> CREATE TEMPORARY TABLE PROCESS_USAGE_SUMMARY USING CarbonAnalytics
>> OPTIONS (tableName "PROCESS_USAGE_SUMMARY_DATA",
>> schema "processDefinitionId string -i *-f*,
>> processVersion string -i,
>> processInstanceId string -i,,
>> primaryKeys "processInstanceId"
>> );
>>
>> is this the way that we can define it in newer version ?
>>
>>
>> On Fri, Apr 22, 2016 at 2:39 AM, Gimantha Bandara 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are planning to remove "FACET" (this type is used to
>>> categorize/group, to get unique values and to drill-down) from indexing
>>> data types and we will introduce an attribute to mark other data types as a
>>> FACET or not.  Earlier FACETs can be defined only for STRING fields and
>>> even if we define a STRING as a FACET, then we will not be able to search
>>> it as a STRING field. With this change, any data type field can be marked
>>> as a FACET and then the field can be used as a FACET and as the usual data
>>> type as well.
>>> This change will not affect the older DAS capps or event-store
>>> configurations; It will be backward compatible with previous DAS versions
>>> (3.0.0 and 3.0.1). However if you try to get the Schema of a table using JS
>>> APIs, REST APIs or the Webservice, FACET type will not be there. A
>>> attribute called "isFacet" is used to identify the FACETed fields. See
>>> below for an example.
>>>
>>>
>>>
>>> *Older schema*
>>> {
>>> "columns" : {
>>>"logFile" : { "type" : "STRING", "isIndex" : true,
>>> "isScoreParam" : false },
>>>"level" : { "type" : "DOUBLE", "isIndex" : true,
>>> "isScoreParam" : false },
>>>"location" : { "type" : "FACET", "isIndex" : true,
>>> "isScoreParam" : false } },
>>> "primaryKeys" : ["logFile", "level"]
>>> }
>>>
>>>
>>> *Equivalent new schema*
>>>
>>>
>>> *{ "columns" : {   "logFile" : { "type" : "STRING",
>>> "isIndex" : true, "isScoreParam" : false, **, isFacet : *false
>>> * },   "*level*" : { "type" : "DOUBLE", "isIndex" : true,
>>> "isScoreParam" : false, **, isFacet : *false* },*
>>> *   "location" : { "type" : "*STRING*", "isIndex" : true,
>>> "isScoreParam" : false, isF*acet : true
>>> * } },//FACET field is removed "primaryKeys" : ["logFile", "*
>>> level
>>>
>>>
>>> *"] }*
>>> --
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Isuru Wijesinghe
>> *Software Engineer*
>> WSO2 inc : http://wso2.com
>> lean.enterprise.middleware
>> Mobile: 0710933706
>> isur...@wso2.com
>>
>
>
> --
> Gimantha Bandara
> Software Engineer
> WSO2. Inc : http://wso2.com
> Mobile : +94714961919
>
>


-- 
Gimantha Bandara
Software Engineer
WSO2. Inc : http://wso2.com
Mobile : +94714961919
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing maven-tools 5.0.1

[Susinda Perera]

In builder machine settings.xml has some username and password.
wso2-nexus-deployer


On Fri, Apr 22, 2016 at 2:24 PM, Viraj Rajaguru  wrote:

> Hi Susinda,
>
> I think we need to add relevant credentials of Nexus to settings.xml
>
> Thanks,
> Viraj.
>
> On Fri, Apr 22, 2016 at 2:16 PM, Susinda Perera  wrote:
>
>> Hi Kasun
>>
>> For the $subject I followed [1]. It gives me following error when mvn
>> release:perform. Any idea, How to proceed from here?
>>
>> Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
>> on project maven-tools: Failed to deploy artifacts: Could not transfer
>> artifact org.wso2.maven:maven-tools:pom:5.0.1 from/to nexus-releases (
>> http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/
>> ):
>> Failed to transfer file:
>> http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/maven/maven-tools/5.0.1/maven-tools-5.0.1.pom
>> .
>> Return code is: 401, ReasonPhrase: Unauthorized
>>
>> [1] - https://docs.wso2.com/display/Carbon441/Releasing+a+Git+Repository
>>
>> Thanks
>> Susinda
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
>> Mobile:(+94)716049075
>> Blog: susinda.blogspot.com
>> WSO2 Inc. http://wso2.com/
>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>
>>
>
>
> --
> Viraj Rajaguru
> Senior Software Engineer
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Releasing maven-tools 5.0.1

[Viraj Rajaguru]

Hi Susinda,

I think we need to add relevant credentials of Nexus to settings.xml

Thanks,
Viraj.

On Fri, Apr 22, 2016 at 2:16 PM, Susinda Perera  wrote:

> Hi Kasun
>
> For the $subject I followed [1]. It gives me following error when mvn
> release:perform. Any idea, How to proceed from here?
>
> Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
> on project maven-tools: Failed to deploy artifacts: Could not transfer
> artifact org.wso2.maven:maven-tools:pom:5.0.1 from/to nexus-releases (
> http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/
> ):
> Failed to transfer file:
> http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/maven/maven-tools/5.0.1/maven-tools-5.0.1.pom
> .
> Return code is: 401, ReasonPhrase: Unauthorized
>
> [1] - https://docs.wso2.com/display/Carbon441/Releasing+a+Git+Repository
>
> Thanks
> Susinda
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>


-- 
Viraj Rajaguru
Senior Software Engineer
WSO2 Inc. : http://wso2.com

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

[Dev] Releasing maven-tools 5.0.1

[Susinda Perera]

Hi Kasun

For the $subject I followed [1]. It gives me following error when mvn
release:perform. Any idea, How to proceed from here?

Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project maven-tools: Failed to deploy artifacts: Could not transfer
artifact org.wso2.maven:maven-tools:pom:5.0.1 from/to nexus-releases (
http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/
):
Failed to transfer file:
http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/maven/maven-tools/5.0.1/maven-tools-5.0.1.pom
.
Return code is: 401, ReasonPhrase: Unauthorized

[1] - https://docs.wso2.com/display/Carbon441/Releasing+a+Git+Repository

Thanks
Susinda

-- 
*Susinda Perera*
Software Engineer
B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
Mobile:(+94)716049075
Blog: susinda.blogspot.com
WSO2 Inc. http://wso2.com/
Tel : 94 11 214 5345 Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Working With VFS Sender in ESB

[Yashothara Shanmugarajah]

Hi,

As the summary of my results herewith I have attached two graphs which is
specifying heap memory usage when streaming and not streaming.

Best Regards,
Yashothara.S

Software Engineer
WSO2


On Tue, Apr 19, 2016 at 12:16 PM, Yashothara Shanmugarajah <
yashoth...@wso2.com> wrote:

> Hi all,
>
> I am testing VFS sender in ESB using different set of files with different
> sizes (10MB to 5 GB which include zip file and txt files) by putting
> streaming as true and false. When streaming is false and normal
> configuration (*-Xms256m -Xmx512m -XX:MaxPermSize=256m)* for ESB heap
> memory allocation until 250MB file was worked fine. After that it gave out
> of memory issue. Then after changing the configuration to heap memory
> allocation (*-Xms2048m -Xmx2048m -XX:MaxPermSize=1024m*) until 1 GB zip
> file it worked fine. But 1 GB txt file got out of memory issue.
>
> But when streaming is true until 5 GB it worked fine. I checked all these
> scenarios with jconsole and got snapshot in that period. When streaming is
> true i got 500MB heap memory usage for 5 GB data. But around 1 GB memory
> space is used when I test 1 Gb file without Streaming.
>
> Herewith I have attached snapshots of jconsole.
>
> Thanks.
>
> Best Regards,
> Yashothara.S
>
> Software Engineer
> WSO2
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Requirements for EMM Dashboard

[Dilan Udara Ariyaratne]

@Ramindu,

If you want to manually check the APIs, please go through the following
documentation to get an access token.
https://docs.wso2.com/display/EMM201/Generating+the+OAuth+2.0+Access+Token

For the provided APIs, following are the request and response formats as
discussed.
[1] GET https://localhost:9443/mdm-admin/dashboard/device-overview
 Response:
 [{
"context": "overview",
"data": [{
 "count": 5,
 "label": "Total",
 "group": "total"
 }, {
 "count": 4,
 "label": "Active",
 "group": "active"
 }, {
 "count": 0,
 "label": "Inactive",
 "group": "inactive"
 }, {
 "count": 1,
 "label": "Removed",
 "group": "removed"
 }]
  }]

[2] GET https://localhost:9443/mdm-admin/dashboard/potential-vulnerabilities

 Response:
 [{
 "context": "potential-vulnerabilities",
 "data": [{
  "count": 5,
  "label": "Non-Compliant",
  "group": "non-complaint"
  }, {
  "count": 0,
  "label": "Unmonitored",
  "group": "unmonitored"
  }]
  }]

Cheers,
Dilan.


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


On Fri, Apr 22, 2016 at 11:24 AM, Dilan Udara Ariyaratne 
wrote:

> Hi Ramindu,
>
> I have just exposed two jax-rs apis for the following gadgets of the
> landing dashboard page as discussed in the last UX/UI meeting held on April
> 11th.
> [1] Device-overview-gadget (GET https://localhost:9443/mdm-admin
> /dashboard/device-overview) :
>  To show device counts as TOTAL, ACTIVE, INACTIVE and REMOVED
> [2] Potential-vlunerabilities (GET https://localhost:9443/mdm-admin/
> dashboard/potential-vulnerabilities) :
>  To show device counts as NON-COMPLIANT, UNMONITORED (NO-PASSCODE and
> NO-ENCRYPTION data capturing in still under development)
>
> Would you be able to get a build of product-emm and try these APIs from
> the portal app?
>
> I would be able to provide all the first-cut APIs for the landing
> dashboard page by this evening.
>
> Cheers,
> Dilan.
>
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Wed, Apr 20, 2016 at 12:07 PM, Ramindu De Silva 
> wrote:
>
>> Hi all,
>>
>> The following are the request-response structures for the IoT dashboard
>> API. Please mention any suggestion or changes to the following
>>
>>
>> 1. Retrieve connectivity status.
>>
>>>
>>> *Request: *POST /connectivityStatus
>>
>> *{}*
>>
>> *response:* [
>>>
>> {
>>
>> "context": "deviceInfo",
>>
>> "data": [
>>
>> {
>>
>> "group": "active",
>>
>> "label": "active",
>>
>> "count": activeNo
>>
>> },
>>
>> {
>>
>> "group": "all",
>>
>> "label": "all",
>>
>> "count": activeNo + inactiveNo
>>
>> },
>>
>> {
>>
>> "group": "inactive",
>>
>> "label": "inactive",
>>
>> "count": inactiveNo
>>
>> }
>>
>> ]
>>
>> }
>>
>> ]
>>
>> 2. Retrieve vulnerabilities
>>
>>
>>> *Request: *POST /securityConcerns
>>> *{*
>>> *}**response:* [
>>>
>> {
>>
>> "context": "securityConcerns",
>>
>> "data": [
>>
>> {
>>
>> "group": "no-passcode",
>>
>> "label": "No Passcode",
>>
>> "countChange": randint(100, 500),
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "no-encryption",
>>
>> "label": "Non encrypted",
>>
>> "countChange": randint(100, 500),
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "unmonitored",
>>
>> "label": "Unmonitored",
>>
>> "countChange": randint(100, 500),
>>
>> "count": randint(100, 500)
>>
>> }
>>
>> ]
>>
>> }
>>
>> ]
>>
>>
>> 3. Retrieve non compliant features
>>
>>
>>> *Request: *POST /nonCompliantDevices
>>> *{*
>>
>> fromIndex: 10,
>>
>> count: 5
>>
>> *}*
>>
>> *response:*[
>>
>>  {
>>
>> "context": "nonCompliantDevices",
>>
>> "data":[
>>
>> {
>>
>> "group": "non-compliant-1",
>>
>> "label": "Non Compliant-1",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-2",
>>
>> "label": "non-compliant-2",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-3",
>>
>> "label": "non-compliant-3",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-4",
>>
>> "label": "non-compliant-4",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-5",
>>
>> "label": "non-compliant-5",
>>
>> "count": randint(100, 500)
>>
>> }
>>
>> ]
>>
>> }
>>
>> ]
>>
>>
>> 4. Retrieve grouping: This has two types of requests request 1 without
>> mentioning any filters and request 2 with a filter
>>
>>
>>> 

Re: [Dev] API Requirements for EMM Dashboard

[Dilan Udara Ariyaratne]

Hi Sumedha,

These higher level APIs are provided at the product-emm level, thus the
path as "mdm-admin/" (root path which we have been using for all the
emm realted console apis).

Cheers,
DIlan.

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


On Fri, Apr 22, 2016 at 11:46 AM, Sumedha Rubasinghe 
wrote:

> Dilan,
> Shouldn't it be '/devicemgt' instead of 'mdm-admin'?
>
> On Fri, Apr 22, 2016 at 11:24 AM, Dilan Udara Ariyaratne 
> wrote:
>
>> Hi Ramindu,
>>
>> I have just exposed two jax-rs apis for the following gadgets of the
>> landing dashboard page as discussed in the last UX/UI meeting held on April
>> 11th.
>> [1] Device-overview-gadget (GET https://localhost:9443/mdm-admin
>> /dashboard/device-overview) :
>>  To show device counts as TOTAL, ACTIVE, INACTIVE and REMOVED
>> [2] Potential-vlunerabilities (GET https://localhost:9443/mdm-admin/
>> dashboard/potential-vulnerabilities) :
>>  To show device counts as NON-COMPLIANT, UNMONITORED (NO-PASSCODE and
>> NO-ENCRYPTION data capturing in still under development)
>>
>> Would you be able to get a build of product-emm and try these APIs from
>> the portal app?
>>
>> I would be able to provide all the first-cut APIs for the landing
>> dashboard page by this evening.
>>
>> Cheers,
>> Dilan.
>>
>>
>> *Dilan U. Ariyaratne*
>> Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>> On Wed, Apr 20, 2016 at 12:07 PM, Ramindu De Silva 
>> wrote:
>>
>>> Hi all,
>>>
>>> The following are the request-response structures for the IoT dashboard
>>> API. Please mention any suggestion or changes to the following
>>>
>>>
>>> 1. Retrieve connectivity status.
>>>

 *Request: *POST /connectivityStatus
>>>
>>> *{}*
>>>
>>> *response:* [

>>> {
>>>
>>> "context": "deviceInfo",
>>>
>>> "data": [
>>>
>>> {
>>>
>>> "group": "active",
>>>
>>> "label": "active",
>>>
>>> "count": activeNo
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "all",
>>>
>>> "label": "all",
>>>
>>> "count": activeNo + inactiveNo
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "inactive",
>>>
>>> "label": "inactive",
>>>
>>> "count": inactiveNo
>>>
>>> }
>>>
>>> ]
>>>
>>> }
>>>
>>> ]
>>>
>>> 2. Retrieve vulnerabilities
>>>
>>>
 *Request: *POST /securityConcerns
 *{*
 *}**response:* [

>>> {
>>>
>>> "context": "securityConcerns",
>>>
>>> "data": [
>>>
>>> {
>>>
>>> "group": "no-passcode",
>>>
>>> "label": "No Passcode",
>>>
>>> "countChange": randint(100, 500),
>>>
>>> "count": randint(100, 500)
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "no-encryption",
>>>
>>> "label": "Non encrypted",
>>>
>>> "countChange": randint(100, 500),
>>>
>>> "count": randint(100, 500)
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "unmonitored",
>>>
>>> "label": "Unmonitored",
>>>
>>> "countChange": randint(100, 500),
>>>
>>> "count": randint(100, 500)
>>>
>>> }
>>>
>>> ]
>>>
>>> }
>>>
>>> ]
>>>
>>>
>>> 3. Retrieve non compliant features
>>>
>>>
 *Request: *POST /nonCompliantDevices
 *{*
>>>
>>> fromIndex: 10,
>>>
>>> count: 5
>>>
>>> *}*
>>>
>>> *response:*[
>>>
>>>  {
>>>
>>> "context": "nonCompliantDevices",
>>>
>>> "data":[
>>>
>>> {
>>>
>>> "group": "non-compliant-1",
>>>
>>> "label": "Non Compliant-1",
>>>
>>> "count": randint(100, 500)
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "non-compliant-2",
>>>
>>> "label": "non-compliant-2",
>>>
>>> "count": randint(100, 500)
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "non-compliant-3",
>>>
>>> "label": "non-compliant-3",
>>>
>>> "count": randint(100, 500)
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "non-compliant-4",
>>>
>>> "label": "non-compliant-4",
>>>
>>> "count": randint(100, 500)
>>>
>>> },
>>>
>>> {
>>>
>>> "group": "non-compliant-5",
>>>
>>> "label": "non-compliant-5",
>>>
>>> "count": randint(100, 500)
>>>
>>> }
>>>
>>> ]
>>>
>>> }
>>>
>>> ]
>>>
>>>
>>> 4. Retrieve grouping: This has two types of requests request 1 without
>>> mentioning any filters and request 2 with a filter
>>>
>>>
 *Request1: *POST /nonCompliantDevices
 *[]*
>>>
>>> *response1:*[
 {
 "context": "platforms",
 "data": [
 {
 "group": "ios",
 "label": "iOS",
 "count": randint(100, 500)
 },
 {
 "group": "android",
 "label": "Android",
 "count": randint(100, 500)
 }
 ]
 },
 {
 "context": "ownerships",
 "data": [
 {
 "group": "cope",
 "label": "COPE",
 "count": randint(100, 500)
 },
 {
 "group": "byod",
 "label": "BYOD",
 "count": randint(100, 500)

Re: [Dev] API Requirements for EMM Dashboard

[Sumedha Rubasinghe]

Dilan,
Shouldn't it be '/devicemgt' instead of 'mdm-admin'?

On Fri, Apr 22, 2016 at 11:24 AM, Dilan Udara Ariyaratne 
wrote:

> Hi Ramindu,
>
> I have just exposed two jax-rs apis for the following gadgets of the
> landing dashboard page as discussed in the last UX/UI meeting held on April
> 11th.
> [1] Device-overview-gadget (GET https://localhost:9443/mdm-admin
> /dashboard/device-overview) :
>  To show device counts as TOTAL, ACTIVE, INACTIVE and REMOVED
> [2] Potential-vlunerabilities (GET https://localhost:9443/mdm-admin/
> dashboard/potential-vulnerabilities) :
>  To show device counts as NON-COMPLIANT, UNMONITORED (NO-PASSCODE and
> NO-ENCRYPTION data capturing in still under development)
>
> Would you be able to get a build of product-emm and try these APIs from
> the portal app?
>
> I would be able to provide all the first-cut APIs for the landing
> dashboard page by this evening.
>
> Cheers,
> Dilan.
>
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Wed, Apr 20, 2016 at 12:07 PM, Ramindu De Silva 
> wrote:
>
>> Hi all,
>>
>> The following are the request-response structures for the IoT dashboard
>> API. Please mention any suggestion or changes to the following
>>
>>
>> 1. Retrieve connectivity status.
>>
>>>
>>> *Request: *POST /connectivityStatus
>>
>> *{}*
>>
>> *response:* [
>>>
>> {
>>
>> "context": "deviceInfo",
>>
>> "data": [
>>
>> {
>>
>> "group": "active",
>>
>> "label": "active",
>>
>> "count": activeNo
>>
>> },
>>
>> {
>>
>> "group": "all",
>>
>> "label": "all",
>>
>> "count": activeNo + inactiveNo
>>
>> },
>>
>> {
>>
>> "group": "inactive",
>>
>> "label": "inactive",
>>
>> "count": inactiveNo
>>
>> }
>>
>> ]
>>
>> }
>>
>> ]
>>
>> 2. Retrieve vulnerabilities
>>
>>
>>> *Request: *POST /securityConcerns
>>> *{*
>>> *}**response:* [
>>>
>> {
>>
>> "context": "securityConcerns",
>>
>> "data": [
>>
>> {
>>
>> "group": "no-passcode",
>>
>> "label": "No Passcode",
>>
>> "countChange": randint(100, 500),
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "no-encryption",
>>
>> "label": "Non encrypted",
>>
>> "countChange": randint(100, 500),
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "unmonitored",
>>
>> "label": "Unmonitored",
>>
>> "countChange": randint(100, 500),
>>
>> "count": randint(100, 500)
>>
>> }
>>
>> ]
>>
>> }
>>
>> ]
>>
>>
>> 3. Retrieve non compliant features
>>
>>
>>> *Request: *POST /nonCompliantDevices
>>> *{*
>>
>> fromIndex: 10,
>>
>> count: 5
>>
>> *}*
>>
>> *response:*[
>>
>>  {
>>
>> "context": "nonCompliantDevices",
>>
>> "data":[
>>
>> {
>>
>> "group": "non-compliant-1",
>>
>> "label": "Non Compliant-1",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-2",
>>
>> "label": "non-compliant-2",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-3",
>>
>> "label": "non-compliant-3",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-4",
>>
>> "label": "non-compliant-4",
>>
>> "count": randint(100, 500)
>>
>> },
>>
>> {
>>
>> "group": "non-compliant-5",
>>
>> "label": "non-compliant-5",
>>
>> "count": randint(100, 500)
>>
>> }
>>
>> ]
>>
>> }
>>
>> ]
>>
>>
>> 4. Retrieve grouping: This has two types of requests request 1 without
>> mentioning any filters and request 2 with a filter
>>
>>
>>> *Request1: *POST /nonCompliantDevices
>>> *[]*
>>
>> *response1:*[
>>> {
>>> "context": "platforms",
>>> "data": [
>>> {
>>> "group": "ios",
>>> "label": "iOS",
>>> "count": randint(100, 500)
>>> },
>>> {
>>> "group": "android",
>>> "label": "Android",
>>> "count": randint(100, 500)
>>> }
>>> ]
>>> },
>>> {
>>> "context": "ownerships",
>>> "data": [
>>> {
>>> "group": "cope",
>>> "label": "COPE",
>>> "count": randint(100, 500)
>>> },
>>> {
>>> "group": "byod",
>>> "label": "BYOD",
>>> "count": randint(100, 500)
>>> }
>>> ]
>>> },
>>> {
>>> "context": "userGroups",
>>> "data": [
>>> {
>>> "group": "sales",
>>> "label": "Sales",
>>> "count": randint(100, 500)
>>> },
>>> {
>>> "group": "marketing",
>>> "label": "Marketing",
>>> "count": randint(100, 500)
>>> },
>>> {
>>> "group": "engineering",
>>> "label": "Engineering",
>>> "count": randint(100, 500)
>>> }
>>> ]
>>> }
>>
>> ]
>>
>>
>>
>>> *Request2: *POST 

Re: [Dev] [DEV][Kubernetes Artifacts] Add /etc/hosts entry using the deploy script

[Imesh Gunaratne]

+1 For the suggestions Chamila!
I guess it would prompt the user for the password as it needs to update the
/etc/hosts file. May be we can print a log describing the action.

Thanks

On Fri, Apr 22, 2016 at 11:05 AM, Chamila De Alwis 
wrote:

> The above command should change to the following. We are checking the HTTP
> port for activity.
>
> cat ${PWD##*/}-default-service.yaml | grep servlet-http -A 4 -w | grep
> nodePort | awk '{print $2}'
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>
> On Fri, Apr 22, 2016 at 11:02 AM, Chamila De Alwis 
> wrote:
>
>> Furthermore, instead of hardcoding the default port value in the
>> deploy.sh script, we can find that out from the
>> [product-name]-default-service.yaml file, using the following bash command.
>> This way, if the user changes the NodePorts for the product, they are not
>> required to repeat it in the script. It's easy to miss this change and get
>> frustrated when the deploy script doesn't work.
>>
>> Con: there shouldn't be any major YAML changes, otherwise the grep -A
>> command might fail.
>>
>> cat ${PWD##*/}-default-service.yaml | grep servlet-https -A 4 | grep
>> nodePort | awk '{print $2}'
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>> On Fri, Apr 22, 2016 at 10:31 AM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>>
>>>
>>> On Fri, Apr 22, 2016 at 10:09 AM, Chamila De Alwis 
>>> wrote:
>>>
 Hi,

 Just noticed that, in the README [1],  we instruct the user to add a
 host mapping manually to access the management console after deploying the
 Service. We can do this in the deploy script itself, and cleanup in the
 undeploy script. WDYT?

>>>
>>> +1, It'll easy the process.
>>>

 [1] -
 https://github.com/wso2/kubernetes-artifacts/blob/master/wso2am/README.md

 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Software Engineer | WSO2 | +94772207163
 Blog: code.chamiladealwis.com



>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>
>>
>


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