Dispatcher configurations manage-your-dispatcher-configurations
Learn how to deploy Dispatcher configuration files using Cloud Manager
Deploy Dispatcher configurations with Cloud Manager deploying-dispatcher-configurations
Cloud Manager is able to deploy web server and Dispatcher configuration files assuming they are stored in the Git repository alongside normal AEM content packages.
To take advantage of this capability, the Maven build should produce a .zip file, which contains at least two directories: conf
and conf.d
. This .zip file can be produced using the maven-assembly-plugin
.
Projects generated by Cloud Manager using the built-in project creation wizard have the correct Maven project structure created automatically. This path is recommended if you are new to ΓΫΆΉΚΣΖ΅ Managed Services (AMS).
When you deploy to a Dispatcher instance, the directories on the instance are replaced with those directories from your Git repository. Because web server and Dispatcher configuration files often require environment-specific details, you must collaborate with your Customer Success Engineers (CSE) to set the appropriate environment variables in /etc/sysconfig/httpd
before using this feature correctly.
Dispatcher configuration for existing managed service customers steps-for-configuring-dispatcher
Follow these steps below to complete the initial Dispatcher configuration.
- Obtain the current production configuration files from your CSE.
- Remove hard-coded environment-specific data such as publish renderer IP and replace with variables.
- Define required variables in key-value pairs for each target Dispatcher and request your CSE to add them to
/etc/sysconfig/httpd
on each instance. - Test the updated configurations in your staging environment.
- Once tested, request your CSE to deploy to production.
- Commit the files to your Git repository.
- Deploy through Cloud Manager.
Example example
The specific file and directory structure may vary based on the specifics of your project, but this example should provide a concrete guide to how to structure your project to include Apache and Dispatcher configurations.
-
Create a subdirectory named
dispatcher
.You may use any name here, but the directory name created in this step must be the same as the name used in step 6.
-
This subdirectory contains a Maven module that builds the Dispatcher .zip file using the Maven Assembly plug-in. In the
dispatcher
directory, create apom.xml
file with this content, changing theparent
reference,artifactId
, andname
as necessary.code language-xml <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <parent> <!-- reference to your parent pom --> </parent> <artifactId>dispatcher</artifactId> <!-- feel free to change this --> <packaging>pom</packaging> <name>dispatcher</name> <!-- feel free to change this --> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <version>3.1.0</version> <executions> <execution> <phase>package</phase> <goals><goal>single</goal></goals> <configuration> <descriptors> <descriptor>assembly.xml</descriptor> </descriptors> <appendAssemblyId>false</appendAssemblyId> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>
- As in Step 1, the artifactId and name here can be other values if you want.
dispatcher
is used here just an example.
- As in Step 1, the artifactId and name here can be other values if you want.
-
The Maven Assembly plug-in requires a
descriptor
to define how the .zip file is created. To create this descriptor, create a file in thedispatcher
subdirectory namedassembly.xml
with the following content. Note that this file name is referenced on line 26 in thepom.xml
file above.code language-xml <assembly xmlns="http://maven.apache.org/ASSEMBLY/2.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.0.0 http://maven.apache.org/xsd/assembly-2.0.0.xsd"> <id>distribution</id> <formats> <format>zip</format> </formats> <includeBaseDirectory>false</includeBaseDirectory> <fileSets> <fileSet> <directory>${basedir}/src</directory> <includes> <include>**/*</include> </includes> <outputDirectory></outputDirectory> </fileSet> </fileSets> </assembly>
-
Create a subdirectory named
src
(as referenced in the assembly descriptor above on line 11) inside the Dispatcher subdirectory to store the actual Apache and Dispatcher configurations. Within thissrc
directory, create directories namedconf
,conf.d
,conf.dispatcher.d
, andconf.modules.d
. -
Populate the
conf
,conf.d
,conf.dispatcher.d
, andconf.modules.d
directories with your configuration files. For example, the default configuration consists of these files and symbolic links.code language-none dispatcher βββ assembly.xml βββ pom.xml βββ src βββ conf β βββ httpd.conf β βββ magic βββ conf.d β βββ README β βββ autoindex.conf β βββ available_vhosts β β βββ aem_author.vhost β β βββ aem_flush.vhost β β βββ aem_health.vhost β β βββ aem_lc.vhost β β βββ aem_publish.vhost β βββ dispatcher_vhost.conf β βββ enabled_vhosts β β βββ aem_author.vhost -> ../available_vhosts/aem_author.vhost β β βββ aem_flush.vhost -> ../available_vhosts/aem_flush.vhost β β βββ aem_publish.vhost -> ../available_vhosts/aem_publish.vhost β βββ rewrites β β βββ base_rewrite.rules β β βββ xforwarded_forcessl_rewrite.rules β βββ userdir.conf β βββ variables β β βββ ams_default.vars β βββ welcome.conf β βββ whitelists β βββ 000_base_whitelist.rules βββ conf.dispatcher.d β βββ available_farms β β βββ 000_ams_author_farm.any β β βββ 001_ams_lc_farm.any β β βββ 999_ams_publish_farm.any β βββ cache β β βββ ams_author_cache.any β β βββ ams_author_invalidate_allowed.any β β βββ ams_publish_cache.any β β βββ ams_publish_invalidate_allowed.any β βββ clientheaders β β βββ ams_author_clientheaders.any β β βββ ams_common_clientheaders.any β β βββ ams_lc_clientheaders.any β β βββ ams_publish_clientheaders.any β βββ dispatcher.any β βββ enabled_farms β β βββ 000_ams_author_farm.any -> ../available_farms/000_ams_author_farm.any β β βββ 999_ams_publish_farm.any -> ../available_farms/999_ams_publish_farm.any β βββ filters β β βββ ams_author_filters.any β β βββ ams_lc_filters.any β β βββ ams_publish_filters.any β βββ renders β β βββ ams_author_renders.any β β βββ ams_lc_renders.any β β βββ ams_publish_renders.any β βββ vhosts β βββ ams_author_vhosts.any β βββ ams_lc_vhosts.any β βββ ams_publish_vhosts.any βββ conf.modules.d βββ 00-base.conf βββ 00-dav.conf βββ 00-lua.conf βββ 00-mpm.conf βββ 00-proxy.conf βββ 00-systemd.conf βββ 01-cgi.conf βββ 02-dispatcher.conf
-
Finally, in the
pom.xml
file in the root of your project, add a<module>
element to include the Dispatcher module.For example, if your existing module list is the following:
code language-xml <modules> <module>core</module> <module>ui.apps</module> <module>ui.content</module> </modules>
Change it to the following:
code language-xml <modules> <module>core</module> <module>ui.apps</module> <module>ui.content</module> <module>dispatcher</module> </modules>
- As noted in step 1, the value of the
<module>
element must match the directory name created.
- As noted in step 1, the value of the
-
To test, run
mvn clean package
in the project root directory. You should see lines like this in the output.code language-none [INFO] --- maven-assembly-plugin:3.1.0:single (default) @ dispatcher --- [INFO] Reading assembly descriptor: assembly.xml [INFO] Building zip: /Users/me/mycompany/dispatcher/target/dispatcher-1.0-SNAPSHOT.zip
You can also unzip this file to view its contents.
code language-shell $ unzip -l dispatcher/target/dispatcher-1.0-SNAPSHOT.zip Archive: dispatcher/target/dispatcher-1.0-SNAPSHOT.zip Length Date Time Name --------- ---------- ----- ---- 0 09-12-2018 12:53 conf.modules.d/ 0 10-19-2018 10:38 conf.dispatcher.d/ 0 09-12-2018 12:53 conf.dispatcher.d/available_farms/ 0 09-12-2018 12:53 conf.dispatcher.d/filters/ 0 09-12-2018 12:53 conf.dispatcher.d/renders/ 0 09-12-2018 12:53 conf.dispatcher.d/cache/ 0 09-12-2018 12:53 conf.dispatcher.d/clientheaders/ 0 09-12-2018 12:53 conf.dispatcher.d/enabled_farms/ 0 09-12-2018 12:53 conf.dispatcher.d/vhosts/ 0 09-12-2018 12:53 conf.d/ 0 09-12-2018 12:53 conf.d/rewrites/ 0 09-12-2018 12:53 conf.d/whitelists/ 0 09-12-2018 12:53 conf.d/variables/ 0 11-01-2018 13:53 conf.d/enabled_vhosts/ 0 09-12-2018 12:53 conf.d/available_vhosts/ 0 09-12-2018 12:53 conf/ 88 09-12-2018 12:53 conf.modules.d/00-systemd.conf 4913 09-12-2018 12:53 conf.dispatcher.d/available_farms/999_ams_publish_farm.any 152 09-12-2018 12:53 conf.dispatcher.d/renders/ams_lc_renders.any 490 09-12-2018 12:53 conf.dispatcher.d/clientheaders/ams_common_clientheaders.any 1727 09-12-2018 12:53 conf.d/rewrites/base_rewrite.rules 36 09-12-2018 12:53 conf.d/enabled_vhosts/aem_author.vhost 11753 09-12-2018 12:53 conf/httpd.conf 957 09-12-2018 12:53 conf.modules.d/00-proxy.conf 944 09-12-2018 12:53 conf.dispatcher.d/available_farms/001_ams_lc_farm.any 220 09-12-2018 12:53 conf.dispatcher.d/cache/ams_author_invalidate_allowed.any 43 09-12-2018 12:53 conf.dispatcher.d/enabled_farms/999_ams_publish_farm.any 516 09-12-2018 12:53 conf.d/welcome.conf 37 09-12-2018 12:53 conf.d/enabled_vhosts/aem_publish.vhost 13077 09-12-2018 12:53 conf/magic 96 09-12-2018 12:53 conf.modules.d/02-dispatcher.conf 2601 09-12-2018 12:53 conf.dispatcher.d/available_farms/000_ams_author_farm.any 837 09-12-2018 12:53 conf.dispatcher.d/cache/ams_author_cache.any 42 09-12-2018 12:53 conf.dispatcher.d/enabled_farms/000_ams_author_farm.any 2926 09-12-2018 12:53 conf.d/autoindex.conf 2555 09-12-2018 12:53 conf.d/available_vhosts/aem_lc.vhost 41 09-12-2018 12:53 conf.modules.d/00-lua.conf 2234 09-12-2018 12:53 conf.dispatcher.d/filters/ams_publish_filters.any 220 09-12-2018 12:53 conf.dispatcher.d/cache/ams_publish_invalidate_allowed.any 402 09-12-2018 12:53 conf.dispatcher.d/dispatcher.any 573 09-12-2018 12:53 conf.d/whitelists/000_base_whitelist.rules 871 09-12-2018 12:53 conf.d/available_vhosts/aem_flush.vhost 139 09-12-2018 12:53 conf.modules.d/00-dav.conf 742 09-12-2018 12:53 conf.dispatcher.d/filters/ams_author_filters.any 557 09-12-2018 12:53 conf.dispatcher.d/cache/ams_publish_cache.any 105 09-12-2018 12:53 conf.dispatcher.d/vhosts/ams_lc_vhosts.any 101 09-12-2018 12:53 conf.dispatcher.d/vhosts/ams_publish_vhosts.any 3582 09-12-2018 12:53 conf.d/dispatcher_vhost.conf 2529 09-12-2018 12:53 conf.d/available_vhosts/aem_publish.vhost 742 09-12-2018 12:53 conf.modules.d/00-mpm.conf 88 09-12-2018 12:53 conf.dispatcher.d/filters/ams_lc_filters.any 177 09-12-2018 12:53 conf.dispatcher.d/clientheaders/ams_lc_clientheaders.any 366 09-12-2018 12:53 conf.d/README 2723 09-12-2018 12:53 conf.d/available_vhosts/aem_author.vhost 3739 09-12-2018 12:53 conf.modules.d/00-base.conf 138 09-12-2018 12:53 conf.dispatcher.d/renders/ams_author_renders.any 44 09-12-2018 12:53 conf.dispatcher.d/clientheaders/ams_publish_clientheaders.any 112 09-12-2018 12:53 conf.dispatcher.d/vhosts/ams_author_vhosts.any 580 09-12-2018 12:53 conf.d/variables/ams_default.vars 35 09-12-2018 12:53 conf.d/enabled_vhosts/aem_flush.vhost 1252 09-12-2018 12:53 conf.d/userdir.conf 451 09-12-2018 12:53 conf.modules.d/01-cgi.conf 321 09-12-2018 12:53 conf.dispatcher.d/renders/ams_publish_renders.any 170 09-12-2018 12:53 conf.dispatcher.d/clientheaders/ams_author_clientheaders.any 220 09-12-2018 12:53 conf.d/rewrites/xforwarded_forcessl_rewrite.rules 1753 09-12-2018 12:53 conf.d/available_vhosts/aem_health.vhost --------- ------- 69017 66 files