Replicating Data Triggers to Publish Servers replicating-data-triggers

Last update: Mon Apr 15 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

Intermediate
Developer

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.

This page helps you learn the manual steps required to publish these configurations separately.

This basically comes down to manual publishing:

ContextHub Store and UI modules configurations
Personalization audiences
Personalization activities

Steps for Replicating Data Triggers to Publish Server replicating-data-triggers-publish

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

Step 1: Replicating ContextHub Configurations replicating-contexthub-configurations

Navigate to Tools > Deployment > Distribution > Publish Agent and select the publishing agent so you can configure your settings.

note note
NOTE
Alternatively, you can use the `http://localhost:4502/libs/granite/distribution/content/distribution-agent.html?agentName=publish` to navigate to the screen directly to configure and test the connection.

Select Test Connection from the action bar so you can validate the communication of the Author with the Publishing instance, as shown in the following:

note note
NOTE
If the test fails, fix the replication agent configuration between the Author and Publishing instance. See Troubleshooting Test Connection for more details.

Select Add from the Distribution Agent screen tree and select the configuration path for your project, for example, /conf/screens/settings/cloudsettings/configuration.
Select Submit.

Replicating the Audiences replicating-audiences

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

Replicating the Activities replicating-activities

Navigate to your AEM instance > Personalization > Activities or use http://localhost:4502/libs/cq/personalization/touch-ui/content/v2/activities.html to navigate directly.
Drill down into your project folder, that is, /content/campaigns/screens/….
Select all activities from the user interface.
Select Manage Publication from the action bar.
Select Next and Publish.

IMPORTANT

Replicating ContextHub configurations and audiences is done during the project setup while replicating activities and are required every time targeting is changed inside a channel.

Result 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 troubleshoot-test

If the test connection fails while replicating the ContextHub configurations, follow the section below for troubleshooting the issue:

Navigate to Tools > Deployment > Distribution > Publish Agent.
Select Edit from the action bar and ensure that the endpoint URL in Importer Endpoints field is also pointing to the publishing server URL in Distribution Agent.
If you are not using the default admin credentials, then you must 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/configMgrso you can open the Adobe Experience Manager Web Console screen.
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. Select Save
5. Use Cmd +F to search for Apache Sling Distribution Agent - Forward Agents Factory to open the configurations and search for Transport Secret Provider.
6. Update the (name=default) with (name=slingTransportSecretProvider).
7. Select Save and run the test connection again from the Distribution Agent screen from your AEM instance again.

recommendation-more-help

adce462a-f916-4dbe-9ab5-0b62cfb0f053