Is it possible to get some guidelines on the use of pooled Select servers? How exactly does this work? It is easy to set-up with the install wizard, but are there any guidelines on the scaling out with multiple pooled servers. What exactly is the work that the Select Server instance doing? Will this work inconjuntion with a DNS entry for the server pool such as "SoftPro.mycompany.com" so that we just point all of our clients to this DNS and it would rout to these pooled servers. Would we need to use NLB for this to work with the DNS?
Thanks,
Jake
Pooled Server Documentation
Re: Pooled Server Documentation
As Select stands right now, you need to configure your load balancer to turn on sticky sessions (such that every client always goes to the same machine). Then you would create a server pool and create servers under the same pool (sharing port and database settings). And obviously you will need to redirect clients to your load balancer.
Select is nowadays a 3-tier application with the backend server handling most - soon all of the communication with the persistence (database) layer, centralized functionality such as authentication/licensing/locking, session state information, and doing more and more of the heavy lifting on behalf of the thinning client.
Select is nowadays a 3-tier application with the backend server handling most - soon all of the communication with the persistence (database) layer, centralized functionality such as authentication/licensing/locking, session state information, and doing more and more of the heavy lifting on behalf of the thinning client.
Re: Pooled Server Documentation
Thanks for the info. We will try with NLB to the pooled servers.