Posts

Running a Standalone WSO2 IoT Server.

WSO2 IoT Server  can be run on single instance with simple configurations.  WSO2 IoT server  consists of 3 major services. IoT Core — This service includes all the major device management capabilities such as operation, policy management etc. It also includes the security and API management capabilities. Analytics — This service includes components for data gathering and analysis in both real-time and batch. It also includes the capability to do machine learning as well complex event processing and fraud detection. Broker — This service acts as the message exchanger between server and devices. By default, WSO2 IoT server uses OAuth as the security mechanism. When a user login into the devicemgt user interface, it uses the OAuth token to validate the user in the underlying infrastructure. It supports few OAuth grant types and by default devicemgt application user the JWT token grant type. And by default WSO2 IoT Server runs as with the hostname as localhost. If you do not

Fix for iOS host name verification failed issue.

If you get the following error when installing the certificates for iOS configurations to WSO2IOT server, please replace " localhost" with your <SERVER_IP> with <IoT_HOME>/repository/deployment/server/synapse-configs/default/api/ [2017-02-02 20:17:21,548] [IoT-Core]  ERROR  -  TargetHandler   I / O   error :  Host   name   verification   failed   for   host  : localhost javax.net.ssl.SSLException:  Host   name   verification   failed   for   host  : localhost at org.apache.synapse.transport. http.conn. ClientSSLSetupHandler.verify( ClientSSLSetupHandler.java: 171) at org.apache.http.nio.reactor. ssl.SSLIOSession.doHandshake( SSLIOSession.java:308) at org.apache.http.nio.reactor. ssl.SSLIOSession. isAppInputReady(SSLIOSession. java:410) at org.apache.http.impl.nio. reactor.AbstractIODispatch. inputReady(AbstractIODispatch. java:119) at org.apache.http.impl.nio. reactor.BaseIOReactor. readable(BaseIOReactor.java: 159) at org.apache.http.impl.n

Getting started with WSO2 Device Cloud APIs

Image
Introduction WSO2 Device Cloud is the latest addition to WSO2’s Cloud offering. It aims to provide device integration and management to rest of the WSO2 cloud. As of now, it allows integrating and managing Android & iOS powered devices. Device Cloud offers an UI to manage connected devices. Fig 1: Device Management Dashboard Page on Device Cloud Fig 2: Listing of all registered devices But the functionality is not limited to a web application. All device management capabilities are offered as OAuth2 protected REST APIs as well.   This tutorial explains how to make programmatic use of these APIs. In order to proceed with examples, you need to have a WSO2 Cloud account ( https://cloud.wso2.com ).  If you do not possess an account please use the following url to register one. https://cloudmgt.cloud.wso2.com/cloudmgt/site/pages/index.jag   API Store All apis related to device management are available in the API Store part of WSO2 Cloud. https://api.

COMPLETE GOVERNANCE WITH GREG, APIM & BAM

Image
Introduction Service oriented architecture (SOA) is best way to develop softwares (services) to achieve any business use case. But SOA requires higher level of coordination and collaboration between lot of teams within the particular enterprise, from business teams to IT (information technology) teams and as well as among other teams and departments.This coordination and collaboration can be achieved by implementing a proper SOA governance model which deals with task, processes and people for defining and managing how services are created, supported and managed. Governance is somewhat a political issue than a technical issue. While technology focuses on the interfaces, protocols and specifications, the business worry about method of serving customer. But both the technical and business emphasis on requirements to satisfy customers. Governance involves in all those aspects even those are separate efforts and processes. Governance conforms that everyone involved in those aspect