Configuring the Robotic Automation Client Retry Mechanism
The client retry mechanism enables the robot to re-send the execution status in a situation where the connection to the ActiveMQ is lost. By default, Robotic Automation Clients are configured to work with the client retry mechanism. The configurations that allow you to set the number of retries and the interval between retries are also set to a default setting (however, these configurations are optional).
You can configure the robot retry mechanism settings manually through the RTClient.exe.config configuration file. The path of the configuration file can exist in two different places depending on whether the Robotic Automation Client has run at least once before:
Configuration file location: %appdata%\Roaming\Nice_Systems\Real-Time
First time run: If the path above does not exist, then this is the first time the Robotic Automation Client has run and the configuration file will be located in the root folder, for example C:\Program Files\NICE Systems\Real-Time Client
To configure the robot retry mechanism using the configuration file:
1. | Open the RTClient.exe.config configuration file. |
2. | Locate the following configurations, change their default settings and save the configuration file. |
Configuration |
Description |
Default Setting |
Min - Max Settings |
Connection Lost Interval |
The interval (in seconds) between connection attempts |
60 seconds |
1 - 65535 |
Connection Lost Number of Retries |
The number of times the robot will attempt to run when the connection to the ActiveMQ is lost |
10 attempts |
1 - 65535 |
When done, continue with Creating an Async Real-Time Client Invoker .