This documentation describes how to integrate AEM with Adobe Campaign Standard, the subscription-based solution. If you are using Adobe Campaign 6.1, see Integrating with Adobe Campaign 6.1 for those instructions.
Adobe Campaign lets you manage email delivery content and forms directly in Adobe Experience Manager.
To use both solutions together at the same, you must first configure them to connect to one another. This involves configuration steps in both Adobe Campaign and Adobe Experience Manager. These steps are described in detail in this document.
Working with Adobe Campaign in AEM includes the ability to send email and forms via Adobe Campaign and is described at Working with Adobe Campaign.
In addition, the following topics may be of interest when integrating AEM with Adobe Campaign:
If you are extending your integration with Adobe Campaign, you may want to see the following pages:
Configuring Adobe Campaign involves the following:
To perform these operations, you must have the administration role in Adobe Campaign.
Make sure you have the following elements beforehand:
The aemserver user must be configured in Adobe Campaign. The aemserver is a technical user that will be used to connect the AEM server to Adobe Campaign.
Go to Administration > Users & Security > Users, and select the aemserver user. Click it to open the user settings.
You must configure an external account that allows you to connect Adobe Campaign to your AEM instance.
In AEM, be sure that you set the password for the campaign-remote user. You need to set this password to connect Adobe Campaign with AEM. Log in as administrator and in the user administration console, search for the campaign-remote user and click Set Password.
To configure an AEM external account:
Go to Administration > Application settings > External accounts.
Select the default aemInstance external account or create a new one by clicking the Create button.
Select Adobe Experience Manageri n the Type field and enter the access parameters used for your AEM authoring instance: server address, account name and password.
Be sure that you do not add an ending / slash at the end of the URL or the connection will not work.
Make sure that the Enabled checkbox is selected, then click Save to save your modifications.
The AEMResourceTypeFilter option is used to filter types of AEM resources that can be used in Adobe Campaign. This allows Adobe Campaign to retrieve AEM contents that are specifically designed to be used in Adobe Campaign only.
This option comes pre-configured; however, if you change this option, it may lead to a non-functioning integration.
To verify the AEMResourceTypeFilter option is configured:
By default, the AEM feature is not enabled in Adobe Campaign’s email templates. You can configure a new email delivery template that will be used to create emails with AEM content.
To create an AEM-specific email delivery template:
Go to Resources > Templates > Delivery templates.
Enable selection by clicking the checkmark in the action bar and selecting the existing Standard email (mail) default template, then duplicate it by clicking the Copy icon and clicking Confirm.
Disable the selection mode by clicking the x and open the newly created Copy of Standard email (mail) template, then select Edit properties from the action bar of the template dashboard.
You can modify the template’s Label.
In the properties Content section, change the Content source to Adobe Experience Manager. Then select the external account that was previously created and click Confirm.
Save your modifications by clicking Confirm and clicking Save.
Email deliveries created from this template will have the AEM content feature enabled.
To configure AEM, you must do the following:
Content created from the AEM authoring instance is first sent to the publishing instance. This publishing instance then transfers the content to Adobe Campaign. The replication agent must therefore be configured to replicate from the AEM authoring instance to the AEM publishing instance.
If you do not want to use the replication URL but instead use the public-facing URL, you can set the Public URL in the following configuration setting in the OSGi (Tools > Web Console > OSGi Configuration > AEM Campaign Integration - Configuration):
Public URL: com.day.cq.mcm.campaign.impl.IntegrationConfigImpl#aem.mcm.campaign.publicUrl
This step is also necessary to replicate certain authoring instance configurations into the publishing instance.
To configure replication between AEM instances:
From the authoring instance, select AEM logo> Tools > Deployment > Replication > Agents on author, then click Default Agent.
Avoid using localhost (that is a local copy of AEM) when configuring your integration with Adobe Campaign unless the publish and author instance are both on the same computer.
Click Edit then select the Transport tab.
Configure the URI by replacing localhost with the IP address or the address of the AEM publishing instance.
Before you can use AEM and Adobe Campaign together, you must establish the link between both solutions so that they can communicate.
Connect to your AEM authoring instance.
Select Tools > Operations > Cloud > Cloud Services, then Configure now in the Adobe Campaign section.
Create a new configuration by entering a Title and click Create, or choose the existing configuration that you want to link with your Adobe Campaign instance.
Edit the configuration so that it matches the parameters of your Adobe Campaign instance.
Select Connect to Adobe Campaign and click OK.
After you create your email and publish it, you need to re-publish the configuration onto your publish instance.
If the connection fails, make sure you check the following:
You need to configure the externalizer in AEM on your author instance. The Externalizer is an OSGi service that lets you transform a resource path into an external and absolute URL. This service provides a central place to configure those external URLs and build them.
See Configure the externalizer for general instructions. For the Adobe Campaign integration, make sure you configure the publish server at
https://<host>:<port>/system/console/configMgr/com.day.cq.commons.impl.ExternalizerImpl not point to
localhost:4503 but to a server that is reachable by the Adobe Campaign console.
If it points to
localhost:4503 or another server that Adobe Campaign cannot reach, your images will not appear on the Adobe Campaign console.