На цій сторінці
Ви переглядаєте довідкову інформацію для версії:
- 6.5
- 6.4
- 6.3
- 6.2
- Старіші версії
Примітка.
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:
Configuring Adobe Campaign involves the following:
- Configuring the aemserver user.
- Creating a dedicated external account.
- Verifying the AEMResourceTypeFilter option.
- Creating a dedicated delivery template.
Примітка.
To perform these operations, you must have the administration role in Adobe Campaign.
Увага!
Operations detailed in the Configuring Adobe Campaign and Configuring Adobe Experience Manager sections are necessary for the integration functionalities between AEM and Adobe Campaign to work correctly.
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 have to set a password for this user. This cannot be done through the UI. This configuration must be done in REST by a technical administrator.
- You can assign specific roles to this user, such as deliveryPrepare, which allows the user to create and edit deliveries.
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.
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.
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:
-
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:
- Configure replication between instances.
- Connect AEM to Adobe Campaign.
- Configure the externalizer.
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.
-
From the authoring instance, select AEM logo> Tools icon > 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.
Before you can use AEM and Adobe Campaign together, you must establish the link between both solutions so that they can communicate.
-
- Username: aemserver, the Adobe Campaign AEM Integration package operator used to establish the link between the two solutions.
- Password: Adobe Campaign aemserver operator password. You may have to re-specify the password for this operator directly in Adobe Campaign.
- API End Point: Adobe Campaign instance URL.
-
Примітка.
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 may encounter a certificate problem when using a secure connection to an Adobe Campaign instance (https). You will have to add the Adobe Campaign instance certificate to the cacerts file of your JDK.
- In addition, see Troubleshooting your AEM/Adobe Campaign Integration.
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 http://<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.
Публікації Twitter™ і Facebook не підпадають під умови ліцензії Creative Commons.