There are several parameters in the platform's configuration files related to RDP sessions for launching robots that will be useful to the user:
Parameter name | Description | |
---|---|---|
rdp.isEnable |
| |
rdp.start.timer.duration | Time during which the Orchestrator will wait for the RDP session to be activated and the robot execution system to be successfully launched. The time is specified in milliseconds. If the time is up but the Orchestrator has not received the desired response, the robot launch on that account will be canceled This time limit is necessary for cases where, due to unknown errors, the Orchestrator does not receive a response back, and as a result, the robot launch freezes without completion | |
rdp.stop.timer.duration | The amount of time Orchestrator will wait for new robot launch requests on this host account before terminating an RDP session on it. The time is specified in milliseconds
This parameter is useful if there is little time between the end of one robot and the start of another - you don't have to waste time unnecessarily terminating the RDP session and re-launching it for the second robot, but just use the previously launched session instead | |
rdp.screen.resolution | The screen resolution that will be set on the host account when an RDP session is connected on it |
All parameters can be configured in the "rms2.properties" file located on the server side of the platform.