Re: [Dev] Update on Kubernetes setup

[Imesh Gunaratne]

​Hi Abhishek,​

On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Imesh,
>
> Most important issue was the IP address of docker container is not
> accessibly directly, so I added a config in the test-config.json to specify
> docker-machine ip address. If it is not present, I try to get the IP
> address of the docker container.
>

​Can you please explain why you are trying to access the containers on K8S
using their IP addresses from the external network? What's your approach?

Thanks

>
> Vishanth,
> I am still working on completing smoke tests so that I can make the
> end-to-end workflow. Once that is done, I will schedule the demo.
>
> Thanks
> Abhishek
>
> On Wed, Aug 3, 2016 at 11:23 AM, Imesh Gunaratne  wrote:
>
>> Hi Abhishek,
>>
>> Please always send mails to WSO2 Dev except when you have sensitive
>> information (such as credentials, etc) to share with us.
>>
>> On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I am able to run Kubernetes cluster on my Mac now and currently working
>>> on deploying ESB on it. I ran into few issues with test framework not
>>> working on Mac.
>>>
>>
>> ​
>> I
>> ​t would be better to be more specific on the errors.​
>>
>>>
>>> Mac uses docker-machine (OSX specific util) to create virtual hosts
>>> where it runs docker daemon, so its a bit different than Unix where daemon
>>> runs directly on host. The IP address of deployed container is not directly
>>> accessible, you need either create forwarding or go through
>>> docker-machine's IP address. There were bunch of other small changes that I
>>> had to do to make the test framework work across both Mac and Unix. Now
>>> that its done, I am working on deployment.
>>>
>>
>> ​What were the changes you did?
>>
>> Thanks
>> ​
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC Dockerfiles] Project update - Migration to Golang

[Vishanth Balasubramaniam]

Hi Abhishek,

I see that you have given absolute path for "TestConfigPath" in
"common/test-context.go". Why don't we give relative path from the project
directory for this?

Regards,
Vishanth

On Mon, Jul 11, 2016 at 5:22 PM, Imesh Gunaratne  wrote:

> Hi Abhishek,
>
> On Mon, Jul 11, 2016 at 1:53 PM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I have been working on migrating the WSO2 Dockerfiles test framework from
>> bash and python to use Golang. I must say, its been quite a ride but
>> finally the migration has been successful. I am happy to offload many
>> important features (logging, JSON parsing etc) to existing Golang packages.
>>
>
>> I have also implemented interval based polling with linear backoff for
>> exposed ports and carbon server status. The changes are committed to the
>> repo [1], would love to get your feedback/comments.
>>
>
> ​Very nice to hear this!​
>
> ​We will go through the code. May be you can arrange a session to review
> this.
>
>
>>
>> Since I am totally new to this language and completely blank on its
>> coding standards, I am following the coding standards used in the open
>> source Kubernetes [2].
>>
>
> ​+1 for following K8S coding standards. A bunch of Google developers are
> involved in that​
>
> ​project and AFAIK coding standards are at their best.
>
>>
>> I absolutely love Golang and those who are interested, I would highly
>> recommend gobyexample [3], I was able to get up to speed within hours.
>>
>
> ​Yeah [3] is really useful. We also did couple of sessions on Golang at
> WSO2 [4]
>
> [4] http://www.slideshare.net/imesh/an-introduction-to-go-55991343
>
> Thanks
> ​
>
>
>>
>> Thanks,
>> Abhishek
>>
>> [1]. https://github.com/abhishek0198/test-framework/
>> [2]. https://github.com/kubernetes/kubernetes
>> [3]. https://gobyexample.com/
>>
>
>
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
>
>


-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Installing Features to Carbon Server

[Eranda Rajapakshe]

Hi,

I am trying to install features to Carbon 4.4.7 from repo [1]
I need to install the feature "WSO2 Carbon - Tasks Core Feature" which has
the feature id of "org.wso2.carbon.ntask.core.feature.group". But this
feature doesn't get listed down as an Available Feature in the Carbon
server.

But when I looked into the content.xml in the p2-repo, that specific
feature is mentioned. Is this feature bundled inside another one (which is
listed in the Carbon server)?
How can I install this feature?

[1]. http://product-dist.wso2.com/p2/carbon/releases/wilkes/


Thanks,
-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update on Kubernetes setup

[Vishanth Balasubramaniam]

Alright Abhishek.

On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi Imesh,
>
> Most important issue was the IP address of docker container is not
> accessibly directly, so I added a config in the test-config.json to specify
> docker-machine ip address. If it is not present, I try to get the IP
> address of the docker container.
>
> Vishanth,
> I am still working on completing smoke tests so that I can make the
> end-to-end workflow. Once that is done, I will schedule the demo.
>
> Thanks
> Abhishek
>
> On Wed, Aug 3, 2016 at 11:23 AM, Imesh Gunaratne  wrote:
>
>> Hi Abhishek,
>>
>> Please always send mails to WSO2 Dev except when you have sensitive
>> information (such as credentials, etc) to share with us.
>>
>> On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari <
>> abhishek.tiwari0...@gmail.com> wrote:
>>
>>> Hi Mentors,
>>>
>>> I am able to run Kubernetes cluster on my Mac now and currently working
>>> on deploying ESB on it. I ran into few issues with test framework not
>>> working on Mac.
>>>
>>
>> ​
>> I
>> ​t would be better to be more specific on the errors.​
>>
>>>
>>> Mac uses docker-machine (OSX specific util) to create virtual hosts
>>> where it runs docker daemon, so its a bit different than Unix where daemon
>>> runs directly on host. The IP address of deployed container is not directly
>>> accessible, you need either create forwarding or go through
>>> docker-machine's IP address. There were bunch of other small changes that I
>>> had to do to make the test framework work across both Mac and Unix. Now
>>> that its done, I am working on deployment.
>>>
>>
>> ​What were the changes you did?
>>
>> Thanks
>> ​
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057
>> W: https://medium.com/@imesh TW: @imesh
>> lean. enterprise. middleware
>>
>>
>


-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC Project: HTTP Load Balancer on Top of WSO2 Gateway Discussion

[Isuru Ranawaka]

Hi venkat,

Yes we can. lets have a call today around 9.30 p.m

On Thu, Aug 4, 2016 at 9:34 AM, Venkat Raman  wrote:

> Hi Isuru,
>
> Good morning.  Yesterday night, I spoke with Kasun regarding the latest
> update on bench-mark results. Even without any locking performance is not
> good after concurrency of 5000.
>
> As you have done bench-mark till concurrency of 3000, we both would like
> to do bench-marking on raw carbon-transport upto concurrency of 10,000 and
> 1,00,000 requests so that we get an idea on this.
>
> How do we do that ? Will a simple response from engine suffice ?  Can I
> use LB to send simple response directly without doing any mediation ?
>
>
>
>
> *Thanks,*
> *Venkat.*
>
> On Thu, Aug 4, 2016 at 12:19 AM, Venkat Raman 
> wrote:
>
>> Hi Isuru,
>>
>> Please find the attached bench-mark results.  As discussed,  I've
>> disabled health-checking and removed synchronized block and used atomic
>> Integer in one test and also did a test without any kind of lock or use of
>> atomic integers.
>>
>> Throughput and latency results are positive.  But, after concurrency
>> level of 5000 it is not that good.  So even If we use read-write lock or
>> stamped lock, we will get performance little performance gain only.
>>
>> I feel that If we can do bench-mark with integration-server upto 1
>> concurrent connections we'll get a better idea.  Is that okay ?
>>
>>
>>
>>
>> *Thanks,*
>> *Venkat.*
>>
>> On Tue, Aug 2, 2016 at 9:39 PM, Venkat Raman 
>> wrote:
>>
>>> Hi Isuru & Kasun,
>>>
>>> Please find the findings from today's code review.
>>>
>>> 1) Locking in getNextLBOutboundEndpoint() method in algorithm
>>> implementation is causing over-head.  We have to find a way to efficiently
>>> handle communication between threads to reduce locking overhead.
>>>
>>> 2) Code repo freeze by August 15th for the sake of GSoC.  If we can find
>>> a way to overcome locking over-head before August 15th that changes will be
>>> added to code repo.  Otherwise it will be added after GSoC.
>>>
>>> 3) TPS, Latency and Memory graphs to be added.
>>>
>>> 4) Blog post and PDF documentation.
>>>
>>>
>>>
>>>
>>> *Thanks,*
>>> *Venkat.*
>>>
>>> On Mon, Aug 1, 2016 at 9:25 AM, Venkat Raman 
>>> wrote:
>>>
 Hi Isuru,

 Good morning.  Please find 10th week's progress.

 1) Had discussion with Kasun.
 2) As suggested, did performance bench-marking using Netty BE, and it
 turns out that our LB is beating Nginx till concurrency level of 6000 after
 which it is not performing well.
 I've attached the results.

 I've started a new thread as Conversation arrangement is not good in
 previous one.

 It would be great if we can have a code review Isuru.  Based on your
 feedback I'll be abe to make changes and we can do bench-marking again.
 Can we do it today 9:30 PM ?  We have only 2 full weeks more.  The last
 week will be for documentation.



 *Thanks,*
 *Venkat.*

>>>
>>>
>>
>


-- 
Best Regards
Isuru Ranawaka
M: +94714629880
Blog : http://isurur.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update on Kubernetes setup

[Abhishek Tiwari]

Hi Imesh,

Most important issue was the IP address of docker container is not
accessibly directly, so I added a config in the test-config.json to specify
docker-machine ip address. If it is not present, I try to get the IP
address of the docker container.

Vishanth,
I am still working on completing smoke tests so that I can make the
end-to-end workflow. Once that is done, I will schedule the demo.

Thanks
Abhishek

On Wed, Aug 3, 2016 at 11:23 AM, Imesh Gunaratne  wrote:

> Hi Abhishek,
>
> Please always send mails to WSO2 Dev except when you have sensitive
> information (such as credentials, etc) to share with us.
>
> On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi Mentors,
>>
>> I am able to run Kubernetes cluster on my Mac now and currently working
>> on deploying ESB on it. I ran into few issues with test framework not
>> working on Mac.
>>
>
> ​
> I
> ​t would be better to be more specific on the errors.​
>
>>
>> Mac uses docker-machine (OSX specific util) to create virtual hosts where
>> it runs docker daemon, so its a bit different than Unix where daemon runs
>> directly on host. The IP address of deployed container is not directly
>> accessible, you need either create forwarding or go through
>> docker-machine's IP address. There were bunch of other small changes that I
>> had to do to make the test framework work across both Mac and Unix. Now
>> that its done, I am working on deployment.
>>
>
> ​What were the changes you did?
>
> Thanks
> ​
>
> --
> *Imesh Gunaratne*
> Software Architect
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Disabling INFO logs per page rendering

[Rasika Perera]

Hi Dilan,

On 4 Aug 2016 06:23, "Dilan Udara Ariyaratne"  wrote:

>

> Hi Rasika,
>
> My specific requirement of this regard would be just enabling either
info, debug or error logs of the files that I explicitly specify at
somewhere configurable
> and disabling every log at anywhere else.
>
Yes. This is the exact requirement i am trying to address. You can keep the
jaggery conf log level into ERROR level. Which means your apps default log
level is ERROR. If you add only your particular logger package into INFO
from log4j.properties only that will print INFO messages.

>
> Regards,
> Dilan.
>
*> Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Wed, Aug 3, 2016 at 8:33 PM, Rasika Perera  wrote:

>>

>> Hi Sinthuja,
>>
>> Please find the inline comments.
>>

>>> AFAIU you mention here is the log4j.properties in the server level
isn't? In that case, IMO having the application log level overriding the
log4j.properties log level is correct, and I don't think that we need to
change.


>>
>>
>>  If you visualize the jaggery root logger(which will pick log level by 
>> jaggery.conf)
as below;
>>
>> log4j.logger.JAGGERY = INFO
>>
>> Allowing custom hierarchical log levels(log4j.properties) would be
something like this;
>>
>> log4j.logger.JAGGERY.app.modules.oauth.token-protected-service.js = ERROR
>>
>> In this case, for the logger named
"JAGGERY.app.modules.oauth.token-protected-service.js"; effective log level
should be ERROR right? Hence, in order to facilitate mentioned example, you
need to allow jaggery.conf log level to be overridden by log4j.properties
file. On the otherhand, by default it will pick the application-scope log
level. Whenever, you have explicitly mentioned log level for a particular
logging package name in log4j.properties it will override the default log
level. Without any modifications; is there any way to achieve it?
>>

>>> IMO I don't think this is possible, because I don't think all
developers will be having access to the file system of the server to modify
the server's log4j.properties (Eg: In cloud environment). And actually this
control needs to be within the application it self, so that the developer
can modify that regardless of the deployment.


>>
>> ​+1 for adding log4j.properties at the application level. Then we need
to think some sort of loading configuration file per each app and pass it
to the LogHostObject which is called when you add "new Log().info()" on
jaggery.
>>
>> My concern is that, for the time being, at least standalone(non-cloud)
developers who can access central log4j.properties file, can benefit with
the mentioned feature(hierarchical log levels), rather than having *single*
application-scope log level property for a given jaggery app.
>>
>> {
>>
>>   "displayName": "Carbon Device Management App",
>>   "logLevel": "error"
>> }
>>
>>
>> Thanks,
>> Rasika
>>
>> On Wed, Aug 3, 2016 at 5:03 PM, Sinthuja Ragendran 
wrote:

>>>

>>> Hi Rasika,
>>>
>>> On Wed, Aug 3, 2016 at 3:48 PM, Rasika Perera  wrote:



 [Adding Sinthuja & Manu]

 Hi Dilan and All,

 I have done a small fix to Jaggery Core level to support
log4j.properties file.

* Current Implementation*
 With the current jaggery implementation; All loggers created on
jaggery(.jag / .js) files will be calling LogHostObject.
On LogHostObject constructor; It will pick the current *application* scope
log level assigned by* jaggery.conf*[1] and setting current logger's log
level into that[2].

* Problem*
 With this approach, even you configure a custom log level through
log4j.properties file at the server level that configuration will be
overridden by application scope log level. This will make the debug hard;
since you cannot change log level on a particular package or file. Instead
it is applied at the application scope.
**
* Solution*
 Hence, I removed the overriding part from the LogHostObject and
implemented following rules;

 1. If a loglevel is set by* log4j.properties* it will get the
