2

I am using single publication and two Target Types/Purpose(Staging, Live) I have setup 2 deployer, 2 discovery service for staging and live.

My issue is when I run discovery service update (java -jar .\discovery-registration.jar update) for staging, The published pages from both of the target go to staging. When I run discovery service update (java -jar .\discovery-registration.jar update) for live, The published pages from both of the target go to live.

I have checked the config setting of deployer/discovery both have their correct path/port set for staging and Live.

Is there anything else I can check?

Thank you in advance

Improve this question
2
  • 1
    Do you have separate discovery service for Staging and live (pointing to different DB) ?
    – vinayknl
    Commented May 13, 2016 at 16:27
  • Switch on debug logging for everything. Run a test and see if you get any new information.
    – Dominic Cronin
    Commented May 15, 2016 at 9:57

1 Answer 1

Reset to default
6

  • You have both discovery pointing to Same DiscoveryDB, When you run update for a discovery(say staging) then all it's capabilities get registered in this DiscoveryDB

  • At the time of publishing to two targets, two discovery are used to determine the respective deployers but as they refer to same DB to get Deployer Capability they both use the deployer registered at that time(staging here) & hence they both publish to staging.

Note- You should use Session-enabled Content Service in place of Content Service for the Staging Enviornment if you are going to use XPM - see here.

Improve this answer
2

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.