from:"Lahiru Madushanka"

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.6.0 RC3

2019-12-19 Thread Lahiru Madushanka

Hi all,

I tested the following,

   - Secure proxy services.
   - Stat publishing to analytics in JDK 8 and 11 ( Linux )
   - Data mapper mediator
   - JMX monitoring


+1 Stable - Go ahead and release.

Thanks,
*Lahiru Madushanka* | Software Engineer | WSO2 Inc.
071 7276083 | lahirum...@wso2.com
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.6.0 RC2

2019-12-17 Thread Lahiru Madushanka

Hi all,

I tested the following

JSON-Transform mediator
Aggregate mediator / Enrich mediator JSON support
Data mapper mediator
Secure proxy services
Profile-creator tool
Stat publishing to Streaming Integrator in WIN, JDK 8 environment.
Carbon application deployment

+1 Stable - go ahead and release

Thanks,
Lahiru

On Mon, Dec 16, 2019 at 11:55 AM Sameera Gunarathne 
wrote:

> Hi All,
>
> We are pleased to announce the second release candidate of WSO2 Enterprise
> Integrator 6.6.0.
>
> Known issues: https://github.com/wso2/product-ei/issues
>
> Source and binary distribution files:
> https://github.com/wso2/product-ei/releases/tag/v6.6.0-rc2
> <https://github.com/wso2/product-ei/releases/tag/v6.6.0-rc2>
>
> The tag to be voted upon:
> https://github.com/wso2/product-ei/tree/v6.6.0-rc2
>
> Please vote as follows:
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> ~The WSO2 Integration Team~
>
> Thanks,
> <https://github.com/wso2/product-ei/releases/tag/v6.6.0-rc1>
> --
> Sameera Gunarathne
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> <http://l.facebook.com/l.php?u=http%3A%2F%2Fwso2.com=gAQEswASa>
> Email: samee...@wso2.com
> Mobile: +94714155561
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Lahiru Madushanka* | Software Engineer | WSO2 Inc.
071 7276083 | lahirum...@wso2.com
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
<http://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to use external property file in ESB 6.3

2019-12-09 Thread Lahiru Madushanka

Hi Kanishka,

This feature is added to the upcoming release EI 6.6.0 ( currently in beta
[1] )

[1] https://github.com/wso2/product-ei/releases/tag/v6.6.0-beta

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

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

2019-05-17 Thread Lahiru Madushanka

Hi,

I tested the following

1. Native JSON support in Aggregate mediator
2. Native JSON support in Enrich mediator
3. Class mediator
4. PropertyGroup mediator
5. DBLookup mediator + auto download feature of JDBC jars
6. DBReport mediator
7. Datamapper mediator
8. Clone mediator
9. Iterate mediator
10. Mediation debug in MicroIntegrator and EI
11. Prometheus stat publishing
12. MicroIntegrator command line tool
13. Docker image creation using IntegrationStudio

+1 to go ahead and release

Thanks,
Lahiru

On Fri, May 17, 2019 at 5:37 PM Hasitha Hiranya  wrote:

