![]() (The size of the “Configuration and state” part of the primary Datastore provides an indication of the current cache size).Ī Relay Server connecting directly to the Datastore needs to have the database client installed for the type of database used for the RES Workspace Manager Datastore. NET Framework 4.0 or higher.Īny of the following server operating systems:Īvailable hard disk storage space must be at least 500 MB plus the current size of the Agent cache. ![]() If you want to deploy an Relay server first take a look at the system requirements: The relay server in the Workspace Manager architecture has the same role as the dispatcher has in the RES Automation Manager architecture. There is no need to install a database driver on your XenApp server because the connections to the datastore go through the relay server. ![]() With the relay server it is easier to scale your environment. It is not needed anymore to replicate the database. The Relay server also makes it easier to deploy RES WM servers on an remote location. With the RES WM 2012 Relay server this consideration is no longer necessary. If you have your logging and configuration data in separated databases the number is 16.381. Some research on the internet places that number somewhere around 32.762. Ok, but how many connections can a SQL server take? The Relay server was created to take some load of the connection to the SQL datastore. Ok, but what does it do?, when do I need it?, what are the requirements and how do I install and configure this role? These are a few questions I will answer in this article. With the release of RES Workspace Manager 2012 (RES WM 2012) came along a new server role in the RES WM 2012 architecture.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |