publish a whole site AEM 6.5

9 replies
5249 views
Translate

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

BrianKasingliAccepted solution

New Participant

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:

Setup: Configure your replication Agent with the correct list of publishers. - link
- test the connection, ensure that you are setup correctly.
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)
Replicate Project Dependencies Script(s): Crx/DE Package Manager, Replicate your supporting dependencies such as ACS Commons, AEM Forms Package, AEM Service Packs, etc..
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.
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>
```
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!

nidhip010816

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

Translate

sunjot16

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

Translate

BrianKasingliAccepted solution

New Participant

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:

Setup: Configure your replication Agent with the correct list of publishers. - link
- test the connection, ensure that you are setup correctly.
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)
Replicate Project Dependencies Script(s): Crx/DE Package Manager, Replicate your supporting dependencies such as ACS Commons, AEM Forms Package, AEM Service Packs, etc..
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.
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>
```
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"
```