> Hi,
>
> I tested below -
>
> backend Funtionlaity and Web UI of wso2ei
>
>1. HTTP proxy
>2. log mediator
>3. JMS message stores
>4. JMS message processor (MB based)
>5. JMS proxy inbound
>6. Sequence mediator
>7. Store mediator
>8. address endpoint
>
> MB profile
>1. Create a queue
>2. Create a subscriber and publisher to a queue
>3. Use MB to implement message store forward
>
> +1 to go ahead and release
>
> Thanks
>
> On Fri, May 17, 2019 at 1:20 PM Hasitha Hiranya  wrote:
>
>> Hi,
>>
>> I smoke tested below -
>>
>> backend Funtionlaity and Web UI of wso2ei
>>
>>1. HTTP proxy
>>2. log mediator
>>3. JMS message stores
>>4. JMS message processor (MB based)
>>5. JMS proxy inbound
>>6. Sequence mediator
>>7. Store mediator
>>8. address endpoint
>>
>> MB profile
>>1. Create a queue
>>2. create a subscriber and publisher to a queue
>>3. Use MB to implement message store forward
>>
>> +1 to go ahead and release
>>
>> Thanks
>>
>> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
>> nirothi...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> We are pleased to announce the first release candidate of WSO2
>>> Enterprise Integrator 6.5.0.
>>>
>>> Please find the list of tasks / bug fixes and improvements shipped with
>>> this release below
>>>
>>>- Tasks/bug fixes and improvements in Enterprise Integrator
>>>
>>> 
>>>- Tasks/bug fixes and improvements in Micro Integrator
>>>
>>> 
>>>
>>> Known Issues
>>>
>>>- https://github.com/wso2/product-ei/issues
>>>- https://github.com/wso2/micro-integrator/issues
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/product-ei/tree/v6.5.0-rc1
>>>
>>> Source and binary distributions:
>>> https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1
>>>
>>> Please test and vote as follows
>>>
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> You may find the official documentation in:
>>> https://docs.wso2.com/display/EI6xx
>>>
>>> ~ The Enterprise Integrator Team ~
>>>
>>>
>>> --
>>>
>>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>>
>>> (m) +94772172692 | (e) nirothi...@wso2.com
>>>
>>> [image: http://wso2.com/signature] 
>>>
>>>
>>
>> --
>> *Hasitha Abeykoon*
>> Associate Technical Lead; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
> --
> *Hasitha Abeykoon*
> Associate Technical Lead; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

2019-05-17 Thread Lahiru Madushanka

Hi,

I tested the following

1. Native JSON support in Aggregate mediator
2. Native JSON support in Enrich mediator
3. Class mediator
4. PropertyGroup mediator
5. DBLookup mediator + auto download feature of JDBC jars
6. DBReport mediator
7. Datamapper mediator
8. Clone mediator
9. Iterate mediator
10. Mediation debug in MicroIntegrator and EI
11. Prometheus stat publishing
12. MicroIntegrator command line tool
13. Docker image creation using IntegrationStudio

+1 to go ahead and release

Thanks,
Lahiru

On Fri, May 17, 2019 at 3:40 PM Hasitha Hiranya  wrote:

> Hi,
>
> I smoke tested below -
>
> backend Funtionlaity and Web UI of wso2ei
>
>1. HTTP proxy
>2. log mediator
>3. JMS message stores
>4. JMS message processor (MB based)
>5. JMS proxy inbound
>6. Sequence mediator
>7. Store mediator
>8. address endpoint
>
> MB profile
>1. Create a queue
>2. create a subscriber and publisher to a queue
>3. Use MB to implement message store forward
>
> +1 to go ahead and release
>
> Thanks
>
> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
> nirothi...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the first release candidate of WSO2 Enterprise
>> Integrator 6.5.0.
>>
>> Please find the list of tasks / bug fixes and improvements shipped with
>> this release below
>>
>>- Tasks/bug fixes and improvements in Enterprise Integrator
>>
>> 
>>- Tasks/bug fixes and improvements in Micro Integrator
>>
>> 
>>
>> Known Issues
>>
>>- https://github.com/wso2/product-ei/issues
>>- https://github.com/wso2/micro-integrator/issues
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-ei/tree/v6.5.0-rc1
>>
>> Source and binary distributions:
>> https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1
>>
>> Please test and vote as follows
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> You may find the official documentation in:
>> https://docs.wso2.com/display/EI6xx
>>
>> ~ The Enterprise Integrator Team ~
>>
>>
>> --
>>
>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>
>> (m) +94772172692 | (e) nirothi...@wso2.com
>>
>> [image: http://wso2.com/signature] 
>>
>>
>
> --
> *Hasitha Abeykoon*
> Associate Technical Lead; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

2019-05-17 Thread Lahiru Madushanka

Hi,

I tested the following

1. Native JSON support in Aggregate mediator
2. Native JSON support in Enrich mediator
3. Class mediator
4. PropertyGroup mediator
5. DBLookup mediator + auto download feature of JDBC jars
6. DBReport mediator
7. Datamapper mediator
8. Clone mediator
9. Iterate mediator
10. Mediation debug in MicroIntegrator and EI
11. Prometheus stat publishing
12. MicroIntegrator command line tool
13. Docker image creation using IntegrationStudio

+1 to go ahead and release

Thanks,
Lahiru

On Fri, May 17, 2019 at 3:40 PM Hasitha Hiranya  wrote:

> Hi,
>
> I smoke tested below -
>
> backend Funtionlaity and Web UI of wso2ei
>
>1. HTTP proxy
>2. log mediator
>3. JMS message stores
>4. JMS message processor (MB based)
>5. JMS proxy inbound
>6. Sequence mediator
>7. Store mediator
>8. address endpoint
>
> MB profile
>1. Create a queue
>2. create a subscriber and publisher to a queue
>3. Use MB to implement message store forward
>
> +1 to go ahead and release
>
> Thanks
>
> On Thu, May 16, 2019 at 7:33 PM Nirothipan Megalingham <
> nirothi...@wso2.com> wrote:
>
>> Hi all,
>>
>> We are pleased to announce the first release candidate of WSO2 Enterprise
>> Integrator 6.5.0.
>>
>> Please find the list of tasks / bug fixes and improvements shipped with
>> this release below
>>
>>- Tasks/bug fixes and improvements in Enterprise Integrator
>>
>> 
>>- Tasks/bug fixes and improvements in Micro Integrator
>>
>> 
>>
>> Known Issues
>>
>>- https://github.com/wso2/product-ei/issues
>>- https://github.com/wso2/micro-integrator/issues
>>
>> The tag to be voted upon:
>> https://github.com/wso2/product-ei/tree/v6.5.0-rc1
>>
>> Source and binary distributions:
>> https://github.com/wso2/product-ei/releases/tag/v6.5.0-rc1
>>
>> Please test and vote as follows
>>
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> You may find the official documentation in:
>> https://docs.wso2.com/display/EI6xx
>>
>> ~ The Enterprise Integrator Team ~
>>
>>
>> --
>>
>> *M.Nirothipan* | Senior Software Engineer | WSO2 Inc.
>>
>> (m) +94772172692 | (e) nirothi...@wso2.com
>>
>> [image: http://wso2.com/signature] 
>>
>>
>
> --
> *Hasitha Abeykoon*
> Associate Technical Lead; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSDL based proxy for SOAP Calculator

2018-12-20 Thread Lahiru Madushanka

Hi Aman,

You can call the above proxy using SoapUI.
Use the following sample payload.

http://schemas.xmlsoap.org/soap/envelope/;
xmlns:tem="http://tempuri.org/;>
   
   
  
 123
 123
  
   


Thanks,
Lahiru

On Fri, Dec 21, 2018 at 10:46 AM Aman Singh  wrote:

> Hi Devs,
>
> I have a sample WSDL(url below) SOAP service for Calculator, which
> performs simple operations like Add, Subtract, Multiply, Divide.
>
> I want to implement and perform say ADD operation. I have  created a WSDL
> based proxy with required WSDl endpoint, service and port.
>
> Can someone please explain me how to proceed for performing ADD operation,
> I am not getting any idea what to do next.
>
> My WSDL proxy service code:-
>
> http://ws.apache.org/ns/synapse;>
> 
>  name="endpoint_urn_uuid_1FF78996948B9A0B6E14565751214774-1218279313">
> http://www.dneonline.com/calculator.asmx?WSDL"/>
> 
> 
> 
> 
> 
> 
> 
> 
>
> WSDL URL:- http://www.dneonline.com/calculator.asmx?WSDL
>
> Help would be appreciated.
>
> Thank you,
> Aman.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Using clone and aggregator in the same sequence

2018-12-09 Thread Lahiru Madushanka

Hi Lahiru,

I tested a sample and it seems not working when aggregated in inSequence
itself.
Appreciate if you can provide a  sample configuration.

Thanks,
Lahiru

On Fri, Dec 7, 2018 at 4:49 PM Lahiru Sandaruwan  wrote:

>
>
> On Fri, Dec 7, 2018 at 5:18 AM Lahiru Sandaruwan  wrote:
>
>> Hi,
>>
>> We do not have any samples at [1] for $subject. They all show having
>> splitting requests in InSequence and aggregation in outSequence.
>>
>> Q1, Is this recommended?
>> Q2, If yes, shall we an a sample?
>>
>> For example,
>>
>> 
>> 
>> 
>> *   // do something*
>> 
>> 
>> 
>> 
>> * // do something*
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > expression="//jsonObject" xmlns:ns="http://org.apache.synapse/xsd;>
>>
>> *// do more with aggregated response*
>>
>> 
>> 
>>
>>
>>
>> Cache mediator has a similar sample at [2], with specific property,
>>
>> .
>>
>> [1] https://docs.wso2.com/display/EI611/Aggregate+Mediator
>> [2] https://docs.wso2.com/display/EI611/Cache+Mediator
>>
>> Thanks.
>>
>> --
>> --
>>
>> Lahiru Sandaruwan
>> WSO2 Inc., http://wso2.com
>>
>> lean.enterprise.middleware
>>
>> m: +1 901 530 2379
>> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
>> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
> --
> --
>
> Lahiru Sandaruwan
> WSO2 Inc., http://wso2.com
>
> lean.enterprise.middleware
>
> m: +1 901 530 2379
> e: lahi...@wso2.com b: https://medium.com/@lahirugmg
> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] API Manager - Retrieving JSON Payload During Mediation

2018-09-26 Thread Lahiru Madushanka

Hi Amith,

Explanation of how json-eval() works.

We have two kinds of path expressions in synapse, synapseJsonPath and
synapseXPath
Following method is where we evaluate the json-eval() expressions

public String stringValueOf(MessageContext synCtx) {
org.apache.axis2.context.MessageContext amc =
((Axis2MessageContext) synCtx).getAxis2MessageContext();
InputStream stream;
if (!JsonUtil.hasAJsonPayload(amc) ||
"true".equals(enableStreamingJsonPath)) {
try {
if (null == amc.getEnvelope().getBody().getFirstElement()) {
// Get message from PT Pipe.
stream = getMessageInputStreamPT(amc);
if (stream == null) {
stream = JsonUtil.getJsonPayload(amc);
} else {
JsonUtil.getNewJsonPayload(amc, stream, true, true);
}
} else {
// Message Already built.
stream =
JsonUtil.toJsonStream(amc.getEnvelope().getBody().getFirstElement());
}
if(stream != null) {
return stringValueOf(stream);
}else{
log.warn("Json Payload is empty.");
return "";
}
} catch (IOException e) {
handleException("Could not find JSON Stream in PassThrough
Pipe during JSON path evaluation.", e);
}
} else {
stream = JsonUtil.getJsonPayload(amc);
return stringValueOf(stream);
}
return "";
}


In all the branches we use *stringValueOf(stream)* method to evaluate the
jsonPath expressions against an input-stream.
Where we take the stream is dependent on certain conditions as in the above
implementation.

If message already build we convert message body to a JSON stream in

stream =
JsonUtil.toJsonStream(amc.getEnvelope().getBody().getFirstElement());

If message is not already built we take the stream from passthrough Pipe

Pipe pipe= (Pipe)
context.getProperty(PassThroughConstants.PASS_THROUGH_PIPE);

In the final else condition we take the stream from a property in axis2
message context

Object o =
messageContext.getProperty(ORG_APACHE_SYNAPSE_COMMONS_JSON_JSON_INPUT_STREAM);


You can find all implementation details in [1]

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

Thanks,
Lahiru

On Wed, Sep 26, 2018 at 7:31 PM Nuwan Dias  wrote:

> Adding Isuru and Shafreen.
>
> The mediation engine (EI/API Gateway) supports transforming or changing
> messages from various protocols to various other protocols. Such as from
> XML to JSON, from Text to XML, from form-url to JSON, likewise. To support
> these various types of transformations, upon receiving a message the engine
> would first convert it into a common base, and then convert it to the
> requested base, likewise. Without doing which, the combinations of these
> transformations would be endless. In the case of EI/API Gateway, this
> common base is XML. So every message, if you need to process it, is first
> converted to XML and then all changes or transformation are done on the
> particular XML message and then converted to whatever the requested format
> is. So as far as I know you can't work with the message on plain JSON
> format only. However, I've added two of my colleagues who have a better
> idea about this than me to see if this is possible.
>
> Thanks,
> NuwanD.
>
> On Wed, Sep 26, 2018 at 2:11 PM Amitha Dissanayake 
> wrote:
>
>> Hi Nuwan,
>>
>> Thanks a lot for the prompt response. That document helped. However, my
>> original question still remains unresolved to me.
>>
>> More specifically, when using the class mediator, I used the property
>> mediator and received the JSON string to the class. But I still have to
>> convert to XML and load it to the axis2 context message envelope (i.e.
>> SOAP).
>>
>> 
>> 
>>
>>
>>
>>
>> I couldn't find how this json-eval() function evaluates the JSON payload
>> (Whether it's accessing a JSON representation or an XML representation).
>>
>> How can I do this without converting the JSON to XML (without converting
>> it to XML and attaching to axis2 message)?
>>
>> How is JSON represented in the EI / API Manager by default (XML or JSON)?
>> I understand that conversions and manipulations are possible either way.
>>
>> Can the the EI / API Manager keep the JSON payload not converted
>> end-to-end (i.e. from the point of backend REST API sending the response
>> with a JSON payload till the requester receiving it?
>>
>> I'm evaluating API Manager, while hoping to apply it to a latency and
>> performance critical application. That is why I'm trying to understand how
>> it works in the EI.
>>
>> Thanks.
>>
>> Regards,
>> Amitha
>>
>> On Sep 26 2018, at 2:12 pm, Nuwan Dias  wrote:
>>
>>
>> Hi Amitha,
>>
>> Maybe this document [1] would help you understand how to deal with JSON
>> payloads better.
>>
>> [1] -
>> https://docs.wso2.com/display/EI630/Working+with+JSON+Message+Payloads
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, Sep 26, 2018

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.4.0 RC1

2018-09-19 Thread Lahiru Madushanka

Hi all,

I have tested the following mediators.
DBLookup
DBReport
Callout
Cache
ForEach
Iterate
Script
Smooks

and

VFS transport
InMemory message store + Message sampling processor
IP based throttling

[+] Stable - Go ahead and release

Thanks,
Lahiru

On Wed, Sep 19, 2018 at 11:40 AM Shakila Sasikaran  wrote:

> Hi all,
>
> I have tested the following and no issues found.
>
> *Core:*
> Call
> Enqueue
> Send
> Loopback
> Sequence
> Respond
> Drop
> Call Template
> Enrich
> Property
> Log
> Filter
> Out
> In
> Validate
> Switch
>
> *Endpoints:*
> Address Endpoints
> LoadBalance Endpoints
> Failover Endpoints
> HTTP Endpoints
> WSDL Endpoints
> Indirect and Resolving Endpoints
> Default Endpoints
> Template Endpoints
> Recipient List Endpoints
>
> *Inbound Endpoints:*
> File inbound
> JMS inbound
>
> [+] Stable - Go ahead and release
>
> Thanks
>
> On Tue, Sep 18, 2018 at 10:04 PM, Dileesha Rajapakse 
> wrote:
>
>> Hi everyone,
>>
>> I have tested the RC1 in the following scenarios.
>>
>>1.  Tested the following EI Analytics features with embedded H2 and
>>MySQL 5.7.
>>   1. Overview Dashboard.
>>   2. Proxy Services Dashboard.
>>   3. API Dashboard.
>>   4. Sequence Dashboard.
>>   5. Endpoint Dashboard.
>>   6. Inbound Endpoint Dashboard
>>   7. Mediator Dashboard.
>>   8. Message Dashboard.
>>2. Tested the following in a two-node cluster.
>>   1. Scheduling Tasks in different time intervals and counts.
>>   2. Scheduling tasks with cron expressions.
>>3. Tested the creation and deployment (as CApps) of the following
>>with tooling.
>>   1. Proxy service.
>>   2. API.
>>   3. Sequence.
>>   4. REST API.
>>   5. Inbound Endpoint.
>>   6. Endpoint.
>>
>> No issues found.
>>
>> [+] Stable - Go ahead and release
>>
>> Regards.
>>
>> On Tue, Sep 18, 2018 at 2:03 PM Thishani Lucas  wrote:
>>
>>> Hi All,
>>>
>>> We are pleased to announce the first release candidate of WSO2
>>> Enterprise Integrator 6.4.0.
>>>
>>> *Known Issues: *https://github.com/wso2/product-ei/issues
>>>
>>> *Source and Binary Distribution Files: *
>>> https://github.com/wso2/product-ei/releases/tag/v6.4.0-rc1
>>>
>>> *The Tag to be Voted Upon: *
>>> https://github.com/wso2/product-ei/tree/v6.4.0-rc1
>>>
>>> Please vote as follows:
>>>
>>> [+] Stable - Go ahead and release
>>> [-] Broken - Do not release (explain why)
>>>
>>> ~The WSO2 Integration Team~
>>>
>>> --
>>> *Thishani Lucas*
>>> *Software Engineer*
>>> *WSO2 Lanka (Private) Limited**: http://wso2.com *
>>> *lean.enterprise.middle-ware*
>>>
>>> *Tel: +94 77 2556931 *
>>>
>>> *LinkedIn: https://www.linkedin.com/in/thishani-lucas/
>>> *
>>>
>>>
>>> 
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>
>>
>> --
>> *Dileesha Rajapakse*
>> Software Engineer | WSO2 Inc.
>> Mobile: +94 772555933
>> http://www.dilee.me
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Shakila Sasikaran
> Software Engineer
> Mobile :+94 (0) 77 526 6848
> shak...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Sending Data Over TCP

2018-08-21 Thread Lahiru Madushanka

Hi Amit,

Please refer to this [1] documentation. ( contains a sample )

[1] https://docs.wso2.com/display/ESB500/TCP+Transport

Thanks,
Lahiru

On Tue, Aug 21, 2018 at 5:28 PM Amit Gupta  wrote:

> Hi ,
>
> I have created a proxy in wso2 esb wherin i can receive data over TCP from
> external parties.
> However my requirement is that i need to develop a proxy wherein esb sends
> request over TCP and then receives a response and then process the response
> further.
>
> Any leads on this or any example will be helpful for me.
>
> Thanks,
>
> Amit Gupta
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Using Class mediator

2018-08-08 Thread Lahiru Madushanka

Hi Aman,

You can add the resulting string to the message context as a property

@Override
public boolean mediate(MessageContext messageContext) {
String result = "This is the resulting String";
messageContext.setProperty("sampleProperty",result);
return true;

Then, inside the proxy/API we can read that property as below


http://ws.apache.org/ns/synapse;
   name="testClass"
   startOnLoad="true"
   statistics="disable"
   trace="disable"
   transports="http,https">
   
  
 
 

 
 
  
   
   


Thanks,
Lahiru

On Wed, Aug 8, 2018 at 5:20 PM Aman Singh  wrote:

> Dear Lahiru,
>
> I have created a custom JAVA class, which produces a "string" as output on
> running that class.  In my WSO2 ESB, I am calling that class with help of
> Class Mediator.
>
> Can you please tell me how can I store the value returned by my JAVA class
> in say a LOG mediator or Property mediator or anything?
>
> Your help would be very much appreciated.
>
> Thank you,
> Aman.
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Requesting suggestions for micro integrator secure vault script name

2018-08-07 Thread Lahiru Madushanka

+1 to *micro-*securevault*.sh*

On Tue, Aug 7, 2018 at 5:19 PM Hasitha Hiranya  wrote:

> Hi Arshardh,
>
> I am +1 for the simple name "*securevault*"
>
> Thanks
>
> On Tue, Aug 7, 2018 at 10:36 AM Arshardh Ifthikar 
> wrote:
>
>> Hi all,
>> The Micro Integrator profile of the Enterprise Integrator, did not
>> support secure vault [1]. One reason for this was, the absence of an user
>> interface to add new entries to the secure vault.
>>
>> Since the micro integrator does not consist of a management console,
>> users will be given the opportunity to add entries to the micro integrator
>> secure vault via executing a script. Once the user enters the alias and the
>> password, the entry will be stored in the micro integrator registry as
>> properties, and will be used subsequently for the vault-lookup function.
>>
>> [image: image.png]
>>
>> The above mentioned script located within the micro integrator bin
>> folder, needs an appropriate name. This particular script is currently
>> named, "*securevault*". Please mention any suggestions for a different
>> name.
>>
>> [1]
>> https://docs.wso2.com/display/EI630/Working+with+Passwords+in+the+ESB+profile
>>
>> Thanks,
>> Arshardh
>>
>> --
>> *Arshardh Ifthikar*
>> Software Engineer | WSO2 Inc.
>>
>> Email: arsha...@wso2.com
>> Mobile: +94719806525
>> Web: http://wso2.com
>>
>> 
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
> --
> *Hasitha Abeykoon*
> Associate Technical Lead; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Storing logs in a File

2018-07-31 Thread Lahiru Madushanka

Hi Aman,

You can try per-service [1] and per-API [2] logging to take logs from
specific proxy/API.
In the log4j configs, you can configure the log level, file location, log
pattern etc ...

[1] https://docs.wso2.com/display/ESB481/Per-Service+Logs+in+WSO2+ESB
[2] https://docs.wso2.com/display/ESB490/Per-API+Logs+in+WSO2+ESB

Thanks,
Lahiru

On Tue, Jul 31, 2018 at 9:52 AM Aman Singh  wrote:

> Hi Team,
>
> Can someone explain me how we can store all the logs which LOG mediator
> holds in a file??
>
> Any help would be appreciated.
>
> Thank you,
> Aman.
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

2018-06-16 Thread Lahiru Madushanka

Hi all,

Tested the following

Ubuntu Windows
Test EI micro-integrator EI + MI
JMS inbound endpoint ✓ ✓ ✓
JMS listener proxy ✓ ✓ ✓
JMS publisher proxy ✓ ✓ ✓
JMS message Store ✓ ✓ ✓
JMS transaction and rollback ✓ ✓
Message sampling processor ✓ ✓ ✓
Class mediator ✓ ✓ ✓
Data Mapper mediator (using CAPP) ✓ ✓

Smoke test management console of all profiles in windows
✓
[+] Stable - go ahead and release

Thanks,
Lahiru

On Sat, Jun 16, 2018 at 1:11 AM Malaka Gangananda  wrote:

> Hi All,
>
> We are pleased to announce the second release candidate of WSO2 Enterprise
> Integrator 6.3.0.
>
> Known issues: https://github.com/wso2/product-ei/issues
>
> Source and binary distribution files:
> https://github.com/wso2/product-ei/releases/tag/v6.3.0-rc2
>
> The tag to be voted upon:
> https://github.com/wso2/product-ei/tree/v6.3.0-rc2
>
> Please vote as follows:
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> ~The WSO2 Integration Team~
>
> Thanks,
>
>
> --
> Malaka.
> --
> Malaka Gangananda - Software Engineer | WSO2
> Email : mala...@wso2.com
> Mobile : +94713564340
> Web : http://wso2.com
>   
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] Error occurred while connecting to back end

2018-02-19 Thread Lahiru Madushanka

Hi all,

Got the same issue for MB 3.2.0 when running integration tests.

Workaround :-
replace jks files inside test suit -> resources -> keystore.products folder
from jks files taken from a wum updated MB 3.2.0 pack.

Thanks,
Lahiru

On Wed, Dec 13, 2017 at 9:10 AM, Viduranga Gunarathne 
wrote:

> Hi,
>
> Please find the link below
>
> https://stackoverflow.com/questions/23322676/javax-net-
> ssl-sslhandshakeexception-sun-security-validator-validatorexception
>
> Thanks,
> Viduranga
>
> On Tue, Dec 12, 2017 at 9:35 PM, Senuwan Withana  wrote:
>
>> Thank Guys, I will look into it.
>>
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> On Tue, Dec 12, 2017 at 7:23 PM, Godwin Shrimal  wrote:
>>
>>> Hi Senuwan,
>>>
>>> Check the validity period of the certificate of the ESB. Maybe it's
>>> expired.
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Tue, Dec 12, 2017 at 6:41 PM, Senuwan Withana 
>>> wrote:
>>>
 Hi Abimaran,

 Well, I did not generate any certificate. What I did was, tried to
 create an API using WSO2 API Manager, Publisher. When I was adding
 Production Endpoint that mentioned error was popping up.

 Thanks.
 *Senuwan Withana*
 Software Engineer - Support Team | WSO2

 Email : senu...@wso2.com
 Mobile: 94773212853
 Web: http://www.wso2.com



 On Tue, Dec 12, 2017 at 5:06 PM, Abimaran Kugathasan  wrote:

> Hi Senuwan,
>
> By checking your exception, it says, your certificate is expired. You
> have to generate a new certificate.
>
> Caused by: java.security.cert.CertificateExpiredException: NotAfter:
> Mon Jun 19 14:43:07 IST 2017
>
> On Tue, Dec 12, 2017 at 4:41 PM, Senuwan Withana 
> wrote:
>
>> Hi Team,
>>
>> I got below error when I'm trying to connect my ESB proxy into the
>> API Manager.  Any suggestion to solve this error?
>>
>>
>> [2017-12-12 16:38:56,137] ERROR - APIProviderHostObject Error
>> occurred while connecting to backend : https://localhost:8243/service
>> s/EmailSender, reason : sun.security.validator.ValidatorException:
>> PKIX path validation failed: 
>> java.security.cert.CertPathValidatorException:
>> timestamp check failed
>> javax.net.ssl.SSLHandshakeException: 
>> sun.security.validator.ValidatorException:
>> PKIX path validation failed: 
>> java.security.cert.CertPathValidatorException:
>> timestamp check failed
>> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
>> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
>> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
>> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHa
>> ndshaker.java:1514)
>> at sun.security.ssl.ClientHandshaker.processMessage(ClientHands
>> haker.java:216)
>> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
>> at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
>> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
>> cketImpl.java:1375)
>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
>> java:1403)
>> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
>> java:1387)
>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>> ocketFactory.java:533)
>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>> ocketFactory.java:401)
>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
>> enConnection(DefaultClientConnectionOperator.java:178)
>> at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(M
>> anagedClientConnectionImpl.java:304)
>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
>> t(DefaultRequestDirector.java:610)
>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
>> efaultRequestDirector.java:445)
>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
>> tractHttpClient.java:863)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:82)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:106)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>> eableHttpClient.java:57)
>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.sen
>> dHttpHEADRequest(APIProviderHostObject.java:4781)
>> at org.wso2.carbon.apimgt.hostobjects.APIProviderHostObject.jsF
>> unction_isURLValid(APIProviderHostObject.java:4173)

