Try our conversational search powered by Generative AI!

Decoupled setup


Trying to figure out some things about the Decoupled setup for CMS 11.20.7 on-premise.

  1. Is the code deployed to the public and internal/admin site the same and on the public site you just change to deny users="*" on edit and admin locations? Or can you somehow skip the presentation on the admin site and skip the admin ui on the public site by removing nuget packages or similar?
  2. Do the sites need individual licenses or can we run the same license?
Feb 02, 2022 9:50


Same code is deployed to all servers.

Licensing is per server and site, so you could have bought lincese for one site and additional server or servers (you need valid licenses also for customer test environments).

Also if you have decoupled setup, you usually want to run the scheduled jobs, only on the admin server. See documentation and find the "enableScheduler" setting. So you would set that to false in web.config for the front-end server and on the admin config you would have it true, so the scheduled jobs are running only on the admin server and not the front-end (publically accessible server(s)).

Feb 03, 2022 13:01
This thread is locked and should be used for reference only.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.