Unknown macro: {style}


Unknown macro: { margin}
Unknown macro: {div}
Kaa releases
Unknown macro: {div}

Page tree
Skip to end of metadata
Go to start of metadata

Kaa provides a mechanism for endpoints aggregation within the application that is based on groups. Grouping endpoints enables you to activate specific configuration parameters, control access to notification topics, etc. Please review the Kaa grouping design reference for more details.

This guide will familiarize you with the basic concepts of designing endpoint groups. It is assumed that you have either set up a Kaa Sandbox, or a fully-blown Kaa cluster already and that you have created a tenant and an application in Kaa. It is also strongly recommended to review collecting endpoint profiles guide before you proceed with this one. 

Basic architecture

The following diagram illustrates basic entities and data flows in scope of the endpoint profile management:

  • Endpoint profiles are generated based on the profile schema created by the developer for the application and profile data entered either by the developer or by the application user
  • Endpoints send their profiles to the Kaa server during the registration
  • The Kaa tenant developer specifies profile filters for endpoint groups using either Admin UI or REST API
  • Kaa Operations Server classifies endpoints into groups based on their profiles and the group profile filters

Configuring Kaa

Each Kaa application has a special, built-in, non-user-editable group "all" with weight 0. The associated profile filter is automatically set equal to "true" for each profile schema version in the system. Therefore, group "all" contains every endpoint registered in the application. You can create your custom endpoint groups using the Admin UI or REST API.  

Once created, an endpoint group does not contain any endpoints, so you will need to create and add custom profile filters to the group.

Profile filters

Each group can be associated with multiple profile filters, each specific to a separate profile schema version. Only one profile filter can be defined for a profile schema version.

We will use profile schema defined in "collecting endpoint profiles guide" section and the following sample profiles:

Profile AProfile BProfile C





    "build":"3.0 RC1"



    "build":"3.0 RC1"


Creating profile filters is possible through either Admin UI or REST API.

Once a profile filter is created, you need to activate it. Filters that are not activated do not impact endpoint groups and do not affect the endpoints.

Custom endpoint groups

The table below demonstrates the use of profile filters and results of filtering for sample profiles.

Group NameFilterresult for profile Aresult for profile Bresult for profile C
Android Froyo endpointsos.toString().equals("Android") and os_version.toString().startsWith("2.2")truefalsefalse
Android endpointsos.toString().equals("Android")truetruefalse
iOS 8 endpoints

os.toString().equals("iOS") and os_version.toString().startsWith("8")



3.0 RC1 QA group endpoints
build.toString().equals("3.0 RC1")

Thus, "Android Froyo endpoints" group will contain only device A; "Android endpoints" group with contain devices A and B; "iOS 8 endpoints" group will contain device C, and "3.0 RC1 QA group endpoints" will contain endpoints B and C.

Copyright © 2014-2015, CyberVision, Inc.

  • No labels