Re: [Dev] Fix wso2/product-ei/issues/1760

2018-01-21 Thread Lahiru Madushanka

Hi Malaka,

Thanks



On Mon, Jan 22, 2018 at 10:06 AM, Malaka Gangananda <mala...@wso2.com>
wrote:

> Hi Lahiru,
>
> Changes have been committed.
>
> Thanks,
>
> On Mon, Jan 22, 2018 at 9:55 AM, Malaka Gangananda <mala...@wso2.com>
> wrote:
>
>> Hi Lahiru,
>>
>> I will do the needful.
>>
>> Thanks,
>>
>> On Mon, Jan 22, 2018 at 9:51 AM, Lahiru Madushanka <lahirum...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> This issue is fixed now.
>>>
>>> I am attaching the diff of the fix below.
>>>
>>> Could someone please add this to the SVN
>>>
>>> Thanks,
>>> Lahiru
>>>
>>
>>
>>
>> --
>> Malaka.
>> --
>> Malaka Gangananda - Software Engineer | WSO2
>> Email : mala...@wso2.com
>> Mobile : +94713564340 <+94%2071%20356%204340>
>> Web : http://wso2.com
>>   <http://wso2.com/signature>
>>
>
>
>
> --
> Malaka.
> --
> Malaka Gangananda - Software Engineer | WSO2
> Email : mala...@wso2.com
> Mobile : +94713564340 <+94%2071%20356%204340>
> Web : http://wso2.com
>   <http://wso2.com/signature>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fix wso2/product-ei/issues/1760

