WKND OOTB Project Dispatcher Deployment independently & along with Author & Publish Deployment

@varaande,

I doubt if that is possible at all in the AEM on-premise setup with maven build profiles created OOTB using ArcheType. 

The maven build and deploy profiles available OOTB with ArcheType have required plugins and configurations to the target AEM (Author and Publish) servers but not the dispatcher.

While building the project, the maven build does create a package of dispatcher configurations but I don't think maven build can deploy the changes as well to the dispatcher.

As of I know, in most of the on-prem setups, to deploy the dispatcher changes

• Either you write a custom shell/bash script to deploy the dispatcher configuration package
• Or deploy them manually to dispatcher server(s).
• Or use Jenkins build to deploy the dispatcher configurations package to dispatcher servers.

Thanks,

Sudheer.

As mentioned by others too, on-prem dispatcher config files will need to be deployed via Jenkins or any other release automation tool.

The problem here is with getting a dedicated OS user on the dispatcher servers with sufficient access to

1. allow deployments,

2. restart Dispatcher when config changes are deployed,

3. create a folder structure for dispatcher setup, when necessary, and,

4. Access to logs when debugging.

Most likely the Middleware engineering team that provisions the servers, should be able to provide such a user on dispatcher servers.

Hope that helps!

regards,

Preetpal

@varaande Do you find the suggestions from users useful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity.