In my colleague Sarah Steinhoff blog article entitled What subscriptions and server groups mean for storefront designs, they mentioned that load balancing VIPs should be used between storefront server group to replicate the subscription data. As part of the Citrix Consulting team worked with clients storefront has to implement, I have been asked on a number of occasions that the recommended setting for this subscription should vServer. This blog entry will detail the recommended means of required for the synchronization of the VPS and the declaration on the establishment of VDS.
First I want that each server group to highlight that a separate need is provided load balancing vServer. This is true if you have multiple server groups within the same data center or server groups in separate data centers . [Please note, that this recommendation itself is not a requirement, as it is possible to use the same VIP address and create a separate vServer using port 808 instead. However, the recommendation to create a separate VIP is for traffic management and operational support purposes.] Please remember, per Sarah products "While subscriptions are automatically synchronized per store to write between servers in the same server group, nothing is synchronized by default between Storefront servers in different server groups." This is an important point is that can not be overstated. If you storefront in a multi-site configuration in which the users are not bound to use a single site, you must ensure that your user is replicated synchronization data to ensure a consistent user experience.
When creating the subscription Sync vServer of
The following settings are to be set up recommended:
- Set the TCP port 808 Subscription Sync VIP
- Select 'Round Robin' as LoadBalanced method
- Select "Persistence" to NONE
- Select "backup Persistence" to NONE
let us now take a look at the above options. First, we chose 'Round Robin' as a method for load balancing of the synchronization VIP. The schedule for synchronization should be set to run at certain times during the day, and as we do not care which server the request accepts during the sync process, as it replicate within the group replication to the rest of the server are we able to use the round robin method for our load balancing. Next, we chose "No" as our perseverance. The connection for the subscription synchronization requires no endurance. If a connection to the storefront server 1 is first made and then 2 Storefront Server the second time, this is no problem, again as in the server group are the replication is done between the server group members.
Again, make sure you have a load balancing vServer created for each storefront server group, go synching subscriptions between. Once you have completed that replication follow instructions for setting the schedule for synchronizing between the server groups, and you are ready to go.
I hope the following overview the facade subscription synchronization load balancer VIP to the setting helpful to your Storefront deployment.
0 Komentar