配置 Adobe Experience Manager 存储库访问权限 aem-admin-settings

在此页面上:​了解管理员如何将沙盒连接到Adobe Experience Manager存储库,设置仅创作或发布访问权限、自定义域和身份验证,以便营销人员能够在其历程和营销活动中使用AEM内容片段。

Adobe Journey Optimizer与​ Adobe Experience Manager as a Cloud Service ​和​ Adobe Experience Manager Managed Service ​集成,因此您可以在历程和营销活动中使用​内容片段。 默认情况下,内容片段​是从Adobe Experience Manager发布存储库中读取的,管理员可以在​ AEM集成 ​菜单中切换到仅创作或调整发布访问权限。

➡️配置存储库后,请继续使用Experience Manager内容片段,在Journey Optimizer中创作和选择任务。

配置存储库 configure-ui

NOTE
AEM集成​保存每个沙盒​的存储库设置。 每个沙盒都保留其自身的集成,因此它们不会跨沙盒应用。

Journey Optimizer为每个组织、沙盒和Adobe Experience Manager存储库存储一个集成。 如果保存同一组合的新集成,它将替换以前的设置,仅保留最新的配置。

➡️ 在视频中发现Adobe Experience Manager托管服务的此功能

要配置存储库,请执行以下操作:

  1. 访问​管理 > 渠道 > AEM集成。

  2. 单击​创建配置。

  3. 选择配置方法:

    • 对于​ Adobe Experience Manager Managed Services ​存储库,在​ AMS存储库主机名 ​字段中输入以adobecqms.net结尾的存储库主机名。

    • 如果您使用​Adobe Experience as a Cloud Service,请选择要配置的存储库,然后单击​下一步。

      此外,您可以单击​ 查看 ​以访问此存储库。

      note important
      IMPORTANT
      为同一组织、沙盒和存储库​ 保存新配置将替换 ​默认配置,即​ 发布 ​存储库。

  4. 输入​ 名称 ​和​描述。

  5. 请在下面的下拉列表中选择您的设置:

    accordion
    仅创作设置

    当Journey Optimizer应仅从Adobe Experience Manager 创作​环境中读取内容片段时,选择​仅创作设置。 不支持从作者复制到发布和实时发布更新。

    accordion
    发布实例设置

    默认情况下,每个​ Adobe Experience Manager as a Cloud Service ​存储库都配置为使用​ 发布 ​实例。 您可以继续内容片段测试步骤,而不更改这些设置。

    如果您的发布实例已经过​身份验证,或者您必须使用自定义发布域,请按照以下步骤操作。

    1. 选择​ 发布实例设置 ​以启用发布实例设置。

    2. 启用​将令牌发送到发布实例,以便服务凭据包含在对发布实例的请求中。

    3. 粘贴有效的​ 服务凭据JSON ​以进行身份验证。

    4. 如果您的组织无法访问默认的AEM发布主机(publish-XX-XX.adobeaemcloud.com)以获取内容,可以选择提供自定义域。

  6. 完成实例设置后,选取内容片段以确认集成是否正常工作。

  7. 在​ 内容审查程序 ​窗口中,选择要测试的片段,然后单击​选择。

  8. 单击​保存。

  9. 在选择了测试内容片段的情况下进行保存时,验证会自动运行。 如果验证失败,将显示错误列表,以便您修复配置。

  10. 要编辑或禁用此存储库集成,请从​ AEM集成 ​菜单访问您之前创建的配置。

保存此配置后,Journey Optimizer会将该存储库的配置存储在当前沙盒中。 然后,在​ 内容审查程序 ​选择器中浏览并选择内容时,您可以使用该存储库及其设置。

操作方法视频 video

了解管理员如何在Journey Optimizer中配置Adobe Experience Manager Managed Services存储库设置,以便营销人员能够在历程和营销活动中使用内容片段。

AI Knowledge Reference

This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.

For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.

  • TL;DR: This page explains how an administrator connects a sandbox to an Adobe Experience Manager repository in the AEM Integration menu, choosing author-only or publish access, custom domains, and authentication, so marketers can use AEM Content Fragments in journeys and campaigns.

Intents:

  • Connect a sandbox to an Adobe Experience Manager as a Cloud Service or Managed Service repository
  • Create a repository configuration from Administration > Channels > AEM Integration
  • Choose between Author only setup and Publish instance setup
  • Enable authentication by sending service credentials to the publish instance
  • Provide a custom domain when the default AEM publish host is blocked
  • Confirm the integration by testing with a Content Fragment

Glossary:

  • AEM Integration: The Administration menu where repository settings are created, edited, or disabled; saves settings per sandbox (product-specific)
  • Author only setup: A configuration where Journey Optimizer reads Content Fragments from the Adobe Experience Manager author environment only (product-specific)
  • Publish instance setup: The configuration that turns on publish instance settings, used when the publish instance is authenticated or requires a custom publish domain (product-specific)
  • Send token to publish instance: An option that includes service credentials with requests to the publish instance (product-specific)
  • Service Credential JSON: The Adobe Experience Manager service credential pasted for authentication of publish instance requests (product-specific)
  • Content Advisor: The selector window used to pick the Content Fragment that confirms the integration works (product-specific)

Guardrails:

  • AEM Integration saves repository settings per sandbox; each sandbox keeps its own integrations and they do not apply across sandboxes.
  • Only one integration is stored per organization, sandbox, and Adobe Experience Manager repository; saving a new integration for the same combination replaces the previous settings and only the latest configuration is kept.
  • With Author only setup, replication from author to publish and live publish updates are not supported.
  • For an Adobe Experience Manager Managed Services repository, the AMS repository hostname must end with adobecqms.net.
  • Authenticating the publish instance requires enabling Send token to publish instance and pasting a valid Service Credential JSON.
  • When you save with a test Content Fragment selected, validation runs automatically; if validation fails, an error list is displayed so you can fix the configuration.

Terminology:

  • Canonical name: AEM Integration — Acronym: n/a — variants: Adobe Experience Manager Configuration, repository configuration
  • Synonyms: “author-only” = “Author only setup”
  • Do not confuse: “Author only setup” (reads Content Fragments from the author environment only) ≠ “Publish instance setup” (uses the publish instance, the default for AEM as a Cloud Service)

FAQ:

  • Q: Where are repository settings configured? — In Administration > Channels > AEM Integration, using Create configuration.
  • Q: Do repository settings apply across sandboxes? — No; AEM Integration saves settings per sandbox and they do not apply across sandboxes.
  • Q: What happens if I save a new configuration for the same repository? — It replaces the previous settings for that organization, sandbox, and repository, and only the latest configuration is kept.
  • Q: When do I need Publish instance setup? — When your publish instance is authenticated or you must use a custom publish domain; otherwise the default publish configuration can be used without changes.
  • Q: How do I confirm the integration works? — Pick a Content Fragment in the Content Advisor window and save; validation runs automatically and shows an error list if it fails.
recommendation-more-help
journey-optimizer-help