1. The directory containing this INSTALL file will be the root and it will be treated as IoT home directory and let it be IoT_HOME.
-----------------
1. The directory containing this INSTALL file will be the root and it is treated as the IoTS home directory, and is referred to as <IoT_HOME>.
2. WSO2 IoT Server comes as a composition of three components namely broker, core and analytics.
2. WSO2 IoT Server comes as a composition of three components namely broker, core, and analytics.
3. Starting order of IoT components shuld be broker, core, analytics.
To start/stop/restart the IoT components one can use wso2server.sh for *nix systems & wso2server.bat for Windows systems which can be found in following locations.
IoT_HOME/broker/bin
IoT_HOME/core/bin
IoT_HOME/analytics/bin
3. The starting order of the WSO2 IoTS components should be broker, core, analytics.
4. The wso2server.sh and wso2server.bat has following commands
4. To start/stop/restart the IoTS components, run wso2server.sh for *nix systems and wso2server.bat for Windows systems, which can be found in following locations.
<IoT_HOME>/broker/bin
<IoT_HOME>/core/bin
<IoT_HOME>/analytics/bin
5. The wso2server.sh and wso2server.bat startup scripts have the following commands:
Welcome to the WSO2 IoT Server (IoTS) 3.0.0 release
Welcome to the WSO2 IoT Server (IoTS) 3.0.0 release.
=======
Key Features
------------
1. Self-service device enrollment and management with end-user IoTS console
Self-service device enrollment and management with an end-user IoTS console.
Installation & Running
----------------------
1. Extract the downloaded zip file
2. Follow the INSTALL.txt file for install instructions
3. Once the server starts, point your Web browser to https://localhost:9443/devicemgt to see available device types and operations
4. Navigate to https://localhost:9443/api-store to see the available device APIs, You can subscribe to these APIs with default application (or by creating new application).
In API store, go to my subscriptions and find client ID and secret. Which can be used to invoke these apis.
1. Extract the downloaded ZIP file.
2. Follow the INSTALL.txt file for install instructions.
3. After the server starts, point your Web browser to https://localhost:9443/devicemgt in order to see the available device types and operations
4. Navigate to https://localhost:9443/api-store to see the available device APIs. You can subscribe to these APIs with the default application (or by creating a new application).
In the API Store, go to my subscriptions and locate the client ID and secret, which can be used to invoke these APIs.
System Requirements
-------------------
1. Minimum memory - 4GB
2. Portal app requires full Javascript enablement of the Web browser
2. The portal app requires full Javascript enablement on the Web browser
WSO2 IoT Server (IoTS) Binary Distribution Directory Structure
@ -28,12 +28,12 @@ WSO2 IoT Server (IoTS) Binary Distribution Directory Structure
IoT core, analytics and broker has similar directory sctructure. As for example core has following structure
The IoTS Core, Analytics, and Broker have similar directory structures. For example Core has the following structure:
IoT_HOME/core
.
├── bin //executables
@ -50,7 +50,7 @@ IoT core, analytics and broker has similar directory sctructure. As for example
- bin
Contains various scripts .sh & .bat scripts.
Contains various scripts (i.e., .sh & .bat scripts).
- dbscripts
Contains the database creation & seed data population SQL scripts for
@ -62,9 +62,8 @@ IoT core, analytics and broker has similar directory sctructure. As for example
- repository
The repository where Carbon artifacts & Axis2 services and
modules deployed in WSO2 Carbon are stored.
In addition to this other custom deployers such as
dataservices and axis1services are also stored.
modules deployed in WSO2 Carbon, and other custom deployers such as
dataservices and axis1services are stored.
- carbonapps
Carbon Application hot deployment directory.
@ -73,7 +72,7 @@ IoT core, analytics and broker has similar directory sctructure. As for example
Contains all OSGi related libraries and configurations.
- conf
Contains server configuration files. Ex: axis2.xml, carbon.xml
Contains server configuration files. e.g., axis2.xml, carbon.xml
- data
Contains internal LDAP related data.
@ -92,16 +91,15 @@ IoT core, analytics and broker has similar directory sctructure. As for example
Contains additional resources that may be required.
- tenants
Directory will contain relevant tenant artifacts
in the case of a multitenant deployment.
This directory will contain relevant tenant artifacts
in the case of a multi-tenant deployment.
- tmp
Used for storing temporary files, and is pointed to by the
java.io.tmpdir System property.
java.io.tmpdir system property.
- webapp-mode
The user has the option of running WSO2 Carbon in webapp mode (hosted as a web-app in an application server).
This directory contains files required to run Carbon in webapp mode.
You have the option of running WSO2 Carbon in the webapp mode (hosted as a web-app in an application server). This directory contains files required to run Carbon in the webapp mode.
- LICENSE.txt
Apache License 2.0 under which WSO2 Carbon is distributed.
@ -113,61 +111,55 @@ IoT core, analytics and broker has similar directory sctructure. As for example
This document contains information on installing WSO2 IoT Server.
- release-notes.html
Release information for WSO2 IoT Server 1.0.0-ALPHA
Release information for WSO2 IoT Server 3.0.0
Secure sensitive information in carbon configuration files
Secure sensitive information in Carbon configuration files
WSO2 Inc. offers a variety of professional Training Programs, including
training on general Web services as well as WSO2 Enterprise Store, Apache Axis2,
Data Services and a number of other products.
For additional support information please refer to
http://wso2.com/training/
WSO2 Inc. offers a variety of professional Training Programs for WSO2 products.
For additional support on training information please goto http://wso2.com/training/
Support
-------
We are committed to ensuring that your enterprise middleware deployment is completely supported
from evaluation to production. Our unique approach ensures that all support leverages our open
development methodology and is provided by the very same engineers who build the technology.
We are committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that all support leverages our open development methodology and is provided by the very same engineers who build the technology.
For additional support information please refer to http://wso2.com/support/
ayyoob
8 years ago