2018-01-21 Thread Lahiru Madushanka

Hi all,

This issue is fixed now.

I am attaching the diff of the fix below.

Could someone please add this to the SVN

Thanks,
Lahiru
Index: 
modules/core/src/main/java/org/apache/synapse/config/SynapseConfigUtils.java
===
--- 
modules/core/src/main/java/org/apache/synapse/config/SynapseConfigUtils.java
(revision 55887)
+++ 
modules/core/src/main/java/org/apache/synapse/config/SynapseConfigUtils.java
(working copy)
@@ -447,16 +447,19 @@
 "HostName verification disabled");
 }
 
-connection.setHostnameVerifier(new 
javax.net.ssl.HostnameVerifier() {
-public boolean verify(String hostname, 
javax.net.ssl.SSLSession session) {
+HostnameVerifier hostnameVerifier = new HostnameVerifier() 
{
+@Override
+public boolean verify(String hostname, SSLSession 
sslSession) {
 if (log.isTraceEnabled()) {
 log.trace("HostName verification disabled");
 log.trace("Host:   " + hostname);
-log.trace("Peer Host:  " + 
session.getPeerHost());
+log.trace("Peer Host:  " + 
sslSession.getPeerHost());
 }
 return true;
 }
-});
+};
+connection.setHostnameVerifier(hostnameVerifier);
+
 } else {
 if (log.isDebugEnabled()) {
 log.debug("Using default HostName verifier...");
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Summarization of JSON data in DAS

2017-08-20 Thread Lahiru Madushanka

Hi Grainier,

Thanks for the reply. I had a discussion with Nirmal and the final solution
was to use Siddhi Map extension as you also suggesting.
However we change our approach later to push avg data directly from the
device agent, than computing them in DAS. (EDGE analytics)

Anyway thanks for the reply, we can use the suggested approach in future
cases.

Regards,
Lahiru


On Mon, Aug 21, 2017 at 8:20 AM, Grainier Perera <grain...@wso2.com> wrote:

> Hi Lahiru,
>
> You can achieve that by using JSON custom mapping [1] + Siddhi MAP
> extension + IfThenElse (optional to check the availability of attributes).
> Basically what you have to do is, have a;
>
> JSON structure like this;
>
>>
>> {
>>"userData": {
>>"timestamp": 19900813115534,
>>
>> *"dataMap": {*
>>
>> *  "id": 1, // these will be your arbitary data
>> "name": grainier**   }*
>>}
>>}
>> }
>
>
> Input mapping like this;
>
>> 
>
>    // other mappings
>
>
>>
>>
>> *
>>   ***
>> 
>
>
> Stream definition like this;
>
>> {
>>   "streamId": "org.wso2.event.user.stream:1.0.0",
>>   "name": "org.wso2.event.user.stream",
>>   "version": "1.0.0",
>>   "nickName": "",
>>   "description": "",
>>   "metaData": [],
>>   "correlationData": [],
>>   "payloadData": [
>> {
>>   "name": "timestamp",
>>   "type": "LONG"
>> },
>>
>>
>>
>> *{  "name": "userData",  "type": "STRING"**}*
>>   ]
>> }
>
>
> Finally within the execution plan;
>
>> @Import('org.wso2.event.user.stream:1.0.0')
>> define stream dataIn (timestamp long, *userData** string*);
>>
>
>
> from dataIn
>> select *map:createFromJSON(**userData) as userData**Map*
>> insert into tempStream;
>
>
>
> from tempStream
>>
>> *select map:get(userDataMap, "id") as id, map:get(userDataMap, "name") as
>> name*insert into tempStream2;
>
>
>
> -- now you can use those arbitary fields here...
>
>
>
> Hope that helped...
>
> [1] https://docs.wso2.com/display/CEP420/Input+Mapping+
> Types#InputMappingTypes-JSONinputmappingJSONInputMapping
> [2] https://docs.wso2.com/display/CEP420/Map+Extension
>
> Regards,
> Grainier.
>
> On Sat, Jul 8, 2017 at 11:34 AM, Lahiru Madushanka <lahirum...@wso2.com>
> wrote:
>
>> Hi Nirmal,
>>
>> Documentation says arbitrary data support can be used with wso2event
>> input format. But in my case its "JSON".
>> Custom event receiver will be an option. But is there a way I can do this
>> without writing a custom event receiver ?
>>
>> Thanks for the help.
>>
>> Regards,
>> Lahiru
>>
>> On Sat, Jul 8, 2017 at 10:02 AM, Nirmal Fernando <nir...@wso2.com> wrote:
>>
>>> Check on arbitrary data support https://docs.wso2.com/
>>> display/DAS310/Input+Mapping+Types
>>>
>>> On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka <lahirum...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I have a requirement where data values published to DAS are not
>>>> predefined (dynamic)
>>>> ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
>>>> Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores":
>>>> 4}
>>>> This JSON string will be changed with no of cores in the PC which
>>>> pushes the data.
>>>>
>>>> Is there a way I can write a summarization query in siddhiql to take
>>>> average of average corePercentages for a time interval. (first take avg of
>>>> percentage values and then average it over time )
>>>>
>>>> Thanks
>>>> Lahiru
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Technical Lead, WSO2 Inc.
>>> Mobile: +94715779733 <+94%2071%20577%209733>
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Grainier Perera
> Senior Software Engineer
> Mobile : +94716122384 <+94%2071%20612%202384>
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 4

2017-08-14 Thread Lahiru Madushanka

Hi all,

I tested

Virtual Fire Alarm
Connected Cup

No blockers were found

[+] Stable - Go ahead and release.

Thanks,
Lahiru


On Mon, Aug 14, 2017 at 4:48 PM, Sumedha Rubasinghe 
wrote:

> I tested following:
> Virtual firealarm (control operations,analytics - realtime & batch)
> Android Device Mgt(enrollment, ring, message)
> Device Type creation (HTTP,MQTT)
> Device pushing data (via API)
>
> No blockers were found.
>
> [+] Stable - Go ahead and release.
>
> Thanks,
> Sumedha
>
>
>
> On Mon, Aug 14, 2017 at 3:07 PM, Pubudu D.P  wrote:
>
>> Hi all,
>>
>> Tested following areas on Windows and Mac with an Android device.
>>
>>- Device enrollment
>>- Push notifications
>>- Device grouping
>>- Device location
>>- Geo Fencing
>>- Device status update
>>- Device search
>>- Operations
>>- Policy
>>- App install
>>
>> Also, verified bug fixes at [1].
>>
>> [1] https://github.com/wso2/product-iots/issues?utf8=%E2%9C%
>> 93=is%3Aissue%20label%3A3.1.0-RC3%20is%3Aclosed%20author%3Apubudup%20
>>
>> No blocking issues encountered.
>>
>> [+] Stable - Go ahead and release.
>>
>> Cheers,
>> Pubudu D.P
>> Senior Software Engineer - QA Team | WSO2 inc.
>> Mobile : +94775464547 <077%20546%204547>
>>
>> Linkedin: https://uk.linkedin.com/in/pubududp
>> Medium: https://medium.com/@pubududp
>>
>>
>> On Sun, Aug 13, 2017 at 10:13 PM, Megala Uthayakumar 
>> wrote:
>>
>>> Hi,
>>>
>>> I tested followings
>>>
>>>- Mobile Device and App Management Quick Start guide with android.
>>>- User Management and Role Management functionalities through device
>>>management console.
>>>- Android device enrollment as a normal user. Tested with some
>>>operations as well.
>>>- Android sense enrollment as a normal user. Was able to see the
>>>relevant graphs.
>>>
>>> Did not encounter any issues. Hence,
>>> [+] Stable - Go ahead and release.
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Megala
>>>
>>> On Fri, Aug 11, 2017 at 7:06 PM, Milan Perera  wrote:
>>>
 Hi Devs,

 We are pleased to announce the release candidate version 4 of WSO2 IoT 
 Server
 3.1.0.

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.

 Known issues : https://github.com/wso2/product-iots/issues-RC4
 

 Source and binary distribution files:
 https://github.com/wso2/product-iots/releases/tag/v3.1.0-RC4

 The tag to be voted upon:
 https://github.com/wso2/product-iots/tree/v3.1.0-RC4

 Please vote as follows.
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 Thank you

 Regards,
 --
 *Milan Perera *| Senior Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 77 309 7088 | Work: +94 11 214 5345
 Email: mi...@wso2.com  | Web: www.wso2.com
 
 

