Configuring ContextHub configuring-contexthub

ContextHub is a framework for storing, manipulating, and presenting context data. For more detail on ContextHub, see the developer documentation. ContextHub replaces Client Context in the touch UI.

Configure the ContextHub toolbar to control whether it appears in Preview mode, to create ContextHub stores, and add UI modules using the Touch-Optimized UI.

Disabling ContextHub disabling-contexthub

By default, ContextHub is enabled in an AEM installation. ContextHub can be disabled to prevent it from loading js/css and initializing.

  • Use CRXDE Lite to set the property disabled to true under /libs/settings/cloudsettings/legacy/contexthub
Due to repository restructuring in AEM 6.4, the location of ContextHub configurations changed from /etc/cloudsettings to:
  • /libs/settings/cloudsettings
  • /conf/global/settings/cloudsettings
  • /conf/<tenant>/settings/cloudsettings

Showing and Hiding the ContextHub UI showing-and-hiding-the-contexthub-ui

Configure the Adobe Granite ContextHub OSGi service to show or hide the ContextHub UI on your pages. The PID of this service is com.adobe.granite.contexthub.impl.ContextHubImpl.

To configure the service you can either use the Web Console or use a JCR node in the repository:

  • Web Console: To show the UI, select the Show UI property. To hide the UI, clear the Hide UI property.
  • JCR node: To show the UI, set the boolean com.adobe.granite.contexthub.show_ui property to true. To hide the UI, set the property to false.

When showing the ContextHub UI, it only appears on pages on AEM author instances. The UI does not appear on pages of publish instances.

Adding ContextHub UI Modes and Modules adding-contexthub-ui-modes-and-modules

Configure the UI modes and modules that appear in the ContextHub toolbar in Preview mode:

  • UI Modes: Groups of related modules
  • Modules: Widgets that expose context data from a store and enable authors to manipulate the context

UI modes appear as a series of icons on the left side of the toolbar. When selected, the modules of a UI mode appear to the right.


Icons are references from the Coral UI icon library.

Adding a UI Mode adding-a-ui-mode

Add a UI mode to group related ContextHub modules. When you create the UI mode, you provide the title and icon that appear in the ContextHub toolbar.

  1. On the Experience Manager rail, click Tools > Sites > Context Hub.

  2. Click the default Configuration Container.

  3. Click the Context Hub Configuration.

  4. Click the Create button, and then click Context Hub UI Mode.


  5. Provide values for the following properties:

    • UI Mode Title: The title that identifies the UI mode
    • Mode Icon: The selector for the Coral UI icon to use, for example, coral-Icon--user
    • Enabled: Select to show the UI mode in the ContextHub toolbar
  6. Click Save.

Adding a UI Module adding-a-ui-module

Add a ContextHub UI module to a UI mode so that it appears in the ContextHub toolbar for previewing page content. When you add a UI module, you are creating an instance of a module type that is registered with ContextHub. To add a UI module, you must know the name of the associated module type.

AEM provides a base UI module type as well several sample UI Module types upon which you can base a UI module. The following table provides a brief description of each one. For information about developing a custom UI module, see Creating ContextHub UI Modules.

The UI module properties include a detail configuration where you can provide values for module-specific properties. You provide the detail configuration in JSON format. The Module Type column in the table provides links to information about the JSON code required for each UI module type.

Module Type
A generic UI module type
Configured in the UI module properties
Displays information about the browser
Displays date and time information
Display the client device
Displays the latitude and longitude of the client, and the location on a map. Enables you to change the location.
Displays the screen orientation of the device (landscape or portrait)
Displays statistics about page tags
Displays the profile information for the current user, including authorizableID, displayName and familyName. You can change the value of displayName and familyName.
  1. On the Experience Manager rail, click Tools > Sites > ContextHub.

  2. Click the Configuration Container to which you want to add a UI module.

  3. Click or typ the ContextHub Configuration to which you want to add the UI module.

  4. Click the UI mode to which you are adding the UI module.

  5. Click the Create button, then click ContextHub UI Module (generic).


  6. Provide values for the following properties:

    • UI Module Title: A title that identifies the UI module
    • Module Type: The module type
    • Enabled: Select to show the UI module in the ContextHub toolbar
  7. (Optional) To override the default store configuration, enter a JSON object to configure the UI Module.

  8. Click Save.

Creating a ContextHub Store creating-a-contexthub-store

Create a Context Hub store to persist user data and access the data as needed. ContextHub stores are based on registered store candidates. When you create the store, you need the value of the storeType with which the store candidate was registered. (See Creating Custom Store Candidates.)

Detailed Store Configuration detailed-store-configuration

When you configure a store, the Detail Configuration property enables you to provide values for store-specific properties. The value is based on the config parameter of the store’s init function. Therefore, whether you need to provide this value, and the format of the value, depends on the store.

The value of the Detail Configuration property is a config object in JSON format.

Sample Store Candidates sample-store-candidates

AEM provides the following sample store candidates upon which you can base a store.

