By integrating AEM with Adobe Campaign, you can manage email delivery, content, and forms directly in AEM. Configuration steps in both Adobe Campaign Classic and AEM are needed to enable bidirectional communication between solutions.
This integration allows AEM and Adobe Campaign Classic to be used independently. Marketers can create campaigns and use targeting in Adobe Campaign, while content creators in parallel can work on content design in AEM. Using the integration, the content and design of the campaign created in AEM can be targeted and delivered by Adobe Campaign.
Integration between AEM and Campaign requires a number of steps in both solutions.
This document leads you through each of these steps in detail.
The AEM Integration package in Adobe Campaign includes a number of standard configurations necessary to connect to AEM.
As an administrator, sign into the Adobe Campaign instance using the client console.
Select Tools > Advanced > Import package….
Click Install a standard package and then click Next.
Check the AEM Integration package.
Click Next, and then Start to begin the installation.
Click Close when the installation completes.
The integration package is now installed.
The integration package automatically creates the aemserver
operator that AEM uses to connect to Adobe Campaign. You must define a security zone for this operator and set its password.
Log into Adobe Campaign as an administrator using the client console.
Select Tools -> Explorer from the menu bar.
In the explorer, navigate to the Administration > Access Management > Operators node.
Select the aemserver
operator.
On the Edit tab of the operator, select the Access Rights sub-tab and then click the Edit the access parameters… link.
Select the appropriate security zone and define the trusted IP mask as necessary.
Click Save.
Log out of the Adobe Campaign client.
On the filesystem of the Adobe Campaign server, navigate to the Campaign installation location and edit the serverConf.xml
file as an administrator. This file is typically located under:
C:\Program Files\Adobe\Adobe Campaign Classic v7\conf
in Windows./usr/local/neolane/nl6/conf/eng
in Linux.Search for securityZone
and ensure that the following parameters are set for the security zone of the AEM operator.
allowHTTP="true"
sessionTokenOnly="true"
allowUserPassword="true"
.Save the file.
Ensure that the security zone does not get overwritten by the respective setting in the config-<server name>.xml
file.
allowUserPassword
attribute to true
.If you want to change the Adobe Campaign Classic server port, replace 8080
with the desired port.
By default, there is no security zone configured for the operator. For AEM to connect to Adobe Campaign, you must select a zone as detailed in the previous steps.
Adobe strongly recommends creating a security zone dedicated to AEM to avoid any security issues. For more on this topic, please refer to the Adobe Campaign Classic documentation.
In the Campaign client, return to the aemserver
operator and select the General tab.
Click the Reset password… link.
Specify a password and store it in a secure location for future use.
Click OK to save the password for the aemserver
operator.
AEM uses the operator you already set up in Campaign in order to communicate with Campaign
Sign into to your AEM authoring instance as an administrator.
From the global navigation side rail, select Tools > Cloud Services > Legacy Cloud Services > Adobe Campaign, then click Configure Now.
In the dialog, create a Campaign service configuration by entering a Title and click Create.
A new window and dialog opens to edit the configuration. Provide the necessary information.
aemserver
.Select Connect to Adobe Campaign to verify the connection and then click OK.
AEM can now communicate with Adobe Campaign.
Make sure that your Adobe Campaign server is reachable via the internet. AEM can not access private networks.
Campaign content is created by content authors on the AEM authoring instance. This instance is typically only available internally at your organization. For content such as images and assets to be accessible to the recipients of your campaign, you need to publish that content.
The replication agent is responsible for publishing your content from the AEM author instance to the publish instance and must be set up for the integration to work properly. This step is also necessary to replicate certain authoring instance configurations into the publishing instance.
To configure replication from your AEM author instance to the publish instance:
Sign into to your AEM authoring instance as an administrator.
From the global navigation side rail, select Tools > Deployment > Replication > Agents on author, then tap or click Default agent (publish).
Tap or click Edit then select the Transport tab.
Configure the URI field by replacing the default localhost
value with the IP address of the AEM publishing instance.
Tap or click OK to save the changes to the agent settings.
You have configured replication to the AEM publish instance so your campaign recipients can access your content.
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 via OSGi
From the global navigation side rail, select Tools > Operations > Web Console > OSGi Configuration and search for AEM Campaign Integration - Configuration. Edit the configuration and change the field Public URL (com.day.cq.mcm.campaign.impl.IntegrationConfigImpl#aem.mcm.campaign.publicUrl
).
The Externalizer is an OSGi service in AEM that transforms a resource path into an external and absolute URL, which is necessary for AEM to serve content that Campaign can use. You must configure it in order for the Campaign integration to work.
Sign into the AEM authoring instance as an administrator.
From the global navigation side rail, select Tools > Operations > Web Console > OSGi Configuration and search for Day CQ link Externalizer.
By default the last entry in the Domains field is intended for the publish instance. Change the URL from the default http://localhost:4503
to your publicly-available publish instance.
Tap or click Save.
You have configured the Externalizer and Adobe Campaign can now access your content.
The publish instance must be reachable from the Adobe Campaign server. If it points to localhost:4503
or another server that Adobe Campaign cannot reach, images from AEM will not appear in the Adobe Campaign console.
In order for Campaign to communicate with AEM, you need to set a password for the campaign-remote
user in AEM.
campaign-remote
user.campaign-remote
user and click Properties to edit the user.campaign-remote
user.When installing the AEM Integration package in Campaign, an external account is created for AEM. By configuring this external account, Adobe Campaign can connect to AEM, enabling two-way communication between the solutions.
Log into Adobe Campaign as an administrator using the client console.
Select Tools -> Explorer from the menu bar.
In the explorer, navigate to the Administration > Platform > External Accounts node.
Locate the external AEM account. By default it has the values:
AEM
AEM Instance
aemInstance
On the General tab of this account, enter the user information that you defined in the Set campaign-remote User Password step.
campaign-remote
user that you set in AEM in the Set campaign-remote User Password step.campaign-remote
user that you set in AEM in the Set campaign-remote User Password step.Select the Enabled checkbox.
Click Save.
Adobe Campaign can now communicate with AEM.
With both Adobe Campaign Classic and AEM configured, the integration is now complete.
You can now learn how to create a newsletter in Adobe Experience Manager by continuing with this document.