Separation of concerns when setting up your environment
Thanks to Topology Manager and the service-based Content Delivery setup, different departments in your organization can concern themselves with only their part of the overall SDL Web infrastructure, without having to take into account the other parts.
| Infrastructure part | Department |
|---|---|
| Content Manager environment | Web content management |
| Content Delivery environments | Core IT |
| Topology Manager | Business IT |
- Web content management
-
The Web team creates a list of requirements about the various Web sites they want to be able to publish to. For each Web site, a number of Content Delivery Capabilities may be desired. For example, one site, a staging site, may require Preview in order to facilitate editing its contents directly using Experience Manager. Another site may require the UGC Capability, to enable commenting and rating. Based on local regulations, the Web team may even demand that the servers they publish to are located in a specific geographical location.
- Core IT
-
The Core IT team can set up any number of physical servers to meet the Web team's requirements. The environments, which can be scaled out and/or put in the Cloud as needed, each have a single entry point: the Discovery Endpoint, exposed through the Discovery Service. Each endpoint exposes the Capabilities that that environment offers.
- Business IT
-
Using a series of simple PowerShell scripts, the Business IT team can configure Topology Manager to map the environments to each other. To the Content Manager environment, it presents a series of logical targets to publish to; on the Content Delivery side, it maps those logical targets to actual Content Delivery environments.