In a medium to large-scale deployment scenario it is typical to accumulate tens of millions of context sessions. Each session is identified by a context session token - a global unique identifier.
Arnica UnifiedLogon provides context session report, a tool for system administrators to monitor context session life-cycle and troubleshoot problems by analyzing intermediate application state saved in the context. However, such analysis may be complicated by a very large quantity of context sessions. To help with this problem, context sessions may be optionally associated with a context group. Filtering by context group narrows down context search and allows context analysis to be more focused on a specific functionality.
Example of context groups are the following: ReportContext, SavedForm, WebAPIWizardState, DataSyncProcessState, etc.
Any context session may be associated with only one context group. Once context is associated with a context group it may not be reassigned to another context group.
Arnica Platform APIs include optional context group services in the APIs which create or update context. If a specified context group does not exist, it is created automatically. Such context group management requires no administration as groups are created on the fly when needed. There is no limit to how many context groups may be created, and programmers decide and make up their own context group reference names.
Arnica Platform applications allow specifying a default context group in application configuration, which makes context session breakdown by context group declarative rather than programmatic.
In the Arnica UnifiedLogon Administrator application, context group management may be accessed from main menu \ configuration. Context session report accepts context group as an optional filter parameter.