>>>
>>>
>>>
>>> --
>>> Megala Uthayakumar
>>>
>>> Software Engineer
>>> Mobile : 0779967122 <077%20996%207122>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Summarization of JSON data in DAS

2017-07-08 Thread Lahiru Madushanka

Hi Nirmal,

Documentation says arbitrary data support can be used with wso2event input
format. But in my case its "JSON".
Custom event receiver will be an option. But is there a way I can do this
without writing a custom event receiver ?

Thanks for the help.

Regards,
Lahiru

On Sat, Jul 8, 2017 at 10:02 AM, Nirmal Fernando <nir...@wso2.com> wrote:

> Check on arbitrary data support https://docs.wso2.com/
> display/DAS310/Input+Mapping+Types
>
> On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka <lahirum...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> I have a requirement where data values published to DAS are not
>> predefined (dynamic)
>> ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
>> Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores": 4}
>> This JSON string will be changed with no of cores in the PC which pushes
>> the data.
>>
>> Is there a way I can write a summarization query in siddhiql to take
>> average of average corePercentages for a time interval. (first take avg of
>> percentage values and then average it over time )
>>
>> Thanks
>> Lahiru
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Technical Lead, WSO2 Inc.
> Mobile: +94715779733 <+94%2071%20577%209733>
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Summarization of JSON data in DAS

2017-07-07 Thread Lahiru Madushanka

Hi all,

I have a requirement where data values published to DAS are not predefined
(dynamic)
( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores": 4}
This JSON string will be changed with no of cores in the PC which pushes
the data.

Is there a way I can write a summarization query in siddhiql to take
average of average corePercentages for a time interval. (first take avg of
percentage values and then average it over time )

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

Re: [Dev] New device type for IOTS ( Laptop agent )

2017-07-06 Thread Lahiru Madushanka

Hi Waruna,

We will have some notification mechanisms in IOTS for infra / team lead
level users.
Ex:-  RAM capacity of device profile X is 8GB, when avg RAM usage of IOT
group + profile X machines reach 7GB IOT team leads and infra team must
receive notifications.

Sure, I will update this thread with the progress.

Thanks all of you guys for the suggestions. I gathered lot more use cases
and different viewpoints.

Thanks,
Lahiru

On Thu, Jul 6, 2017 at 12:13 PM, Waruna Jayaweera <waru...@wso2.com> wrote:

> Hi Lahiru,
>
> Few Suggestions. You can also add alerts mechanism like [1] based on
> analysed data. As an example if laptop cpu utilization is more than 90%
> then send email to operation user.
>
> As others said you can reuse most of existing components for dashboard and
> analysis. Your sample use cases are applied for any device types as we can
> use same way to do predicative maintenance in iot devices. If we have new
> device type , send some attributes to server and take some decisions. So
> you can come up with documentation as if as how we can reuse those
> components to support similar use cases in any device type/agent.
>
> [1]https://docs.wso2.com/display/DAS310/Creating+Alerts
>
> Thanks,
> Waruna
>
>
>
> On Thu, Jul 6, 2017 at 11:04 AM, Lahiru Madushanka <lahirum...@wso2.com>
> wrote:
>
>> Hi Harshan,
>>
>> Sorry for the unclarity of my initial statement. This is a continuation
>> of "Laptop" device type developed by Thisari.
>> Yeah the process is same as you explained.
>>
>> Thanks
>>
>> On Thu, Jul 6, 2017 at 10:16 AM, Harshan Liyanage <hars...@wso2.com>
>> wrote:
>>
>>> Hi Lahiru,
>>>
>>> Could you please clarify why we need a new device-type in this scenario?
>>> It looks like a feature on-top of "PC" or "Laptop" device-type.
>>> Analytics/ML part can be separated from the device-type. What we need to do
>>> is to just get the required data like RAM, CPU, HDD usage etc from that
>>> particular device type and push them into DAS. This is somewhat similar to
>>> what we are currently doing with the Android device-type. I'm wondering why
>>> we can't use the same approach here.
>>>
>>> Thanks,
>>>
>>> Harshan Liyanage
>>> EMM/IoT TG
>>> Mobile: *+94765672894*
>>> Email: hars...@wso2.com
>>> Blog : http://harshanliyanage.blogspot.com/
>>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>>> lean.enterprise.middleware.
>>>
>>> On Wed, Jul 5, 2017 at 10:57 PM, Pasindu Jayaweera <pasin...@wso2.com>
>>> wrote:
>>>
>>>> Hi Lahiru,
>>>> Q.) Other than pushing data from the laptop, will there be any
>>>> operations or policies than can be applied from the server-side?
>>>>
>>>> Q) What could be the agent's behavior;
>>>>
>>>> a.) when the laptop is out of the network?
>>>>
>>>> b.) when the laptop has multiple operating systems?
>>>>
>>>>
>>>> When designing analytics views and creating ML plans, I would like to
>>>> suggest to make them in such a way that those units can be plugged not only
>>>> with the laptops, but also with any device type that provide the same stats
>>>> that you are planning to get from the laptops at this moment. Because the
>>>> stats like RAM, CPU utilization can be fetched from most of the other
>>>> devices as well.  So that upon the use case, those device types can reuse
>>>> the same unit in future. WDYT?
>>>>
>>>> Thanks.
>>>>
>>>> On Wed, Jul 5, 2017 at 8:19 PM, Lahiru Madushanka <lahirum...@wso2.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Currently I am working on a new device type for IOTS which can collect
>>>>> stats from Laptops and use them for analytics and decision making process.
>>>>> This is achieved by an agent running on PC which pushes collected stats to
>>>>> the IOTS in given time intervals.
>>>>>
>>>>> Sample use case 1 :- Average ram / CPU utilization of team X can be
>>>>> use as a measurement when buying new PCs for team X.
>>>>>
>>>>> Sample use case 2 :- Prediction of average memory requirement of team
>>>>> X for next year
>>>>>
>>>>> Development Phases
>>>>>
>>>>> Phase 1
>>>>> Devel

Re: [Dev] New device type for IOTS ( Laptop agent )

2017-07-05 Thread Lahiru Madushanka

Hi Harshan,

Sorry for the unclarity of my initial statement. This is a continuation of
"Laptop" device type developed by Thisari.
Yeah the process is same as you explained.

Thanks

On Thu, Jul 6, 2017 at 10:16 AM, Harshan Liyanage <hars...@wso2.com> wrote:

