Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

publish a whole site AEM 6.5

key-key
Level 4
Level 4

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? 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution
BrianKasingli
Correct answer by
Community Advisor
Community Advisor

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!

 

 

View solution in original post

9 Replies
Veena_Vikram
Community Advisor
Community Advisor

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

berliant
Employee
Employee

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

adobe57138
Level 2
Level 2

@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
Correct answer by
Community Advisor
Community Advisor

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!

 

 

View solution in original post

key-key
Level 4
Level 4
thank you so much - i am only AEM content author so option 4 should be the one for me.
BrianKasingli
Community Advisor
Community Advisor
Thats correct, our content authors also use option 4. Where Touch UI replication will also replicate all the referenced templates, cq;tags, images, content-fragments, experience-fragements, etc... that the targeted page will be replicated. Nice one!
sunjot16
Employee
Employee

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.ht...

 

The following doc may be helpful in creating packages:

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

nidhip010816
Employee
Employee

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-tr...

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