priority.
>>>
>>>
>>> AFAIU you mention here is the log4j.properties in the server level
isn't? In that case, IMO having the application log level overriding the
log4j.properties log level is correct, and I don't think that we need to
change. For example, by default the server level there will be default
configuration for all apps to have INFO log level, and if it's needed to be
changed to DEBUG log level by a particular application then it's that
application developer's decision.
>>>



 2. Otherwise, new logger will get the application scope log level set
by* jaggery.conf* file.




 PR is in https://github.com/wso2/jaggery/pull/164

* Example*
 Suppose you have following entries on js, jaggery.conf and
log4j.properties;

 >> 

[Dev] [IoTS] Failed to connect to the MQTT topic again after disconnect for a while in 1.0.0 alpha

[云展智创]

Hi all,

I downloaded a raspberry pi agent from IoTS 1.0.0 alpha, ran the raspberry pi 
agent and uploaded the temperature data successfully. But after I disconnected 
the agent for a while, the MQTT connection could not be setup again. Can anyone 
help me for this? Thanks.


MQTT_LISTENER: Connected with result code 4
MQTT_LISTENER: Subscribing with topic carbon.super/raspberrypi/rkwrklcphsmu


－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

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

[Dev] [IOTS] Failed to get realtime data from IoTS in 1.0.0 alpha

[云展智创]

Hi all,

When I open the IoTS devicemgt ui to view the realtime statistic data of my 
raspberry pi device, I always get below error, so that the graph can now show 
any temperature line. Can anyone help me? Thanks.

WebSocket connection to 
'wss://192.168.2.109:9443/secured-outputui/org.wso2.iot.devices.temperature/1.0.0?token=ecd222ae10d959deb02d3bf2b8f6=1iukwdj4luwxe=raspberrypi'
 failed: WebSocket opening handshake was canceled

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

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

Re: [Dev] [IoTS] when will the IoTS be GA?

[云展智创]

Hi Sumedha,

Any suggestions? Thanks.

－－
Zhanwen Zhou (Jason)
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: API Management, IOT

On Aug 2, 2016, at 12:45 PM, 云展智创  wrote:

> Hi Sumedha,
> 
> Any suggestions? Thanks.
> 
> －－
> Zhanwen Zhou (Jason), General Manager
> +86 13922218435
> zhanwen.z...@smartcloudex.com
> Guangzhou Smart Cloudex Technology Co., Ltd.
> Business: API Management, IOT
> 
> On Jul 31, 2016, at 9:20 PM, Sumedha Rubasinghe  wrote:
> 
>> Hi Jason,
>> UIs in IoTS Master is not fully functional due to on going work I mentioned 
>> b4.
>> 
>> Will get back to you with an alternative plan by tomorrow.
>> 
>> 
>> On Jul 31, 2016 2:48 PM, "云展智创"  wrote:
>> Hi Sumedha,
>> 
>> Yes, I thought the IoTS would be GA on mid of July. I have a project using 
>> IoTS to manage some smart devices. IoTS is the core backend component in the 
>> project.  I also need the cdmf-devicetype-archetype tools to create the 
>> plugins. Could you give me some advices on how to build the latest stable 
>> release from the code? 
>> 
>> by the way, I found that the real time device statistics data could not be 
>> showed on the graph of device view in 1.0.0 Alpha release. Is that a know 
>> error? Thanks.
>> 
>> －－
>> Zhanwen Zhou (Jason), General Manager
>> +86 13922218435
>> zhanwen.z...@smartcloudex.com
>> Guangzhou Smart Cloudex Technology Co., Ltd.
>> Business: API Management, IOT
>> 
>> On Jul 31, 2016, at 11:20 AM, Sumedha Rubasinghe  wrote:
>> 
>>> Hi Jason,
>>> After the IoTS 1.0.0 Alpha, we are in the middle of a strategic change 
>>> which involves our mobile device management capabilities. 
>>> As you may already be aware, we have brought down all core device 
>>> management capabilities into one level and implementing specific device 
>>> management plugins on top of this. These device management plugins also 
>>> cover our Android, iOS, Windows mobile plugins (as well as plugins for all 
>>> other devices).
>>> 
>>> Originally 1.0.0 GA release date of IoTS was scheduled for July. But due to 
>>> a customer commitment we have shifted our focus to stabilising Android 
>>> device management until end of August.
>>> 
>>> Specific new release date of IoTS 1.0.0 GA will be decided after August.
>>> 
>>> If you have a project that gets impacted due to this shift please fill up 
>>> our contact us form @ http://wso2.com/contact/ with your concern and we 
>>> will see what we can do.
>>>  
>>> Thanks,
>>> Sumedha
>>> 
>>> 
>>> On Sat, Jul 30, 2016 at 3:03 PM, 云展智创  wrote:
>>> Hi,
>>> 
>>> Could anyone tell me when will the IoTS be GA? Thanks a lot.
>>> 
>>> －－
>>> Zhanwen Zhou (Jason),
>>> +86 13922218435
>>> zhanwen.z...@smartcloudex.com
>>> Guangzhou Smart Cloudex Technology Co., Ltd.
>>> Business: API Management, IOT
>>> 
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>> 
>>> 
>>> 
>>> -- 
>>> /sumedha
>>> m: +94 773017743
>>> b :  bit.ly/sumedha
>> 
>> 
> 
> ___
> 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] Disabling INFO logs per page rendering

[Dilan Udara Ariyaratne]

Hi Rasika,

My specific requirement of this regard would be just enabling either info,
debug or error logs of the files that I explicitly specify at somewhere
configurable
and disabling every log at anywhere else.

I am not sure how I can achieve this capability by the approach that you
are proposing here.

Regards,
Dilan.

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


On Wed, Aug 3, 2016 at 8:33 PM, Rasika Perera  wrote:

> Hi Sinthuja,
>
> Please find the inline comments.
>
> AFAIU you mention here is the log4j.properties in the server level isn't?
>> In that case, IMO having the application log level overriding the
>> log4j.properties log level is correct, and I don't think that we need to
>> change.
>
>
>  If you visualize the jaggery root logger(which will pick log level by
> jaggery.conf) as below;
>
> log4j.logger.JAGGERY = INFO
>
> Allowing custom hierarchical log levels(log4j.properties) would be
> something like this;
>
> log4j.logger.JAGGERY.app.modules.oauth.token-protected-service.js = ERROR
>
> In this case, for the logger named
> "JAGGERY.app.modules.oauth.token-protected-service.js"; effective log level
> should be ERROR right? Hence, in order to facilitate mentioned example,
> you need to allow jaggery.conf log level to be overridden by
> log4j.properties file. On the otherhand, by default it will pick the
> application-scope log level. Whenever, you have explicitly mentioned log
> level for a particular logging package name in log4j.properties it will
> override the default log level. Without any modifications; is there any
> way to achieve it?
>
> IMO I don't think this is possible, because I don't think all developers
>> will be having access to the file system of the server to modify the
>> server's log4j.properties (Eg: In cloud environment). And actually this
>> control needs to be within the application it self, so that the developer
>> can modify that regardless of the deployment.
>
> ​+1 for adding log4j.properties at the application level. Then we need to
> think some sort of loading configuration file per each app and pass it to
> the LogHostObject which is called when you add "new Log().info()" on
> jaggery.
>
> My concern is that, for the time being, at least standalone(non-cloud)
> developers who can access central log4j.properties file, can benefit with
> the mentioned feature(hierarchical log levels), rather than having *single*
> application-scope log level property for a given jaggery app.
>
> {
>
>   "displayName": "Carbon Device Management App",
>   "logLevel": "error"
> }
>
>
> Thanks,
> Rasika
>
> On Wed, Aug 3, 2016 at 5:03 PM, Sinthuja Ragendran 
> wrote:
>
>> Hi Rasika,
>>
>> On Wed, Aug 3, 2016 at 3:48 PM, Rasika Perera  wrote:
>>
>>> [Adding Sinthuja & Manu]
>>>
>>> Hi Dilan and All,
>>>
>>> I have done a small fix to Jaggery Core level to support
>>> log4j.properties file.
>>>
>>> *Current Implementation*
>>> With the current jaggery implementation; All loggers created on
>>> jaggery(.jag / .js) files will be calling LogHostObject.
>>> On LogHostObject constructor; It will pick the current *application* scope
>>> log level assigned by *jaggery.conf*[1] and setting current logger's
>>> log level into that[2].
>>>
>>> *Problem*
>>> With this approach, even you configure a custom log level through
>>> log4j.properties file at the server level that configuration will be
>>> overridden by application scope log level. This will make the debug hard;
>>> since you cannot change log level on a particular package or file. Instead
>>> it is applied at the application scope.
>>>
>>> *Solution*
>>> Hence, I removed the overriding part from the LogHostObject and
>>> implemented following rules;
>>>
>>> 1. If a loglevel is set by *log4j.properties* it will get the priority.
>>>
>>
>> AFAIU you mention here is the log4j.properties in the server level isn't?
>> In that case, IMO having the application log level overriding the
>> log4j.properties log level is correct, and I don't think that we need to
>> change. For example, by default the server level there will be default
>> configuration for all apps to have INFO log level, and if it's needed to be
>> changed to DEBUG log level by a particular application then it's that
>> application developer's decision.
>>
>>
>>> 2. Otherwise, new logger will get the application scope log level set by
>>> *jaggery.conf* file.
>>>
>>
>>> PR is in https://github.com/wso2/jaggery/pull/164
>>>
>>> *Example*
>>> Suppose you have following entries on js, jaggery.conf and
>>> log4j.properties;
>>>
>>> >> token-protected-service-invokers.js
>>> var log = new Log(
>>> "app.modules.oauth.token-protected-service-invokers.js);
>>>
>>> >> jaggery.conf
>>> {
>>>
>>>   "displayName": "Carbon Device Management App",
>>>   "logLevel": "error"
>>> }
>>>
>>> >> log4.properties
>>>
>>> 

Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hi all,
Problem solved

On Thu, Aug 4, 2016 at 2:08 AM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Hello all,
> I tried to build a carbon component by referring to this[1] tutorial and
> my attempts keep getting failed. I couldn't get the wsdl doc generated for
> service. Tomcat returns 404 whenever I try that . Is there a way to find
> out whether a service is deployed in carbon sever by observing logs
> ?(without looking at the mgt console)
>
> B.r,
> Dinanjana
>
> [1] :
> http://wso2.com/library/tutorials/2014/03/how-to-create-a-feature-from-wso2-carbon-component/
>
> On Mon, Jul 25, 2016 at 1:59 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Hi Kasun,
>> Currently our solution has following capabilities.
>> Monitoring memory and CPU loads
>> Monitoring request load
>> Monitoring responsiveness of ESB.
>> Creating thread and heap dumps
>> Creating a report
>> Storing request count and relevant details in Derby embedded db
>> When any adverse effect taking place on esb this variables can indicate
>> that. Currently we are monitoring those aspects in an event based system.
>> Each event can be configured by the user by changing parameters in
>> respective config files. So when an anomaly detected by those monitors
>> respective event will be triggered. This will result in logging the event
>> in a report. Also thread dumps heap dumps will be collected according to
>> users specifications. We can schedule a demo on Wednesday preferably in the
>> night since I have an interview on the same day. I will confirm it once I
>> discuss this with my mentors
>>
>> On Jul 25, 2016 9:30 AM, "Kasun Indrasiri"  wrote:
>>
>>> What's the current state of this project? Shall we do a end to end demo
>>> on what you have done so far?
>>>
>>> On Tue, Jun 21, 2016 at 6:24 PM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Here are the minutes of the review meeting we had yesterda
 y
  -Some code refactoring was suggested. Reducing use of static variables
 and static methods was suggested.
  -As the next milestone adding user configurable esb issue reporting
 suggested. This will change the current implementation to event   base
 implementation.There will be pre defined events for monitoring tool.
   -E.g Out of memory event
  Configurable options :Memory threshold
  Outcomes (heap
 dumps,thread dumps)
  Frequency of extracting
 dumps

 - Creating a class diagram



 On Wed, Jun 1, 2016 at 10:13 PM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Hello all,
>
> Progress of the tool so far
>
> The tool can be deployed in a remote machine to monitor ESB instance.
> It connects to MBanServer of the targeted machine through RMI. Currently 
> it
> monitors memory usage, CPU usage and Network traffic of the ESB. Network
> traffic details are gathered through PassThruHttpSender/receiver mbeans.
> These metrics values are queried periodically. Period can be defined on a
> property file under the resources folder inside the working dir. There are
> three threads running inside the tool.
>
> Thread 1: Periodically query memory and operating system mbeans to
> find out about heap memory usage & cpu load avearge
>Threshold values for max memory usage and max cpu load
> average can be set on the property file. So is the period.
>If memory usage exceeds this max value heap dump will
> be automatically generated on the remote ESB Home. User can
>specify any location. By default it will be created on ESB home. If the
> average CPU load exceeds the max value the Threaddump will
> be generated inside the tool. Location to thread dumps to be saved can be
> specified by the user. Each time a heapdump requested a
> seperate thread will be created to handle it.
>
> Thread 2: Periodically monitors network traffic from
> PassThruHTTPSender/receiver mbeans. As we discussed earlier network 
> details
>are persisted to an embedded derby db. Period can be set.
>
> Thread 3: This handles persistence services. Period can be set.
>
> Name of the heap dumps are created as this "HeapDump "
> +date.toString().replaceAll(":","")+".bin"
> Name of the thread dumps are created as this  "ThreadDump"+new
> Date().toString().replaceAll(":","")+".txt"
>
> Let me know if I got it right :)
>
>
> On Mon, May 30, 2016 at 7:30 PM, Dinanjana Gunaratne <
> dinanjanagunara...@gmail.com> wrote:
>
>> Thanks Viraj
>> On May 30, 2016 7:23 PM, "Viraj Senevirathne" 
>> wrote:
>>
>>> 
>>> org.apache.synapse

Re: [Dev] GSOC 2016: Proposal 7

[Dinanjana Gunaratne]

Hello all,
I tried to build a carbon component by referring to this[1] tutorial and my
attempts keep getting failed. I couldn't get the wsdl doc generated for
service. Tomcat returns 404 whenever I try that . Is there a way to find
out whether a service is deployed in carbon sever by observing logs
?(without looking at the mgt console)

B.r,
Dinanjana

[1] :
http://wso2.com/library/tutorials/2014/03/how-to-create-a-feature-from-wso2-carbon-component/

On Mon, Jul 25, 2016 at 1:59 PM, Dinanjana Gunaratne <
dinanjanagunara...@gmail.com> wrote:

> Hi Kasun,
> Currently our solution has following capabilities.
> Monitoring memory and CPU loads
> Monitoring request load
> Monitoring responsiveness of ESB.
> Creating thread and heap dumps
> Creating a report
> Storing request count and relevant details in Derby embedded db
> When any adverse effect taking place on esb this variables can indicate
> that. Currently we are monitoring those aspects in an event based system.
> Each event can be configured by the user by changing parameters in
> respective config files. So when an anomaly detected by those monitors
> respective event will be triggered. This will result in logging the event
> in a report. Also thread dumps heap dumps will be collected according to
> users specifications. We can schedule a demo on Wednesday preferably in the
> night since I have an interview on the same day. I will confirm it once I
> discuss this with my mentors
>
> On Jul 25, 2016 9:30 AM, "Kasun Indrasiri"  wrote:
>
>> What's the current state of this project? Shall we do a end to end demo
>> on what you have done so far?
>>
>> On Tue, Jun 21, 2016 at 6:24 PM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Here are the minutes of the review meeting we had yesterda
>>> y
>>>  -Some code refactoring was suggested. Reducing use of static variables
>>> and static methods was suggested.
>>>  -As the next milestone adding user configurable esb issue reporting
>>> suggested. This will change the current implementation to event   base
>>> implementation.There will be pre defined events for monitoring tool.
>>>   -E.g Out of memory event
>>>  Configurable options :Memory threshold
>>>  Outcomes (heap dumps,thread
>>> dumps)
>>>  Frequency of extracting
>>> dumps
>>>
>>> - Creating a class diagram
>>>
>>>
>>>
>>> On Wed, Jun 1, 2016 at 10:13 PM, Dinanjana Gunaratne <
>>> dinanjanagunara...@gmail.com> wrote:
>>>
 Hello all,

 Progress of the tool so far

 The tool can be deployed in a remote machine to monitor ESB instance.
 It connects to MBanServer of the targeted machine through RMI. Currently it
 monitors memory usage, CPU usage and Network traffic of the ESB. Network
 traffic details are gathered through PassThruHttpSender/receiver mbeans.
 These metrics values are queried periodically. Period can be defined on a
 property file under the resources folder inside the working dir. There are
 three threads running inside the tool.

 Thread 1: Periodically query memory and operating system mbeans to find
 out about heap memory usage & cpu load avearge
Threshold values for max memory usage and max cpu load
 average can be set on the property file. So is the period.
If memory usage exceeds this max value heap dump will be
 automatically generated on the remote ESB Home. User can
  specify any location. By default it will be created on ESB home. If the
 average CPU load exceeds the max value the Threaddump will
 be generated inside the tool. Location to thread dumps to be saved can be
 specified by the user. Each time a heapdump requested a
 seperate thread will be created to handle it.

 Thread 2: Periodically monitors network traffic from
 PassThruHTTPSender/receiver mbeans. As we discussed earlier network details
are persisted to an embedded derby db. Period can be set.

 Thread 3: This handles persistence services. Period can be set.

 Name of the heap dumps are created as this "HeapDump "
 +date.toString().replaceAll(":","")+".bin"
 Name of the thread dumps are created as this  "ThreadDump"+new
 Date().toString().replaceAll(":","")+".txt"

 Let me know if I got it right :)


 On Mon, May 30, 2016 at 7:30 PM, Dinanjana Gunaratne <
 dinanjanagunara...@gmail.com> wrote:

> Thanks Viraj
> On May 30, 2016 7:23 PM, "Viraj Senevirathne"  wrote:
>
>> 
>> org.apache.synapse
>> synapse-nhttp-transport
>> 
>>
>> On Sun, May 29, 2016 at 9:19 AM, Dinanjana Gunaratne <
>> dinanjanagunara...@gmail.com> wrote:
>>
>>> Hello all,
>>> I am facing a problem when trying to create a proxy object. I
>>> 

Re: [Dev] [CDMF] [EMM] [IoT] Obtaining Tenancy Details of a User at EMM/IoT UI client layer

[Rasika Perera]

​Hi Dilan,

Sorry I was trying to make my answer very short thus some points were not
clearly explained.
​


> Instead of the direct OSGI call to user management, what we are hoping to
> achieve is doing one network call to user management admin service.

​This is the exact problem I am trying to emphasize.
​When we invoke REST service or SOAP service from the Jaggery App; flow
will be similar to the following.

[image: Inline image 1]

Browser will invoke the jaggery api / jaggery page. Then the page will do a
web service call using a HTTP client. Hence we are making two network calls
here. Network calls are costlier and adds another set of problems such as
connection timeouts...etc. We can avoid second network call by directly
calling the OSGi service.

Our EMM or IoT servers are meant to be run as either manager or worker
> nodes.
> ​ ​
> Manager node is the place where we deploy the UI. Any of these servers is
> a carbon server
> ​ ​
> and in every carbon server, user management feature comes by default.

​Yes. correct. ​This is why we need to avoid calling another HTTP call to
invoke user management apis.

I did not understand your second point either.

​My second point ​is that currently how we install jaggery apps into the
product distribution is via Carbon Features. To be exact; we are using p2
touchpoints to copy jaggery apps into relevant path(i.e.
/repository/deployments/server/jaggeryapps). Suppose our
jaggery app is "Foo" and it needs a backend called "Bar". Since our jaggery
app is a carbon feature we can declare feature dependencies in the pom.xml
so that we explicitly declare when you using this jaggery app "Foo"; "Bar"
feature should be co-exist.

Thanks
Rasika


On Tue, Aug 2, 2016 at 5:47 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Rasika,
>
> I did not get the point of "two network calls" here.
>
> Instead of the direct OSGI call to user management, what we are hoping to
> achieve is doing one network call to user management admin service.
>
> I did not understand your second point either.
>
> Our actual consideration is that a direct OSGI call from the UI to a
> back-end feature like user management brings the unnecessary concern
> of maintaining additional features in the server except the Jaggery
> runtime on top of tomcat.
>
> However, Please do correct me if these considerations are wrong.
>
> For example, I too have the following doubt.
>
> Our EMM or IoT servers are meant to be run as either manager or worker
> nodes.
> Manager node is the place where we deploy the UI. Any of these servers is
> a carbon server
> and in every carbon server, user management feature comes by default.
>
> In that case, I also have the question of why should we do a costly
> network call to user management via admin services
> when the same functionality is anyway accessible so easily by a direct
> OSGI call via Jaggery wrapper functions.
>
> @prabatha, WDYT?
>
> Regards
> Dilan.
>
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Tue, Aug 2, 2016 at 3:13 PM, Rasika Perera  wrote:
>
>> Hi All,
>>
>> We would be able to easily provide a REST API for this at device-mgt api
>>> layer.
>>> But, due to the fact that such an API is OAuth token protected, this is
>>> again not a solution
>>> because by this point of time, the logged-in user has not even received
>>> a token.
>>> As a result, current suggestion is to do a SOAP webservice call using
>>> basic-auth to
>>> user management admin services and retrieve tenant information.
>>
>> In this case, I am -1 to do two network calls. When designing new UUF,
>> this was one of main concern too. Whenever possible you need to do direct
>> method calls(i.e. OSGi call).
>>
>>
>>> This direct coupling of backend OSGi services with the UI is not
>>> encouraged as that creates an unnecessary requirement
>>> such that UI jaggery app and the carbon user management OSGi service to
>>> co-exist in the same server.
>>
>> With the current jaggery app delivery mechanism, We can easily solve this
>> problem by adding carbon feature level dependency to the user management
>> OSGi service(whatever feature that brings OSGi service of our concern).
>>
>> For instance;
>> If our jaggery app feature is "org.wso2.carbon.device.mgt.ui.feature" we
>> can add;
>>
>> 
>>  {groupId}:{artifactId}
>> 
>>
>> WDYT?
>>
>> On Tue, Aug 2, 2016 at 2:45 PM, Dilan Udara Ariyaratne 
>> wrote:
>>
>>> Hi All,
>>>
>>> At EMM/IoTs UI web app level,
>>> for setting up an OAuth token pair for a newly authenticated user,
>>> we require the use of tenant-based client app credentials.
>>>
>>> These credentials will be retrieved by the provided tenant domain of the
>>> authenticated user
>>> and it seems that currently the particular information is retrieved via
>>> a jaggery wrapper function called
>>> "carbon.server.tenantDomain({username: 

[Dev] [GSoC 2016] Final Evaluation

[Imesh Gunaratne]

Dear Students,

This is to give you a heads up on $subject.

We have seen in the past students being inactive time to time and trying to
complete the deliverables at the last minute when the submission deadline
is nearby.

Please note that at the final evaluation we will be evaluating your overall
effort throughout the project period in addition to the deliverables that
you submit. On high level this would include following:

   - Planning
   - Researching
   - Problem solving
   - Initiatives
   - Level of communication
   - Community interaction
   - Continuous effort on design & implementation
   - Deliverables
   - Documentation
   - Quality of code & all deliverables

GSoC student manual [1] will be really helpful for you to understand this
better.

[1]
http://write.flossmanuals.net/gsocstudentguide/what-is-google-summer-of-code/

Thanks

-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DAS visualization recommendation system

[Gokul Balakrishnan]

Hi Lahiru,

Could you please explain your use-case in a bit more detail please
(specifically, the sort of functionality you expect from DAS)?

Thanks,

On 3 August 2016 at 10:21, Lahiru Madushanka  wrote:

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


-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
M +94 77 5935 789 | +44 7563 570502
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IS 5.2.0-SNAPSHOT - 03/08/2016

[Pandula Kariyawasam]

[+ Dilini and Kavitha]

On Wed, Aug 3, 2016 at 7:00 PM, Kasun Bandara  wrote:

> Hi All,
>
> Please find today's latest build pack for IS 5.2.0-SNAPSHOT [1]
>
> Thanks,
> Kasun.
>
> [1]
> http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/is/wso2is/5.2.0-SNAPSHOT/
>
>
>
>
> --
> Kasun Bandara
> *Software Engineer*
> Mobile : +94 (0) 718 338 360
> <%2B94%20%280%29%20773%20451194>
> kas...@wso2.com 
>



-- 

*Pandula Kariyawasam K.B.*
*Senior Software Engineer*
Mobile: +94772314510



*WSO2 Inc.lean . enterprise . middlewear.http://www.wso2.com
*

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

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

[Osura Rathnayake]

Hi Imesh,

Thank you for highlighting the issues. I'm right on solving them.

You can find the artifacts here [1]. Using the template.json, you can
deploy a manager node, worker node and the DB VMs and other related
resources such as network interfaces and network security groups. also you
can pass the VM image for each of them. For an example If you pass a WSO2
AS manager VM image to the the manager VM in the template, you can deploy
that manager VM with WSO2 AS. you can do the same for worker node VM and DB
VM. Next task is to create VM images for each product as manager and
worker. I will soon update the readme file for each of them as well.

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

thank you,

On Wed, Aug 3, 2016 at 11:44 AM, Imesh Gunaratne  wrote:

> Hi Osura,
>
> I have reported some issues in your git repository, please have a look:
> https://github.com/osuran/azure-membership-scheme/issues
>
> Where can we find the artifacts that you have created for deploying WSO2
> AS on Azure?
>
> Thanks
>
> On Wed, Aug 3, 2016 at 10:30 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you for the corrections. I will update you with the findings.
>>
>> On Wed, Aug 3, 2016 at 10:17 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> Thanks for the notes.
>>>
>>> On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi All,

 following are the meeting minutes of the hangout we had on 2nd of
 August, 2016.

 We discussed about how to automate the deployment process and came to
 the conclusion to use Azure Automation Script feature where you can
 generate a script to automate the deployment of a particular resource.
 Output of this can be in Azure Template( JSON), CLI, PowerShell, .NET or
 Ruby.
 next task : 1) As the initial step, come up with templates and CLI
 scripts for deployments of WSO2 AS, AM and ESB where there are a manager
 node and two worker with hardcoded credentials and then use puppet. 2)
 Research on the flow of automated deployment considering the dependencies.

 I was instructed to implement a method to get metering information
 incurred on WSO2 products.

>>> Correction: we need to check if Azure side supports the level of
>>> metering that is required. As per the information we have up to now, Azure
>>> has some billing information for the usage, in which we cannot drill down
>>> and get fine grained information.
>>>

 I was instructed to do the documentation on each automated deployment
 template, in Github in markdown format.

>>> From the R'n D point of view, lets prioritize the following:
>>>
>>>1. automating the distributed deployment for few products (AS and
>>>APIM, etc.)
>>>2. Check the possibility of using WSO2 Puppet modules to create the
>>>VM.
>>>
>>>
 Thank you,

 On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> It's good to see the blog posts!
> IMO it would be better if you can start writing documentation in
> parallel to blog posts, may be using Markdown format in Github.
>
> Thanks
>
> On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake  > wrote:
>
>> Hi Isuru,
>>
>> I'm researching about automation in Azure. Shall we please have the
>> hangout on Monday?
>> BTW I will be able to complete the documentation on centralized
>> logging, monitoring, auto scaling and load balancing by this weekend and 
>> I
>> will update my blog with the progress. Your feedback is much appreciated.
>>
>> Thank you,
>>
>> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake <
>>> osura...@gmail.com> wrote:
>>>
 Hi All,

 Following are the meeting notes of the hangout we had on 25th of
 July, 2016.

 *Centralized logging*

 Azure Log Analytics provides centralized logging which facilitates
 the users to get logs from a given location in a VM, to a centralized
 location so that they can analyse and query those logs as they need.
 *next task - Documentation in terms of a blog post or webinar

 *Auto scaling*

 Auto scaling is achieved through scale sets in Azure. Scale set is
 a set of VMs and auto scaling rules that defines auto scale metrics &
 actions and the specification of the VMs.

 *Limitations - Azure portal doesn't support addition of auto scale
 rules, it only allows to add a simple scale set with a given number of
 instances. Whereas azure CLI, Powershell and REST API supports full
 functionality.

Re: [Dev] [DAS 310 beta] Scatter plot now showing the max value

[Sachith Withana]

Hi Dunith,

Forgot to mention, this is a realtime chart.

