Show Menu
主題×

Replicating Data Triggers to Publish Servers

When using ContextHub and AEM Targeting Engine to customize content based on data triggers in an author/publish setup, all the ContextHub and Personalization related configurations are not automatically replicated with the channels when they are published.
Follow this page to learn the manuals steps required to publish these configurations separately.
This basically comes down to manually publishing:
  1. ContextHub Store and UI modules configurations
  2. Personalization audiences
  3. Personalization activities

Steps for Replicating Data Triggers to Publish Server

Follow the steps below to replicate the data triggers to publish server.

Step 1: Replicating ContextHub Configurations

  1. Navigate to Tools > Deployment > Distribution > Publish Agent and click on the publish agent to configure your settings.
  2. Click Test Connection from the action bar to validate the communication of the author with the publish instance, as shown in the figure below.
  3. Select Add from the Distribution Agent screen tree and select the configuration path for your project, for example, /conf/screens/settings/cloudsettings/configuration. /conf/screens/settings/cloudsettings/configuration
  4. Click Submit .

Replicating the Audiences

  1. Navigate to your AEM instance > Personalization > Audiences or use http://localhost:4502/libs/cq/personalization/touch-ui/content/v2/audiences.html to navigate direcly.
  2. Drill down into your project folder, for example, /conf/screens/ .
  3. Select all audiences and segments from the the user interface.
  4. Click Manage Publication from the action bar.
  5. Click Next and Publish .

Replicating the Activities

  1. Navigate to your AEM instance > Personalization > Activities or use http://localhost:4502/libs/cq/personalization/touch-ui/content/v2/activities.html to navigate direcly.
  2. Drill down into your project folder, that is, /content/campaigns/screens/… .
  3. Select all activities from the user interface.
  4. Click Manage Publication from the action bar.
  5. Click Next and Publish .
Replicating ContextHub configurations and audiences is done during the project setup, while replicating activities and will be required every time targeting is changed inside a channel.

Result

If replication is successful, you should view the following structure on the publish instance (or similar for your project):
/conf/screens/settings/cloudsettings/configuration/… /conf/screens/settings/wcm/segments/… /content/campaigns/screens/…

Troubleshooting Test Connection

If the test connection fails while replicating the ContextHub configurations, follow the section below for troubleshooting the issue:
  1. Navigate to Tools > Deployment > Distribution > Publish Agent .
  2. Click Edit from the action bar and ensure the endpoint URL in Importer Endpoints field is also pointing to the publish server URL in Distribution Agent.
  3. If you not using the default admin credentials, then you need to configure the distribution agent with a different username and password.
    Follow the steps below:
    1. Navigate to Tools > Operations > Web Console http://localhost:4502/system/console/configMgr
    2. Search for Apache Sling Distribution Transport Credentials - User Credentials based DistributionTransportSecretProvider
    3. Create a configuration, by populating Name, User name and password, for example, slingTransportSecretProvider.
    4. Click Save
    5. Use Cmd +F to search for Apache Sling Distribution Agent - Forward Agents Factory to open the configurations and search for for Transport Secret Provider .
    6. Update the (name=default) with (name=slingTransportSecretProvider) .
    7. Click Save and run the test connection again from the Distribution Agent screen from your AEM instance again.