AcquistaBuy
1-855-856-7678
SupportoSupport
EN
Il contenuto non è disponibile nella lingua di destinazione, ma solo in inglese.
Getting Started with Windows Azure Traffic Manager
[This topic contains preliminary content for the CTP release of Windows Azure Traffic Manager. To begin using the feature, go to the Virtual Network tab located in the Windows Azure Management Portal.]
You can use Windows Azure Traffic Manager (WATM) to control the distribution of user traffic to similar hosted services that are running within the same data center or in different data centers across the world. You may want to send traffic to the best data center for performance, business continuity, price, compliance, legal, or tax purposes. Traffic Manager works by applying an intelligent policy engine to the DNS queries on your domain names.
The main page of the Windows Azure Traffic Manager in the Windows Azure Platform Management Portal shows a graphic (Figure 1) that outlines:
-
Conceptual traffic flow – A flow of user traffic from a conceptual point of view. For more information on the actual flow, see Windows Azure Traffic Manager Overview.
-
The steps to create a working Traffic Manager policy and domain – Numbering shows the order that you need to follow in order to create a functional Traffic Manager policy and domain.
Figure 1 – Windows Azure Traffic Manager main page graphic
The following numbered steps below match those in the above graphic. Use the references to get help for a specific step.
 Note |
|---|
| These steps can be done in a slightly different order once you have a firm understanding of how to create a policy and the best practices. Steps 2, 3, and 4 are performed in the Create Policy dialog box within Traffic Manager. |
| Step | References |
|---|---|
|
1 – Deploy your hosted services into your production environment. When you create a policy, you must associate it to a subscription. You can then add hosted services in production that are part of the same subscription. If a hosted service is not in a Windows Azure production environment or in the same subscription, it will not be available to add. |
|
|
2 – Pick a load balancing method. Three different load balancing methods are available. Understand your options before creating a policy. |
|
|
3 – Set up monitoring. Traffic Manager monitors hosted services to ensure that they are online, regardless of the load balancing method. It will not send traffic to hosted services that are offline according to the monitoring system. If Traffic Manager determines that all the hosted services are offline, or cannot detect the hosted services in a policy, it will load balance traffic by using the load balancing method selected for that policy. For example, if your load balancing method is Round Robin and all hosted services are detected offline, Traffic Manager will continue to load balance traffic using Round Robin. In order to set up Traffic Manager monitoring
You may:
|
|
|
4 – Decide on a name for your Traffic Manager Domain. Consider a name for your domain with a unique prefix. The later part of the domain is fixed. |
|
|
5 – Create the policy. This involves actually putting data from Steps 2, 3, and 4 into the Create Traffic Manager Policy dialog box. The articles that are listed as references can walk you through creating each type of policy end-to-end. |
|
|
6 – Test your Traffic Manager policy. Test that your policy and domain are working as expected. You can use publicly available tools. |
|
|
7 – Point your company domain’s DNS resource record to the policy in order to make it live. For example, change the DNS resource record on your servers to include the following line to point the company domain to the Traffic Manager domain as outlined in Figure 1:
|
See Also
