diff --git a/modules/distribution/README.txt b/modules/distribution/README.txt index 1ae28d44..adf903cc 100644 --- a/modules/distribution/README.txt +++ b/modules/distribution/README.txt @@ -1,11 +1,11 @@ -WSO2 Mobile Device Manager (MDM) +WSO2 IoT Server ---------------------- -Welcome to the WSO2 Mobile Device Manager Manager (MDM) 2.0.0-SNAPSHOT release +Welcome to the WSO2 IoT Server (IoTS) 1.0.0-ALPHA release ======= Key Features ------------ -1. Self-service device enrollment and management with end-user MDM console +1. Self-service device enrollment and management with end-user IoTS console Installation & Running @@ -14,68 +14,19 @@ Installation & Running 2. Run the wso2server.sh or wso2server.bat file in the bin directory 3. Once the server starts, point your Web browser to https://localhost:9443/ -4. An external API manager is necessary to access the APIs MDM exposes for Android agent. - Create the following APIs, - i. http://:9763/cdm-android-api/enrollment/ - Keeps the context as /enroll and version as 1.0.0 - ii. http://:9763/cdm-android-ap/devices/license - Keeps the context as /license and version as 1.0.0 - iii. http://:9763/cdm-android-ap/operations/ - Keeps the context as /operation and version as 1.0.0 - -5. After publishing these APIs, subscribe to these APIs with default app/any app. +4. After publishing these APIs, subscribe to these APIs with default app/any app. In API store, go to my subscriptions and find client ID and secret. -6. Please find the maven-archetype in repository/tools to generate the mdm-android-agent project & follow the README file. - -7. Go to MDM admin console. - Add a license with following properties. - Ex -: Provider -: Any text - Name -: android - Language -: en-us - Valid From -: date in {dd-mm-yyyy} format. - Valid To -: date in {dd-mm-yyyy} format. - License -: License Text - -8. Configure email account. - Go to Following path and open CARBON_HOME/repository/conf/axis2 and open axis2_client.xml. - Un comment following entry and give correct credentials for email account. - - - wso2demomail@gmail.com - wso2demomail - mailpassword - smtp.gmail.com - - 587 - true - true - - -9. Install following features using carbon admin features. - MDM - iOS APNS Server 1.9.2.SNAPSHOT More Info. - MDM - iOS Device Management JAX-RS Web Application 1.9.2.SNAPSHOT More Info. - MDM - iOS Device Management Server. - -10. Change Urls and settings in ios-config.xml found in CARBON_HOME/repository/conf. - -11. Follow the instructions in following document to generate keys. - https://docs.wso2.com/display/EMM110/iOS+Server+Configurations - - -For more details, see the Installation Guide +5. Please find the maven-archetype in repository/tools to generate the mdm-android-agent project & follow the README file. System Requirements ------------------- -1. Minimum memory - 2GB +1. Minimum memory - 4GB 2. Portal app requires full Javascript enablement of the Web browser -For known issues see -https://wso2.org/jira/issues/?filter=12190 -WSO2 Mobile Device Manager (MDM) Binary Distribution Directory Structure +WSO2 IoT Server (IoTS) Binary Distribution Directory Structure ----------------------------------------------------- EMM_HOME @@ -101,7 +52,7 @@ WSO2 Mobile Device Manager (MDM) Binary Distribution Directory Structure various supported databases. - lib - Contains the basic set of libraries required to startup WSO2 Enterprise Mobility Manager + Contains the basic set of libraries required to startup WSO2 IoT Server in standalone mode - repository @@ -154,10 +105,10 @@ WSO2 Mobile Device Manager (MDM) Binary Distribution Directory Structure This document. - INSTALL.txt - This document contains information on installing WSO2 Enterprise Mobility Manager. + This document contains information on installing WSO2 IoT Server. - release-notes.html - Release information for WSO2 Enterprise Mobility Manager 2.0.0-SNAPSHOT + Release information for WSO2 IoT Server 1.0.0-ALPHA Secure sensitive information in carbon configuration files ---------------------------------------------------------- @@ -216,4 +167,4 @@ development methodology and is provided by the very same engineers who build the For additional support information please refer to http://wso2.com/support/ --------------------------------------------------------------------------- -(c) Copyright 2015 WSO2 Inc. +(c) Copyright 2016 WSO2 Inc. diff --git a/modules/distribution/release-notes.html b/modules/distribution/release-notes.html index 997f55f9..67c39923 100644 --- a/modules/distribution/release-notes.html +++ b/modules/distribution/release-notes.html @@ -1,234 +1,119 @@ - - - - - - -
- -

WSO2 IoT Server -1.0.0 Alpha Released

- -

We are pleased to announce WSO2 IoT Server 1.0.0 alpha release. It can be -downloaded fromhttps://github.com/wso2-incubator/product-iot-server/releases/tag/IoTS-1.0.0-alpha

- -

 

- -

WSO2 -IoT Server is an extensible, open-source, multi -tenant, Internet of Things Platform for implementing server-side of IoT Reference Architecture. It comes with a few reference -implementations for the device layer.

- -


-

- -

WSO2 -IoT Server supports:

- -

 

- -

Device -Management

- -

Extensions for registering device types

- -

Self-service enrolment and management of -connected devices

- -

Group, manage and monitor connected devices

- -

Share device operations / data with other users

- -

Distribution and management of applications and -firmware to devices

- -

Edge computing powered by WSO2 CEP streaming -engine (Siddhi - https://github.com/wso2/siddhi)

- -

OOTB support for some known device types such as -Raspberry Pi, Arduino Uno, Android

- -

IoT -Protocol Support

- -

Leverage MQTT, HTTP, Websockets -and XMPP protocols for device communications with IoT -Server

- -

Framework extension for adding more protocols -and data formats

- -

Analytics

- -

Support for batch, interactive, real-time and -predictive analytics through WSO2 DAS

- -

Pre-built visualisation -support for sensor readings

- -

View instant, visualised -statistics of individual or multiple devices

- -

Traverse through, analyse -and zoom in/out of filtered data

- -

Stats-API to write your own visualisation

- -

Pre-built graphs for common sensor reading types -like temperature, velocity

- -

API Management for App Development

- -

Devices are represented as REST APIs

- -

Develop applications using Device APIs

- -

Identity and Access Management

- -

Identity Management for devices

- -

Token based access control for devices & -operations (protect back end services via exposing device type APIs)

- -

Support -for SCEP protocol (encryption and authenticity)

- -


-List of known issues
-

- -

รก  https://wso2.org/jira/issues/?filter=13055

- -

 

- -

 

- -

Thanks and Regards,

- -

 

- -

~ EMM / IoTS Team ~

- -

 

- -
- - - - + Release Notes - WSO2 IOT Server - Version 1.0.0 - Alpha + +

Bug +

+
    +
  • [IOTS-17] - MQTT endpoints are not secured for agent communication +
    • +
  • [IOTS-19] - XMPP sessions not closed before server shutdown +
    • +
  • [IOTS-21] - Jaggery API calls are not secured +
    • +
  • [IOTS-34] - Backend Service Invoker Fails Intermittently with Unexpected token: < +
    • +
  • [IOTS-37] - Could not generate a new access token (using refresh token) by using the current token endpoint +
    • +
  • [IOTS-47] - Update the release note in the release packs as it is about EMM +
    • +
  • [IOTS-50] - users whos iot-admin role is removed is shown all options for enrol devices as users with iot-admin role +
    • +
  • [IOTS-55] - Considerable delay in server startup +
    • +
  • [IOTS-57] - Error when starting the IOT pack after pointing to the mysql database +
    • +
  • [IOTS-64] - The wso2carbon log file is growing rapidly +
    • +
  • [IOTS-68] - when a tenant is created with the same user name as super tenant seems the super tenant data are shown +
    • +
  • [IOTS-69] - until device admin was disabled the camera policy was in effect preventing the use of camera on android device +
    • +
  • [IOTS-75] - view API throws a Caused by: java.lang.NullPointerException: Tenant domain has not been set in CarbonContext +
    • +
  • [IOTS-81] - IOT devices are allways in active status +
    • +
  • [IOTS-92] - Error in executing task: Table Not Found: X1234_DeviceBatterySummaryData java.lang.RuntimeException: Table Not Found: X1234_DeviceBatterySummaryData is thown when pointing to mysql +
    • +
  • [IOTS-93] - XMPP server details are hardcoded in virtual fire alarm and devicemgt-config.xml file +
    • +
  • [IOTS-94] - Virtual firealarms that were downloaded before xmpp was enabled can not connect to xmpp protocol after enabling. +
    • +
  • [IOTS-100] - When integrating ActiveMQ as an external message broker IOTS fails to start +
    • +
  • [IOTS-102] - Device analytic line graph does not get generated when the device type has a capital letter +
    • +
  • [IOTS-104] - Remove the device type configs that is used for UI from conf directory +
    • +
  • [IOTS-105] - clean unnecessary jaggery apis +
    • +
  • [IOTS-106] - A emm console url is shown in carbon log at server startup +
    • +
  • [IOTS-110] - No email confirmation is sent to user when administrator creates a user +
    • +
  • [IOTS-112] - A prefix as " Device " is set to the devices that is been created +
    • +
  • [IOTS-114] - Change Role permissions: the user is unable to deselect a child node +
    • +
  • [IOTS-117] - Edit/ create Role: Domain needs to be marked as a mandatory field +
    • +
  • [IOTS-122] - Tenant - admin cannot enroll to virtual fire alarm, raspberry pi & arduino +
    • +
  • [IOTS-124] - Group: View analytics loads an error +
    • +
  • [IOTS-127] - Admin cannot reset user passwords +
    • +
  • [IOTS-129] - If devicemgt-user role is deleted users cannot register +
    • +
  • [IOTS-130] - The line graph is not generated correctly for virtual firealarm +
    • +
  • [IOTS-131] - Publishing stats via MQTT protocol to iot server fails +
    • +
  • [IOTS-134] - Server startup fails when configured to use MySQL +
    • +
  • [IOTS-136] - User signup for tenant is not supported +
    • +
  • [IOTS-150] - Arduino sample is not getting proper responses +
    • +
  • [IOTS-151] - Server startup fails when configured to use Oracle +
    • +
  • [IOTS-152] - Platform Configuration display android, iOS and windows Configuration +
    • +
  • [IOTS-153] - Error is thrown when accessing device API details page +
    • +
  • [IOTS-154] - Typo /enrollmentdevicesg/download for raspberypi (g) +
    • +
  • [IOTS-155] - When browsing analytics error 500 shown to user from a group which has no devices assigned +
    • +
  • [IOTS-156] - 404 page when cancel clicked in "Add New Group" page +
    • +
  • [IOTS-157] - Signed up users shown an error page when navigated to policy page +
    • +
  • [IOTS-158] - Signed up users cannot create policies +
    • +
  • [IOTS-159] - Meaningful message to be shown when On / Off issued to virtual fire alarm +
    • +
  • [IOTS-161] - Remove the phrase "Below QR code can also be used to enroll a device" +
    • +
  • [IOTS-163] - Android sensor: only admin can login to the app +
    • +
  • [IOTS-164] - When an existing user name is used by admin no proper validation message shown +
    • +
  • [IOTS-165] - Server startup throws "The following exception occurred when fetching http://www.google-analytics.com/urchin" +
    • +
  • [IOTS-166] - Connected cup device analytics is failing to load +
    • +
  • [IOTS-167] - Considerable delay is taken to initialize transports for device types +
    • +
+ +

Improvement +

+
    +
  • [IOTS-87] - not able to compare two event streams in current IOT server +
    • +
  • [IOTS-145] - Remove the second confirmation message to remove a user or role +
    • +
  • [IOTS-149] - Remove Windows device type from IOTS +
    • +
+ diff --git a/modules/distribution/src/assembly/filter.properties b/modules/distribution/src/assembly/filter.properties index 548761f3..36417a15 100644 --- a/modules/distribution/src/assembly/filter.properties +++ b/modules/distribution/src/assembly/filter.properties @@ -17,11 +17,11 @@ # product.name=WSO2 IoT Server -product.version=1.0.0-SNAPSHOT +product.version=1.0.0-ALPHA product.key=IOT hotdeployment=true hotupdate=true -carbon.version=4.4.2 +carbon.version=4.4.3 default.server.role=IoTServer cep.server.role=ComplexEventProcessor das.server.role=DataAnalyticsServer