設定 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 Managed Service的功能

若要設定您的存放庫:

  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. 啟用​將Token傳送至發佈執行個體,以便服務認證包含在發佈執行個體的要求中。

    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