Improved security: Credentials used to communicate with the Datastore are not required on the Agent or during installation, instead an environment password is provided which does not grant access to a database server.No need for native database drivers on Agents : Since the communication with the Datastore is handled by the Relay Server this is the only machine that requires special drivers.Improve availability of the Datastore in a non-persistent environment: As explained here.Prevent database cluster: High availability and resiliency is achieved by using multiple Relay Servers which are easier to setup and do not require an expensive license.There are number of use cases that could justify the use of an additional component: As a general consideration: don’t overdesign your environment but keep it simple ( KISS). The use of a Relay Server in RES Workspace Manager is optional and it should only be used when necessary. Martin Lako explained how this can be achieved using Workspace containers in this article. Separation of agents based on their location: Depending on their physical location agents could contact the nearest Relay Server. This makes the Relay Server architecture very flexible and scalable. Relay Servers can retrieve the content of the Datastore also from a sibling Relay Server, it doesn’t have to communicate directly with the Datastore. Especially when compare to configuring database clusters and it’s cheaper too. The configuration of multiple Relay Servers is straightforward, simple even. With a Relay Server in a remote site only the Relay Server communicates over the WAN link, all agents can communicate via the LAN with the Relay Server. To prevent each Agent from communicating with the Datastore (or Relay Server) via a WAN connection a Relay Server can be placed in each remote site. This (of course) does not mean less license are needed, each agent still requires a license. When Agents are configured to communicate with the Relay Server the number of connections to the Datastore is decreased to two per Relay Server, regardless of the number of Agents. When the Datastore is stored on an Oracle server this limit is “100s of thousands”. With each Agent having two connections (one for the configuration database and one for the logging database) a Microsoft SQL server could reach its User Connection limit of 32.767 (see Maximum Capacity Specification for SQL Server). In a large environment the server hosting the Datastore could reach its connection limit. This could led to challenging situations because either the Datastore needs be replicated to multiple sites or each Agent communicates via a WAN connection to a remote Datastore. This requires that the Agents are able to communicate to the Datastore, even when they are in different locations. 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 Datastore a 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 |