ContextHub is a framework for storing, manipulating, and presenting context data. For more detail on ContextHub, please see the ContextHub developer overview.
You can configure the ContextHub toolbar to control whether it appears in Preview mode, to create ContextHub stores, and add UI modules.
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:
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.
Configure the UI modes and modules that appear in the ContextHub toolbar in Preview mode:
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.
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.
On the Experience Manager rail, click or tap Tools > Sites > Context Hub.
Click or tap the default Configuration Container.
Click or tap the Context Hub Configuration.
Click or tap the Create button, and then click or tap Context Hub UI Mode.
Provide values for the following properties:
coral-Icon--user
Click or tap Save.
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 | Description | Store |
---|---|---|
contexthub.base | A generic UI module type | Configured in the UI module properties |
contexthub.browserinfo | Displays information about the browser | surferinfo |
contexthub.datetime | Displays date and time information | datetime |
contexthub.location | Displays the latitude and longitude of the client, as well as the location on a map. Enables you to change the location. | geolocation |
contexthub.screen-orientation | Displays the screen orientation of the device (landscape or portrait) | emulators |
contexthub.tagcloud | Displays statistics about page tags | tagcloud |
granite.profile | Displays the profile information for the current user, including authorizableID , displayName and familyName . You can change the value of displayName and familyName . |
profile |
On the Experience Manager rail, click or tap Tools > Sites > ContextHub.
Click or tap the Configuration Container to which you want to add a UI module.
Click or typ the ContextHub Configuration to which you want to add the UI module.
Click or tap the UI mode to which you are adding the UI module.
Click or tap the Create button, then click or tap ContextHub UI Module (generic).
Provide values for the following properties:
(Optional) To override the default store configuration, enter a JSON object to configure the UI Module.
Click or tap Save.
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.)
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.
AEM provides the following sample store candidates upon which you can base a store.
Store Type | Description |
---|---|
aem.segmentation | Store for resolved and unresolved ContextHub segments. Automatically retrieves segments from the ContextHub SegmentManager |
contexthub.geolocation | Stores the latitude and longitude of the browser location. |
granite.emulators | Defines properties and capabilities for a number of devices, and detects the current client device |
granite.profile | Stores profile data for the current user |
contexthub.surferinfo | Stores information about the client, such as device information, browser type, and window orientation |
On the Experience Manager rail, click or tap Tools > Sites > ContextHub.
Click or tap the default configuration container.
Click or tap Contexthub Configuration
To add a store, click or tap the Create icon and then click or tap ContextHub Store Configuration.
Provide values for the basic configuration properties and then click or tap Next:
(Optional) To override the default store configuration, enter a JSON object in the Detail Configuration (JSON) box.
Click or tap Save.
This example illustrates how to configure a store and display the data in a UI module. In this example, the MD5 service of the jsontest.com 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 https://md5.jsontest.com/?text=%22text%20to%20md5%22
. The service returns the following data which is displayed in a UI module:
{
"md5": "919a56ab62b6d5e1219fe1d95248a2c5",
"original": "\"text to md5\""
}
The contexthub.generic-jsonp sample store candidate enables you to retrieve data from a JSONP service or a web service 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 jsontest.com 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):
{
"service": {
"jsonp": false,
"timeout": 1000,
"ttl": 1800000,
"secure": false,
"host": "md5.jsontest.com",
"port": 80,
"params":{
"text":"text to md5"
}
}
}
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 Persona UI Mode. For the UI Module, use the following property values:
UI Module Title: MD5
Module Type: contexthub.base
Detail Configuration (JSON):
{
"icon": "coral-Icon--data",
"title": "MD5 Conversion",
"storeMapping": { "md5": "md5" },
"template": "<p> {{md5.original}}</p>;
<p>{{md5.md5}}</p>"
}
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.
Edit the ContextHub’s configuration and check the option Debug
Use CRXDE Lite to set the property debug
to true under:
/conf/global/settings/cloudsettings
or/conf/<site>/settings/cloudsettings
Configure the Adobe Granite ContextHub OSGi service (PID = com.adobe.granite.contexthub.impl.ContextHubImpl
) to log detailed Debug messages that are useful when developing.
To configure the service you can either use the Web Console or use a JCR node in the repository:
com.adobe.granite.contexthub.debug
property to true
.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 don’t want any debug information at all. Because it is a global setting, it is enabled via OSGi.
http://<host>:<port>/system/console/configMgr
ContextHub can be disabled to prevent it from loading js/css and initializing. There are two options to disable ContextHub:
Edit the ContextHub’s configuration and check the option Disable ContextHub
or
disabled
to true under /conf/global/settings/cloudsettings/<configName>/contexthub