Automai Robot Manager is a service for robots (ScenarioStation or rTester) to maintain sessions active in order for the scenario images to be buffered and to prevent any connection errors during scenario playback. It can start automatically and run in background while executing processes (scenarios/scripts) without human supervision.
This service is useful when:
- The machines (Workstation/PC or Server) get restarted.
- The sessions get disconnected.
- The sessions get logged off.
- In case of locked screen sessions. (To prevent getting black screenshots)
Important: Please keep in mind that you need to enter an authorized user credential (username and password used to login to the Windows machine where Robot is installed) during the installation process, so the service can start and run.
How to use Robot Manager?
After installing the Robot Manager, it will launch automatically and "Add new session" window will display.
Click here to download Automai Robot Manager.
Once you install the application, an icon is displayed in your notification area (system tray).
Right-clicking the icon displays the Robot Manager menu.
Note: Closing the Robot Manager tray does not close the Automai Robot service.
To add a new session, click "Add new session" via the system tray or double-click Robot Manager shortcut on the desktop.
The "Add new session" will open.
Username: Enter the username of the system (Workstation or Server) where the robot is installed.
Password: Enter the system user's password
Domain: Enter the domain name if needed. This field is optional.
Screen resolution: Select display resolution for the session
Select color quality: Choose color depth for the session
Use font smoothing: Enhances text recognition. If it is checked, the Font Smoothing option over RDP connections is turned on.
Send enter key: If it is checked, the "Enter" key will be sent to the RDP window while the robot runs in the background.
Lastly, select a module used for the connection file.
If "Robot" is selected, the Automai Robot Manager will create a session if the session does not exist.
If "ScenarioBuilder" is selected, a dedicated session will be created for the purpose of creating a scenario.
Note: If "ScenarioBuilder" option is only selected, you need to specify the hostname as well.
Important: The same resolution, color quality, and font smoothing settings should be used for the ScenarioBuilder and all Robot connection files including the sessions created by SSrdpManager, so there will not be any differences between the scenario creation environment and the execution environment.
Once all the fields are filled out, click “Submit” to complete creating the connection file.
The "Connection created successfully" message will be displayed and the window will get closed.
If the connection file contains the "ScenarioBuilder" module option, an item with the session name will be added to the menu.
To connect to a session, right-click the icon on the systray and click your desired item (i.e. Open Robot1 session).
The session will open;
Through this connection, you can create scenarios.
To edit a session file, right-click the Automai Robot Manager icon on the systray and click "Manage Sessions"
The "Automai Robot Manager" window will open,
Click "Edit connection"
When you are done editing, enter the password and click “Submit” to make the changes.
To delete a session, click delete button
If your robots (ScenarioStation or rTester) are installed on workstation/PC, you need to install Robot Manager on each workstation/PC.
By default, the Robot Manager creates a session with the Automai Robot Service running if the application is installed in a Workstation/PC.
You can only use the "Robot" module if the machine is a Workstation/PC. If you select the "ScenarioBuilder" option and try to connect to the session using the Robot Manager, you will get disconnected. Therefore, if you need to connect to those machines remotely for the purpose of creating a scenario, you should install Robot Manager on a different Workstation/PC or Server and create connection files to connect to the robots ((ScenarioStation or rTester).
The keyboard might stop working very rarely while ScenarioBuilder user session is open. If this happens, try to minimize and then maximize the session window or close and reopen the session.