Configure AEM CQ6 (author + publish + Apache Dispatcher + Ubuntu)

Source: Internet
Author: User
Tags apache log docker run

AEM CQ Series is the Enterprise Content management system under Adobe, now some enterprises known such as Deloitte,ford Racing, here do not do more basic introduction, see!

Today in Docker configuration author instance, publish instance, Apache dispatcher

Document Architecture

Author

-cq-author-4505.jar

-license.properties

Publish

-cq-author-4503.jar

-license.properties

Author Instance

From Ubuntu:14.04run mkdir/opt/aem/run apt-get install-y software-properties-commonrun add-apt-repository PPA: Webupd8team/javarun Apt-get update# Automatically accept Oracle Licenserun echo Oracle-java7-installer shared/ Accepted-oracle-license-v1-1 Select True | /usr/bin/debconf-set-selections# and install Java 7 Oracle jdkrun apt-get-y install Oracle-java7-installer && apt -get cleanrun update-alternatives--display javaenv java_home/usr/lib/jvm/java-7-oracleworkdir/opt/aem/add Cq-author-4505.jar/opt/aem/cq-author-4505.jar ADD license.properties/opt/aem/license.properties RUN Java-jar Cq-author-4505.jar-unpack-v

Run Author instance

Docker Run-i–t–d-p 4505:4505 <yourname>/aem-auth:6.0/bin/bash

We manually start the AEM instance

Java-jar Cq-author-4505.jar

After running http://192.168.59.103:4505, let's upgrade the service pack manually (and then we'll modify Docker to let him upgrade the service pack automatically)

Publish Instance

Here set publish instance very similar to author instance, just run

<yourName>/aem-pub:6.0/bin/bash 

And

Java-jar Cq-author-4503.jar

Run http://192.168.59.103:4503 again, we're going to upgrade the service Pack

Dispatcher

Here we use the ubuntu:14.04 mirror, where we open a port 8888来 map the internal 80 port

Docker run-i-t–d-p 8888:80--name aem-dispatcher ubuntu:14.04

Into the instance of dispatcher.

Docker Exec-i-T Aem-dispatcher/bin/bash

Installing Apache2

Apt-get Updateapt-get install-y apache2

Here Apache default root folder is/var/www

1th Step (step a bit more, write separately)

    • Download the config for AEM dispatcher, download and unzip wget https://www.adobeaemcloud.com/content/companies/public/adobe/dispatcher/ Dispatcher/_jcr_content/top/download_6/file.res/dispatcher-apache2.4-linux-x86-64-4.1.8.tar.gz

After download

    • Create a Conf folder in the/etc/apache2 directory and copy the Dispatcher.any file that you just unzipped to the previous CP dispatcher.any/etc/apache2/conf

    • Copy dispatcher-apache2.4-4.1.8.so to/usr/lib/apache2/modules (here the name is not modified, if it is production, it is recommended to modify the Apache standard name such as mod_aem.so )

2nd Step (Modify/etc/apache2/apache2.conf file)

Paste the following to the bottom of this apache2.conf, make sure that the name of the red note can exist within the system

LoadModule Dispatcher_module/usr/lib/apache2/modules/dispatcher-apache2.4-4.1.8.so<IfmoduleDisp_apache2.c># Location of the configuration file. Eg: ' Conf/dispatcher.any ' dispatcherconfig/etc/apache2/conf/dispatcher.any# location of the dispatcher log file. Eg: ' Logs/dispatcher.log ' dispatcherlog/var/log/apache2/dispatcher.log# log level for the dispatcher log# 0 errors# 1 Warn ings# 2 infos# 3 debugdispatcherloglevel 3# if turned to 1, the dispatcher looks like a normal Moduledispatchernoserverhea Der 0# if turned to 1, request to/are not handled by the dispatcher# and the Mod_alias then for the correct MAPPINGDISPA Tcherdeclineroot 0# if turned to 1, the dispatcher uses the URL already processed# by handlers preceeding the dispatcher ( i.e. Mod_rewrite) # Instead of the original one passed to the Web server. Dispatcheruseprocessedurl 0# if turned to 1, the dispatcher does not spool a error# response to the client (where the STA Tus code is greater# or equal than), but passes the status code to# Apache, which e.g. allows an errordocument directi ve# to process such a status code. Dispatcherpasserror 0</ifmodule><Directory /><ifmodule disp_apache2.c>  # Enable dispatcher for all request. If this was too restrictive, # move it to another locationsethandler Dispatcher-handler</ifmodule>
                          
                           options followsymlinksallowoverride None
                           </Directory>   
                            
3rd Step (Modify the/etc/apache2/conf/dispatcher.any file
/renders{/rend01{/hostname "192.168.59.103" [2]-->/port "4503"}}
And
/cache{    # The docroot must is equal to the document root of the webserver.      the # Dispatcher would store files relative to this directory and subsequent      # requests could be ' declined ' by the Di Spatcher, allowing the Webserver      # to deliver them just like static files.  /docroot "/var/www"

And

    /allowauthorized "1"

4th step, start apache2 service

This is nothing to say, if there is a mistake, please double check

Service Apache2 Start

Configure Publisher's author inside the

To configure publisher on author,

Http://192.168.59.103:4505/etc/replication/agents.author/publish.html

The default is not modified, but I use Docker under Windows, so I need to modify the IP,

Well, basically done, now is testing whether we are configured correctly. Let's use Geometrixx to make an example.

On author's instance, join us with this page http://192.168.59.103:4505/cf#/content/geometrixx/en.html, when released,

On Publisher's instance, let's check this page http://192.168.59.103:4503/content/geometrixx/en.html

Then we'll check if dispatcher is working, http://192.168.59.103:8888/content/geometrixx/en.html.

Okay, one last thing, we need to check to see if dispatcher has the cache on these pages? We are going to/var/www to see, the content has not been the cache to live, this is why?

We have to check Apache log, log written very clearly, because there is no permission to write to/var/www, okay, let's give him a privilege.

Chown-r www-data:www-data/var/www

Checking the/var/www

Done. If you have a chance, you will be introduced to AEM development.

Configure AEM CQ6 (author + publish + Apache Dispatcher + Ubuntu)

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.