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

Hi all, I tested the below mentioned as a super tenant user and tenant admin: 1. User Management 2. Policy Managment 3. Role and Permission Managment 4. Configuration Managment. 5. IOS Device enrollment and policy publishing 6. VFL Enrollment and Analytics 7. Android mobile

Re: [Dev] [APIM] [Golang] Implementing HTTP PUT in Golang

What are the errors you see on the server side when invoked with the Go client? Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Senior Software Engineer | WSO2 Blog: https://medium.com/@chamilad On Mon, Aug 14, 2017 at 9:40 AM, Menuka Warushavithana

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

Hi, I have tested followings in Linux and windows platforms, - Android mobile device enrollment and operations - Android policy compliance - Geo fencing alert generation - Device grouping - Enterprise App installation and scheduled app installation from mobile app store No

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

Hi all, Tested following areas on Windows and Mac with an Android device. - Device enrollment - Push notifications - Device grouping - Device location - Geo Fencing - Device status update - Device search - Operations - Policy - App install Also, verified bug fixes

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

Hi all, I've tested the following for Android Device (Android 6.0 OS) from Admin user. 1. Device enrollment 2. Device operations (Ring, Mute, Message, Change Lock-code, Clear Lock-code, Enterprise-wipe) 3. App installation via App Store. 4. Observe Device status changing. (Active <-> Removed,

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

Hi All, I have tested the following functionalities for Android Sense device type. 1. Enrollment 2. Sensor Data publishing and viewing them in device view. 3. Removing device and re-enrolling to a new user. 4. Geo Fencing features. +1 Stable - Go ahead and release. Thanks and Regards, Menaka

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

I tested following: Virtual firealarm (control operations,analytics - realtime & batch) Android Device Mgt(enrollment, ring, message) Device Type creation (HTTP,MQTT) Device pushing data (via API) No blockers were found. [+] Stable - Go ahead and release. Thanks, Sumedha On Mon, Aug 14, 2017

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

Hi All, I have tested following functionalities for IOS device type. (v 10.1.1) - Enrolling device with/without ios-agent. - Operation execution (Device lock, Ring, Location, Notification, Enterprise-Wipe) - Changing platform configurations. - Passcode and restriction policies.

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

Hi all, I tested Virtual Fire Alarm Connected Cup No blockers were found [+] Stable - Go ahead and release. Thanks, Lahiru On Mon, Aug 14, 2017 at 4:48 PM, Sumedha Rubasinghe wrote: > I tested following: > Virtual firealarm (control operations,analytics - realtime &

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

Hi all, Tested following areas in Linux platform, 1. Sample device types deployment. 2. Connected-Cup device type deployment. 3. Geo fencing artifact deployment *With Super Tenant * Android 1. Device enrollment 2. Device operations (location, ring, lock) 3. Device renaming

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

Hi all, Thanks for testing and verifying the WSO2 IoT Server RC4. We are closing the vote now. This vote has passed with 15 (+1)s and 0 (-1)s. Therefore we are proceeding with the WSO2 IoT Server 3.1.0 release. 15 (+1) 0(-1) Regards, On Mon, Aug 14, 2017 at 6:32 PM, Nirothipan Mehalingam

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

Hi All, I have tested the following with a custom device type created from maven archetype, 1. Device type deployment 2. Device enrolment 3. Push operation to device (MQTT) 4. Real time analytics 5. Batch analytics No issues were found. [+] Stable - go ahead and release. Thanks

[Dev] jndi.properties MB in AWS

Hi, When configuring the message broker connections in jndi.properties. we need to specify the brokerlist with all broker servers that we can connect to. So, this list is fixed. In case we have a deployment on AWS where the MB can be scaled up and down. How can we setup jndi.properties to work