> Hi Lahiru,
>
> Could you please clarify why we need a new device-type in this scenario?
> It looks like a feature on-top of "PC" or "Laptop" device-type.
> Analytics/ML part can be separated from the device-type. What we need to do
> is to just get the required data like RAM, CPU, HDD usage etc from that
> particular device type and push them into DAS. This is somewhat similar to
> what we are currently doing with the Android device-type. I'm wondering why
> we can't use the same approach here.
>
> Thanks,
>
> Harshan Liyanage
> EMM/IoT TG
> Mobile: *+94765672894*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
> lean.enterprise.middleware.
>
> On Wed, Jul 5, 2017 at 10:57 PM, Pasindu Jayaweera <pasin...@wso2.com>
> wrote:
>
>> Hi Lahiru,
>> Q.) Other than pushing data from the laptop, will there be any operations
>> or policies than can be applied from the server-side?
>>
>> Q) What could be the agent's behavior;
>>
>> a.) when the laptop is out of the network?
>>
>> b.) when the laptop has multiple operating systems?
>>
>>
>> When designing analytics views and creating ML plans, I would like to
>> suggest to make them in such a way that those units can be plugged not only
>> with the laptops, but also with any device type that provide the same stats
>> that you are planning to get from the laptops at this moment. Because the
>> stats like RAM, CPU utilization can be fetched from most of the other
>> devices as well.  So that upon the use case, those device types can reuse
>> the same unit in future. WDYT?
>>
>> Thanks.
>>
>> On Wed, Jul 5, 2017 at 8:19 PM, Lahiru Madushanka <lahirum...@wso2.com>
>> wrote:
>>
>>>
>>> Hi all,
>>>
>>> Currently I am working on a new device type for IOTS which can collect
>>> stats from Laptops and use them for analytics and decision making process.
>>> This is achieved by an agent running on PC which pushes collected stats to
>>> the IOTS in given time intervals.
>>>
>>> Sample use case 1 :- Average ram / CPU utilization of team X can be use
>>> as a measurement when buying new PCs for team X.
>>>
>>> Sample use case 2 :- Prediction of average memory requirement of team X
>>> for next year
>>>
>>> Development Phases
>>>
>>> Phase 1
>>> Developing the initial agent which runs on PC and publish statistics to
>>> the IoTS through the MB.
>>> Creating event receivers / publishers and execution plans in DAS to
>>> handle data.
>>> Creating initial analytics and real time analytics views for a single
>>> device
>>>
>>> Phase 1 was already done by Thisari Patabendi.
>>>
>>> Phase 2
>>> Adding "Device profiles" to the device database.
>>> Data purging and summarization
>>> Implementing group analytics view for roles "team lead" and "infra level
>>> user".
>>>
>>> Phase 3
>>> Collect data by running agent on several test machines.
>>> Applying analytics on collected data and create ML plan.
>>> Creating analytic result dashboards
>>>
>>> Suggestions are highly appreciated.
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "WSO2 IoT Team Group" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to iot-group+unsubscr...@wso2.com.
>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>>
>>
>>
>>
>> --
>> *Pasindu Jayaweera*
>> Software Engineer | WSO2 Inc
>> Mobile: +94 718187375 <+94%2071%20818%207375>
>> Blog: blog.pasindujayaweera.com
>> <http://wso2.com/signature>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to iot-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] New device type for IOTS ( Laptop agent )

2017-07-05 Thread Lahiru Madushanka

Hi Pasidu,

Q1) We are planning to apply policies like restricting the removal of agent
from the laptop. However these capabilities will be saved for another phase
after the core functionalities are done. I will update this thread once we
start those implementations.

Q2) a) We can save data in the client side until the connection established
again. However exact implementation will change with the data purging plain
in DAS.
   b) This will depend on the use case. If infra team installing OS
behalf of the users they can install agent in all operating systems. If
users are allowed the change / add operating systems they have to install
agent by them-self. We will have a unified agent for all 3 operating
systems.

Yeah, that's possible. For this device type also we can reuse some units
from Android Sense dashboard.

Thank you very much for for pointing out these information.

On Wed, Jul 5, 2017 at 10:57 PM, Pasindu Jayaweera <pasin...@wso2.com>
wrote:

> Hi Lahiru,
> Q.) Other than pushing data from the laptop, will there be any operations
> or policies than can be applied from the server-side?
>
> Q) What could be the agent's behavior;
>
> a.) when the laptop is out of the network?
>
> b.) when the laptop has multiple operating systems?
>
>
> When designing analytics views and creating ML plans, I would like to
> suggest to make them in such a way that those units can be plugged not only
> with the laptops, but also with any device type that provide the same stats
> that you are planning to get from the laptops at this moment. Because the
> stats like RAM, CPU utilization can be fetched from most of the other
> devices as well.  So that upon the use case, those device types can reuse
> the same unit in future. WDYT?
>
> Thanks.
>
> On Wed, Jul 5, 2017 at 8:19 PM, Lahiru Madushanka <lahirum...@wso2.com>
> wrote:
>
>>
>> Hi all,
>>
>> Currently I am working on a new device type for IOTS which can collect
>> stats from Laptops and use them for analytics and decision making process.
>> This is achieved by an agent running on PC which pushes collected stats to
>> the IOTS in given time intervals.
>>
>> Sample use case 1 :- Average ram / CPU utilization of team X can be use
>> as a measurement when buying new PCs for team X.
>>
>> Sample use case 2 :- Prediction of average memory requirement of team X
>> for next year
>>
>> Development Phases
>>
>> Phase 1
>> Developing the initial agent which runs on PC and publish statistics to
>> the IoTS through the MB.
>> Creating event receivers / publishers and execution plans in DAS to
>> handle data.
>> Creating initial analytics and real time analytics views for a single
>> device
>>
>> Phase 1 was already done by Thisari Patabendi.
>>
>> Phase 2
>> Adding "Device profiles" to the device database.
>> Data purging and summarization
>> Implementing group analytics view for roles "team lead" and "infra level
>> user".
>>
>> Phase 3
>> Collect data by running agent on several test machines.
>> Applying analytics on collected data and create ML plan.
>> Creating analytic result dashboards
>>
>> Suggestions are highly appreciated.
>>
>> Thanks.
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to iot-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>
>
>
> --
> *Pasindu Jayaweera*
> Software Engineer | WSO2 Inc
> Mobile: +94 718187375 <+94%2071%20818%207375>
> Blog: blog.pasindujayaweera.com
> <http://wso2.com/signature>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] DAS visualization recommendation system

2016-08-02 Thread Lahiru Madushanka

Hi all,

We are a group of final year students at CSE .
We are developing a context aware visualization recommendation system for
our final year project.

We need to know some facts about data extraction process of DAS.

Is it capable of automatically identifying inter column hierarchies,
relationships, context etc.

If so can you please direct us to some resources.

Thanks

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.6.0 RC3

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.6.0 RC2

Re: [Dev] How to use external property file in ESB 6.3

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

Re: [Dev] [VOTE] Release WSO2 Enterprise Integrator 6.5.0 RC1

Re: [Dev] WSDL based proxy for SOAP Calculator

Re: [Dev] Using clone and aggregator in the same sequence

Re: [Dev] API Manager - Retrieving JSON Payload During Mediation

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.4.0 RC1

Re: [Dev] Sending Data Over TCP

Re: [Dev] Using Class mediator

Re: [Dev] Requesting suggestions for micro integrator secure vault script name

Re: [Dev] Storing logs in a File

Re: [Dev] [Architecture] [VOTE] Release WSO2 Enterprise Integrator 6.3.0 RC2

Re: [Dev] [APIM] Error occurred while connecting to back end

Re: [Dev] Fix wso2/product-ei/issues/1760

[Dev] Fix wso2/product-ei/issues/1760

Re: [Dev] Summarization of JSON data in DAS

Re: [Dev] [Architecture] [VOTE] Release of WSO2 IoT Server 3.1.0 RC version 4

Re: [Dev] Summarization of JSON data in DAS

[Dev] Summarization of JSON data in DAS

Re: [Dev] New device type for IOTS ( Laptop agent )

Re: [Dev] New device type for IOTS ( Laptop agent )

Re: [Dev] New device type for IOTS ( Laptop agent )

[Dev] DAS visualization recommendation system

26 matches

Site Navigation

Mail list logo

Footer information