This documentation is archived and is not being maintained.

Walkthrough: Applying Constraints to a Logical Datacenter 

This walkthrough guides you through adding an existing logical datacenter diagram to your solution and applying constraints against the applications that might be hosted in the datacenter modeled on this diagram. In a later walkthrough, you will use this diagram to test deployment by binding applications in your system to hosts in the datacenter.

In this walkthrough, you will complete the following tasks:

  • Load an existing logical datacenter diagram.

  • Specify communication and application hosting constraints.

A sample that demonstrates the outcome of this walkthrough is available on the Microsoft Download Center at

To open an existing logical datacenter diagram

This diagram contains three zones (PerimeterNetwork, Intranet, and SecureData). Each of these zones represents different communication boundaries in the datacenter. Web, Windows, and database servers that can host the applications in Catalog.sln are contained in these zones.

Now that you have a representation of the datacenter, you can specify constraints on the communication pathways and hosting relationships within it. For example, you could constrain the HardenedIIS Web server so that it could not host Web service applications.

To specify and configure constraints

  1. Select ApplicationServer in the Intranet zone and view the Setting and Constraints Editor by choosing Settings and Constraints from the View, Other Windows menu.

    Two groups of constraints are provided. The top-level group represents a set of hosting constraints. For example, by selecting ASP.NETWebApplication, you are allowing this logical server to host ASP.NET Web applications. Clearing this check box prevents these applications from being hosted.

    Under the top-level hosting constraints is a set of predefined constraints that consolidate common configuration settings. For example, the ASP.NET Security constraint combines settings related to ASP.NET application security.

  2. Ensure the ASP.NETWebApplication constraint check box is selected.

  3. Select the ASP.NET Security constraint and then click ASP.NET Security.

  4. In the constraint dialog box, ensure that "Forms" is the only value selected under Allowed Security Modes. The default constraint for this type of server is "Forms" and "Windows."

  5. Select Requires Impersonation.

  6. Under Password Format, select "SHA1."

  7. Save eCommerceDatacenter.ldd.

You are now ready to bind the applications within the system you created in previous walkthroughs to the datacenter to which you added constraints in this walkthrough. After binding, you can validate the system against the datacenter to determine whether any errors would occur during deployment. To complete this next step, see Walkthrough: Validating an Application System for Deployment.