About Symphony clients

Symphony uses EGO as its underlying resource allocation engine. A Symphony client not only connects to Symphony’s Session Director (SD) and Session Manager (SSM) servers but to EGO’s kernel daemon (VEMKD) and Service Controller, as well. This is because a Symphony client indirectly uses the EGO API to communicate with EGO. More specifically, a Symphony client is linked with the Symphony SDK library that uses the Symphony API (e.g. sessions). The Symphony API internally uses the EGO API to communicate with EGO, so the Symphony SDK client internally is also an EGO client.

To avoid ambiguity during the SSL configuration process, we will use the terms Symphony SDK client and EGO client in lieu of the generic Symphony client. Connections to both clients must be configured to ensure security for all communications between the clients and their respective servers.