Thanks,
Sachith

On Tue, Aug 2, 2016 at 8:28 PM, Dunith Dhanushka  wrote:

> Hi Sachith,
>
> You don't have to use maxlength property here. It only shows 15 points on
> the x axis. That property is being used for realtime charts.
>
> Thanks,
> Dunith
>
>
> On Wednesday, August 3, 2016, Sachith Withana  wrote:
>
>> Hi all,
>>
>> I have a generated scatter plot, but it does not show some values beyond
>> 800 although there are values that are higher than 800. (refer to the
>> attached image).
>>
>> Observed this in DAS 3.1.0 beta pack.
>>
>> The chart config I have is as follows:
>>   conf.x = _chartConfig.x;
>> conf.charts = [];
>> conf.width = 1300;
>> conf.height = 400;
>> conf.xTitle = "Time";
>> conf.yTitle = "Product Price";
>> conf.maxLength = 15;
>> conf.zero = true;
>> conf.charts[0] = {
>> type : "scatter",
>> y: _chartConfig.y
>> };
>>
>> Thanks,
>> Sachith
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
> --
> Regards,
>
> Dunith Dhanushka,
> Associate Technical Lead
> WSO2 Inc,
>
> Mobile - +94 71 8615744
> Blog - *https://medium.com/@dunithd *
> Twitter - @dunithd 
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Balana] No getter for ObligationId in Obligation

[Manujith Pallewatte]

Hi Farasath,

Yeah I will do that, also if I use the the local snapshot of Balana in the
project, I would have to change my Balana version in the IS pom dependency
right? so it will give a merge conflict when i try to PR the new
entitlement service?

Thank You
Manujith

On Tue, Aug 2, 2016 at 10:04 PM, Farasath Ahamed  wrote:

> Hi Manujith,
>
> It would be great if you could send a PR as well :).
> For now, you can fix this locally and continue working.
>
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>
> On Tue, Aug 2, 2016 at 1:29 PM, Manujith Pallewatte  > wrote:
>
>> Hi,
>>
>> Posted in JIRA [1], thanks for all the help
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-4889
>>
>>
>> On Tue, Aug 2, 2016 at 1:17 PM, Harsha Thirimanna 
>> wrote:
>>
>>> Hi,
>>>
>>> You can create a JIRA here[1]. Follow the other ticket to get an idea.
>>>
>>> [1] https://wso2.org/jira/browse/IDENTITY
>>>
>>> *Harsha Thirimanna*
>>> Associate Tech Lead | WSO2
>>>
>>> Email: hars...@wso2.com
>>> Mob: +94715186770
>>> Blog: http://harshathirimanna.blogspot.com/
>>> Twitter: http://twitter.com/harshathirimann
>>> Linked-In: linked-in:
>>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> 
>>>
>>> On Tue, Aug 2, 2016 at 1:02 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi Harsha,

 Sorry I'm new to JIRA, can you point me where I could post the issue?
 Also i found a previous open issue in balana github issue list [1],
 should I open a new one in JIRA as well?

 [1] https://github.com/wso2/balana/issues/12

 On Tue, Aug 2, 2016 at 12:48 PM, Harsha Thirimanna 
 wrote:

> Yes, can you create a public JIRA
>
> *Harsha Thirimanna*
> Associate Tech Lead | WSO2
>
> Email: hars...@wso2.com
> Mob: +94715186770
> Blog: http://harshathirimanna.blogspot.com/
> Twitter: http://twitter.com/harshathirimann
> Linked-In: linked-in:
> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> 
>
> On Tue, Aug 2, 2016 at 12:41 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi Harsha,
>>
>> Okay thank you, so it would be safe to assume that it will be there
>> in the next Balana release? since I really need to use it
>>
>> Manujith
>>
>> On Tue, Aug 2, 2016 at 11:43 AM, Harsha Thirimanna 
>> wrote:
>>
>>> I think, if there are any usage for that, we have to implement that
>>> get method.
>>>
>>> *Harsha Thirimanna*
>>> Associate Tech Lead | WSO2
>>>
>>> Email: hars...@wso2.com
>>> Mob: +94715186770
>>> Blog: http://harshathirimanna.blogspot.com/
>>> Twitter: http://twitter.com/harshathirimann
>>> Linked-In: linked-in:
>>> http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> 
>>>
>>> On Tue, Aug 2, 2016 at 10:57 AM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi all,

 I'm in the process of implementing the XACML 3.0 JSON profile for
 requests and responses and in writing the responses, I need to obtain 
 the
 Obligation Id of each Obligation [1]. But as seen in [1], there's no 
 public
 getter method available to obtain the Id from the Obligation object.
 Is there a workaround or can a getter be added?


 [1]
 https://github.com/wso2/balana/blob/master/modules/balana-core/src/main/java/org/wso2/balana/xacml3/Obligation.java

 Thank You
 Manujith

 --



 Manujith Pallewatte
 [image: https://]about.me/manzzup

 

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


>>>
>>
>>
>> --
>>
>>
>>
>> Manujith Pallewatte
>> [image: https://]about.me/manzzup
>>
>> 
>>
>
>


 --



 Manujith Pallewatte
 [image: https://]about.me/manzzup

 

>>>
>>>
>>
>>
>> --
>>
>>
>>
>> Manujith Pallewatte
>> [image: https://]about.me/manzzup
>>
>> 

[Dev] IS 5.2.0-SNAPSHOT - 03/08/2016

[Kasun Bandara]

Hi All,

Please find today's latest build pack for IS 5.2.0-SNAPSHOT [1]

Thanks,
Kasun.

[1]
http://maven.wso2.org/nexus/content/repositories/snapshots/org/wso2/is/wso2is/5.2.0-SNAPSHOT/




-- 
Kasun Bandara
*Software Engineer*
Mobile : +94 (0) 718 338 360
<%2B94%20%280%29%20773%20451194>
kas...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Integration tests are failing due to NoClassDefFoundError

[Lakshani Gamage]

Hi all,

When running App Manager test cases, few test cases are randomly failing
due to following [1] and [2] errors.

Does anyone know a reason for this? Appreciate your help to find the reason.

[1]
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- [2016-08-03 11:12:29,623] ERROR - ContextLoader Context initialization
failed
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'services': Cannot create inner bean
'org.wso2.carbon.appmgt.rest.api.publisher.AppsApi#5c6bbc21' of type
[org.wso2.carbon.appmgt.rest.api.publisher.AppsApi] while setting bean
property 'serviceBeans' with key [2]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'org.wso2.carbon.appmgt.rest.api.publisher.AppsApi#5c6bbc21'
defined in ServletContext resource [/WEB-INF/beans.xml]: Instantiation of
bean failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[org.wso2.carbon.appmgt.rest.api.publisher.AppsApi]: Constructor threw
exception; nested exception is java.lang.NoClassDefFoundError:
org/wso2/carbon/appmgt/impl/AppRepository


[2]
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- [2016-08-03 11:13:47,982] ERROR - ApplicationContext
StandardWrapper.Throwable
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'mobileAppServiceV1': Cannot resolve reference to bean
'discoveryServiceV1' while setting bean property 'serviceBeans' with key
[1]; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'discoveryServiceV1' defined in URL
[jndi:/localhost/api/WEB-INF/cxf-servlet.xml]: Instantiation of bean
failed; nested exception is
org.springframework.beans.BeanInstantiationException: Could not instantiate
bean class
[org.wso2.carbon.appmgt.services.api.v1.apps.discovery.service.DiscoveryService]:
Constructor threw exception; nested exception is
java.lang.NoClassDefFoundError:
org/wso2/carbon/appmgt/impl/discovery/DiscoveryCredentials
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveManagedList(BeanDefinitionValueResolver.java:353)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:153)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1327)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
INFO  [org.wso2.carbon.automation.extensions.servers.utils.ServerLogReader]
- at

Re: [Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Hasitha Aravinda]

yes, that is correct, But I am not sure, whether we have covered scenario,
when tenant is unloaded in the system. We need to test that as well.

Thanks,
Hasitha.

On Wed, Aug 3, 2016 at 4:43 PM, Amal Gunatilake  wrote:

> Hi Hasitha,
>
> In the readme configurations[1][2] we have given the configurations that
> support for tenant context.
> Since there have been many updates over the time. I can't remember the
> exact results on tests done with tenants.
>
> [1] #tenat context eg: tenant mode 
> tenant.context=https://localhost:9443/t/abc.com
>
> [2]
> https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/readme
>
> Best regards,
> Amal
>
> On Wed, Aug 3, 2016 at 4:27 PM, Hasitha Aravinda  wrote:
>
>> Hi Amal,
>>
>> Have we tested this for a Unloaded tenant. ? I think we will face same
>> issue because tenant space is not loaded at the time we try to remove
>> artifacts from registry.
>>
>> Thanks,
>> Hasitha.
>>
>>
>> On Wed, Aug 3, 2016 at 4:06 PM, Amal Gunatilake  wrote:
>>
>>> Hi Malith,
>>>
>>> There is an inbuilt tool packaged with BPS for process instance cleanup.
>>> The same tool can be used to clean packages as well.
>>> While the server is running you can run the cleanup script
>>> \bin\processcleanuptool.sh side by side.
>>> You will have to do the configurations specific to tenant which is
>>> similar to example[2].
>>> Once you run the tool, it will list down all the packages according to
>>> given filter configurations. Then you can select what packages to delete.
>>>
>>> [1]
>>> https://github.com/wso2/product-bps/tree/master/modules/samples/product/process-tools
>>> [2]
>>> https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/src/main/resources/process-cleanup.properties
>>>
>>> Best regards,
>>> Amal.
>>>
>>>
>>> On Wed, Aug 3, 2016 at 3:40 PM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi Malith,

 Can you have a look into the process instance cleanup tool. It has the
 capability to delete bpel packages as well.

 Regards
 Nandika

 On Wed, Aug 3, 2016 at 3:28 PM, Malith Munasinghe 
 wrote:

> Hi All,
>
> While writing a Package undeployer tool for BPES 3.2.0 for several
> tenants I did the following to undeploy a BPEL package. While starting the
> tenant flow with super tenant I was able to successfully undeploy the
> releveant package. Starting the tenant flow with a tenant I get the below
> warning with the undeployed result as SUCCESS.
>
> WARN
> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>  Cannot find BPEL package with name
> ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the 
> bpel
> package is un-deployed through the management console or if this node is a
> member of a cluster, please ignore this warning.
>
> When I check the artifact though carbon console I still find the
> Package and the undeployment is not successful.
>
> While debugging I found even though the tenant flow is started the
> tenantProcessStore returns a null because the tenant specific process 
> store
> is not set. So is there a specific method that I should call to load this
> process store before undeploying the package for the specific user.
>
> Attached below is the code snippet used to undeploy the package.
>
> try {
> PrivilegedCarbonContext.startTenantFlow();
> PrivilegedCarbonContext privilegedCarbonContext =
> PrivilegedCarbonContext.getThreadLocalCarbonContext();
> privilegedCarbonContext.setTenantId(1);
> privilegedCarbonContext.setTenantDomain("abc.com");
> packageManagementServiceSkeleton = new
> BPELPackageManagementServiceSkeleton();
>
> packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
> } finally {
> PrivilegedCarbonContext.endTenantFlow();
> }
>
>
> Regards,
> Malith
>
>
> --
> Malith Munasinghe | Software Engineer
> M: +94 (71) 9401122
> E: mali...@wso2.com
> W: http://wso2.com
> 
>



 --
 Nandika Jayawardana
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> *Amal Gunatilake*
>>> WSO2 Inc.; http://wso2.com
>>> Lean . Enterprise . Middleware
>>>
>>> mobile: (+94) 773561195
>>> blog: amalg-blogs.blogspot.com; twitter: @daag123
>>> linkedIn: https://www.linkedin.com/in/amalgunatilake
>>>
>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Associate Technical Lead,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>
>
>
> --
> *Amal Gunatilake*
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> mobile: (+94) 773561195
> blog: amalg-blogs.blogspot.com; 

[Dev] [ESB 490] RelayUtils Error while building Passthrough stream in call mediator

[Udara Liyanage]

Hi,

I get the following exception in ESB for following call mediator. There are
some other previous call mediators which are successful and we can see the
request/responses in wire log. But  for this there is no wire logs that
shows weather ESB sends the requests out. Please note that this is
intermittent.

What could cause the following exception.

  

   

[2016-08-03 16:57:30,597] ERROR - RelayUtils Error while building
Passthrough stream
java.lang.NullPointerException: charsetName
at java.io.InputStreamReader.(InputStreamReader.java:99)
at
org.apache.synapse.commons.builders.XFormURLEncodedBuilder$1.run(XFormURLEncodedBuilder.java:206)
at
org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:132)
at
org.apache.synapse.commons.builders.XFormURLEncodedBuilder.extractParametersFromRequest(XFormURLEncodedBuilder.java:203)
at
org.apache.synapse.commons.builders.XFormURLEncodedBuilder.processDocumentWrapper(XFormURLEncodedBuilder.java:128)
at
org.apache.synapse.commons.builders.XFormURLEncodedBuilder.processDocument(XFormURLEncodedBuilder.java:52)
at
org.apache.synapse.transport.passthru.util.DeferredMessageBuilder.getDocument(DeferredMessageBuilder.java:138)
at
org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:133)
at
org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.buildMessage(Axis2SynapseEnvironment.java:716)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:459)
at
org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:372)
at org.apache.synapse.endpoints.HTTPEndpoint.send(HTTPEndpoint.java:89)
at
org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.java:55)
at
org.apache.synapse.mediators.builtin.CallMediator.handleNonBlockingCall(CallMediator.java:204)
at
org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:87)
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.filters.FilterMediator.mediate(FilterMediator.java:160)
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.mediators.base.SequenceMediator.mediate(SequenceMediator.java:214)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:261)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:679)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:244)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:529)
at
org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:172)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:247)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[2016-08-03 16:57:30,598] ERROR - Axis2SynapseEnvironment Error while
building message
org.apache.axis2.AxisFault: Error while building Passthrough stream
at
org.apache.synapse.transport.passthru.util.RelayUtils.handleException(RelayUtils.java:283)
at
org.apache.synapse.transport.passthru.util.RelayUtils.builldMessage(RelayUtils.java:142)
at
org.apache.synapse.transport.passthru.util.RelayUtils.buildMessage(RelayUtils.java:98)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.buildMessage(Axis2SynapseEnvironment.java:716)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:459)
at
org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:372)
at org.apache.synapse.endpoints.HTTPEndpoint.send(HTTPEndpoint.java:89)
at
org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.java:55)
at
org.apache.synapse.mediators.builtin.CallMediator.handleNonBlockingCall(CallMediator.java:204)
at
org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:87)
at

Re: [Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Malith Munasinghe]

Hi All,

Thank you for the directions I will look in to this approach and get back
with my findings.

Regards,
Malith

On Wed, Aug 3, 2016 at 4:43 PM, Amal Gunatilake  wrote:

> Hi Hasitha,
>
> In the readme configurations[1][2] we have given the configurations that
> support for tenant context.
> Since there have been many updates over the time. I can't remember the
> exact results on tests done with tenants.
>
> [1] #tenat context eg: tenant mode 
> tenant.context=https://localhost:9443/t/abc.com
>
> [2]
> https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/readme
>
> Best regards,
> Amal
>
> On Wed, Aug 3, 2016 at 4:27 PM, Hasitha Aravinda  wrote:
>
>> Hi Amal,
>>
>> Have we tested this for a Unloaded tenant. ? I think we will face same
>> issue because tenant space is not loaded at the time we try to remove
>> artifacts from registry.
>>
>> Thanks,
>> Hasitha.
>>
>>
>> On Wed, Aug 3, 2016 at 4:06 PM, Amal Gunatilake  wrote:
>>
>>> Hi Malith,
>>>
>>> There is an inbuilt tool packaged with BPS for process instance cleanup.
>>> The same tool can be used to clean packages as well.
>>> While the server is running you can run the cleanup script
>>> \bin\processcleanuptool.sh side by side.
>>> You will have to do the configurations specific to tenant which is
>>> similar to example[2].
>>> Once you run the tool, it will list down all the packages according to
>>> given filter configurations. Then you can select what packages to delete.
>>>
>>> [1]
>>> https://github.com/wso2/product-bps/tree/master/modules/samples/product/process-tools
>>> [2]
>>> https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/src/main/resources/process-cleanup.properties
>>>
>>> Best regards,
>>> Amal.
>>>
>>>
>>> On Wed, Aug 3, 2016 at 3:40 PM, Nandika Jayawardana 
>>> wrote:
>>>
 Hi Malith,

 Can you have a look into the process instance cleanup tool. It has the
 capability to delete bpel packages as well.

 Regards
 Nandika

 On Wed, Aug 3, 2016 at 3:28 PM, Malith Munasinghe 
 wrote:

> Hi All,
>
> While writing a Package undeployer tool for BPES 3.2.0 for several
> tenants I did the following to undeploy a BPEL package. While starting the
> tenant flow with super tenant I was able to successfully undeploy the
> releveant package. Starting the tenant flow with a tenant I get the below
> warning with the undeployed result as SUCCESS.
>
> WARN
> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>  Cannot find BPEL package with name
> ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the 
> bpel
> package is un-deployed through the management console or if this node is a
> member of a cluster, please ignore this warning.
>
> When I check the artifact though carbon console I still find the
> Package and the undeployment is not successful.
>
> While debugging I found even though the tenant flow is started the
> tenantProcessStore returns a null because the tenant specific process 
> store
> is not set. So is there a specific method that I should call to load this
> process store before undeploying the package for the specific user.
>
> Attached below is the code snippet used to undeploy the package.
>
> try {
> PrivilegedCarbonContext.startTenantFlow();
> PrivilegedCarbonContext privilegedCarbonContext =
> PrivilegedCarbonContext.getThreadLocalCarbonContext();
> privilegedCarbonContext.setTenantId(1);
> privilegedCarbonContext.setTenantDomain("abc.com");
> packageManagementServiceSkeleton = new
> BPELPackageManagementServiceSkeleton();
>
> packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
> } finally {
> PrivilegedCarbonContext.endTenantFlow();
> }
>
>
> Regards,
> Malith
>
>
> --
> Malith Munasinghe | Software Engineer
> M: +94 (71) 9401122
> E: mali...@wso2.com
> W: http://wso2.com
> 
>



 --
 Nandika Jayawardana
 WSO2 Inc ; http://wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> *Amal Gunatilake*
>>> WSO2 Inc.; http://wso2.com
>>> Lean . Enterprise . Middleware
>>>
>>> mobile: (+94) 773561195
>>> blog: amalg-blogs.blogspot.com; twitter: @daag123
>>> linkedIn: https://www.linkedin.com/in/amalgunatilake
>>>
>>
>>
>>
>> --
>> --
>> Hasitha Aravinda,
>> Associate Technical Lead,
>> WSO2 Inc.
>> Email: hasi...@wso2.com
>> Mobile : +94 718 210 200
>>
>
>
>
> --
> *Amal Gunatilake*
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> mobile: (+94) 773561195
> blog: amalg-blogs.blogspot.com; twitter: @daag123
> linkedIn: 

Re: [Dev] Fwd: GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with online data for WSO2 Machine Learner-Samoa Integration

[Mahesh Dananjaya]

Hi supun,
We have been using v0.4.0 for the cep integration,since the last verstion
is pretty outdated and lack with algorithms for streaming. So i am now
using my locally built v0.4.0 for the project. dependencies are working
fine, because it has been using on the extensions that we develop outside
the carbon-ml as regular extensions. same error appears when i was not
using -U. seems to be that maven search for remote repo rather than local
one.this is the error i got.

[ERROR] Failed to execute goal on project
org.wso2.carbon.ml.siddhi.extension: Could not resolve dependencies for
project 
org.wso2.carbon.ml:org.wso2.carbon.ml.siddhi.extension:bundle:1.1.2-SNAPSHOT:
The following artifacts could not be resolved:
org.apache.samoa:samoa-api:jar:0.4.0-incubating,
org.apache.samoa:samoa-local:jar:0.4.0-incubating: Could not find artifact
org.apache.samoa:samoa-api:jar:0.4.0-incubating in wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/)

seems to be aven prefer remote one for samoa rather than local one. This is
only when i build carbon-ml adding samoa local dependencies. Other
extensions used samoa,which are outside carbon-ml are working fine.
thank you..
BR,
Mahesh.

On Wed, Aug 3, 2016 at 3:11 PM, Supun Sethunga  wrote:

