Setup Sling Dynamic Include

Video-Anleitung zur Installation und Verwendung von Apache Sling Dynamic Include mit AEM Dispatcher läuft Apache HTTP Web Server.

HINWEIS

Stellen Sie sicher, dass die neueste Version von AEM Dispatcher lokal installiert ist.

Laden Sie die Sling Dynamic Include Bundle.

Konfigurieren Sling Dynamic Include über die OSGi Configuration Factory at http://<host>:<port>/system/console/configMgr/org.apache.sling.dynamicinclude.Configuration.

Oder erstellen Sie, um eine AEM Code-Basis hinzuzufügen, die entsprechenden sling:OsgiConfig Knoten unter:

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0"
    xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
    jcr:primaryType="sling:OsgiConfig"
    include-filter.config.enabled="{Boolean}true"
    include-filter.config.path="/content"
    include-filter.config.resource-types="[my-app/components/content/highly-dynamic]"
    include-filter.config.include-type="SSI"
    include-filter.config.add_comment="{Boolean}false"
    include-filter.config.selector="nocache"
    include-filter.config.ttl=""
    include-filter.config.required_header="Server-Agent=Communique-Dispatcher"
    include-filter.config.ignoreUrlParams="[]"
    include-filter.config.rewrite="{Boolean}true"
    />
<!--
* include-filter.config.include-type="SSI | ESI | JSI"
* include-filter.config.ttl is # of seconds (requires AEM Dispatcher 4.1.11+)
-->

(Optional) Wiederholen Sie den letzten Schritt, um Komponenten zuzulassen für gesperrter (anfänglicher) Inhalt bearbeitbarer Vorlagen über SDI sowie Der Grund für die zusätzliche Konfiguration besteht darin, dass gesperrte Inhalte bearbeitbarer Vorlagen aus /conf anstelle von /content.

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0"
    xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"
    jcr:primaryType="sling:OsgiConfig"
    include-filter.config.enabled="{Boolean}true"
    include-filter.config.path="/conf"
    include-filter.config.resource-types="[my-app/components/content/highly-dynamic]"
    include-filter.config.include-type="SSI"
    include-filter.config.add_comment="{Boolean}false"
    include-filter.config.selector="nocache"
    include-filter.config.ttl=""
    include-filter.config.required_header="Server-Agent=Communique-Dispatcher"
    include-filter.config.ignoreUrlParams="[]"
    include-filter.config.rewrite="{Boolean}true"
    />
<!--
* include-filter.config.include-type="SSI | ESI | JSI"
* include-filter.config.ttl is # of seconds (requires AEM Dispatcher 4.1.11+)
-->

Aktualisieren Apache HTTPD Web servers httpd.conf -Datei, um die Include -Modul.

$ sudo vi .../httpd.conf

LoadModule include_module libexec/apache2/mod_include.so

Aktualisieren Sie die vhost -Datei, die die Richtlinien einhält.

$ sudo vi .../vhosts/aem-publish.local.conf

<VirtualHost *:80>
...
   <Directory /Library/WebServer/docroot/publish>
      ...
      # Add Includes to enable SSI Includes used by Sling Dynamic Include
      Options FollowSymLinks Includes

      # Required to have dispatcher-handler process includes
      ModMimeUsePathInfo On

      # Set includes to process .html files
      AddOutputFilter INCLUDES .html
      ...
   </Directory>
...
</VirtualHost>

Aktualisieren Sie die Konfigurationsdatei "dispatcher.any", um sie zu unterstützen (1). nocache Selektoren und (2) aktivieren TTL-Unterstützung.
```
$ sudo vi .../conf/dispatcher.any
```
```
/rules {
  ...
  /0009 {
    /glob "*.nocache.html*"
    /type "deny"
  }
}
```
TIPP

Verlassen des Verlaufs * in der Globe *.nocache.html* -Regel, kann zu Probleme in Anforderungen für Unter-Ressourcen.
```
/cache {
    ...
    /enableTTL "1"
}
```
Immer neu starten Apache HTTP Web Server , nachdem Sie Änderungen an den Konfigurationsdateien oder der dispatcher.any.
```
$ sudo apachectl restart
```

HINWEIS

Wenn Sie Sling Dynamic Includes für die Bereitstellung von Edge-Side Includes (ESI) müssen Sie dann sicherstellen, dass Sie die relevanten Antwortheader im Dispatcher-Cache. Mögliche Kopfzeilen sind: