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.
3. The starting order of the WSO2 IoTS components should be broker, core, analytics.
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:
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).
==================================
Running the Integrator
==================================
1. Extract wso2iot-3.1.0.zip and go to the extracted directory/bin.
2. Run iot-server.sh or iot-server.bat.
3. Point your favourite browser to https://localhost:9443/devicemgt in order to see the available device types and operations.
4. Use the following username and password to login
username : admin
password : admin
5. 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.
Running other runtimes individually (Analytics, Broker)
The IoTS Core, Analytics, and Broker have similar directory structures. For example Core has the following structure:
IoT_HOME/core
.
├── bin //executables
├── dbscripts //DBScripts
├── INSTALL.txt
├── lib
├── LICENSE.txt
├── modules //Jaggery Modules
├── README.txt
├── release-notes.html
├── repository // repository
├── tmp
├── webapp-mode
- bin
Contains various scripts (i.e., .sh & .bat scripts).
WSO2 EI distribution directory
=============================================
- bin
Contains various scripts .sh & .bat scripts
- database
Contains the database
- dbscripts
Contains the database creation & seed data population SQL scripts for
various supported databases.
Contains all the database scripts
- lib
Contains the basic set of libraries required to startup WSO2 IoT Server
in standalone mode
Contains the basic set of libraries required to startup IoT Server
in standalone mode
- repository
The repository where Carbon artifacts & Axis2 services and
modules deployed in WSO2 Carbon, and other custom deployers such as
dataservices and axis1services are stored.
The repository where services and modules deployed in WSO2 IoT.
are stored.
- conf
Contains configuration files specific to IoT.
- logs
Contains all log files created during execution of IoT.
- resources
Contains additional resources that may be required, including sample
configuration and sample resources
- carbonapps
Carbon Application hot deployment directory.
- samples
Contains some sample services and client applications that demonstrate
the functionality and capabilities of WSO2 IoT.
- components
Contains all OSGi related libraries and configurations.
- tmp
Used for storing temporary files, and is pointed to by the
java.io.tmpdir System property
- conf
Contains server configuration files. e.g., axis2.xml, carbon.xml
- LICENSE.txt
Apache License 2.0 and the relevant other licenses under which
WSO2 EI is distributed.
- data
Contains internal LDAP related data.
- README.txt
This document.
- database
Contains the WSO2 Registry & User Manager database.
- release-notes.html
Release information for WSO2 IoT 3.1.0
- deployment
Contains server side and client side Axis2 repositories.
All deployment artifacts should go into this directory.
- patches
Used to add patches related for all runtimes.
- logs
Contains all log files created during execution.
-dropins
Used to add external jars(dependencies) of all runtimes.
- resources
Contains additional resources that may be required.
-extensions
Used to add carbon extensions.
- tenants
This directory will contain relevant tenant artifacts
in the case of a multi-tenant deployment.
-servicepacks
Used to add service packs related to all runtimes.
- tmp
Used for storing temporary files, and is pointed to by the
java.io.tmpdir system property.
-webapp-mode
- 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.
-wso2/components
Contains profiles for all runtimes and the plugins folder
- LICENSE.txt
Apache License 2.0 under which WSO2 Carbon is distributed.
-wso2/lib
Contains jars that are required/shared by all runtimes.
- README.txt
This document.
-wso2/analytics
Contains analytics runtime related files/folders.
- INSTALL.txt
This document contains information on installing WSO2 IoT Server.
-wso2/analytics/conf
Analytics runtime specific configuration files.
-wso2/analytics/repository
Where deployments of Analytics runtime is stored.
-wso2/broker
Contains broker runtime related files/folders.
-wso2/broker/conf
Broker runtime specific configuration files.
-wso2/broker/repository
Where deployments of broker runtime is stored.
- release-notes.html
Release information for WSO2 IoT Server 3.0.0
Secure sensitive information in Carbon configuration files
sinthuja
8 years ago