The idea back then was that every Citrix server would open a connection with every other Citrix server in the farm. thinking back to that gives me the chills!)
Those of you who’ve been working with Citrix for awhile know that WinFrame and MetaFrame 1.x made use of the first option via something known as the “ICA Browser Service.” (Whoo. Any incoming requests could be forwarded to the server that knows what’s going on. Design CPS product so that one server was the “king of gossip,” tasked with knowing everything about the state of every server.Design CPS so that all servers shared this information with all other servers, thus ensuring that any server receiving an information request would know what to do with it.In order to make these things work in Presentation Server, Citrix could have done one of two things: The system needs to know the server load in order to load-balance an incoming connection request.The system needs to know which servers are online so it can route incoming requests to servers that are running.The management console needs to show the admin which users are on which servers.This dynamic information is needed in several cases, such as: Things like which users are running sessions on which servers, which servers are online and offline, how much load is on each server, etc. This is basically all of the settings that you configure via the management consoles.īut as you can imagine, a Presentation Server environment requires that the servers keep track of a lot of dynamic information too. In other words, the data store only contains information that needs to be “remembered” when the server is turned off. It's not used to store any information about the current state of the environment. It’s crucially important that you know this database is only used for static configuration information. Remember from the last section that Citrix Presentation Server stores all of its configuration in a database called the IMA Data Store.