Dispatcher-only deployment pipeline availability in AEM Managed Services

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article explains whether Adobe Experience Manager Managed Services supports independent Dispatcher-only deployment pipelines and outlines current limitations and available workarounds.

Description description

Environment

  • Adobe Experience Manager (AEM) Managed Services (all versions)

Symptoms

  • All AEM application and Dispatcher configuration modules are built and deployed together from a single repository via Cloud Manager.
  • Dispatcher configuration is maintained in a separate Git repository, but there is no option to deploy only Dispatcher changes independently of the main application code.
  • In AEM as a Cloud Service, Dispatcher configuration can be deployed separately using dedicated pipelines, but this capability is not available for Managed Services programs.
  • All deployments require a full build and push, even for Dispatcher-only changes.
  • There is no option to register multiple repositories or pipelines per program for Managed Services.
  • No error messages are shown, but the deployment process is less flexible than in AEM as a Cloud Service.

Cause

This limitation is by design: Managed Services Cloud Manager supports only one repository and pipeline per program, and does not provide independent Dispatcher-only deployment pipelines.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the current deployment architecture for AEM Managed Services: only a single repository and pipeline can be registered per Cloud Manager program.

  2. All code, including application and Dispatcher configuration, must be built and deployed together.

  3. If independent Dispatcher deployments are required, consider these workarounds:

    • Integrate Dispatcher configuration updates into the main repository and trigger a full pipeline run for any changes.

    • Use branching or modularization within the main repository to isolate Dispatcher changes, but a full build and deployment is still required.

  4. Monitor Adobe Experience Manager Release Notes for future enhancements to pipeline flexibility in Managed Services.

Verify that all deployments complete successfully after following the above steps.

recommendation-more-help
experience-cloud-kcs-help-kbarticles