The purpose of this article is to dip a little into the storefront multi-site settings to another element that comes a lot Web interface has changed. As part of the Citrix Consulting organization many of our customers are starting to make the transition to Storefront Web Interface, looking especially as our XenApp 6.5 clients migrating to 7.5 and 7.6. We are much more questions about these settings, such as the number of farms (see pages per new 7.x terminology and now clarify any reference to "site" in the rest of this post should have a XenApp / XenDesktop 7.x are contemplated page not a storefront site) are enumerated tends XenApp to increase going 7.x Schoten 6.5 zone based architectures datacenter-based XenApp / XenDesktop. In this article we will see what these settings are, why they are important, and some examples of how we have used them in the field.
To shortcut for these settings, which is closest Embedded Web Set Interface equivalent farm
In this way, the next user is parallel the web interface "high availability and load balancing" Code published by Dan Allen from some of our large customers XenDesktop used. I make no promises, the storefront can through this code, but the overall goal is the same done everything fit: to take what can do web interface to filter which resources users see by default one step further. Although these settings are used with XenApp 6.5, in the field, we can use it by far the most with XenDesktop / XenApp 7.x because we usually have more sites have site-per-datacenter enumerate the following directive when we with XenApp 6.5 and had farms that could span multiple data centers.
So without further ado, we're going to get in a few examples. The storefront multi-site settings from version 2.5, only config-file-based and documented in eDocs here. I have a sample structure copied below for reference.
...
aggregation group = " aggregation groupName "> ... ...
For our terms, define the primary day, we have the field using and will cover in the following examples are:
- user farm mapping : used to a group of users to a selection assign pages. Closest direct correspondence to the Web Farm
Group parameters - equivalentFarmSet . A number of sites (within the "primaryFarmRefs" day). That are considered identical An enumeration request is given to only one of the sides in the set on the load balancing mechanism (either the first in the list if "failover" is specified or randomly when "load balancing" is specified) sent to the base. The "backupFarmRefs" sites are queried only if all primary sites are down
- aggregation group . A number of pages in various equivalent farm sets from which identical resources are placed in a single symbol (eg but single-site resources are shown on all sides). So if "My Desktop" published in two pages for all users, users see only a symbol, instead of two. But if "word" is only available in Site A and "Excel" in location B only available, both also displayed.
Now that we have an understanding of the parameters below are some examples of how we have used these settings in the field. These are not designed to include every scenario, but hopefully an idea of how these settings can be used, and an idea of how the settings can be combined, if your needs match a combination of the above scenarios.
- Scenario 1 : Identical, (broken down several XenDesktop peppers, for example due to scale) active / active sites on the same data center or LAN speed connected data centers.
- Desired User Experience :. Users round robin are distributed between the sides
- Alternate Configuration : All pages in the "primaryFarmRefs" the same "equivalentFarmSet" set with "load balanced" as load balancing mode. The aggregation group tag is not important if only one equivalent indicated Farm sentence.
| ...
|
- scenario 2: Two identical, active / passive pages either in the same or different data centers.
- Desired User Experience .: The user is sent to the primary site and only on the passive site for disaster recovery
- sent Possible configuration: Same "equivalentFarmSet" with "failover" as the load-balancing mode.
|
|
- scenario 3: same, active / active pages (or sets of pages) in the different data centers with resources that are to be aggregated.
- Desired User Experience .: users are directed to the "local" site for new connections (but connected regardless of location as required again), not random balanced load
- Possible configuration: Different "equivalentFarmSet" work with the same "aggregation group" day. The order of "equivalentFarmSet" list works as a preference. So are the storefront server colocated with Site1 would look like and the storefront server colocated with Site2 would the page order reversed.
|
|
- scenario 4: several heterogeneous sites, including some identical resources that should be aggregated, and some unique resources.
- Desired User Experience: should see user unique resources from all sides, but only a symbol for identical resources. If they start from a unique app / desktop, will introduce an aggregated resources to continue in the same site
- Possible configuration :. Different "equivalentFarmSet" sets tag with the same "aggregation group".
|
...
|
- scenario 5: Totally unique pages.
- Desired User Experience: user should see resources from all sides, in which they published resources
- Possible configuration :. This is a bit of a trick scenario: if we completely unique pages are no multi-site settings then unnecessary - Storefront (and web interface) aggregated resources from all enumerated pages natively. However, when increasing the number of unique pages, enumeration tends time also increase, which can lead login delays. This is greatly improved with parallel enumeration, as previously referred to, but we recommend checking and counting and timing for optimal performance, users should be assigned only to the sites to which they have access.
0 Komentar