The TotalAccess™ Server is tightly integrated with the Axeda® Enterprise Server and the Axeda® IDM Agent. To display a diagram that shows the layout and relationships of the TotalAccess components and the other portions of the solution, click here; click again to hide the diagram.
The TotalAccess Server or cluster of servers is installed on a machine in the web tier, usually on a dedicated server. The TotalAccess "HSC" is installed on or near the "asset" in conjunction with the Remote Desktop Server (for example, Axeda® Desktop Server or the UltraVNC or Real VNC Server) or other server programs. For more information on the asset side installation of TotalAccess, please refer to the Axeda® IDM Agent Installation Guide.
To provide horizontal scalability and failover, the TotalAccess Server (TAS) supports multiple concurrent servers on one or more computers. To display a diagram that shows the deployment for a TotalAccess Server cluster, click here; click again to hide the diagram.
The current cluster solution requires a commercial load balancer. All asset-side connections to the TAS cluster are made through a single URL managed by the load balancer that distributes the load across the configured TotalAccess servers. The TotalAccess servers may reside on the same physical/virtual host or on different hosts, as long as there are no conflicts with addresses and port numbers. For example, TAS 1 and TAS 2 are on the same machine, but TAS 1 may be accepting connections on HOST-A:9100 and TAS 2 is accepting connections on HOST-A:9101. Alternatively HOST-A may have multiple IP addresses and the TotalAccess servers are accepting on the same port number, but different addresses.
The TotalAccess application records the connections for each TotalAccess server in the cluster and directs the TotalAccess HCC ("client" side ActiveX control) to the one TotalAccess server that is managing the connection(s) for the desired application. This is known as the "client URL". The deployment shown in the diagram has the client URL s managed by the load balancer as well, even though these connections map to only one server on the back end. The advantage of this deployment is that the SSL termination can be performed at the load balancer, offloading this work from each of the TotalAccess servers. The client URL may also refer directly to the TotalAccess server, bypassing the load balancer.
For more information about the TotalAccess Server, refer to the installation guide for the Total Access Server.
