Hi all,
IMO, having DB update and in-memory queues are two different methods we can
resolve this issue. Updating DB supports near reliable messaging and this
can be done only from a single server. Because we cannot have multiple
servers reading and updating database without coordination. Implement
On Thu, Mar 23, 2017 at 12:15 PM, Sinthuja Ragendran
wrote:
> Hi Geeth,
>
>
> On Thu, Mar 23, 2017 at 11:42 AM, Geeth Munasinghe wrote:
>
>> Hi all,
>>
>> IMO, having DB update and in-memory queues are two different methods we
>> can resolve this is
u are subscribed to the Google Groups
> "WSO2 IoT Team Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iot-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>
--
*Gee
Hi all,
We are closing this vote for RC1, We will proceed with new RC soon.
Thanks
Geeth
On Tue, Jul 18, 2017 at 12:20 PM, Geeth Munasinghe wrote:
> -1,
>
> Due to packing old registry versions which are having some security
> issues.
>
> Thanks
> Geeth
>
> On M
--
> You received this message because you are subscribed to the Google Groups
> "WSO2 IoT Team Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to iot-group+unsubscr...@wso2.com.
> For more options, visit https://groups.google.com
You received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to iot-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google
in why)
Thanks
Geeth
--
*Geeth Munasinghe*
*WSO2, Inc. http://wso2.com <http://wso2.com/> *
*lean.enterprise.middleware.*
email: ge...@wso2.com
phone:(+94) 777911226
<http://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
htt
nks & regards,
> /charithag
>
> On Thu, Mar 15, 2018 at 4:20 AM, Geeth Munasinghe wrote:
>
>> Hi all,
>>
>> We are pleased to announce the release candidate of WSO2 IoT Server 3.3.0.
>>
>> This is the Release Candidate version 1 of the WSO2 IoT Serve
Hi all,
Retrieving device information plays a vital role for device management. A
device consists of static data such as device name, vendor, os etc... and
dynamic data such as device location, cpu usage, memory usage etc So
retrieving these information is a must specially for analytics and ta
Hi Ayyoob
Thanks for the valuable feedback.
Please see my comments in line.
On Sat, Apr 2, 2016 at 10:32 PM, Ayyoob Hamza wrote:
> Hi Geeth,
> Looks cool and as my understanding I see that there are two capabilities
> that has been described here.
> 1) Trigger operations through tasks.
> 2) Sea
Hi Chathura,
Please see my comments in line.
On Mon, Apr 4, 2016 at 10:39 AM, Chathura Ekanayake
wrote:
> Hi Geeth,
>
> Nice work. Few points..
>
> 1) When joining search criteria, is it possible to enforce order of join
> operators using parentheses? E.g. (cpu usage > 30% or battery level < 10
Hi Prabath
In the context of EMM/IoT product, we already have apis implemented, Now it
is matter of documenting them with swagger. Given the fact that swagger has
provided annotation based documenting strategy for already implemented
apis, we can utilize them within EMM/IoT for documentation.
I a
IMO, I would prefer first solution in which any conflict arises, we choose
the feature in highest priority policy to be in the composite policy. I
think it is a simple solution which can implemented easily and end-user can
understand easily.
I am -1 with implementing a policy conflicts resolution
Hi all,
Tested following scenarios.
1. Android device enrollment.
2. User and role creation and assigning permission.
3. Sending email with user invite.
4. Create/Edit policy
5. Applying policy to device.
6. Reapplying changed policy.
7. Add few operations.
[+] - Stable - g
ne.
>>
>> [+] - stable - go ahead and release.
>>
>> Thanks
>> Hasunie
>>
>> On Thu, Dec 1, 2016 at 10:41 AM, Geeth Munasinghe wrote:
>>
>>> Hi all,
>>>
>>> Tested following scenarios.
>>>
>>>
>>>
Hi all,
We have encountered an issue with balancing load distribution of device +
server communication. Device and server communication happens through
following ways.
1. Polling - Device keeps polling the server
2. Push notification - Server sends a notification to device to come
retrie
Hi all,
CDM is capable of applying configurations (profiles) to managed devices.
These configurations (or profiles) will defend on device types, device
supported OS versions, device owners privileges, time and location of the
devices.
Configurations are such as disable/enable camera, change wifi
26
On Mon, Mar 16, 2015 at 12:27 PM, Geeth Munasinghe wrote:
> Hi all,
>
> CDM is capable of applying configurations (profiles) to managed devices.
> These configurations (or profiles) will defend on device types, device
> supported OS versions, device owners privileges, time and loca
Hi all,
We are pleased to announce that WSO2EMM 2.0.0 Milestone 7 is released.
This release includes the following features and improvements.
1. Adding users and sending email invitations. (admin ui)
2. Adding roles (admin ui)
3. View device details (Admin ui)
4. Android device mana
Hi all,
We are pleased to announce that WSO2EMM 2.0.0 Milestone 8 is released.
This release includes the following features and improvements.
1. Adding users and sending email invitations. (admin ui)
2. Adding roles (admin ui)
3. View device details (Admin ui)
4. Android device mana
*WSO2 Enterprise Mobility Manager 2.0.0 Alpha Released..!*
Date : 21st November 2015
The WSO2 CDM team is pleased to announce the release of* WSO2EMM 2.0.0
Alpha*. You can download the distribution from [1].
New release of WSO2EMM 2.0.0 is a complete rewrite which addresses few
shortcomings of
*WSO2 Enterprise Mobility Manager 2.0.0 Beta Released..!*
Date : 11st December 2015
The WSO2 CDM team is pleased to announce the release of* WSO2EMM 2.0.0 Beta*.
You can download the distribution from [1].
New release of WSO2EMM 2.0.0 is a complete rewrite which addresses few
shortcomings of p
Hi Dilan,
We may have to include the following too.
1. Device count by groups,
2. Device groups
3. Active/Inactive devices
4. Blocked/Removed devices
5. Unreachable devices
6. Number of enrolled devices within give time frame (new devices added)
Thanks
Geeth
*G. K. S. Munasin
Hi Dilan,
On Fri, Feb 12, 2016 at 12:32 PM, Dilan Udara Ariyaratne
wrote:
> Hi All,
>
> For the upcoming EMM 2.1.0 release, we have identified following basic
> use-cases
> for the pre-defined reports of Reporting Feature with respect to devices,
> policies and users.
>
> [1] All MDM portal user
Hi Ayyoob,
It should be other way around where default profile has everything. When a
user start the standalone server with "sh wso2server.sh", it should have
everything complete their use case (Including MB and DAS features).
And in real deployment user will use IoT server with only IoT related
Hi
Following components in carbon-commons get dependencies from other projects
as follows.
- application-deployers/org.wso2.carbon.application.deployer.synapse
- org.wso2.carbon.mediation.initializer -
carbon-mediation
- org.wso2.carbon.mediation.registry
Hi
According to proposed project architecture on github, we need to move
data-bridge and data-agents to carbon-commons project. When moving these
two to carbon-common project, need to make sure that there is no
dependencies resolving from other projects such as BAM and CEP. Because
most of the proj
Hi
As per the offline chat with Azeez, we are removing following stratos
features from AS. We have to remove them from other products too. If we
need to ship them with products we have to bring the source related
following stratos features to git repo.
1. org.wso2.carbon.stratos.common.feature
olicy definition is just a set of actions that do not
>> contain any
>> applicable conditions, it was suggested to rename it as 'profile'.
>>
>> Thanks
>>
>> On Wed, Dec 3, 2014 at 11:06 AM, Manoj Gunawardena
>> wrote:
>>
>>
d
>
> Regards,
> Nira
>
>
> On Fri, Dec 5, 2014 at 11:49 AM, Geeth Munasinghe wrote:
>
>> Hi Sumedha,
>>
>> I will do the change accordingly.
>>
>> Thanks
>> Geeth
>>
>>
>> *G. K. S. Munasinghe*
>> *Software Engineer,
Hi
On Wed, Dec 17, 2014 at 2:23 PM, Isuruwan Herath wrote:
>
> [moved to architecture]
>
> Hi Sameera,
>
> Please see the comments inline.
>
> On Mon, Dec 15, 2014 at 11:00 PM, Sameera Kannangara
> wrote:
>>
>> Hi all,
>>
>> $Subject refers to the functionality required to fulfill the following
Hi
Following fields are chosen to use as payload data and meta data as suggestions
Payload data -
webappName
webappDisplayName - The set in web.xml
webappOwnerTenant
webappVersion - web-app servlet version. Ex. 2.5, 3.0
timestamp
webappType - Possible values are JAX
, Sagara Gunathunga wrote:
> Hi Geeth,
>
> Could you please update current status of this task ?
>
> Thanks !
>
>
> On Mon, May 13, 2013 at 12:04 PM, Geeth Munasinghe wrote:
>
>> Hi
>>
>> Following fields are chosen to use as payload data and m
HI
In code review of "AS Webapp Staitistic Publishing to BAM" discussed moving
the following class[1] in to the data-bridge to be used as a single api.
The reason this code will be repeated in web app statistic publishing
component also.
[1]
https://svn.wso2.org/repos/wso2/carbon/platform/trunk/c
On Fri, Jul 12, 2013 at 11:26 AM, Shariq Muhammed wrote:
> Hi folks,
>
> I was looking into capturing webapp statistics for aPaaS work, and came
> across the webapp.stat.publisher component written by the AS team. It
> uses a tomcat valve [1] and publish a whole heap of stats, the list can be
> f
On Sat, Jul 27, 2013 at 7:21 PM, Kasun Gajasinghe wrote:
> Hi,
>
> We have added support for webapp metadata persistence. This is used to
> synchronize the metadata changes in a cluster, and to reload the metadata
> during server restarts. Currently, we use this to persist the per webapp
> BAM we
...@wso2.com
phone:(+94) 777911226
On Wed, Jul 31, 2013 at 10:33 AM, Geeth Munasinghe wrote:
>
>
> On Sat, Jul 27, 2013 at 7:21 PM, Kasun Gajasinghe wrote:
>
>> Hi,
>>
>> We have added support for webapp metadata persistence. This is used to
>> synchronize the m
Hi
I am trying to implement a try-it functionality for jax-rs web apps.
Currently this functionality is available axis2 services and jax-ws web
apps.
I used swagger to accomplish this. Swagger has implemented a ui using
jquery which is independent from swagger java implementation.
Swagger java i
+1 Interesting idea. I think installing features on carbon kernel will not
be flexible thing here. Instead we should package a single server to
install. Because if some one wants to install both ESB and App Server as
separate servers on the same machine, then person has to install carbon
kernal twi
instance, for example in a development environment. Prod environments
>> could use lxc to install multiple tomcats to give each war its own jvm if
>> required.
>>
>> Does this make sense?
>> On 8 Jan 2014 06:36, "Geeth Munasinghe" wrote:
>>
>>&g
40 matches
Mail list logo
