When administering RES Workspace Manager the Console always communicates directly with the Datastore, never via a Relay Server.īy default Agents connect directly to the Datastore. This makes the Datastorea critical component in a RES Workspace Manager infrastructure. RES Workspace Manager stores all the configuration, logging and usage tracking data in a RES Workspace Manager Datastore. Just like the Relay Server the RES WM Agent will poll the Relay Server every x time (default: 5 seconds) and update its local cache after x time (default: immediately) Since this location is on the system drive (by default) it will monitor the available free disk space to prevent resource depletion (see other facts). The Relay Server stores the entire RES Workspace Manger Datastore in its cache location: %ProgramData%\RES\Relay Server, this location can be changed. The Relay Server polls for changes every x time (default 5 seconds)and updates its local cache after x time (default: immediately). While the name suggest the Relay Server relays the traffic between a RES WM Agent and the RES WM DataStore it actually doesn’t, instead it acts as intermediate storage. It is a Windows Service that can be installed on a Windows operating system and by default listens on TCP port 1942 (registered at IANA), the same port that’s used by the RES WM Agent (see other facts). The Relay Server is an intermediate component between the RES WM Agent and the Workspace Manager Datastore, if required Agents can still connect directly to a Datastore. The Relay Server was introduced with RES Workspace Manager 2012 as an optional component. In this article I’ll explain what the Relay Server is, how it can help you in your Workspace Manager (WM) environment and reveal some of its mysteries. With the release of RES Workspace Manager 2012 a new component was introduced: the Relay Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |