Hi all,
As discussed in [1] we will be using a single instance of Async data
publisher when implementing the publisher for EMM.
[1] [dev] Using AsyncDataPublisher of BAM
Regards,
Inosh
On Tue, Sep 30, 2014 at 8:46 AM, Inosh Perera wrote:
> Hi Harshan,
>
> yes, I will add it. Its kind of simila
Hi Harshan,
yes, I will add it. Its kind of similar to the 3rd point under policy. "Policy
violation frequency- per user/ over roll/ during a time period"
Regards,
Inosh
On Mon, Sep 29, 2014 at 11:40 AM, Harshan Liyanage wrote:
> Hi Inosh,
>
> Please find my comments inline.
>
> >>> User's who
Hi Inosh,
Please find my comments inline.
>>> User's who have violated a policy during a certain period.(This will
catch if the user violates a policy and then again adheres to it later)
I think it would be better to get the list of users who have violated a
particular policy first. Lets give the
Hi all,
Following are some of the information we can extract once we integrate BAM,
Please update the list if you see anything missing,
Info-
User's location during a certain time period
How many times the user visited an area.
Battery levels variation of a device during its life time or during a
Hi all,
Based on an offline discussion we had with EMM team on the where to pick
the data in order to publish, we decided it would be best, not to write a
custom valve and handle it, instead collect all the data at EMM level. This
is because, some data doesn't go through API manager valve currently
Hi Dilshan,
Stat publisher component is written in Java, and there will be APIs to
publish each event to BAM. With current implementation of EMM, Jaggery will
call these APIs when it is necessary to publish data. And this call will
happen in a separate thread[1] and inside java publishing component
Hi Inosh,
With the proposed refactoring discussions there is a high chance that most
of the existing code get migrated to components. Hence is it possible to
move this stat publisher logic into Java components and call them through
API layer or some other generic point rather than adding them in a
Hi Inosh,
And you need to extract parameter fields in the Application level and note
that these field set should be fixed for all the events. You can send
custom key-value pairs as well inside a separate string map . (Refer
https://docs.wso2.com/display/BAM241/Data+Publisher)
Thanks.
*Maninda E
Hi Maninda/Gihan,
Based on the offline discussions we had, your suggestions here seems to be
the ideal solution for our scenario. Since the payloads coming to EMM have
complex Json objects, writing a custom valve and extracting data doesn't
seem like a good option. We will have to extract data at a
Hi Inosh,
Yes, this is correct. You can use data agent that installs in EMM to send
captured data to BAM. For this you need to implement thrift based client.
Also, you can use the HTTP event adaptor that comes with BAM 2.5.0 to
achieve this task. Still, we are preparing the final documents for th
Hi all, We are trying to integrate BAM with EMM to provide ability to
analyse data coming from devices. Bellow is the initial architecture
diagram.
According to the requirement we have, we need to read data that comes with
the payload, not meta data. These data, come from devices as Json and si
11 matches
Mail list logo
