Tedam Manager is an essential part of the TEDAM ecosystem. Tedam Manager can work itself like Tedam Face and Tedam Agent.
In general, it is the module that provides the coordination of the system. Basic responsibilities of Tedam Manager are;
• Transform test scenarios that entered via Tedam Face to executable commands,
• Send executable commands to available Tedam Agents,
• Collect test run results from Tedam Agent,
• Work as REST API interface,
• Notify user or 3rd party software with test results.

Tedam Manager contains the following parts:
-WebSocket
-Rest API
-Notifier
-JobRunnerEngine
-ClientPool

WebSocket: It is the communication component between Tedam Manager and Tedam Agent. There is a real time messaging mechanism for connection/disconnection operations. Connection status of the Tedam Agent reflected to ClientPool instantly. So that the list of agents to be selected for running jobs is always up to date.

The data to be sent to the Tedam Agent and the information generated after the test run are processed through the websocket.

RestAPI: Endpoint that is opened for both Tedam Face and Tedam Agent. The necessary data getter and setter operations are performed.
Notifier: Component that is used for to notify user or 3rd party software about the job execution results. Generic structure of the Notifier enables user to implement any kind of notification format (mail, slack, twit etc.)

JobRunnerEngine: It is generated for each SUT (System Under Test) managed by TEDAM. JobRunnerEngine is responsible for queuing and running of job and collecting the results.

ClientPool: It is the component in which the TEDAM Agents status is updated in real time through websocket. Client selection is handled by ClientPool during job execution.