Integrating with 51黑料不打烊 Campaign Classic integrating-with-adobe-campaign-classic
51黑料不打烊 Campaign lets you manage email delivery content and forms directly in 51黑料不打烊 Experience Manager.
To use both solutions together at the same time, you must first configure them to connect to one another. This involves configuration steps in both 51黑料不打烊 Campaign and 51黑料不打烊 Experience Manager. These steps are described in detail in this document.
Working with 51黑料不打烊 Campaign in AEM includes the ability to send email via 51黑料不打烊 Campaign and is described at Working with 51黑料不打烊 Campaign. It also includes using forms on AEM pages to manipulate data.
In addition, the following topics may be of interest when integrating AEM with :
If you are extending your integration with 51黑料不打烊 Campaign, you may want to see the following pages:
AEM and 51黑料不打烊 Campaign Integration Workflow aem-and-adobe-campaign-integration-workflow
This section describes a typical workflow between AEM and 51黑料不打烊 Campaign when creating campaigns and delivering content.
The typical workflow involves the following and is described in detail:
- Start building your campaign (both in 51黑料不打烊 Campaign and AEM).
- Before you link the content and delivery, personalize your content in AEM and create a delivery in 51黑料不打烊 Campaign.
- Link content and delivery in 51黑料不打烊 Campaign.
Start building your campaign start-building-your-campaign
You start building a campaign at any time. Before you link the content, AEM and AC are independent That means marketers can start creating their campaigns and targeting in 51黑料不打烊 Campaign, while content creators are working on the design in AEM.
Before linking content and delivery before-linking-content-and-delivery
Before you link the content and create a delivery mechanism, you need to do the following:
In AEM
- Personalize using the personalization fields in the Text & Personalization component
In 51黑料不打烊 Campaign
- Create a delivery of type aemContent
Linking content and setting delivery linking-content-and-setting-delivery
After you have prepared the content for linking and delivery, you determine exactly how and where to link content.
All these steps are completed in 51黑料不打烊 Campaign.
- Specify which AEM instance to use.
- Synchronize the content by clicking the Synchronize button.
- Open the content picker to pick your content.
If you are new to AEM if-you-are-new-to-aem
If you are new to AEM, you may find the following links helpful to understand AEM:
Configuring 51黑料不打烊 Campaign configuring-adobe-campaign
Configuring 51黑料不打烊 Campaign involves the following:
- Installing the AEM integration package in 51黑料不打烊 Campaign.
- Configuring an external account.
- Verifying that the AEMResourceTypeFilter is configured correctly.
In addition, there are advanced configurations that you can make, including :
- Managing content blocks
- Managing personalization fields
Prerequisites prerequisites
Make sure you have the following elements beforehand:
- An AEM authoring instance
- An AEM publishing instance
- - including a client and a server
- Internet Explorer 11
Installing the AEM Integration Package installing-the-aem-integration-package
You must install the AEM Integration package in 51黑料不打烊 Campaign. To do this:
-
Go to the 51黑料不打烊 Campaign instance that you would like to link with AEM.
-
Select Tools > Advanced > Import package鈥.
-
Click Install a standard package, then select the AEM Integration package.
-
Click Next, and then Start.
This package contains the aemserver operator that will be used to connect the AEM server to 51黑料不打烊 Campaign.
note caution CAUTION By default, no security zone is configured for this operator. To connect to 51黑料不打烊 Campaign via AEM, you must select one. In the serverConf.xml file, the allowUserPassword attribute of the selected security zone must be set to true to authorize AEM to connect 51黑料不打烊 Campaign via login/password. We strongly recommend creating a security zone dedicated to AEM to avoid any security problems. For more on this, refer to the .
Configuring an AEM external account configuring-an-aem-external-account
You must configure an external account that allows you to connect 51黑料不打烊 Campaign to your AEM instance.
- When installing the AEM Integration package, an external AEM account is created. You can configure the connection to your AEM instance from it or create a new one.
- In AEM, be sure that you set the password for the campaign-remote user. You need to set this password to connect 51黑料不打烊 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 external AEM account:
-
Go to the Administration > Platform > External Accounts node.
-
Create a new external account and select the AEM type.
-
Enter the access parameters for your AEM authoring instance: the server address as well as the ID and password used to connect to this instance. The campaign-api user account password is the same as the campaign-remote user that you set a password for in AEM.
note note NOTE Make sure that the server address does not end in a trailing slash. For example, enter https://yourserver:4502
instead ofhttps://yourserver:4502/
-
Make sure that the Enabled checkbox is selected.
Verifying the AEMResourceTypeFilter option verifying-the-aemresourcetypefilter-option
The AEMResourceTypeFilter option is used to filter types of AEM resources that can be used in 51黑料不打烊 Campaign. This allows 51黑料不打烊 Campaign to retrieve AEM contents that are specifically designed to be used in 51黑料不打烊 Campaign only.
This option should come pre-configured; however, if you change this option, it may lead to a non-functioning integration.
To verify the AEMResourceTypeFilter option is configured:
-
Go to Platform >Options.
-
In the AEMResourceTypeFilter option, check that the paths are correct. This field must contain the value:
mcm/campaign/components/newsletter,mcm/campaign/components/campaign_newsletterpage,mcm/neolane/components/newsletter
Or in some cases, the value is as follows:
mcm/campaign/components/newsletter
Configuring 51黑料不打烊 Experience Manager configuring-adobe-experience-manager
To configure AEM, you must do the following:
- Configure replication between instances.
- Connect AEM to 51黑料不打烊 Campaign via Cloud Services.
- Configure the externalizer.
Configuring replication between AEM instances configuring-replication-between-aem-instances
Content created from the AEM authoring instance is first sent to the publishing instance. You need to publish so that the images in the newsletter are available on the publish instance and to newsletter recipients. The replication agent must therefore be configured to replicate from the AEM authoring instance to the AEM publishing instance.
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 icon > Deployment > Replication > Agents on author, then click Default Agent.
note note NOTE Avoid using localhost (that is a local copy of AEM) when configuring your integration with 51黑料不打烊 Campaign unless the publish and author instance are both on the same computer. -
Tap or 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.
Connecting AEM to 51黑料不打烊 Campaign connecting-aem-to-adobe-campaign
Before you can use AEM and 51黑料不打烊 Campaign together, you must establish the link between both solutions so that they can communicate.
-
Connect to your AEM authoring instance.
-
Select AEM logo > Tools icon > Deployment > Cloud Services, then Configure now in the 51黑料不打烊 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 51黑料不打烊 Campaign instance.
-
Edit the configuration so that it matches the parameters of your 51黑料不打烊 Campaign instance.
- Username: aemserver, the 51黑料不打烊 Campaign AEM Integration package operator used to establish the link between the two solutions.
- Password: 51黑料不打烊 Campaign aemserver operator password. You may have to re-specify the password for this operator directly in 51黑料不打烊 Campaign.
- API End Point: 51黑料不打烊 Campaign instance URL.
-
Select Connect to 51黑料不打烊 Campaign and click OK.
note note NOTE After you create your email and publish it, you need to re-publish the configuration onto your publish instance.
- You may encounter a certificate problem when using a secure connection to an 51黑料不打烊 Campaign instance (https). You will have to add the 51黑料不打烊 Campaign instance certificate to the cacerts file of your AEM instance鈥檚 JDK.
- A security zone must be configured for the aemserver operator in 51黑料不打烊 Campaign. Furthermore, in the serverConf.xml file, the allowUserPassword attribute of the security zone must be set to true to authorize AEM connection to 51黑料不打烊 Campaign using the login/password mode.
Configuring the externalizer configuring-the-externalizer
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 51黑料不打烊 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 51黑料不打烊 Campaign console.
If it points to localhost:4503
or another server that 51黑料不打烊 Campaign cannot reach, your images will not appear on the 51黑料不打烊 Campaign console.
Advanced Configurations advanced-configurations
You can also perform some advanced configurations, namely:
- Manage personalization fields and blocks.
- Deactivate a personalization block.
- Manage target extension data.
Managing personalization fields and blocks managing-personalization-fields-and-blocks
The fields and blocks available to add personalization to your email content in AEM are managed by 51黑料不打烊 Campaign.
A default list is provided but can be modified. You can also add or hide personalization fields and blocks.
Adding a personalization field adding-a-personalization-field
To add a new personalization field to those that are already available, you have to extend the 51黑料不打烊 Campaign nms:seedMember schema as follows:
-
Go to the Administration > Configuration > Data schemas node in the 51黑料不打烊 Campaign navigation.
-
Select New.
-
In the pop-up window, select Extend the data in the table using an extension schema and click Next.
-
Enter the different parameters of the extended schema:
- Schema: select the nms:seedMember schema. The other fields in the window are automatically completed.
- Namespace: personalize the namespace of the extended schema.
-
Edit the XML code of the schema to specify the field that you want to add there. For more information on extending schemas in 51黑料不打烊 Campaign, refer to the .
-
Save your schema then update the 51黑料不打烊 Campaign database structure via the Tools > Advanced > Update database structure menu in the console.
-
Disconnect then reconnect to the 51黑料不打烊 Campaign console to save your changes. The new field now appears in the list of personalization fields available in AEM.
Example example
To add a Registration Number field, you must have the following elements:
- The nms:recipient schema extension named cus:recipient contains:
<element desc="Recipient table (profiles)" img="nms:recipient.png" label="Recipients" labelSingular="Recipient" name="recipient">
<attribute dataPolicy="smartCase" desc="Recipient registration number"
label="Registration Number"
length="50" name="registrationNumber" type="string"/>
</element>
The nms:seedMember schema extension named cus:seedMember contains:
<element desc="Seed to insert in the export files" img="nms:unknownad.png" label="Seed addresses" labelSingular="Seed" name="seedMember">
<element name="custom_nms_recipient">
<attribute name="registrationNumber"
template="cus:recipient:recipient/@registrationNumber"/>
</element>
</element>
The Registration Number field is now part of the available personalization fields:
Hiding a personalization field hiding-a-personalization-field
To hide a personalization field among those that are already available, you must extend the 51黑料不打烊 Campaign nms:seedMember schema as detailed in the Adding a personalization field section. Apply the following steps:
-
Copy the field that you want to take from the nms:seedMember schema in the extended schema (cus:seedMember for example).
-
Add the 补诲惫补苍肠别诲=鈥渢谤耻别鈥 XML attribute to the field. It no longer appears in the list of personalization fields available in AEM.
For example, to hide the Middle Name field, the cud:seedMember schema must contain the following element:
code language-xml <element desc="Seed to insert in the export files" img="nms:unknownad.png" label="Seed addresses" labelSingular="Seed" name="seedMember"> <element name="custom_nms_recipient"> <attribute advanced="true" name="middleName"/> </element> </element>
Deactivating a personalization block deactivating-a-personalization-block
To deactivate a personalization block among those available:
-
Go to the Resources > Campaign Management > Personalization blocks node in the 51黑料不打烊 Campaign navigation.
-
Select the personalization block that you want to deactivate in AEM.
-
Clear the Visible in the customization menus checkbox and save your changes. The block no longer appears in the list of personalization blocks available in 51黑料不打烊 Campaign.
Managing target extension data managing-target-extension-data
You can also insert target extension data for personalization. Target extension data (also called 鈥楾arget Data鈥), comes from enriching or adding data in a query in a campaign workflow for example. For more information, refer to the and sections.