Cloud Service Configurations cloud-service-configurations

Configurations are designed to provide the logic and structure for storing service configurations.

You can extend the existing instances to create your own configurations.

Concepts concepts

The principles used in developing the configurations have been based on the following concepts:

  • Services/Adapters are used to retrieve the configurations.
  • Configurations (for example, properties/paragraphs) are inherited from the parents.
  • Referenced from analytics nodes by path.
  • Easily extensible.
  • Has the flexibility to cater for more complex configurations, such as Adobe Analytics.
  • Support for dependencies (for example, Adobe Analytics plugins need an Adobe Analytics configuration).

Structure structure

The base path of the configurations is:


For each type of configuration, a template and a component is provided. This makes it possible to have configuration templates that can fulfill most needs after being customized.

To provide a configuration for new services, do the following:

  • Create a servicepage in


  • Under this:

    • a configuration template
    • a configuration component

The template and component must inherit the sling:resourceSuperType from the base template:


Or base component respectively


The service provider should also provide the service page:


Template template

Your template extends the base template:


And define a resourceType that points to the custom component.

sling:resourceSuperType = cq/cloudserviceconfigs/templates/configpage
allowedChildren = /libs/cq/analytics/templates/sitecatalyst
allowedPaths = /etc/cloudservices/analytics/*, /etc/cloudservices/analytics/.*
componentReference = cq/analytics/components/sitecatalyst
cq:designPath = /etc/designs/cloudservices
sling:resourceType = cq/analytics/components/sitecatalystpage

sling:resourceSuperType = cq/cloudservices/templates/configpage
allowedChildren = /libs/cq/analytics/templates/generictracker
allowedPaths = /etc/cloudservices/analytics/*, /etc/cloudservices/analytics/.*
cq:designPath = /etc/designs/cloudservices
sling:resourceType = cq/analytics/components/generictrackerpage

Components components

Your component should extend the base component:




After setting up your template and component, you can add your configuration by adding subpages under:


Content Model content-model

The content model is stored as cq:Page under:



The configurations are stored under the subnode jcr:content.

  • Fixed properties, defined in a dialog should be stored on the jcr:node directly.
  • Dynamic elements (using parsys or iparsys) use a subnode to store the component data.
/etc/cloudservices/service/config/jcr:content as nt:unstructured
par/component/ as cq:Component

API api

For reference documentation on the API, see

AEM Integration aem-integration

Available services are listed in the Cloud Services tab of the Page Properties dialog (of any page that inherits from foundation/components/page or wcm/mobile/components/page).

The tab also provides:

  • a link to the location where you can enable the service
  • choose a configuration (subnode of the service) from a path field

Password Encryption password-encryption

When storing user credentials for the service, all passwords should be encrypted.

You can achieve this by adding a hidden form field. This field should have the annotation @Encrypted in the property name; that is, for the password field the name would be written as:


The property will then be automatically encrypted (using the CryptoSupport service) by the EncryptionPostProcessor.

This is similar to the standard [SlingPostServlet]( annotations.
By default the EcryptionPostProcessor only encrypts POST requests made to /etc/cloudservices.

Additional Properties for Service Page jcr:content Nodes additional-properties-for-service-page-jcr-content-nodes

Reference path to a component to be automatically included in the page.
This is used for additional functionality and JS inclusions.
This includes the component on the page where
is included (normally before the body tag).
In case the of Adobe Analytics and Adobe Target, we use this to include additional functionality, such as JavaScript calls to track visitor behavior.
Short description of the service.
Extended description of the service.
Service ranking for use in listings.
Filter for displaying configurations in page properties dialog.
URL to service website.
Label for service URL.
Path to thumbnail for service.
Visibility in page properties dialog; visible by default (optional)

Use Cases use-cases

These services are provided by default: