We are planning to develop MDM solution based on WSO2 EMM.
Since WSO2 EMM is 100% open source and Apache licensed, IĀ hope there is no cost associated with it provided we host and support it.
For iOS platform configuration, the documentation says CSR file needs to be submitted to WSO2 and then WSO2 will send back the signed CSR, P2 repository for enabling the iOS features.
I have an doubt, what is the criteria WSO2 uses for sending back signed WS02. And is there any hidden costĀ associated with this process.
Any help will be appreciated.
There is no cost associate with the process. However you will be evaluated before they sending back the signed CSR.
Related
When I Try to download WSO2 Process Server, It redirects me to API Manager.
The link is http://wso2.com/products/business-process-server
Is the WSO2 Process Server deprecated?
WSO2 Business Process Server(BPS) is now deprecated and discontinued. But you can still use it. WSO2 BPS was merged to WSO2 Enterprise Integrator a couple of years back as a different runtime. So if you want to use BPS capabilities you can download WSO2 EI from here and start the Business Process Profile. You can read more about the BPS Profile here.
Yes, the product is not available now.
You can migrate to EI 6.6.0 if you are using WSO2 BPS 3.6.0 - https://docs.wso2.com/display/EI660/Upgrading+from+WSO2+Business+Process+Server
In the latest EI/MI versions do not come with the BPS solution.
It's best to migrate to Micro-integrator 4.1.0 and use the latest capabilities of the enterprise integration. Micro-integrator is the latest version of the WSO2 ESB platform. However, it does not support BPS capabilities as moving forward, WSO2 will continue to provide only the interprise integration capabilities through the platform and for some of the features such as Message Broker and BPS have been deprecated. For use cases on Message Broker and BPS, you need to integrate with 3rd party products such as Camunda (for BPS) and RabbitMQ (for Message Broker).
I have setup WSO 2 emm 2.0.1 in development environment. I was able to successfully enroll android device and check the MDM policies of android device. I did not do any additional platform configuration by creating any kind of certificate to get android emm working. But in case of IOS wso2 profile is not getting installed. And while installing iOS agent error is can not connect serverIP. Do I need to create all the certificate as mentioned in the link https://docs.wso2.com/display/EMM201/iOS+Platform+Configurations . I have never worked with android and iOS devices previously .
Please help !!
Yes you need to follow all the instructions provided in the following documentation in order to enable communication with your ios devices.
These are protocols provided by Apple to ensure the device security.
https://docs.wso2.com/display/EMM201/iOS+Platform+Configurations
https://docs.wso2.com/display/EMM201/Generating+a+MDM+APNS+Certificate
Make sure to complete all the configurations where you need to put your ip or domain as provided in the documentations
Obtaining a signed CSR from wso2 also required in order to use emm server to manage ios devices.
Refer to the below tutorial if you are using a public server with a SSL certificate obtain from a know Certificate Authority.
http://kamidupunchihewa.blogspot.com/2016/07/configure-device-communication-when.html
I am facing problems while connecting with the emm store from my device.
I want to know what changes I have to make so that I can access emm store and can download the apps on my device. Any help will really be appreciated. I am not able to understand this
You do not have to perform any android configurations for the emm server in order to enroll android devices. EMM server contains configurations for android.
In the documentation you are provided with instructions how to modify
the agent app to use https protocol rather than http protocol and
generate a new .apk file.
In order to connect your login to store and install applications to your device you need to provide related permissions to the related user. Use the carbon console for grant permissions
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!
The WSO2 Identity Server features list XDAS, but I can't find any more information on how WSO2 uses it.
Is there any documentation available about how the WSO2 Identity Server uses XDAS?
Does the Identity Server have an XDAS service API that it can offer auditing services for use by other (external) applications?
WSO2 offer a Centralized Auditing & Monitoring solution. How can I set this up for myself?
We have done some work with XDAS in the WSO2 platform and the effort is on hold due to the less demand for XDAS.
You can find additional details from here : http://mail.wso2.org/mailarchive/architecture/2011-February/004868.html
I have checked out the whole WSO2 trunk and performed a find for files containing XDAS in their filename and a grep for files containing XDAS in their contents. Nothing was found.
My guess is that XDAS has not been implemented in the WSO2 platform.