> Hi Mahesh,
>
> you should build carbon-ml *without *-U option. -U means you force mvn to
> look for updates in remote repo. Rather run it with -o option. Also, can
> you double check whether the dependencies are defined correctly (group
> Id's, versions etc).
>
> Alternatively, it seems there is a samoa released version in mvn repo.
> Maybe you could try that one as well. But that's v0.3.0..
>
> [1] https://mvnrepository.com/artifact/org.apache.samoa
>
> On Wed, Aug 3, 2016 at 2:54 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Supun,
>> I just neeed a little help. I am in the process of integrating my samoa
>> core functions and extension into carbon-ml's siddhi extension. For samoa i
>> am using locally built samoa project to provide samoa 0.4.0
>> dependencies,since we dont have it in the maven repo or else where. But
>> when i build carbon-ml by adding samoa dependencies, it seems to be maven
>> search for remote location, not the local maven repo first. I am running
>> maven with -U option. But still the problems occurs. Is there any specific
>> thing in carbon-ml like settings to search remote before local one? I just
>> need to give local maven repo for the dependency. My extension seperately
>> working fine, so there is no problem wihat the local dependencies outside
>> carbon-ml. So can you please help me with this.thank you.
>> regards,
>> Mahesh.
>>
>> On Fri, Jul 22, 2016 at 3:17 PM, Srinath Perera  wrote:
>>
>>> Hi Mahesh,
>>>
>>> On Thu, Jul 21, 2016 at 2:10 PM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi All,
 I am onto connecting cep streams with samoa streams to data analysis
 using samoa framework. To connect samoa with cep siddhi event streams what
 i we can do is that try to convert cep streams into samoa streams or else
 writing wrpper for samoa for cep  streasm to be used. In both cases i have
 to covert siddhi cep streasm into samoa streams. Samoa is using MOA to
 analyse data. Moo contains ML framework to analyse stream data. Samoa is
 wrapping MOA withsome of its classes.

 Samoa streams is based on MOA, Instance and InstanceStreams. Samoa see
 streams as a stream of instances [1]. So if we are going to convert cep
 events into samoa instances , it will take time. But if we have some
 similarity between cep siddhi streams and samoa streasm we can reduce the
 time.
 1. What is the underlying infrastructure for cep siddhi streasm.?
 2. Are there anything as Instances or InstanceStreams kind of
 implmentation underlying cep streams?
 3. How can i get more underestanding on CEP siddhi streams.

 On the other hand i can use my cep siddhi extension and put those
 events into event queue and convert them into samoa instances and feed them
 into samoa streaming ml topologies.

>>> I think this is OK. I assume this is much easier. Let's do this and
>>> check the performance.
>>>
>>>
 There is another option. In Samoa what they are basically doing is that
 wrapping MOA ML framework and write some classes for build streaming ml
 topologies. So as the other option i can wrap samoa moa with my design and
 use moa ml framework directly. (No need for Samoa extension). I have
 building some topologies to streaming data analysis [2]. Main problem is
 that lack of documentation. Anyway i had go through their whole samoa
 design.thank you.

>>>
>>> If we use MOA directly, would we loose the distributed support in SAOMA.
>>> Let's do a call when you can, so we can dsicuss this in detail.
>>>
>>> --Srinath
>>>
>>>
>>>
 regards,
 Mahesh.

 [1]
 

Re: [Dev] Disabling INFO logs per page rendering

[Sinthuja Ragendran]

Hi Rasika,

On Wed, Aug 3, 2016 at 3:48 PM, Rasika Perera  wrote:

> [Adding Sinthuja & Manu]
>
> Hi Dilan and All,
>
> I have done a small fix to Jaggery Core level to support log4j.properties
> file.
>
> *Current Implementation*
> With the current jaggery implementation; All loggers created on
> jaggery(.jag / .js) files will be calling LogHostObject.
> On LogHostObject constructor; It will pick the current *application* scope
> log level assigned by *jaggery.conf*[1] and setting current logger's log
> level into that[2].
>
> *Problem*
> With this approach, even you configure a custom log level through
> log4j.properties file at the server level that configuration will be
> overridden by application scope log level. This will make the debug hard;
> since you cannot change log level on a particular package or file. Instead
> it is applied at the application scope.
>
> *Solution*
> Hence, I removed the overriding part from the LogHostObject and
> implemented following rules;
>
> 1. If a loglevel is set by *log4j.properties* it will get the priority.
>

AFAIU you mention here is the log4j.properties in the server level isn't?
In that case, IMO having the application log level overriding the
log4j.properties log level is correct, and I don't think that we need to
change. For example, by default the server level there will be default
configuration for all apps to have INFO log level, and if it's needed to be
changed to DEBUG log level by a particular application then it's that
application developer's decision.


> 2. Otherwise, new logger will get the application scope log level set by
> *jaggery.conf* file.
>

> PR is in https://github.com/wso2/jaggery/pull/164
>
> *Example*
> Suppose you have following entries on js, jaggery.conf and
> log4j.properties;
>
> >> token-protected-service-invokers.js
> var log = new Log("app.modules.oauth.token-protected-service-invokers.js);
>
> >> jaggery.conf
> {
>
>   "displayName": "Carbon Device Management App",
>   "logLevel": "error"
> }
>
> >> log4.properties
>
> log4j.logger.app.modules.oauth.token-protected-service-invokers.js=INFO
>
> This will change only the particular logger (i.e.
> token-protected-service-invokers.js) into INFO level. With the previous
> approach you will need to change jaggery.conf log level which will
> ultimately turn on all loggers into INFO level in that application.
>

> WDYT?
>

IMO I don't think this is possible, because I don't think all developers
will be having access to the file system of the server to modify the
server's log4j.properties (Eg: In cloud environment). And actually this
control needs to be within the application it self, so that the developer
can modify that regardless of the deployment.

Therefore I propose it would be better to bundle the application specific
log4j.properties within the jaggery app itself to control the logging level
for packages, etc. And that will override the configurations provided from
the server's log4j.properties.

Thanks,
Sinthuja.

[1]
> https://github.com/wso2/jaggery/blob/release-0.12.2/components/jaggery-core/org.jaggeryjs.jaggery.app.mgt/src/main/java/org/jaggeryjs/jaggery/app/mgt/TomcatJaggeryWebappsDeployer.java#L726
> [2]
> https://github.com/wso2/jaggery/blob/release-0.12.2/components/hostobjects/org.jaggeryjs.hostobjects.log/src/main/java/org/jaggeryjs/hostobjects/log/LogHostObject.java#L101-L114
> [3] https://github.com/wso2/jaggery/pull/164
>
> On Mon, Aug 1, 2016 at 8:52 PM, Dilan Udara Ariyaratne 
> wrote:
>
>> Hi Rasika,
>>
>> These info logs have been enabled during a recent refactoring and test
>> run to
>> jaggeryapps/devicemgt/app/modules/oauth/token-protected-service-invokers.js
>> and
>> it seems like mistakenly committed to the source repository;
>> thus commented the lines and recommitted.
>>
>> However, for anyone working on the current EMM UUF 0.2 migration effort
>> and debugging the REST API request handling both at browser layer
>> and jaggery layer, these info logs would be extremely useful and can be
>> uncommented and enabled at any time.
>>
>> The main reason for using info logs instead of debugging logs was that we
>> could not enable debug mode logging specifically for what we wanted.
>> For example: specifically for token-protected-service-invokers.js
>>
>> In jaggery level, it seemed that we could only enable debug mode
>> globally.
>> when this was done, all the unnecessary debugging logs, specifically the
>> huge amount of debugging logs from UUF framework level
>> did appear on console which made it hard to trace what we actually wanted.
>>
>> But, this was in UUF 0.1 and may not be an issue with UUF 0.2.
>>
>> Cheers,
>> Dilan.
>>
>>
>> *Dilan U. Ariyaratne*
>> Senior Software Engineer
>> WSO2 Inc. 
>> Mobile: +94766405580 <%2B94766405580>
>> lean . enterprise . middleware
>>
>>
>> On Mon, Aug 1, 2016 at 3:16 PM, Prabath Abeysekera 
>> wrote:
>>
>>> [Looping dev@]
>>>
>>> Folks, 

[Dev] [PC] Analytics charts visualization using VizGrammar

[Sameera Gunarathne]

Hi all,

I have used VizGrammar js for chart generation for Process Center
analytics. There I give data as follows,

 [{
  "metadata": {
"names": [
  "Task Instance Id",
  "Execution Time"
],
"types": [
  "ordinal",
  "linear"
]
  },
  "data": []
}]

where data is given as a json array with tulpes of (Task Instance
Id,Execution Time) like ["15091",11455],["15069",11545] and they are given
in the sorted order on execution time. But the visualization seems like
it's sorted on Task Instance Id [1]. I need to visualize charts sorted by
execution time. What can be cause for this? Any help is appreciated.

[1]


Thanks.
Regards,
-- 
Sameera Gunarathne
Software Engineer, WSO2 Inc. http://wso2.com

Email: samee...@wso2.com
Mobile: +94714155561
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Amal Gunatilake]

Hi Hasitha,

In the readme configurations[1][2] we have given the configurations that
support for tenant context.
Since there have been many updates over the time. I can't remember the
exact results on tests done with tenants.

[1] #tenat context eg: tenant mode
tenant.context=https://localhost:9443/t/abc.com

[2]
https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/readme

Best regards,
Amal

On Wed, Aug 3, 2016 at 4:27 PM, Hasitha Aravinda  wrote:

> Hi Amal,
>
> Have we tested this for a Unloaded tenant. ? I think we will face same
> issue because tenant space is not loaded at the time we try to remove
> artifacts from registry.
>
> Thanks,
> Hasitha.
>
>
> On Wed, Aug 3, 2016 at 4:06 PM, Amal Gunatilake  wrote:
>
>> Hi Malith,
>>
>> There is an inbuilt tool packaged with BPS for process instance cleanup.
>> The same tool can be used to clean packages as well.
>> While the server is running you can run the cleanup script
>> \bin\processcleanuptool.sh side by side.
>> You will have to do the configurations specific to tenant which is
>> similar to example[2].
>> Once you run the tool, it will list down all the packages according to
>> given filter configurations. Then you can select what packages to delete.
>>
>> [1]
>> https://github.com/wso2/product-bps/tree/master/modules/samples/product/process-tools
>> [2]
>> https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/src/main/resources/process-cleanup.properties
>>
>> Best regards,
>> Amal.
>>
>>
>> On Wed, Aug 3, 2016 at 3:40 PM, Nandika Jayawardana 
>> wrote:
>>
>>> Hi Malith,
>>>
>>> Can you have a look into the process instance cleanup tool. It has the
>>> capability to delete bpel packages as well.
>>>
>>> Regards
>>> Nandika
>>>
>>> On Wed, Aug 3, 2016 at 3:28 PM, Malith Munasinghe 
>>> wrote:
>>>
 Hi All,

 While writing a Package undeployer tool for BPES 3.2.0 for several
 tenants I did the following to undeploy a BPEL package. While starting the
 tenant flow with super tenant I was able to successfully undeploy the
 releveant package. Starting the tenant flow with a tenant I get the below
 warning with the undeployed result as SUCCESS.

 WARN
 {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
  Cannot find BPEL package with name
 ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the bpel
 package is un-deployed through the management console or if this node is a
 member of a cluster, please ignore this warning.

 When I check the artifact though carbon console I still find the
 Package and the undeployment is not successful.

 While debugging I found even though the tenant flow is started the
 tenantProcessStore returns a null because the tenant specific process store
 is not set. So is there a specific method that I should call to load this
 process store before undeploying the package for the specific user.

 Attached below is the code snippet used to undeploy the package.

 try {
 PrivilegedCarbonContext.startTenantFlow();
 PrivilegedCarbonContext privilegedCarbonContext =
 PrivilegedCarbonContext.getThreadLocalCarbonContext();
 privilegedCarbonContext.setTenantId(1);
 privilegedCarbonContext.setTenantDomain("abc.com");
 packageManagementServiceSkeleton = new
 BPELPackageManagementServiceSkeleton();

 packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
 } finally {
 PrivilegedCarbonContext.endTenantFlow();
 }


 Regards,
 Malith


 --
 Malith Munasinghe | Software Engineer
 M: +94 (71) 9401122
 E: mali...@wso2.com
 W: http://wso2.com
 

>>>
>>>
>>>
>>> --
>>> Nandika Jayawardana
>>> WSO2 Inc ; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> *Amal Gunatilake*
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> mobile: (+94) 773561195
>> blog: amalg-blogs.blogspot.com; twitter: @daag123
>> linkedIn: https://www.linkedin.com/in/amalgunatilake
>>
>
>
>
> --
> --
> Hasitha Aravinda,
> Associate Technical Lead,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile : +94 718 210 200
>



-- 
*Amal Gunatilake*
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

mobile: (+94) 773561195
blog: amalg-blogs.blogspot.com; twitter: @daag123
linkedIn: https://www.linkedin.com/in/amalgunatilake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with online data for WSO2 Machine Learner-Samoa Integration

[Miyuru Dayarathna]

Adding Jayan to this email thread.

-- 
Thanks,
Miyuru Dayarathna
Senior Technical Lead
Mobile: +94713527783
Blog: http://miyurublog.blogspot.com

On Wed, Aug 3, 2016 at 3:11 PM, Supun Sethunga  wrote:

> Hi Mahesh,
>
> you should build carbon-ml *without *-U option. -U means you force mvn to
> look for updates in remote repo. Rather run it with -o option. Also, can
> you double check whether the dependencies are defined correctly (group
> Id's, versions etc).
>
> Alternatively, it seems there is a samoa released version in mvn repo.
> Maybe you could try that one as well. But that's v0.3.0..
>
> [1] https://mvnrepository.com/artifact/org.apache.samoa
>
> On Wed, Aug 3, 2016 at 2:54 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi Supun,
>> I just neeed a little help. I am in the process of integrating my samoa
>> core functions and extension into carbon-ml's siddhi extension. For samoa i
>> am using locally built samoa project to provide samoa 0.4.0
>> dependencies,since we dont have it in the maven repo or else where. But
>> when i build carbon-ml by adding samoa dependencies, it seems to be maven
>> search for remote location, not the local maven repo first. I am running
>> maven with -U option. But still the problems occurs. Is there any specific
>> thing in carbon-ml like settings to search remote before local one? I just
>> need to give local maven repo for the dependency. My extension seperately
>> working fine, so there is no problem wihat the local dependencies outside
>> carbon-ml. So can you please help me with this.thank you.
>> regards,
>> Mahesh.
>>
>> On Fri, Jul 22, 2016 at 3:17 PM, Srinath Perera  wrote:
>>
>>> Hi Mahesh,
>>>
>>> On Thu, Jul 21, 2016 at 2:10 PM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi All,
 I am onto connecting cep streams with samoa streams to data analysis
 using samoa framework. To connect samoa with cep siddhi event streams what
 i we can do is that try to convert cep streams into samoa streams or else
 writing wrpper for samoa for cep  streasm to be used. In both cases i have
 to covert siddhi cep streasm into samoa streams. Samoa is using MOA to
 analyse data. Moo contains ML framework to analyse stream data. Samoa is
 wrapping MOA withsome of its classes.

 Samoa streams is based on MOA, Instance and InstanceStreams. Samoa see
 streams as a stream of instances [1]. So if we are going to convert cep
 events into samoa instances , it will take time. But if we have some
 similarity between cep siddhi streams and samoa streasm we can reduce the
 time.
 1. What is the underlying infrastructure for cep siddhi streasm.?
 2. Are there anything as Instances or InstanceStreams kind of
 implmentation underlying cep streams?
 3. How can i get more underestanding on CEP siddhi streams.

 On the other hand i can use my cep siddhi extension and put those
 events into event queue and convert them into samoa instances and feed them
 into samoa streaming ml topologies.

>>> I think this is OK. I assume this is much easier. Let's do this and
>>> check the performance.
>>>
>>>
 There is another option. In Samoa what they are basically doing is that
 wrapping MOA ML framework and write some classes for build streaming ml
 topologies. So as the other option i can wrap samoa moa with my design and
 use moa ml framework directly. (No need for Samoa extension). I have
 building some topologies to streaming data analysis [2]. Main problem is
 that lack of documentation. Anyway i had go through their whole samoa
 design.thank you.

>>>
>>> If we use MOA directly, would we loose the distributed support in SAOMA.
>>> Let's do a call when you can, so we can dsicuss this in detail.
>>>
>>> --Srinath
>>>
>>>
>>>
 regards,
 Mahesh.

 [1]
 https://github.com/apache/incubator-samoa/blob/master/samoa-api/src/main/java/org/apache/samoa/streams/clustering/ClusteringStream.java
 [2]
 https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming

 On Mon, Jul 18, 2016 at 11:40 AM, Mahesh Dananjaya <
 dananjayamah...@gmail.com> wrote:

> Hi Maheshakya,
> Samoa modules built as topologies that connect streams with the
> internal processors. I have already written some examples to test the ML
> algorithms and samoa analysis topologies. What we need to done is mostly
> developing a wrapper around samoa topologies to connect their input and
> output streams with our cep streams. So i am currently going through their
> stream architecture to connect our streams with their streams. Couple of
> examples exapaining samoa ml topologies and streaming can be found in my
> git hub repo [1]. Samoa using MOA ml algorithms by wrapping them with 
> their
> classes. Initailly i am 

Re: [Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Hasitha Aravinda]

Hi Amal,

Have we tested this for a Unloaded tenant. ? I think we will face same
issue because tenant space is not loaded at the time we try to remove
artifacts from registry.

Thanks,
Hasitha.


On Wed, Aug 3, 2016 at 4:06 PM, Amal Gunatilake  wrote:

> Hi Malith,
>
> There is an inbuilt tool packaged with BPS for process instance cleanup.
> The same tool can be used to clean packages as well.
> While the server is running you can run the cleanup script
> \bin\processcleanuptool.sh side by side.
> You will have to do the configurations specific to tenant which is similar
> to example[2].
> Once you run the tool, it will list down all the packages according to
> given filter configurations. Then you can select what packages to delete.
>
> [1]
> https://github.com/wso2/product-bps/tree/master/modules/samples/product/process-tools
> [2]
> https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/src/main/resources/process-cleanup.properties
>
> Best regards,
> Amal.
>
>
> On Wed, Aug 3, 2016 at 3:40 PM, Nandika Jayawardana 
> wrote:
>
>> Hi Malith,
>>
>> Can you have a look into the process instance cleanup tool. It has the
>> capability to delete bpel packages as well.
>>
>> Regards
>> Nandika
>>
>> On Wed, Aug 3, 2016 at 3:28 PM, Malith Munasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> While writing a Package undeployer tool for BPES 3.2.0 for several
>>> tenants I did the following to undeploy a BPEL package. While starting the
>>> tenant flow with super tenant I was able to successfully undeploy the
>>> releveant package. Starting the tenant flow with a tenant I get the below
>>> warning with the undeployed result as SUCCESS.
>>>
>>> WARN
>>> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>>>  Cannot find BPEL package with name
>>> ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the bpel
>>> package is un-deployed through the management console or if this node is a
>>> member of a cluster, please ignore this warning.
>>>
>>> When I check the artifact though carbon console I still find the Package
>>> and the undeployment is not successful.
>>>
>>> While debugging I found even though the tenant flow is started the
>>> tenantProcessStore returns a null because the tenant specific process store
>>> is not set. So is there a specific method that I should call to load this
>>> process store before undeploying the package for the specific user.
>>>
>>> Attached below is the code snippet used to undeploy the package.
>>>
>>> try {
>>> PrivilegedCarbonContext.startTenantFlow();
>>> PrivilegedCarbonContext privilegedCarbonContext =
>>> PrivilegedCarbonContext.getThreadLocalCarbonContext();
>>> privilegedCarbonContext.setTenantId(1);
>>> privilegedCarbonContext.setTenantDomain("abc.com");
>>> packageManagementServiceSkeleton = new
>>> BPELPackageManagementServiceSkeleton();
>>>
>>> packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
>>> } finally {
>>> PrivilegedCarbonContext.endTenantFlow();
>>> }
>>>
>>>
>>> Regards,
>>> Malith
>>>
>>>
>>> --
>>> Malith Munasinghe | Software Engineer
>>> M: +94 (71) 9401122
>>> E: mali...@wso2.com
>>> W: http://wso2.com
>>> 
>>>
>>
>>
>>
>> --
>> Nandika Jayawardana
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> *Amal Gunatilake*
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> mobile: (+94) 773561195
> blog: amalg-blogs.blogspot.com; twitter: @daag123
> linkedIn: https://www.linkedin.com/in/amalgunatilake
>



-- 
--
Hasitha Aravinda,
Associate Technical Lead,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile : +94 718 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Amal Gunatilake]

Hi Malith,

There is an inbuilt tool packaged with BPS for process instance cleanup.
The same tool can be used to clean packages as well.
While the server is running you can run the cleanup script
\bin\processcleanuptool.sh side by side.
You will have to do the configurations specific to tenant which is similar
to example[2].
Once you run the tool, it will list down all the packages according to
given filter configurations. Then you can select what packages to delete.

[1]
https://github.com/wso2/product-bps/tree/master/modules/samples/product/process-tools
[2]
https://github.com/wso2/product-bps/blob/master/modules/samples/product/process-tools/src/main/resources/process-cleanup.properties

Best regards,
Amal.


On Wed, Aug 3, 2016 at 3:40 PM, Nandika Jayawardana 
wrote:

> Hi Malith,
>
> Can you have a look into the process instance cleanup tool. It has the
> capability to delete bpel packages as well.
>
> Regards
> Nandika
>
> On Wed, Aug 3, 2016 at 3:28 PM, Malith Munasinghe 
> wrote:
>
>> Hi All,
>>
>> While writing a Package undeployer tool for BPES 3.2.0 for several
>> tenants I did the following to undeploy a BPEL package. While starting the
>> tenant flow with super tenant I was able to successfully undeploy the
>> releveant package. Starting the tenant flow with a tenant I get the below
>> warning with the undeployed result as SUCCESS.
>>
>> WARN
>> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>>  Cannot find BPEL package with name
>> ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the bpel
>> package is un-deployed through the management console or if this node is a
>> member of a cluster, please ignore this warning.
>>
>> When I check the artifact though carbon console I still find the Package
>> and the undeployment is not successful.
>>
>> While debugging I found even though the tenant flow is started the
>> tenantProcessStore returns a null because the tenant specific process store
>> is not set. So is there a specific method that I should call to load this
>> process store before undeploying the package for the specific user.
>>
>> Attached below is the code snippet used to undeploy the package.
>>
>> try {
>> PrivilegedCarbonContext.startTenantFlow();
>> PrivilegedCarbonContext privilegedCarbonContext =
>> PrivilegedCarbonContext.getThreadLocalCarbonContext();
>> privilegedCarbonContext.setTenantId(1);
>> privilegedCarbonContext.setTenantDomain("abc.com");
>> packageManagementServiceSkeleton = new
>> BPELPackageManagementServiceSkeleton();
>>
>> packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
>> } finally {
>> PrivilegedCarbonContext.endTenantFlow();
>> }
>>
>>
>> Regards,
>> Malith
>>
>>
>> --
>> Malith Munasinghe | Software Engineer
>> M: +94 (71) 9401122
>> E: mali...@wso2.com
>> W: http://wso2.com
>> 
>>
>
>
>
> --
> Nandika Jayawardana
> WSO2 Inc ; http://wso2.com
> lean.enterprise.middleware
>



-- 
*Amal Gunatilake*
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

mobile: (+94) 773561195
blog: amalg-blogs.blogspot.com; twitter: @daag123
linkedIn: https://www.linkedin.com/in/amalgunatilake
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Changes from Activiti rest api 5.21 to BPS rest api

[Nandika Jayawardana]

Hi Sudharma,

Can you look into the rest API implementation and merge the changes to our
rest API implementation.

Regards
Nandika

On Wed, Aug 3, 2016 at 3:52 PM, Sudharma Subasinghe 
wrote:

> Hi all,
>
> This is related to jira[1]. I have attached a doc[2] which contains
> identified changes. Appreciate your ideas.
>
> [1] https://wso2.org/jira/browse/BPS-1089
>
> [2]
> https://docs.google.com/a/wso2.com/spreadsheets/d/1c-zBkBg-zVs8n6T_EdEKAFWd5xl82N4db_s1o-5arCo/edit?usp=sharing
>
> Thanks
> Sudharma
>
> --
> Sudharma Subasinghe,
> Software Engineer,
> WSO2 Inc.
> Email: sudhar...@wso2.com 
> Mobile : +94 710 565 157 <%2B94%20718%20210%20200>
>



-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Disabling INFO logs per page rendering

[Rasika Perera]

[Adding Sinthuja & Manu]

Hi Dilan and All,

I have done a small fix to Jaggery Core level to support log4j.properties
file.

*Current Implementation*
With the current jaggery implementation; All loggers created on
jaggery(.jag / .js) files will be calling LogHostObject.
On LogHostObject constructor; It will pick the current *application* scope
log level assigned by *jaggery.conf*[1] and setting current logger's log
level into that[2].

*Problem*
With this approach, even you configure a custom log level through
log4j.properties file at the server level that configuration will be
overridden by application scope log level. This will make the debug hard;
since you cannot change log level on a particular package or file. Instead
it is applied at the application scope.

*Solution*
Hence, I removed the overriding part from the LogHostObject and implemented
following rules;

1. If a loglevel is set by *log4j.properties* it will get the priority.
2. Otherwise, new logger will get the application scope log level set by
*jaggery.conf* file.

PR is in https://github.com/wso2/jaggery/pull/164

*Example*
Suppose you have following entries on js, jaggery.conf and log4j.properties;

>> token-protected-service-invokers.js
var log = new Log("app.modules.oauth.token-protected-service-invokers.js);

>> jaggery.conf
{

  "displayName": "Carbon Device Management App",
  "logLevel": "error"
}

>> log4.properties

log4j.logger.app.modules.oauth.token-protected-service-invokers.js=INFO

This will change only the particular logger (i.e.
token-protected-service-invokers.js) into INFO level. With the previous
approach you will need to change jaggery.conf log level which will
ultimately turn on all loggers into INFO level in that application.

WDYT?

[1]
https://github.com/wso2/jaggery/blob/release-0.12.2/components/jaggery-core/org.jaggeryjs.jaggery.app.mgt/src/main/java/org/jaggeryjs/jaggery/app/mgt/TomcatJaggeryWebappsDeployer.java#L726
[2]
https://github.com/wso2/jaggery/blob/release-0.12.2/components/hostobjects/org.jaggeryjs.hostobjects.log/src/main/java/org/jaggeryjs/hostobjects/log/LogHostObject.java#L101-L114
[3] https://github.com/wso2/jaggery/pull/164

On Mon, Aug 1, 2016 at 8:52 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Rasika,
>
> These info logs have been enabled during a recent refactoring and test run
> to
> jaggeryapps/devicemgt/app/modules/oauth/token-protected-service-invokers.js
> and
> it seems like mistakenly committed to the source repository;
> thus commented the lines and recommitted.
>
> However, for anyone working on the current EMM UUF 0.2 migration effort
> and debugging the REST API request handling both at browser layer
> and jaggery layer, these info logs would be extremely useful and can be
> uncommented and enabled at any time.
>
> The main reason for using info logs instead of debugging logs was that we
> could not enable debug mode logging specifically for what we wanted.
> For example: specifically for token-protected-service-invokers.js
>
> In jaggery level, it seemed that we could only enable debug mode globally.
> when this was done, all the unnecessary debugging logs, specifically the
> huge amount of debugging logs from UUF framework level
> did appear on console which made it hard to trace what we actually wanted.
>
> But, this was in UUF 0.1 and may not be an issue with UUF 0.2.
>
> Cheers,
> Dilan.
>
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Mon, Aug 1, 2016 at 3:16 PM, Prabath Abeysekera 
> wrote:
>
>> [Looping dev@]
>>
>> Folks, please refrain from discussing development related stuff in
>> private.
>>
>> Cheers,
>> Prabath
>>
>> On Mon, Aug 1, 2016 at 3:08 PM, Milan Perera  wrote:
>>
>>> +1.
>>> We should have to definitely remove them.
>>> As I remember , this was mistakenly committed by Dilan Aiya for debug
>>> purpose and Prabath aiya asked to remove them.
>>>
>>>
>>> On Mon, Aug 1, 2016 at 2:55 PM, Rasika Perera  wrote:
>>>
 [+Milan]

 On Mon, Aug 1, 2016 at 2:28 PM, Rasika Perera  wrote:

> Can we do $subject as it affects performance of the rendering.
>
> Most of the seems belongs to DEBUG and TRACE levels.
>
> [2016-08-01 14:24:12,623]  INFO {JAGGERY.lib.pages:jag} -  ##
> Permissions : {"LIST_DEVICES" : true, "LIST_OWN_DEVICES" : true,
> "LIST_ALL_GROUPS" : true, "LIST_GROUPS" : true, "LIST_USERS" : true,
> "LIST_ROLES" : true, "LIST_ALL_POLICIES" : true, "LIST_POLICIES" : true,
> "ADD_DEVICE" : true, "ADD_GROUP" : true, "ADD_USER" : true, "REMOVE_USER" 
> :
> true, "ADD_ROLE" : true, "ADD_ADMIN_POLICY" : true, "ADD_POLICY" : true,
> "CHANGE_POLICY_PRIORITY" : true, "VIEW_DASHBOARD" : true,
> "TENANT_CONFIGURATION" : true}
> [2016-08-01 14:24:13,433]  INFO
> 

Re: [Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Nandika Jayawardana]

Hi Malith,

Can you have a look into the process instance cleanup tool. It has the
capability to delete bpel packages as well.

Regards
Nandika

On Wed, Aug 3, 2016 at 3:28 PM, Malith Munasinghe  wrote:

> Hi All,
>
> While writing a Package undeployer tool for BPES 3.2.0 for several tenants
> I did the following to undeploy a BPEL package. While starting the tenant
> flow with super tenant I was able to successfully undeploy the releveant
> package. Starting the tenant flow with a tenant I get the below warning
> with the undeployed result as SUCCESS.
>
> WARN
> {org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
>  Cannot find BPEL package with name
> ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the bpel
> package is un-deployed through the management console or if this node is a
> member of a cluster, please ignore this warning.
>
> When I check the artifact though carbon console I still find the Package
> and the undeployment is not successful.
>
> While debugging I found even though the tenant flow is started the
> tenantProcessStore returns a null because the tenant specific process store
> is not set. So is there a specific method that I should call to load this
> process store before undeploying the package for the specific user.
>
> Attached below is the code snippet used to undeploy the package.
>
> try {
> PrivilegedCarbonContext.startTenantFlow();
> PrivilegedCarbonContext privilegedCarbonContext =
> PrivilegedCarbonContext.getThreadLocalCarbonContext();
> privilegedCarbonContext.setTenantId(1);
> privilegedCarbonContext.setTenantDomain("abc.com");
> packageManagementServiceSkeleton = new
> BPELPackageManagementServiceSkeleton();
>
> packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
> } finally {
> PrivilegedCarbonContext.endTenantFlow();
> }
>
>
> Regards,
> Malith
>
>
> --
> Malith Munasinghe | Software Engineer
> M: +94 (71) 9401122
> E: mali...@wso2.com
> W: http://wso2.com
> 
>



-- 
Nandika Jayawardana
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC1

[Jagath Sisirakumara Ariyarathne]

Hi All,

We will call off this vote due to the issue reported in [1] and will start
a new vote for ESB 5.0.0 RC2.

[1] - https://wso2.org/jira/browse/ESBJAVA-4333

Thanks.

On Tue, Aug 2, 2016 at 10:44 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> Hi All,
>
> This is the 1st Release Candidate of WSO2 Enterprise Service Bus 5.0.0
>
> Please download, test the product and vote. Vote will be open for 72 hours
> or as needed.
>
> *Source and distribution*
>
> Run-time: https://github.com/wso2/product-esb/releases/tag/v5.0.0-rc1
> Tooling   :
> https://github.com/wso2/devstudio-tooling-esb/releases/tag/v5.0.0-RC1
> Analytics:
> https://github.com/wso2/analytics-esb/releases/tag/v5.0.0-rc1
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 ESB Team -
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
> 
>



-- 
Jagath Ariyarathne
Technical Lead
WSO2 Inc.  http://wso2.com/
Email: jaga...@wso2.com
Mob  : +94 77 386 7048

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

[Dev] [DEV][BPS][320] Undeploying BPEL packages for tenants

[Malith Munasinghe]

Hi All,

While writing a Package undeployer tool for BPES 3.2.0 for several tenants
I did the following to undeploy a BPEL package. While starting the tenant
flow with super tenant I was able to successfully undeploy the releveant
package. Starting the tenant flow with a tenant I get the below warning
with the undeployed result as SUCCESS.

WARN
{org.wso2.carbon.bpel.core.ode.integration.store.TenantProcessStoreImpl} -
 Cannot find BPEL package with name
ApplicationRegistrationWorkflowProcess_1.0.0 in the repository. If the bpel
package is un-deployed through the management console or if this node is a
member of a cluster, please ignore this warning.

When I check the artifact though carbon console I still find the Package
and the undeployment is not successful.

While debugging I found even though the tenant flow is started the
tenantProcessStore returns a null because the tenant specific process store
is not set. So is there a specific method that I should call to load this
process store before undeploying the package for the specific user.

Attached below is the code snippet used to undeploy the package.

try {
PrivilegedCarbonContext.startTenantFlow();
PrivilegedCarbonContext privilegedCarbonContext =
PrivilegedCarbonContext.getThreadLocalCarbonContext();
privilegedCarbonContext.setTenantId(1);
privilegedCarbonContext.setTenantDomain("abc.com");
packageManagementServiceSkeleton = new
BPELPackageManagementServiceSkeleton();

packageManagementServiceSkeleton.undeployBPELPackage("ApplicationRegistrationWorkflowProcess_1.0.0");
} finally {
PrivilegedCarbonContext.endTenantFlow();
}


Regards,
Malith


-- 
Malith Munasinghe | Software Engineer
M: +94 (71) 9401122
E: mali...@wso2.com
W: http://wso2.com

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

Re: [Dev] Fwd: GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with online data for WSO2 Machine Learner-Samoa Integration

[Supun Sethunga]

Hi Mahesh,

you should build carbon-ml *without *-U option. -U means you force mvn to
look for updates in remote repo. Rather run it with -o option. Also, can
you double check whether the dependencies are defined correctly (group
Id's, versions etc).

Alternatively, it seems there is a samoa released version in mvn repo.
Maybe you could try that one as well. But that's v0.3.0..

[1] https://mvnrepository.com/artifact/org.apache.samoa

On Wed, Aug 3, 2016 at 2:54 PM, Mahesh Dananjaya 
wrote:

> Hi Supun,
> I just neeed a little help. I am in the process of integrating my samoa
> core functions and extension into carbon-ml's siddhi extension. For samoa i
> am using locally built samoa project to provide samoa 0.4.0
> dependencies,since we dont have it in the maven repo or else where. But
> when i build carbon-ml by adding samoa dependencies, it seems to be maven
> search for remote location, not the local maven repo first. I am running
> maven with -U option. But still the problems occurs. Is there any specific
> thing in carbon-ml like settings to search remote before local one? I just
> need to give local maven repo for the dependency. My extension seperately
> working fine, so there is no problem wihat the local dependencies outside
> carbon-ml. So can you please help me with this.thank you.
> regards,
> Mahesh.
>
> On Fri, Jul 22, 2016 at 3:17 PM, Srinath Perera  wrote:
>
>> Hi Mahesh,
>>
>> On Thu, Jul 21, 2016 at 2:10 PM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi All,
>>> I am onto connecting cep streams with samoa streams to data analysis
>>> using samoa framework. To connect samoa with cep siddhi event streams what
>>> i we can do is that try to convert cep streams into samoa streams or else
>>> writing wrpper for samoa for cep  streasm to be used. In both cases i have
>>> to covert siddhi cep streasm into samoa streams. Samoa is using MOA to
>>> analyse data. Moo contains ML framework to analyse stream data. Samoa is
>>> wrapping MOA withsome of its classes.
>>>
>>> Samoa streams is based on MOA, Instance and InstanceStreams. Samoa see
>>> streams as a stream of instances [1]. So if we are going to convert cep
>>> events into samoa instances , it will take time. But if we have some
>>> similarity between cep siddhi streams and samoa streasm we can reduce the
>>> time.
>>> 1. What is the underlying infrastructure for cep siddhi streasm.?
>>> 2. Are there anything as Instances or InstanceStreams kind of
>>> implmentation underlying cep streams?
>>> 3. How can i get more underestanding on CEP siddhi streams.
>>>
>>> On the other hand i can use my cep siddhi extension and put those events
>>> into event queue and convert them into samoa instances and feed them into
>>> samoa streaming ml topologies.
>>>
>> I think this is OK. I assume this is much easier. Let's do this and check
>> the performance.
>>
>>
>>> There is another option. In Samoa what they are basically doing is that
>>> wrapping MOA ML framework and write some classes for build streaming ml
>>> topologies. So as the other option i can wrap samoa moa with my design and
>>> use moa ml framework directly. (No need for Samoa extension). I have
>>> building some topologies to streaming data analysis [2]. Main problem is
>>> that lack of documentation. Anyway i had go through their whole samoa
>>> design.thank you.
>>>
>>
>> If we use MOA directly, would we loose the distributed support in SAOMA.
>> Let's do a call when you can, so we can dsicuss this in detail.
>>
>> --Srinath
>>
>>
>>
>>> regards,
>>> Mahesh.
>>>
>>> [1]
>>> https://github.com/apache/incubator-samoa/blob/master/samoa-api/src/main/java/org/apache/samoa/streams/clustering/ClusteringStream.java
>>> [2]
>>> https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming
>>>
>>> On Mon, Jul 18, 2016 at 11:40 AM, Mahesh Dananjaya <
>>> dananjayamah...@gmail.com> wrote:
>>>
 Hi Maheshakya,
 Samoa modules built as topologies that connect streams with the
 internal processors. I have already written some examples to test the ML
 algorithms and samoa analysis topologies. What we need to done is mostly
 developing a wrapper around samoa topologies to connect their input and
 output streams with our cep streams. So i am currently going through their
 stream architecture to connect our streams with their streams. Couple of
 examples exapaining samoa ml topologies and streaming can be found in my
 git hub repo [1]. Samoa using MOA ml algorithms by wrapping them with their
 classes. Initailly i am trying to develop a KMeansClustering analysis with
 cep streams with samoa ml topologies.
 And also i could not find a maven repo for samoa 0.4.0 incubating. So i
 am currently using my local m2 repo's samoa 0..4.0 incubating for my
 dependencies to work. The local one is built by original samoa source.thank
 you.

Re: [Dev] Fwd: GSOC2016: [ML][CEP] [SAMOA]Predictive analytic with online data for WSO2 Machine Learner-Samoa Integration

[Mahesh Dananjaya]

Hi Supun,
I just neeed a little help. I am in the process of integrating my samoa
core functions and extension into carbon-ml's siddhi extension. For samoa i
am using locally built samoa project to provide samoa 0.4.0
dependencies,since we dont have it in the maven repo or else where. But
when i build carbon-ml by adding samoa dependencies, it seems to be maven
search for remote location, not the local maven repo first. I am running
maven with -U option. But still the problems occurs. Is there any specific
thing in carbon-ml like settings to search remote before local one? I just
need to give local maven repo for the dependency. My extension seperately
working fine, so there is no problem wihat the local dependencies outside
carbon-ml. So can you please help me with this.thank you.
regards,
Mahesh.

On Fri, Jul 22, 2016 at 3:17 PM, Srinath Perera  wrote:

> Hi Mahesh,
>
> On Thu, Jul 21, 2016 at 2:10 PM, Mahesh Dananjaya <
> dananjayamah...@gmail.com> wrote:
>
>> Hi All,
>> I am onto connecting cep streams with samoa streams to data analysis
>> using samoa framework. To connect samoa with cep siddhi event streams what
>> i we can do is that try to convert cep streams into samoa streams or else
>> writing wrpper for samoa for cep  streasm to be used. In both cases i have
>> to covert siddhi cep streasm into samoa streams. Samoa is using MOA to
>> analyse data. Moo contains ML framework to analyse stream data. Samoa is
>> wrapping MOA withsome of its classes.
>>
>> Samoa streams is based on MOA, Instance and InstanceStreams. Samoa see
>> streams as a stream of instances [1]. So if we are going to convert cep
>> events into samoa instances , it will take time. But if we have some
>> similarity between cep siddhi streams and samoa streasm we can reduce the
>> time.
>> 1. What is the underlying infrastructure for cep siddhi streasm.?
>> 2. Are there anything as Instances or InstanceStreams kind of
>> implmentation underlying cep streams?
>> 3. How can i get more underestanding on CEP siddhi streams.
>>
>> On the other hand i can use my cep siddhi extension and put those events
>> into event queue and convert them into samoa instances and feed them into
>> samoa streaming ml topologies.
>>
> I think this is OK. I assume this is much easier. Let's do this and check
> the performance.
>
>
>> There is another option. In Samoa what they are basically doing is that
>> wrapping MOA ML framework and write some classes for build streaming ml
>> topologies. So as the other option i can wrap samoa moa with my design and
>> use moa ml framework directly. (No need for Samoa extension). I have
>> building some topologies to streaming data analysis [2]. Main problem is
>> that lack of documentation. Anyway i had go through their whole samoa
>> design.thank you.
>>
>
> If we use MOA directly, would we loose the distributed support in SAOMA.
> Let's do a call when you can, so we can dsicuss this in detail.
>
> --Srinath
>
>
>
>> regards,
>> Mahesh.
>>
>> [1]
>> https://github.com/apache/incubator-samoa/blob/master/samoa-api/src/main/java/org/apache/samoa/streams/clustering/ClusteringStream.java
>> [2]
>> https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming
>>
>> On Mon, Jul 18, 2016 at 11:40 AM, Mahesh Dananjaya <
>> dananjayamah...@gmail.com> wrote:
>>
>>> Hi Maheshakya,
>>> Samoa modules built as topologies that connect streams with the internal
>>> processors. I have already written some examples to test the ML algorithms
>>> and samoa analysis topologies. What we need to done is mostly developing a
>>> wrapper around samoa topologies to connect their input and output streams
>>> with our cep streams. So i am currently going through their stream
>>> architecture to connect our streams with their streams. Couple of examples
>>> exapaining samoa ml topologies and streaming can be found in my git hub
>>> repo [1]. Samoa using MOA ml algorithms by wrapping them with their
>>> classes. Initailly i am trying to develop a KMeansClustering analysis with
>>> cep streams with samoa ml topologies.
>>> And also i could not find a maven repo for samoa 0.4.0 incubating. So i
>>> am currently using my local m2 repo's samoa 0..4.0 incubating for my
>>> dependencies to work. The local one is built by original samoa source.thank
>>> you.
>>>
>>> regards,
>>> Mahesh.
>>>
>>> [1]
>>> https://github.com/dananjayamahesh/GSOC2016/tree/master/gsoc/samoa/streaming/src/main/java/org/gsoc/samoa/streaming
>>>
>>>
>>> On Mon, Jul 18, 2016 at 8:32 AM, Maheshakya Wijewardena <
>>> mahesha...@wso2.com> wrote:
>>>
 Hi Mahesh,

 Can you  please share your samoa project?

 On Sun, Jul 17, 2016 at 11:19 AM, Mahesh Dananjaya <
 dananjayamah...@gmail.com> wrote:

>
> -- Forwarded message --
> From: Mahesh Dananjaya 
> Date: Sun, Jul 17, 2016 at 11:18 AM
> Subject: Re: GSOC2016: [ML][CEP] 

[Dev] WSO2 Mesos Artifacts 1.0.0 Released!

[Pubudu Gunatilaka]

WSO2 PaaS team is pleased to announce the release of WSO2 Mesos Artifacts
1.0.0.

Mesos is an open source cluster manager that provides efficient resource
isolation and sharing across distributed applications, or frameworks. Mesos
Artifacts for WSO2 products provide Marathon applications that need to be
deployed on Mesos DC/OS, to maintain a cluster of various profiles of the
WSO2 products. Furthermore, WSO2 Mesos Artifacts are released under Apache
Software License Version 2.0, one of the most business-friendly licenses
available today.


Main Features:

   -

   A consistent set of Mesos Artifacts with recommended best practices for
   deploying following WSO2 Products on Mesos DC/OS:


   -

   WSO2 API Manager 1.10.0


   -

   WSO2 Application Server 5.3.0
   -

   WSO2 Business Process Server 3.5.1
   -

   WSO2 Business Rules Server 2.2.0
   -

   WSO2 Complex Event Processor 4.0.0
   -

   WSO2 Data Analytics Server 3.0.1
   -

   WSO2 Data Services Server 3.5.0
   -

   WSO2 Enterprise Store 2.0.0
   -

   WSO2 Enterprise Service Bus 4.9.0
   -

   WSO2 Governance Registry 5.1.0
   -

   WSO2 Governance Registry 5.1.0 with API Manager Publisher Store
   -

   WSO2 Identity Server 5.1.0
   -

   WSO2 Identity Server 5.1.0 as Key Manager
   -

   WSO2 Message Broker 3.1.0


   -

   A well-defined workflow for building Docker images using WSO2
   Dockerfiles and WSO2 Puppet Modules, which is used to deploy WSO2 products
   on Mesos DC/OS.
   -

   Support for distributed deployment patterns for WSO2 products on Mesos
   DC/OS with minimum configuration steps.
   -

   A Carbon membership scheme for automated cluster discovery on Mesos
   DC/OS.
   -

   Customized Marathon load balancer (LB) with sticky session support.
   -

   Apache SVN Mesos Artifacts for Deployment Synchronization.
   -

   A set of helper scripts for deployment automation on Mesos DC/OS:
   -

  Load Docker images to Mesos slave nodes
  -

  Create shared database
  -

  Deploy and undeploy Mesos artifacts

Release Artifacts:
https://github.com/wso2/mesos-artifacts/releases/tag/v1.0.0

Documentation:
https://docs.wso2.com/display/MA100/WSO2+Mesos+Artifacts+Documentation

Please report any issues/suggestion for improvements at:
https://wso2.org/jira/browse/MESOSARFTS


Thank you!
WSO2 PaaS Team.
-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Imesh Gunaratne]

Hi Osura,

I have reported some issues in your git repository, please have a look:
https://github.com/osuran/azure-membership-scheme/issues

Where can we find the artifacts that you have created for deploying WSO2 AS
on Azure?

Thanks

On Wed, Aug 3, 2016 at 10:30 AM, Osura Rathnayake 
wrote:

> Hi Isuru,
>
> Thank you for the corrections. I will update you with the findings.
>
> On Wed, Aug 3, 2016 at 10:17 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> Thanks for the notes.
>>
>> On Wed, Aug 3, 2016 at 10:09 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> following are the meeting minutes of the hangout we had on 2nd of
>>> August, 2016.
>>>
>>> We discussed about how to automate the deployment process and came to
>>> the conclusion to use Azure Automation Script feature where you can
>>> generate a script to automate the deployment of a particular resource.
>>> Output of this can be in Azure Template( JSON), CLI, PowerShell, .NET or
>>> Ruby.
>>> next task : 1) As the initial step, come up with templates and CLI
>>> scripts for deployments of WSO2 AS, AM and ESB where there are a manager
>>> node and two worker with hardcoded credentials and then use puppet. 2)
>>> Research on the flow of automated deployment considering the dependencies.
>>>
>>> I was instructed to implement a method to get metering information
>>> incurred on WSO2 products.
>>>
>> Correction: we need to check if Azure side supports the level of metering
>> that is required. As per the information we have up to now, Azure has some
>> billing information for the usage, in which we cannot drill down and get
>> fine grained information.
>>
>>>
>>> I was instructed to do the documentation on each automated deployment
>>> template, in Github in markdown format.
>>>
>> From the R'n D point of view, lets prioritize the following:
>>
>>1. automating the distributed deployment for few products (AS and
>>APIM, etc.)
>>2. Check the possibility of using WSO2 Puppet modules to create the
>>VM.
>>
>>
>>> Thank you,
>>>
>>> On Mon, Aug 1, 2016 at 12:44 PM, Imesh Gunaratne  wrote:
>>>
 Hi Osura,

 It's good to see the blog posts!
 IMO it would be better if you can start writing documentation in
 parallel to blog posts, may be using Markdown format in Github.

 Thanks

 On Fri, Jul 29, 2016 at 10:49 AM, Osura Rathnayake 
 wrote:

> Hi Isuru,
>
> I'm researching about automation in Azure. Shall we please have the
> hangout on Monday?
> BTW I will be able to complete the documentation on centralized
> logging, monitoring, auto scaling and load balancing by this weekend and I
> will update my blog with the progress. Your feedback is much appreciated.
>
> Thank you,
>
> On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa 
> wrote:
>
>> Hi Osura,
>>
>> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake > > wrote:
>>
>>> Hi All,
>>>
>>> Following are the meeting notes of the hangout we had on 25th of
>>> July, 2016.
>>>
>>> *Centralized logging*
>>>
>>> Azure Log Analytics provides centralized logging which facilitates
>>> the users to get logs from a given location in a VM, to a centralized
>>> location so that they can analyse and query those logs as they need.
>>> *next task - Documentation in terms of a blog post or webinar
>>>
>>> *Auto scaling*
>>>
>>> Auto scaling is achieved through scale sets in Azure. Scale set is a
>>> set of VMs and auto scaling rules that defines auto scale metrics & 
>>> actions
>>> and the specification of the VMs.
>>>
>>> *Limitations - Azure portal doesn't support addition of auto scale
>>> rules, it only allows to add a simple scale set with a given number of
>>> instances. Whereas azure CLI, Powershell and REST API supports full
>>> functionality.
>>>
>>> I have added the template to the github repo which I used to create
>>> the auto scale settings which includes the ability to add a custom VM 
>>> image
>>> and auto scale rules. When you deploy from this template you should give
>>> the URI of the VM image. you can edit auto scale rules using CLI, Power
>>> shell or REST API. Azure Resource Explorer
>>>  can be used if you choose REST API to
>>> modify.
>>>
>>> *next tasks - 1) Have to figure out a way to pass application and
>>> user data such as usernames and passwords of database, to the VM image
>>> through the template. 2) Documentaion
>>>
>>>
>>> *Load balancing*
>>>
>>> Following are some key terms you need to know.
>>>
>>> · Backend pool: This is a pool of virtual machines that
>>> share the traffic
>>>
>>> · Probe: The