28 sept 2020 · EUROPE'S LEADING AEM DEVELOPER CONFERENCE There can only be one single dispatcher the packages should be installed
Previous PDF | Next PDF |
[PDF] Adobe AEM Dispatcher Caching Basics
The Apache HTTP Server (“httpd”) was launched in 1995 and it has been the most popular web server on the Internet since April 1996 It has celebrated its 20th
[PDF] Introduction of an Advanced Caching Layer - UPCommons
21 jui 2018 · Table 2 4: Required Resources for Apache 2 2 3 Dispatcher Dispatcher is an out of the box AEM caching tool, therefore it requires the same
[PDF] Hosting Adobe Experience Manager® on AWS - Awsstatic
AEM Dispatcher installed on Amazon EC2 instance is an Apache httpd based static webserver that provides caching, load balancing and application security EBS
[PDF] Running Adobe Experience Manager on AWS - Awsstatic
25 nov 2020 · AEM Dispatcher is installed on a web server (Apache httpd on Amazon EC2 instance), and it is a key caching layer It provides caching, load
[PDF] CREATING THE PERFECT AEM/CQ DEPLOYMENT - Rackspace
out there My first CQ deployment involved several relatively brittle Apache Ant architecture, whether or not your publishers and dispatchers are lined up 1:1
[PDF] EnterpriseTrack Installation Guide - Oracle Help Center
This document describes how to install EnterpriseTrack software on the following platforms Microsoft SQL Server database Install the supporting software
[PDF] Use Cloud Manager to deploy CONGA-based AEM Applications
28 sept 2020 · EUROPE'S LEADING AEM DEVELOPER CONFERENCE There can only be one single dispatcher the packages should be installed
[PDF] Automate AEM Deployment with Ansible and wcmio CONGA
27 sept 2017 · definitions File templates Environment PROD QS Configuration Apache AEM Tomcat PROD dispatcher HTTPd config ▫ JSON files
[PDF] Enhancing Adobe Experience Manager (CQ5) with Varnish
28 nov 2013 · AEM technical setup: How cache flushing works Apache Webserver CQ5 Publisher Docroot Web request Dispatcher Module Request from
[PDF] aéroport biarritz pays basque anglet
[PDF] aeroport cdg terminal 2e rer
[PDF] aéroport charles de gaulle terminal 2e rer
[PDF] aeroport charles de gaulle terminal 2e rer b
[PDF] aeroport de biarritz pays basque
[PDF] aéroport de montréal arrivées
[PDF] aéroport de montréal emploi
[PDF] aéroport de montréal jobs
[PDF] aéroport de montréal pierre elliott trudeau
[PDF] aéroport de montréal stationnement
[PDF] aeroport espagne pays basque
[PDF] aeroport international pays basque
[PDF] aeroport pays basque france
[PDF] aeroport saint sebastien pays basque
EUROPE'S LEADING AEM DEVELOPER CONFERENCE
28thÿ30thSEPTEMBER 2020
Use Cloud Manager to deploy CONGA-based AEM ApplicationsStefan Seifert, pro!vision GmbH
About the Speaker
2AEM Developer
Apache Sling PMC
Apache Member
Stefan Seifert
https://www.pro-vision.de https://diva-e.com/Starting point
3AEM projects with a more complex/automated
build setupWe are using wcm.io CONGA to
Separate build artifacts and configuration
Define artifact order and conditions
Describe environments
CONGA abstracts AEM configuration
4Config Definitionin AEM project
Repository 1
OSGi configs
Configs in Content
(e.g. replication agents)Dispatcher config
Templates with
placeholdersEnvironmentsin Config Mgmt
Repository 2
AEM project env. config
Domain names
IP Addresses
Number of instances
Machine sizing
Credentials
Challenges
working with AEM Cloud ManagerPhoto by Jukan Tateision Unsplash
Artifacts to deploy
6 detect the artifacts to deployDeploy artifact heuristics
7TypeHow to detectRemarks
Content PackagesFilename: *.zip
͞META-INF/vault/properties.xml͟
Properties are checked for a
cloudManagerTargetproperty ʹDispatcher configurationFilename: *.zip
There can only beonesingle dispatcher
configuration per repositoryFunctional tests
(Integration tests)Filename: *.jar
Contains Manifest entry:
Cloud-Manager-TestType=integration-test
Tests executed automatically when found
UI Tests
(WebdriverIO)Filename: *ui-test-docker-context.tar.gz
Tests executed automatically when found
Content Packages
8Only the ąĆpackage should be deployed
All other content packages must be
marked with cloudManagerTarget=noneĄąembeddedpackages
Clear separation between mutableand immutable
content packages 9Folder names (convention)DescriptionExample
/apps/Context-Aware Configuration
/content, /conf, /etc /apps/Instance runmodes: author, publish
Env runmodes: dev, stage, prod
Not all runmodecombinations supported!
10Package typeImmutable
content packagesMutable
content packagesInstance type:
author/ publishEnvironment:
dev/ stage/ prod*Other run modes**
* Works locally & on-premise but not with Cloud Manager & AEM Cloud ServicePackage install order
11Can be controlled via package dependencies
(defined in package properties/POM)Problematic with:
3rdparty packages
Conditional packages
Runmode-specific packages
Single dispatcher configuration
12Single dispatcher config for dev/stage/prod
Variables/Conditionalscan be used:
# Simple usage of the environment variableServerName ${ENVIRONMENT_TYPE}.company.com
# When more logic is requiredDefine VIRTUALHOST stage.example.com
Define VIRTUALHOST prod.example.com
Steps to
make your AEM project ready for the cloudPhoto by Barry Rijkseon Unsplash
The obvious steps
14Use latest AEM SDK API
Remove obsolete Sling/3rdparty bundles
Do not deploy AEM SPs/CFPs
Do not deploy Core Component packages
Use split content packages from ACS AEM Commons *
Update dependencies
* Use ACS AEM Commons 5.0.0 or higherPimp your content packages
15Update to latest Content Package plugin
Use org.apache.jackrabbit:filevault-package-maven-pluginSeparate mutable from immutable
Set packageType
Take validation errors seriously and fix them
Set cloudManagerTarget=none
Make use of repoinit
16Example use cases
Create service users, set ACLs
Create resources, set properties
Define via OSGi factory configs
Limitations: Not possible to remove/replace,
not suited for big chunks of content repoinitExample 17 # Create assets root folder create path /content/dam/app1(sling:Folder) # Create service user for accessing assets create service user app1SystemUser set ACL on /content/dam/app1 allow jcr:read,rep:write for app1SystemUser endHTML Client library URL fingerprinting
18AEM Cloud service automatically enables
Ąąclientlibs(hash)
Example:
Remove:
Manual/Automatic set of longCacheKeyparam
ACS AEM Commons Versioned Clientlibs
wcm.io CONGA Support for AEM CloudManager Photo by Stacey Gabrielle Koenitz Rozellson UnsplashCONGA config for AEM Cloud projects
20Config Definitionin AEM project
Repository
OSGi configs
Configs in Content
(e.g. replication agents)Dispatcher config
Templates with
placeholdersEnvironmentsin Config Mgmt
AEM project env. config
Domain names
IP Addresses
Number of instances
Machine sizing
Credential references
CONGA-generated AEM packages
21Set package types
Apply FileVaultvalidation
Use repoinitfor system users & ACLs
22definitions
Distinguishes author and publish run modes
Automatically generates package dependencies -
based on file order in CONGA definitionsDispatcher configuration
23CONGA AEM Definitions provides new role
aem-dispatcher-cloudSupports single dispatcher config with
conditionalsAnd much more like Short URL Mapping
Demo 24AEM Cloud project
with CONGA DefinitionsGive it a try
25wcm.io Maven Archetype for AEM
CONGA support
AEM Cloud support
wcm.io Handler (optional)Photo by Sergiy Tryapitsyn
Other Pitfalls
and SolutionsPhoto by Bart Christiaanseon Unsplash
No crypto key support
27New approach to provide secretsin OSGi
system configurationSet environment variables via Adobe I/O:
$ aio cloudmanager:set-environment-variables 12345 --variable PARAM_1 "value1" $ aio cloudmanager:set-environment-variables 12345 --secret PARAM_2 "secret2"Reference environment variables in OSGi config:
com.app1.ServiceConfiguration secretParam2="$[env:PARAM_2]"Make sure to use UPPERCASE_UNDERLINE
notation for variable names | DocumentationDo not overwrite default log level
28This will break the Cloud Manager build:
org.apache.sling.commons.log.LogManagerBundles with Sling-Initial-Content
29Works with AEM Cloud Service
feature in Maven project -to ensure consistent ordering of entries in bundle JAR fileOutdated versions in build environment
30Currently you are limited to:
Maven 3.6.0
Java 8 *)
* AEM Documentationdescribes a way to use Java 11, I was not able to get it workingUpdate 30.09.20:
Java 11 support is working as described in the Adobe documentation (with maven-toolchains-plugin). But: Not all Maven plugins support this way ʹespecially the maven-enforcer-plugindoes not support it, remove Java 11 constraint from it.Define own Maven repositories
31By default, only Maven Central is used
Define alternative repos in POM
(enclosed in profile)Define credentials via own settings.xml
(see documentation)Or use maven-ext-repos-from-env
References
32Example project: https://github.com/adaptto/2020-aem-sample-project-conga-cloud wcm.io CONGA adaptTo() 2015: CONGA -Configuration generation for Sling and AEM adaptTo() 2017: Automate AEM Deployment with Ansible and wcm.io CONGA adaptTo() 2018: Maven Archetypes for AEM & Cloud Deployment