We are currently running SDL Tridion 2013 SP1. We are in the process of upgrading to SDL Web 8 and also deploying High Availability for the Presentation Side (as a completely new setup parallel to the existing production environment).

The website is Java based running off IIS and Tomcat. In the suggested architecture there are 2 web servers running IIS forwarding requests for dynamic contents to 2 Application servers running Tomcat. The same application servers would also be hosting the SDL Web 8 content delivery Discovery and Deployer micro-services.

We suggested running the Discovery and Deployer services in a active/passive fail-over configuration so that the CMS always publishes to only 1 deployer (active at that moment). Both application servers would be communicating with the same Content Broker database. And all published files (JSP, CSS, JS, JPG, etc) would be stored on the filesystem on AppServer1 and then be replicated to AppServer2 using Microsoft DFSR.

In case 1 of the app servers goes down or is offline for maintenance then the the NLB would automatically route all publishing traffic to the other app server (actve/passive fail-over) and publishing would continue seamlessly. As soon as the other server comes back online DFSR would replicate all new/updated files to this server from the other server.

However DFSR requires that both app servers be connected to the domain controller which is a problem for the client's IT Security.

They have asked us to suggest an alternate approach where the CMS can publish to both servers directly and avoid any file replication. If we were to publish to both app servers separately what would be recommended setup?

  1. would both app servers be communicating with their own independent Content Broker databases?

  2. if one of the app servers goes down (or is taken offline for scheduled maintenance), how would the contents be synced between the two once the server is brought up?

I have read the online SDL documentation (Content Delivery Presentation Server load balancing) but did not find sufficient information.

Kindly advice considering this would be running on SDL Web 8.

  • 1
    Web 8.5 includes multiple destination publishing and will be out by end of year. Would this be an option?
    – Nuno Linhares
    Nov 24, 2016 at 16:32
  • What about using a shared filesystem (NAS or SAN) instead of file replication? Nov 25, 2016 at 9:40
  • @NunoLinhares Could you please give me some details on how would the below be handled with the multi-destination publishing model of 8.5: "if one of the app servers goes down (or is taken offline for scheduled maintenance), how would the contents be synced between the two once the server is brought up?" Nov 25, 2016 at 19:43
  • Good point, I jumped the gun on that. With DD4T/DXA models this won't be an issue (DB publishing), but for file system it won't work. With multi-destination publishing files won't publish if one target is offline.
    – Nuno Linhares
    Nov 25, 2016 at 20:20
  • Thanks Nuno. So for physical files based model we would have to stick to some kind of file replication for this to work. Right? Nov 26, 2016 at 8:44


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.