Publish environment setup

[khamat_bn]

Hi All,

I am working on new project where I have created a Dev author env. in aws and deployed code in it via cmd. 

But can you guys please guide me

1. how I can replicate Package to publisher in one go.
2. What and  all things I have to replicate over dev author just page or packages from package Manager.
3. How we can replicate bundle.
4. What about the Experience Fragments, DAM Assets, editable template, How we can manage publishing of this 
5. I Dont want  We- retail page or project in publish env.
6. How we can directly access project first page just like we got we-retails page when we open publisher.

[hamidk92094312]

You need to review the relevant document:

https://docs.adobe.com/content/help/en/experience-manager-64/deploying/configuring/replication.html

The contents that will be replicated to publish instance depends on the contents you have authored.

You can uninstall we-retail package if you do not want it.

[ArpitVarshney]

Hi @khamat_bn 

1. how I can replicate Package to publisher in one go. - Setup a replication agent in AEM based on the number of publishers you are using. After setup, you will be able to replicate any package/page or asset from author to publishers. Here is the guide https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/replication.html
2. What and  all things I have to replicate over dev author just page or packages from package Manager - You mentioned that it has been deployed on author. But in order to deploy it to publishers, you can just replicate the package from author to publisher or deploy the codebase on each publisher instance. Also, Here is the guide to publish pages https://docs.adobe.com/content/help/en/experience-manager-65/authoring/authoring/publishing-pages.ht...
3. How we can replicate bundle. - I assume that the bundle will be a part of the codebase that you have installed via command so replicating the package or just installing it in each publisher will also include the bundle.
4. What about the Experience Fragments, DAM Assets, editable template, How we can manage the publishing of this - You can just publish it directly once you create/upload any asset or experience fragment.
5. I Dont want  We- retail page or project in publish env. - You can deactivate we-retail content pages from publishers.
6. How we can directly access project first page just like we got we-retails page when we open publisher. - You need to make changes in Root mapping servlet configuration. Refer this thread https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/configure-default-publish-...

[kautuk_sahni]

This is great reply.

[Theo_Pendle · Accepted solution]

Hi @khamat_bn,

@ArpitVarshney's answer covers most of your points, but I'll just add a few of my own:

1. Once you've configured your replication agent to replicate to Publisher, you can replicate packages through CRX DE with the following option:

2. This depends on your project and your content. If you are joining a project that already has code and content deployed and you're not sure what to replicate, a good place to start is to look in the ui.apps and ui.content module of the maven project. This will show you what kinds of things are used in your project. For example:

• Templates (and policies)
• Tags
• Sites
• Configurations
• Assets
• Forms

If you google any one of those terms, you'll find a refrence to where they are stored in the JCR. Another good place to check is by browsing this list of popularly used repository locations: https://docs.adobe.com/content/help/en/experience-manager-64/deploying/restructuring/all-repository-...

3. Any bundles you have deployed SHOULD be part of a codebase. For example, it is common practice for ui.apps to embed your java code in a JAR in the /apps/site/install folder and install the bundle at the same time as the package. If you replicate that package, you will also replicate the embedded bundle You should not be replicating OOTB bundles since they will be installed when you boot up your Publisher instance for the first time. 

4. As mentioned for number 2, once you've identified which are the root folders where your content is located (there shouldn't be more than 4-6 of these per site), you can quite easily replicate by using the TouchUI Publish button and making sure to include all children an dependencies.

5. Simply launch your publisher for the first time with the nosamplecontent flag (more information here: https://docs.adobe.com/content/help/en/experience-manager-65/administering/security/production-ready...) and then avoid publishing the We.Retail content 

6. Nothing to add

Hope that helps!

[khamat_bn]

Thanks @Theo_Pendle and @ArpitVarshney. This will help me a lot

[Theo_Pendle]

Happy to help