As the question suggests, anyone know if the WSO2 IOT Server supports apple DEP or VPP for MDM management?
WSO2 IoT Server does support DEP. However, the implementation is still in experimental form and we have not merged the features to the main product as yet. You can expect DEP support to be available in future releases.
Related
I am trying to utilise multitenancy feature in WSO2 by using github releases(https://github.com/wso2/product-is/releases/tag/v5.11.0). I just wanted to understand if there are any limitations for the same between enterprise version downloaded from wso2 site and github releases.
Thanks
WSO2 doesn't have an Enterprise Version of the product. Everybody uses the same base release and if you have a subscription you will be receiving product updates for bug fixes, improvements, security issues etc. Other than that there are no hidden features or limitations in the Opensource version.(Rarely some features are introduced as updates, in these cases you may not receive them) The subscription is for getting updates and getting support from WSO2.
You can read more about WSO2 subscription from here.
Adding to #YCR answer, yes, multi tenancy is supported in IS 5.11.0 and IS 6.0.0 and it was supported throughout IS 5.x series. Please see Tenant Management on WSO2 documentation.
Currently I'm interested in building a (small?) Internet of Things project. During research I found WSO2, an open source platform. I decided to use it and searched for developed projects. I found one decent project!
This project uses MQTT as communication protocol, Raspberry Pi<->Message Broker, and Message Broker<->Complex Event Manager.
My questions are the following:
1) Does the current version of the WSO2 Message Broker (v2.2.0) already support MQTT? Because I can't find documentation of this version supporting MQTT.
2) According to some references the WSO2 Message Broker v3.x.x will support MQTT, is that correct and when will this version be released?
3) Are there any other possibilities to use the WSO2 platform components in combination with the MQTT protocol?
4) Are there any other documented Internet of Things projects that use the WSO2 platform?
According to this article:
The WSO2 MB team was working on adding MQTT support; WSO2’s Co-Founder
and CTO Paul Fremantle used this for MQTT interop test at EclipseCon,
in San Francisco in March 2014, where he presented a talk. We decided
that MQTT was the ideal message protocol for devices due to its open,
less message overhead nature.
According to this article:
Upcoming WSO2 Message Broker (MB) 3.x.x release will be supporting
MQTT in addition to AMQP.
There is a relevant source code in this repository.
You could find more information on the WSO2 Message Broker architecture and capabilities through referring the article,
http://wso2.com/library/articles/2015/10/article-using-wso2-message-broker-as-a-scalable-mqtt-broker/
To answer to you questions,
MQTT will be supported from broker 3.0.0 version. and currently in RC stage. This will be released soon.
It provides seamless integration with other WSO2 products. i.e WSO2 CEP (Complex Event Processor), WSO2 ESB (Enterprise Service Bus).
Until released, you can use the Beta version of WSO2 Message Broker 3.0.0 which supports MQTT to test out your project.
WSO2 Message Broker 3.0.0 Beta
The 2.2.0 version does not support MQTT.
Furthermore, since all WSO2 products are based on OSGI concept, you can integrate any of features available from any WSO2 product.
Installing Features via the UI
But if you're looking some simple integration, try integrating WSO2 ESB with MB using MQTT.
WSO2 ESB MQTT Inbound Protocol
Halo everybody (maybe Asela? :),
Can anyone guide me how can I implement Oracle Coherence as a Cache provider with WSO2 Identity Server 5.0.0 clustered using with WSO2 ELB?
I found some very useful links on that topic, from which I consider this one as a good start: Clustering Identity Server
But I cannot find a way how to find solution for changing Hazelcast cache provider for any other provider.
I also realized, WSO2 is not using javax.caching implementation from JDK (since it was introduced in 1.7 and later), it is using its own based on JSR-107 (from which JSR I suppose Java JDK JCache is originated.
This article shows, that there is a way, how to somehow implement user JSR 107 JCache, but I don't see it configured for whole Identity Server:
WSO2 Multi-tenant Cache: JSR-107 (JCache)
I'm expecting answer which will guide me, what to change or add (for instance to carbon core) and where to setup / configure those changes, to make them global used within WSO2 Identity Server 5.0.0.
I hope it is relevant question and since this Carbon based platform is very rich and configurable, I hope this will be possible with some time invested.
Thank you in advance,
Josef
Coherence supports the real JCache APIs, so if WSO2 uses JCache, it should be easy to integrate Coherence!
I would like to know whether current version of enterprise mobility manager support Email containerization via Nitrodesk Touchdown & app containerization? If yes, Please provide me the steps..
WSO2 EMM does not support Email containerization & app containerization at the moment. But you could use WSO2 EMM to configure Email settings & control the apps that can be installed on a device.
WSO2 EMM supports email containerization via Nitrodesk touchdown. Anyway this goes with the support customers. But app containerization is not supported at the moment. For app containerization strategies you may look at Knox or iOS provided containerization strategies to be integrated into this.
Our client have recently decided to have WSO2 ESB as one of the integration platform in the system landscape. Here, we have lots of partners exchanging messages using AS2 service.
How can we provide AS2 service via ESB? Is there any support in WSO2 ESB for AS2 service or do we need to build this feature ourselves?
Thanks for your reply!
Br,
Jyoti
At the moment WSO2 ESB does not have any support for AS2. We can't predict about a certain timeline when this support will be available.
If you want, you can implement this by yourself. Basically, this will have to be implemented as a new transport for the ESB. AFAIK, you can get it done by WSO2 via sponsored development too.