publish a whole site AEM 6.5 | Adobe Higher Education
Skip to main content
key-key
Level 4
June 9, 2020
Beantwoord

publish a whole site AEM 6.5

  • June 9, 2020
  • 7 reacties
  • 5249 Bekeken

As a content author, How can i publish a whole site in AEM 6.5 in one go?  I suppose its using the manage publication feature and adding the root page to include subpages? 

Er kunnen geen reacties meer worden geplaatst op dit onderwerp.
Beste antwoord door BrianKasingli

Hi @key-key,

To successfully publish your entire AEM site to all your publishers, and assuming your website is not too large, and assuming that you only have access to the Author you can:

  1. Setup: Configure your replication Agent with the correct list of publishers. - link
    - test the connection, ensure that you are setup correctly. 
  2. Replicate Project Script(s): Crx/DE Package Manager, Replicate your scripts content package (typically in ui.apps if you follow the AEM Maven Archetype folder structures)
  3. Replicate Project Dependencies Script(s): Crx/DE Package Manager, Replicate your supporting dependencies such as ACS Commons, AEM Forms Package, AEM Service Packs, etc..
  4. Replicate Content - Option A: Replicate pages and it's References.
    - Replicate via AEM's built-in Publish Reference Feature - link
    Replicate your content via Touch UI you can multi-select pages to be activated; activating pages from Touch UI has a feature where it will also activate DAM assets, editable components, tags, and all other AEM resources that are used/linked to that page, so you will not forget to publish pages.
  5. Replicate Content - Option B: Replicate it all via Content packages. - link
    - Replicate all content; assuming that all content is for the public.
    Create a new content package in with the filters below (catches most of the content related filters a basic AEM site would hold); build and replicate the package.
    <filter root="/conf/my-site"></filter>
    <filter root="/content/cq:tags/my-site"></filter>
    <filter root="/content/dam/my-site"></filter>
    <filter root="/content/experience-fragments/my-site"></filter>
    <filter root="/content/my-site"></filter>
  6. Replicate Content - Option C: Replicate it all via Tree Activation - link
    http://localhost:4502/libs/replication/treeactivation.htm
    - Replicate all content; assuming that all content is for the public. 
    "/conf/my-site"
    "/content/cq:tags/my-site"
    "/content/dam/my-site"
    "/content/experience-fragments/my-site"
    "/content/my-site"

 Good Luck!

 

 

7 reacties

Ankur_Khare
Community Advisor
Community Advisor
June 9, 2020

You can replicate entire content hierarchy from here-

http://localhost:4502/libs/replication/treeactivation.html 

VeenaVikraman
Community Advisor
Community Advisor
June 9, 2020

Tree Activation is the way to do it in one go. But depends on if the author is given permission  to do so. 

Adobe Employee
June 9, 2020

Another option is to create a package of your site with all dependencies and replicate the package itself from the Package Manager

Harwinder-singh
Community Advisor
Community Advisor
June 9, 2020

@key-key 

If it is just content, you can use tree activation option.

But remember the tree activation is no longer under /etc but rather under /libs

Instead the url that you should be using is - http://<HOST>:<PORT>/libs/replication/treeactivation.html

 

 

BrianKasingli
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 9, 2020

Hi @key-key,

To successfully publish your entire AEM site to all your publishers, and assuming your website is not too large, and assuming that you only have access to the Author you can:

  1. Setup: Configure your replication Agent with the correct list of publishers. - link
    - test the connection, ensure that you are setup correctly. 
  2. Replicate Project Script(s): Crx/DE Package Manager, Replicate your scripts content package (typically in ui.apps if you follow the AEM Maven Archetype folder structures)
  3. Replicate Project Dependencies Script(s): Crx/DE Package Manager, Replicate your supporting dependencies such as ACS Commons, AEM Forms Package, AEM Service Packs, etc..
  4. Replicate Content - Option A: Replicate pages and it's References.
    - Replicate via AEM's built-in Publish Reference Feature - link
    Replicate your content via Touch UI you can multi-select pages to be activated; activating pages from Touch UI has a feature where it will also activate DAM assets, editable components, tags, and all other AEM resources that are used/linked to that page, so you will not forget to publish pages.
  5. Replicate Content - Option B: Replicate it all via Content packages. - link
    - Replicate all content; assuming that all content is for the public.
    Create a new content package in with the filters below (catches most of the content related filters a basic AEM site would hold); build and replicate the package.
    <filter root="/conf/my-site"></filter>
    <filter root="/content/cq:tags/my-site"></filter>
    <filter root="/content/dam/my-site"></filter>
    <filter root="/content/experience-fragments/my-site"></filter>
    <filter root="/content/my-site"></filter>
  6. Replicate Content - Option C: Replicate it all via Tree Activation - link
    http://localhost:4502/libs/replication/treeactivation.htm
    - Replicate all content; assuming that all content is for the public. 
    "/conf/my-site"
    "/content/cq:tags/my-site"
    "/content/dam/my-site"
    "/content/experience-fragments/my-site"
    "/content/my-site"

 Good Luck!

 

 

key-key
key-keyAuteur
Level 4
June 11, 2020
thank you so much - i am only AEM content author so option 4 should be the one for me.
sunjot16
Adobe Employee
Adobe Employee
June 11, 2020

You can use Manage Publication or even create package of the entire site on your instance and deploy it on other environments.

 

The following doc may be helpful in publishing sites/pages:

https://docs.adobe.com/content/help/en/experience-manager-65/authoring/authoring/publishing-pages.html

 

The following doc may be helpful in creating packages:

https://docs.adobe.com/content/help/en/experience-manager-65/administering/contentmanagement/package-manager.html

nidhip010816
Adobe Employee
Adobe Employee
June 11, 2020

Hello @key-key 

 

Tree Activation could be used for the use case you have - 

https://www.cqtutorial.com/courses/cq-admin/cq-admin-lessons/configure-cq-replication/cq-activate-tree

Note - Now tree activation is done from <host:prt>/libs/replication/treeactivation.html

 

But since you need to publish the whole site, you may want to do via Package method. Just create a package of your site and install it over destination instance.

 

Hope this helps!

 

Best Regards,

Nidz