From the following thread my comprehension of WSO2 EMM is it allows multiple devices per user.
WSO2 EMM: Delete device from Device Management.
Is true that once registered is impossible to remove. only manually delete from EMM ?
Is there a way to enforce / limit one device per user (in both scenario: BYOD & COPE)
You can use Wipe or Enterprise Wipe to remove a device form a user.
(Wipe will remove all the data which is in the device and remove the device from EMM. Enterprise Wipe will remove only the enterprise data and remove the device from EMM)
Currently you cannot. But you can customize EMM for that purpose since WSO2 EMM is free and opensource.
Related
Can someone explaine me step by step how configure location tracking with WSO2 iot 3.1.0 analytics for 1000 android and mobiles devices?
We have a lot of tecniciens working on fields and we need to track them when they are out of their itinaries or not. We have several groups of techniciens across the country.
My hope is to have several custom reports base on location with devices and tecniciens intinaries on an Analytics dashboard. When the guy is out of the zone, I receive alerte message.
I have a plateform with wso2iot-3.1.0-update1, running on 1 server OS: Centos 6.7 .
The geofencing is activated in devicemgt (In zone, out of zone, )
I'm still using the default open sreet map
Devices are already in device management and users accounts but when we clic on location of a device, the itinary is not well adjusted to the map.
is it possible to do this with open street map or I must used google map and how?
Notice that is for real time tracking.
Documenttaion used:
https://docs.wso2.com/display/IoTS310/Monitoring+Devices+Using+Location+Based+Services
https://docs.wso2.com/display/IoTS310/Understanding+the+WSO2+IoT+Server+Analytics+Framework
Thanks in advance
When clustering WSO2 products, you create a database for the registry and other items that WSO2 product use for operations. With the combined WSO2 Enterprise Integrator, it consist of multiple elements (ESB, Business Process Manager, Message Broker, Analytics, and MSF4J).
Do you create different registry database for each sub-product or you use only one that is created for the first?
OPTION #1: WSO2_USER_DB, REGISTRY_DB, REGISTRY_LOCAL1, REGISTRY_LOCAL2
OPTION #2: ESB_WSO2_USER_DB, ESB_REGISTRY_DB, ESB_REGISTRY_LOCAL1, ESB_REGISTRY_LOCAL2, MB_WSO2_USER_DB, MB_REGISTRY_DB, MB_REGISTRY_LOCAL1, MB_REGISTRY_LOCAL2 ... etc.
I understand that user database can be shared since the authentication manager is similar. But is it the case with the registry database?
I'm new to clustering so this question might be a little not appropriate for advanced users.
WSO2 EI can offer various services, usually separately. For example WSO2 EI for integration or WSO2 EI for process automation.
When you install this product in clustering you do it under a specific role and not combined.
In essence you have local registry for each node and one shared for the synchronization of artifacts.
I hope it helps you.
Each of the profiles included in the EI is separate runtimes. You need to configure the profiles only according to your use case.
For example: If you are using Integrator profile (ESB) and MB profile (MB) you need to maintain two different registry data sources for ESB and MB as defined in your second option.
OPTION #2: ESB_WSO2_USER_DB, ESB_REGISTRY_DB, ESB_REGISTRY_LOCAL1, ESB_REGISTRY_LOCAL2, MB_WSO2_USER_DB, MB_REGISTRY_DB, MB_REGISTRY_LOCAL1, MB_REGISTRY_LOCAL2.
If you want to share the users across both applications, you can use one USER_DB instead of using two separate USER_DBs for ESB_WSO2_USER_DB and MB_WSO2_USER_DB.
EI clustering guide can be found from https://docs.wso2.com/display/EI610/Clustered+Deployment
Is there another way to cluster WSO2 Identity Servers aside from connecting to another node's embedded-LDAP user store? I turn off embedded-LDAP anyway per other instructions. Would it be better to connect to another user's JDBC store instead?
https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server+5.1.0%2C+5.2.0+and+5.3.0
Sharing the user stores is mandatory for the functionality of the cluster as both nodes of the cluster should be exposed to the same user base but the user store doesn't have to be the embedded LDAP. The embedded LDAP is usually used for development purposes. It is not recommended to use them in the production environment. So if your still in PoC stage, it is fine to point both nodes one embedded LDAP otherwise I recommend you to have an external user store such as LDAP, AD or a JDBC one.
You can either use an existing LDAP/AD or point to an outside JDBC user store. But both nodes should point to the same user store. You can refer [1] for more information on configuring different types of user stores.
I am trying to set up a clustered environment for WSO2 API Manager. In the environment I need there is no need for an external store. I looking to start with the least amount of nodes and JVMs that yet is scalable with growing number of API requests.
Having looked at the WSO2 documentation
Clustering WSO2 API Manager and specifically the "Store and Publisher components in a single server node" model.
Some questions on this deployment model
Where is the Gateway Manager deployed?
I understand the publisher and store are on the same server node. Can they be run in the same JVM? If so would you use the default profile that also starts up KM and Gateway or soemthing else?
(Appologies but I can't post the image due to my low reputation value. I would have thought the image of the model would have helped)
Yes - API Store and Publisher will be running in the same JVM. As there is no profile for Store & Publisher (see [1] for available profiles), we need to start API Manager in the default profile. And yes it will start KM & Gateway components as well. But you can block (not expose) gateway ports. And regarding gateway manager, I guess one gateway node can act as both manager and worker in this deployment pattern.
[1] https://docs.wso2.com/display/AM180/Product+Profiles
As per the design publisher is a subset of store. So, If you start with profile api-store you will eventually get publisher as well. In this case you can start the server with following option.
-Dprofile=api-store
I am trying to understand the whole WSO2 SOA topology, but not able to understand
how the CEP and BAM fit together
Can CEP provide visual monitoring of processed events e.g. integration with WSO2 GS
Although WSO2 website says CEP is tightly integrated with BAM for post processing I couldnt
find any scenario explaining the same or how its done..( can CEP feed BAM ? how to configure the same)
Why would you have CEP + BAM together ? Any use case
Answers
All WSO2 projects are capable of integrating with each other because they are based on the same underlying platform (WSO2 Carbon). In this particular case, WSO2 CEP and GS. One way is, persisting processed results from CEP in a data store or file, and reading it from a Gadget backend so that the gadget (the frontend) can visualize it in the GS. If you want, you can install GS features (dashboard, gadget repo, etc) on top of CEP as well and use the same server runtime. But, for the latter it has to be based on the same Carbon version
This means, that the same data agent can send events to BAM as well as CEP. They both share the Thrift and REST APIs. Similar to 1, CEP and BAM can exist in the same runtime or can be downloaded and used separately. One related article is at here
The primary use case was processing the same event for real time analytics for CEP and a just-in-time (near real time) batch based processing for BAM. Ex: Processing up time related analytics for servers can be broken down to fit both servers. For CEP the query can do, Alert me a server does not respond for 3 requests in 30 secs. For BAM, you can plot the uptime trend within a hour/day/week.