Store Type
Store for resolved and unresolved ContextHub segments. Automatically retrieves segments from the ContextHub SegmentManager
Stores the currently resolved segments. Listens to the ContextHub SegmentManager service to automatically update the store
Stores the latitude and longitude of the browser location.
Stores the current date, time, and season for the browser location
Defines properties and capabilities for several devices, and detects the current client device
Retrieves and stores data from a JSONP service
Stores profile data for the current user
Stores information about the client, such as device information, browser type, and window orientation
Stores page tags and tag counts
  1. On the Experience Manager rail, click Tools > Sites > ContextHub.

  2. Click the default configuration container.

  3. Click Contexthub Configuration

  4. To add a store, click the Create icon and then click ContexHub Store Configuration.


  5. Provide values for the basic configuration properties and then click Next:

    • Configuration Title: The title that identifies the store
    • Store Type: The value of the storeType property of the store candidate upon which to base the store
    • Required: Select
    • Enabled: Select to enable the store
  6. (Optional) To override the default store configuration, enter a JSON object in the Detail Configuration (JSON) box.

  7. Click Save.

Example: Using a JSONP Service example-using-a-jsonp-service

This example illustrates how to configure a store and display the data in a UI module. In this example, the MD5 service of the site is used as a data source for a store. The service returns the MD5 hash code of a given string, in JSON format.

A contexthub.generic-jsonp store is configured so that it stores data for the service call The service returns the following data which is displayed in a UI module:

   "md5": "919a56ab62b6d5e1219fe1d95248a2c5",
   "original": "\"text to md5\""

Creating a contexthub.generic-jsonp Store creating-a-contexthub-generic-jsonp-store

The contexthub.generic-jsonp sample store candidate enables you to retrieve data from a JSONP service or a web servcie that returns JSON data. For this store candidate, use the store configuration to provide details about the JSONP service to use.

The init function of the ContextHub.Store.JSONPStore JavaScript class defines a config object that initializes this store candidate. The config object contains a service object that includes details about the JSONP service. To configure the store, you provide the service object in JSON format as the value for the Detail Configuration property.

To save data from the MD5 service of the site, use the procedure in Creating a ContextHub Store using the following properties:

  • Configuration Title: md5

  • Store Type: contexthub.generic-jsonp

  • Required: Select

  • Enabled: Select

  • Detail Configuration (JSON):

    code language-xml
     "service": {
     "jsonp": false,
     "timeout": 1000,
     "ttl": 1800000,
     "secure": false,
     "host": "",
     "port": 80,
     "text":"text to md5"

Adding a UI Module for the md5 Data adding-a-ui-module-for-the-md-data

Add a UI module to the ContextHub toolbar to display the data that is stored in the example md5 store. In this example, the contexthub.base module is used to produce the following UI module:


Use the procedure in Adding a UI Module to add the UI module to an existing UI Mode, such as the sample Perona UI Mode. For the UI Module, use the following property values:

  • UI Module Title: MD5

  • Module Type: contexthub.base

  • Detail Configuration (JSON):

    code language-xml
     "icon": "coral-Icon--data",
     "title": "MD5 Converstion",
     "storeMapping": { "md5": "md5" },
     "template": "<p> {{md5.original}}</p>;

Debugging ContextHub debugging-contexthub

A debugging mode for the ContextHub can be enabled to allow for troubleshooting. The debug mode can be enabled either through the ContextHub configuration or via CRXDE.

Via the Configuration via-the-configuration

Edit the ContextHub’s configuration and check the option Debug

  1. In the rail click Tools > Sites > ContextHub
  2. Click the default Configuration Container
  3. Select the ContextHub Configuration and click Edit Selected Element
  4. Click Debug and click Save

Via CRXDE via-crxde

Use CRXDE Lite to set the property debug to true under:

  • /conf/global/settings/cloudsettings or
  • /conf/<tenant>/settings/cloudsettings
For ContextHub configurations still located under their legacy paths, the location to set the debug property is /libs/settings/cloudsettings/legacy/contexthub.

Silent Mode silent-mode

Silent mode suppresses all debug information. Unlike the normal debug option, which can be set independently for each ContextHub configuration, silent mode is a global setting which takes precedent over any debug settings on the ContextHub configuration level.

This is useful for your publish instance, where you do not want any debug information at all. Because it is a global setting, it is enabled via OSGi.

  1. Open the Adobe Experience Manager Web Console Configuration at http://<host>:<port>/system/console/configMgr
  2. Search for Adobe Granite ContextHub
  3. Click the configuration Adobe Granite ContextHub to edit its properties
  4. Check the option Silent Mode and click Save

Recovering ContextHub Configurations After Upgrading recovering-contexthub-configurations-after-upgrading

When an upgrade to AEM is performed, the ContextHub configurations are backed up and stored in a safe location. During the upgrade, the default ContextHub configurations are installed, replacing the existing configurations. The backup is required to preserve any changes or additions that you have made.

ContextHub configurations are stored in a folder named contexthub under the following nodes:

  • /conf/global/settings/cloudsettings
  • /conf/<tenant>/settings/cloudsettings

After an upgrade, the backup is stored in a folder named contexthub below a node named:

/conf/global/settings/cloudsettings/default-pre-upgrade_yyyymmdd_xxxxxxx or

The yyyymmdd portion of the node name is the date when the upgrade was performed.

To recover your ContextHub configurations, use CRXDE Lite to copy the nodes that represent your stores, UI modes, and UI modules from below the default-pre-upgrade_yyyymmdd_xxxxxx node to below:

  • /conf/global/settings/cloudsettings or
  • /conf/<tenant>/settings/cloudsettings