Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Publishing to preview environment.

Avatar

Level 1

Hey guys,

 

Author: localhost:4502

publish1: localhost:4503 

publish2: localhost:4504

 

i have an requirement i.e. from author user will be provided an option to publish a page from author to either publish1 or publish2 ar a time, please let me know if we can provide an option i.e. 'publish to publish1' and 'publish to publish2' so that there will not be any relation between publish1 and publish 2 during publishing.

 

please let me know if any more information required.

 

 

 

 

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@mahithab9670023,

The best way to achieve this is by creating two workflows.

  • Workflow One will publish to publish1
  • Workflow Two will publish to publish2

You will need to set two replication agents with the main identifier, agentID. Within the back-end, you can target which replication agent to use, using the com.day.cq.replication.AgentIdFilter.

I found a tutorial online that will steer you to the correct path - https://www.albinsblog.com/2018/02/approach-to-implement-content-preview-in-adobe-experience-manager...

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@mahithab9670023,

The best way to achieve this is by creating two workflows.

  • Workflow One will publish to publish1
  • Workflow Two will publish to publish2

You will need to set two replication agents with the main identifier, agentID. Within the back-end, you can target which replication agent to use, using the com.day.cq.replication.AgentIdFilter.

I found a tutorial online that will steer you to the correct path - https://www.albinsblog.com/2018/02/approach-to-implement-content-preview-in-adobe-experience-manager...

Avatar

Level 4

One alternative is to change the trigger on publish2 (assuming that is the preview server)  to be "On Modification". Then when any page or asset is changed - it is automatically replicated to the preview publisher with no additional effort by the author.

 

But if you use this feature - You probably also want to check "No Version" as well as "No Status Update" as well.  Otherwise - you may be deceived into believing items were activated to your production publisher while they actually were not.