Publishing to preview environment. | Community
Skip to main content
M
mahithab9670023
March 10, 2020
Solved

Publishing to preview environment.

  • March 10, 2020
  • 2 replies
  • 3748 views

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.

 

 

 

 

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

@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.html#.XmeJlZP7TUI

2 replies

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
March 10, 2020

@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.html#.XmeJlZP7TUI

    tim_funk
    tim_funk
    March 12, 2020

    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.

     

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...