# mulesoft RPA Bot - Full Documentation --- product: RPA Bot version: 1.6 --- # Configuring RPA Bot > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the RPA Bot Configurator application to change the default settings of a bot. To find the application navigate to **MuleSoft** > **RPA Bot Configurator**. The RPA Bot Configuration tool has the following configuration panels: - [Common](#common-settings) - [Proxy](#proxy-settings) - [Session Settings](#session-settings) - [Secure Session Settings](#secure-session) - [System Settings](#system-settings) - [Session Monitoring](#session-monitoring) - [Diagnostic Infos](#diagnostic-infos) > [!TIP] After saving your changes, restart the RPA Bot Service for the changes to take effect. ## Common Settings ![The RPA Bot Configurator application showing the Common settings panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-common.png) - **RPA Bot ID** ID generated during the installation process of RPA Bot, which identifies the bot in RPA Manager (even if the IP or MAC-Address changes). If you need a new ID, uninstall and then reinstall RPA Bot. - **RPA Manager to connect** The URL address of the RPA Manager instance the bot connects to. There is no default setting. - **API Key** The API key entered during the installation of the robot. You can change this setting. - **TEST CONNECTION** Click **TEST CONNECTION** to verify that the bot can establish a connection to RPA Manager. - **Alive interval** Time interval in milliseconds after which the bot connects to the RPA Manager to show that it is still alive. - **Check interval** Time interval in milliseconds after which the bot connects to RPA Manager and checks for provided packages to collect (such as scheduling tasks or activities). - **Cleanup activities on start** Select this option to delete the activities that are no longer assigned to a configuration but are still stored locally in the bot. - **Cleanup runtime packages on next start** Select this option to delete all runtime packages that are stored locally in the bot. The process activities retrieve the required runtime packages from the RPA Manager on the next run. After the runtime packages are deleted, the Bot Configurator deselects this setting. - **Maximum number of sessions** Set the maximum number of Secure Sessions that the bot can use. Enabling this setting limits the number of Secure Sessions, but doesn’t overwrite the same setting in RPA Manager Bot Management. ## Proxy Settings ![The RPA Bot Configurator application showing the Proxy settings panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-proxy.png) - **Proxy** The bot and RPA Manager communicate through the HTTP protocol at Port 80. If you connect to the internet through a proxy server, enter the proxy address in this field Format: `http://:`, for example: `http://myproxy.de:881`. ## Session Settings To specify a default user account that the RPA Bot uses to log in to the session and run processes on the computer, enter the credentials here. When users create a process run configuration in RPA Manager, they can choose this user or specify another there. ![The RPA Bot Configurator application showing the Secure Session settings panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-session-settings.png) - **Default Session User** To specify a default user account that the RPA Bot uses to log in to the session and run processes on the computer, enter the credentials here. If the environment of the computer the bot is installed on is embedded in a domain and you want to use a local user, write the user name as follows: `.\username`. For domain users, use the following form: `mydomain\username`. - **Send images for process streaming** Select this checkbox to transfer screenshots used for process streaming to RPA Manager. Deselect the checkbox if not everyone on the process team is allowed to view the processed data. For the Process Streaming to work, the usage of the Windows Taskbar must be enabled in the process-run configuration, too. ## Secure Session Settings ![The RPA Bot Configurator application showing the Secure Session Settings panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-secure-session.png) - **Activate certificate based login on SSL enabled terminal servers** Enable this option if you are installing the bot on a terminal server that only allows SSL protected RDP connections. - **Handle “Always prompt client for password” option** Enable this option if the `fPromptForPassword` Group Policy is enabled. The `fPromptForPassword` policy requests the password to be entered a second time when the RDP session is established. Some machines request the second password entry via a popup dialog. Other machines embed the prompt into the same screen, like the regular Windows login. - **Handle a “Custom LogonMessage”** Enable this option if you are prompted with a custom logon message when connecting to your system via RDP. Some systems show a custom logon message screen after logging into an RDP session, and this message has to be acknowledged by pressing a button. - **Allow usage of SmartCards inside Secure Sessions** Enables authentication via SmartCard within the Secure Session. - **Use the Credential Security Support Provider (CredSSP) for authentication** Select this option to use the CredSSP for authentication. - **Use alternative RDP handling for Secure Session login (recommended for Windows 10 and Windows Server 2016)** If the group policy _Always prompt for password upon connection_ is enabled, the password must be entered twice when logging into the RDP session. This might prevent the Secure Session from running smoothly, especially on Windows 2010 and Windows Server 2016. If this is the case, activate this option so that the credentials can be entered correctly in the second query. In this context, ensure that you have selected the option **Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)** in the Windows system properties. - **Session connection timeout** With an established connection, the session connection timeout defines the time that a call can remain unanswered before the bot cancels the call. - **Retries in timeout** Defines how often the bot tries to reach a started StSec via session connection. - **Seconds to wait between each try** The wait time specifies how long the bot waits between every individual attempt. ### Test Settings Optionally, click **TEST SETTINGS** to test your connection settings for the Secure Session. In the **TEST SETTINGS** dialog, enter test parameters for the Secure Session. ![The RPA Bot Configurator application showing the Test Settings window](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-test-settings.png) If you click **TEST**, the application starts a non-operational Secure Session in which you can see a list of parameters for the Secure Session. Click **Logout** to end this non-operational Secure Session. > [!NOTE] On single session systems, such as Windows 10 and 11, a message shows that the test may > fail if no further sessions are available. ## Session Monitoring ![The RPA Bot Configurator application showing the Session Monitoring settings panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-session-monitoring.png) - **Take Analysis Pictures** Specifies whether the bot takes screenshots while executing a process. - **Analyze Pictures Count** Specifies the number of screenshots to take. - **Analyze Picture Seconds** Defines the interval at which the bot takes screenshots. - **Analysis package on OK** Sends analysis packages if the Activity Workflow terminates with OK. - **Custom Analysis package folder of failed workflows** Define a folder location for the analysis packages of failed workflow runs. - **Custom Analysis package folder of succeeded workflows** Define a folder location for the analysis packages of successful workflow runs. ## System Settings ![The RPA Bot configurator application showing the System Settings panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-system-settings.png) This panel indicates whether a terminal server software is installed and displays a list of all known registry keys with their current value. The panel also includes a `Bot Service State` entry, which shows the current RPA Bot Windows Service state and configuration. If a setting prevents RPA Bot from operating correctly, it is marked with a warning icon. You can fix the registry key settings directly from the panel by doing the following: 1. Right-click the warning icon. 2. Click **Fix it**. A confirmation pop-up displays to indicate the setting was fixed successfully. If the fix fails, access documentation from the panel for information about why the fix failed and how to resolve it. To fix the terminal server setting, which is needed for Secure Sessions, ensure the software is installed. Visit [Hardware and Software Requirements](https://docs.mulesoft.com/rpa-bot/1.6/hardware-software-requirements) for more information about requirements for Secure Sessions. ## Diagnostic Infos The diagnostics panel shows important runtime information to help you identify current and potential problems with RPA Bot. The panel also shows which Windows session is currently being used by which secure session. Some values cannot be determined when RPA Bot is not running. ![The RPA Bot Configurator application showing the Diagnostic Infos panel](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-diagnostic-infos.png) - **Bot Service state** Shows the current status of the Windows service. - **Bot start time (local time)** Shows the last bot start time and running time. The time is shown in the time zone of the current RPA Bot user. - **Process execution count** Shows the number of processes that executed successfully since the last bot start time. - **Workflow execution count** Shows the number of workflows executed successfully since the last bot start time. - **Average Secure session count** Shows the average number of secure sessions at the same time, the bot needs to run the processes since it was last started. - **Max. Secure session count** Shows the maximum number of secure sessions at the same time the bot needs to run the processes since it was last started. - **Last Time used to established a new secure session** Shows the time a secure session was last created. If a secure session has not been created since the last bot start time, then a value is not shown. - **Session creation errors occurred in the last hour** Shows the number of errors that occurred in the last hour when creating a secure session. - **Session creation errors occurred in the last day** Shows the number of errors that occurred in the last 24 hours when creating a secure session. - **Connection errors occurred in the last hour** Shows the number of errors that occurred in the last hour when establishing a connection to RPA Manager. - **Connection errors occurred in the last day** Shows the number of errors that occurred in the last 24 hours when establishing a connection to RPA Manager. - **Last average of download speed** Shows the average download speed when RPA Bot is downloading the last runtime package. This is an indicator of the connection quality between RPA Bot and RPA Manager. If no runtime packages have been downloaded since the last bot start time, then a value is not shown. - **Time used for RPA Manager connection test** When you refresh the Diagnostic Infos panel, RPA Bot runs a connection test to RPA Manager. This field shows the amount of time RPA Bot used to test the connection to RPA Manager. This is an indicator of the connection quality between RPA Bot and RPA Manager. - **Temp folder size** Shows the current size of the files in the Bot Temp folder (`C:\ProgramData\Mulesoft\RPABot\temp`) on disk. - **Warnings count** Shows the number of warnings that have occurred in the bot since the last bot start, the last hour, and the last 24 hours. - **Errors count** Shows the number of errors that have occurred in the bot since the last bot start, the last hour, and the last 24 hours. - **Fatal count** Shows the number of fatal errors that have occurred in the bot since the last bot start, the last hour, and the last 24 hours. ## Editing RPA Bot Configurator While Recording When a change is made to the RPA Bot Configurator while a recording is in progress, the configurator must be restarted for the changes to take effect. Clicking **OK** in the RPA Bot Configurator to save your changes opens the **Restart RPA Bot Service** dialog, which lets you decide if you want to defer or force the restart, restart manually, or continue configuring your changes. > [!NOTE] If a deployed process is running on the bot instance, the process may be canceled if RPA > Bot is restarted as a result of a change made to the RPA Bot Configurator. ![The RPA Bot Configurator application showing the Restart RPA Bot Service dialog](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-configurator-restart-service.png) ## See Also - [RPA Manager - Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview#getting-started) - [RPA Manager - Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) - [RPA Manager - Streaming Processes](https://docs.mulesoft.com/rpa-manager/processmonitoring-stream) --- product: RPA Bot version: 1.7 is-latest-version: true --- # Configuring RPA Bot > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use the RPA Bot Configurator application to change the default settings of a bot. To find the application navigate to **MuleSoft** > **RPA Bot Configurator**. The RPA Bot Configuration tool has the following configuration panels: - [Common](#common-settings) - [Proxy](#proxy-settings) - [Session Settings](#session-settings) - [Secure Session Settings](#secure-session) - [System Settings](#system-settings) - [Session Monitoring](#session-monitoring) - [Diagnostic Infos](#diagnostic-infos) > [!TIP] After saving your changes, restart the RPA Bot Service for the changes to take effect. ## Common Settings ![The RPA Bot Configurator application showing the Common settings panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-common.png) - **RPA Bot ID** ID generated during the installation process of RPA Bot, which identifies the bot in RPA Manager (even if the IP or MAC-Address changes). If you need a new ID, uninstall and then reinstall RPA Bot. - **RPA Manager to connect** The URL address of the RPA Manager instance the bot connects to. There is no default setting. - **API Key** The API key entered during the installation of the robot. You can change this setting. - **TEST CONNECTION** Click **TEST CONNECTION** to verify that the bot can establish a connection to RPA Manager. - **Alive interval** Time interval in milliseconds after which the bot connects to the RPA Manager to show that it is still alive. - **Check interval** Time interval in milliseconds after which the bot connects to RPA Manager and checks for provided packages to collect (such as scheduling tasks or activities). - **Cleanup activities on start** Select this option to delete the activities that are no longer assigned to a configuration but are still stored locally in the bot. - **Cleanup runtime packages on next start** Select this option to delete all runtime packages that are stored locally in the bot. The process activities retrieve the required runtime packages from the RPA Manager on the next run. After the runtime packages are deleted, the Bot Configurator deselects this setting. - **Maximum number of sessions** Set the maximum number of Secure Sessions that the bot can use. Enabling this setting limits the number of Secure Sessions, but doesn’t overwrite the same setting in RPA Manager Bot Management. ## Proxy Settings ![The RPA Bot Configurator application showing the Proxy settings panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-proxy.png) - **Proxy** The bot and RPA Manager communicate through the HTTP protocol at Port 80. If you connect to the internet through a proxy server, enter the proxy address in this field Format: `http://:`, for example: `http://myproxy.de:881`. ## Session Settings To specify a default user account that the RPA Bot uses to log in to the session and run processes on the computer, enter the credentials here. When users create a process run configuration in RPA Manager, they can choose this user or specify another there. ![The RPA Bot Configurator application showing the Secure Session settings panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-session-settings.png) - **Default Session User** To specify a default user account that the RPA Bot uses to log in to the session and run processes on the computer, enter the credentials here. If the environment of the computer the bot is installed on is embedded in a domain and you want to use a local user, write the user name as follows: `.\username`. For domain users, use the following form: `mydomain\username`. - **Send images for process streaming** Select this checkbox to transfer screenshots used for process streaming to RPA Manager. Deselect the checkbox if not everyone on the process team is allowed to view the processed data. For the Process Streaming to work, the usage of the Windows Taskbar must be enabled in the process-run configuration, too. ## Secure Session Settings ![The RPA Bot Configurator application showing the Secure Session Settings panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-secure-session.png) - **Activate certificate based login on SSL enabled terminal servers** Enable this option if you are installing the bot on a terminal server that only allows SSL protected RDP connections. - **Handle “Always prompt client for password” option** Enable this option if the `fPromptForPassword` Group Policy is enabled. The `fPromptForPassword` policy requests the password to be entered a second time when the RDP session is established. Some machines request the second password entry via a popup dialog. Other machines embed the prompt into the same screen, like the regular Windows login. - **Handle a “Custom LogonMessage”** Enable this option if you are prompted with a custom logon message when connecting to your system via RDP. Some systems show a custom logon message screen after logging into an RDP session, and this message has to be acknowledged by pressing a button. - **Allow usage of SmartCards inside Secure Sessions** Enables authentication via SmartCard within the Secure Session. - **Use the Credential Security Support Provider (CredSSP) for authentication** Select this option to use the CredSSP for authentication. - **Use alternative RDP handling for Secure Session login (recommended for Windows 10 and Windows Server 2016)** If the group policy _Always prompt for password upon connection_ is enabled, the password must be entered twice when logging into the RDP session. This might prevent the Secure Session from running smoothly, especially on Windows 2010 and Windows Server 2016. If this is the case, activate this option so that the credentials can be entered correctly in the second query. In this context, ensure that you have selected the option **Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)** in the Windows system properties. - **Session connection timeout** With an established connection, the session connection timeout defines the time that a call can remain unanswered before the bot cancels the call. - **Retries in timeout** Defines how often the bot tries to reach a started StSec via session connection. - **Seconds to wait between each try** The wait time specifies how long the bot waits between every individual attempt. ### Test Settings Optionally, click **TEST SETTINGS** to test your connection settings for the Secure Session. In the **TEST SETTINGS** dialog, enter test parameters for the Secure Session. ![The RPA Bot Configurator application showing the Test Settings window](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-test-settings.png) If you click **TEST**, the application starts a non-operational Secure Session in which you can see a list of parameters for the Secure Session. Click **Logout** to end this non-operational Secure Session. > [!NOTE] On single session systems, such as Windows 10 and 11, a message shows that the test may > fail if no further sessions are available. ## Session Monitoring ![The RPA Bot Configurator application showing the Session Monitoring settings panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-session-monitoring.png) - **Take Analysis Pictures** Specifies whether the bot takes screenshots while executing a process. - **Analyze Pictures Count** Specifies the number of screenshots to take. - **Analyze Picture Seconds** Defines the interval at which the bot takes screenshots. - **Analysis package on OK** Sends analysis packages if the Activity Workflow terminates with OK. - **Custom Analysis package folder of failed workflows** Define a folder location for the analysis packages of failed workflow runs. - **Custom Analysis package folder of succeeded workflows** Define a folder location for the analysis packages of successful workflow runs. ## System Settings ![The RPA Bot configurator application showing the System Settings panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-system-settings.png) This panel indicates whether a terminal server software is installed and displays a list of all known registry keys with their current value. The panel also includes a `Bot Service State` entry, which shows the current RPA Bot Windows Service state and configuration. If a setting prevents RPA Bot from operating correctly, it is marked with a warning icon. You can fix the registry key settings directly from the panel by doing the following: 1. Right-click the warning icon. 2. Click **Fix it**. A confirmation pop-up displays to indicate the setting was fixed successfully. If the fix fails, access documentation from the panel for information about why the fix failed and how to resolve it. To fix the terminal server setting, which is needed for Secure Sessions, ensure the software is installed. Visit [Hardware and Software Requirements](https://docs.mulesoft.com/rpa-bot/latest/hardware-software-requirements) for more information about requirements for Secure Sessions. ## Diagnostic Infos The diagnostics panel shows important runtime information to help you identify current and potential problems with RPA Bot. The panel also shows which Windows session is currently being used by which secure session. Some values cannot be determined when RPA Bot is not running. ![The RPA Bot Configurator application showing the Diagnostic Infos panel](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-diagnostic-infos.png) - **Bot Service state** Shows the current status of the Windows service. - **Bot start time (local time)** Shows the last bot start time and running time. The time is shown in the time zone of the current RPA Bot user. - **Process execution count** Shows the number of processes that executed successfully since the last bot start time. - **Workflow execution count** Shows the number of workflows executed successfully since the last bot start time. - **Average Secure session count** Shows the average number of secure sessions at the same time, the bot needs to run the processes since it was last started. - **Max. Secure session count** Shows the maximum number of secure sessions at the same time the bot needs to run the processes since it was last started. - **Last Time used to established a new secure session** Shows the time a secure session was last created. If a secure session has not been created since the last bot start time, then a value is not shown. - **Session creation errors occurred in the last hour** Shows the number of errors that occurred in the last hour when creating a secure session. - **Session creation errors occurred in the last day** Shows the number of errors that occurred in the last 24 hours when creating a secure session. - **Connection errors occurred in the last hour** Shows the number of errors that occurred in the last hour when establishing a connection to RPA Manager. - **Connection errors occurred in the last day** Shows the number of errors that occurred in the last 24 hours when establishing a connection to RPA Manager. - **Last average of download speed** Shows the average download speed when RPA Bot is downloading the last runtime package. This is an indicator of the connection quality between RPA Bot and RPA Manager. If no runtime packages have been downloaded since the last bot start time, then a value is not shown. - **Time used for RPA Manager connection test** When you refresh the Diagnostic Infos panel, RPA Bot runs a connection test to RPA Manager. This field shows the amount of time RPA Bot used to test the connection to RPA Manager. This is an indicator of the connection quality between RPA Bot and RPA Manager. - **Temp folder size** Shows the current size of the files in the Bot Temp folder (`C:\ProgramData\Mulesoft\RPABot\temp`) on disk. - **Warnings count** Shows the number of warnings that have occurred in the bot since the last bot start, the last hour, and the last 24 hours. - **Errors count** Shows the number of errors that have occurred in the bot since the last bot start, the last hour, and the last 24 hours. - **Fatal count** Shows the number of fatal errors that have occurred in the bot since the last bot start, the last hour, and the last 24 hours. ## Editing RPA Bot Configurator While Recording When a change is made to the RPA Bot Configurator while a recording is in progress, the configurator must be restarted for the changes to take effect. Clicking **OK** in the RPA Bot Configurator to save your changes opens the **Restart RPA Bot Service** dialog, which lets you decide if you want to defer or force the restart, restart manually, or continue configuring your changes. > [!NOTE] If a deployed process is running on the bot instance, the process may be canceled if RPA > Bot is restarted as a result of a change made to the RPA Bot Configurator. ![The RPA Bot Configurator application showing the Restart RPA Bot Service dialog](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-configurator-restart-service.png) ## See Also - [RPA Manager - Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview#getting-started) - [RPA Manager - Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) - [RPA Manager - Streaming Processes](https://docs.mulesoft.com/rpa-manager/processmonitoring-stream) --- product: RPA Bot version: 1.6 --- # Hardware and Software Requirements > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before installing RPA Bot, ensure that your environment meets the minimum hardware and software requirements. ## Hardware Requirements - For optimal performance, use a dedicated computer for running the RPA Bot. - The following table shows the minimum and the recommended hardware requirements for running one process:
MinimumRecommended

Dual-core 2 GHz CPU (MMX/SSE compatible)

Dual-core 3 GHz CPU (MMX/SSE compatible)

8 GB of RAM

16 GB of RAM

30 GB of disk space

30 GB (SSD) of disk space

To run more than one process in parallel, when using Secure Sessions, you must add 2 GB of RAM plus the RAM needed to run the process for each parallel run to these recommended values. For example, to run two different processes in parallel: - Process 1 requires one GB of RAM and runs 10 times in parallel. - Process 2 requires three GB of RAM and runs five times in parallel. In this case, use the following formula to calculate that you need a computer with a minimum of 63 GB of RAM: ### Unsupported Hardware Configurations - Notebooks with Intel Graphics 520 and 530 ## Software Requirements
SoftwareRequired version

Microsoft .NET Framework

  • 4.5

  • 4.7.2

Operating System

Any of the following:

  • Windows 10 (64 bit)

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).

    • Enterprise LTSC

  • Windows 11

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).

  • Windows Server 2019

  • Windows Server 2022

### System Settings - Display resolution: - Minimum: 1280 x 1080 - Recommended: Full HD 1080p (1920 × 1080) or higher - `Custom scaling` of text and other items on the screen: 100% - `ClearType`: turned off ### Requirements for the Secure Session Technology Secure Sessions are hidden Desktop sessions that run in the background and are accessible only to the bot. An additional advantage of using Secure Sessions is that the bot can multiply itself to run several process instances in parallel. To use Secure Sessions you must ensure that all prerequisites are met and all responsible persons are informed. - You can’t use Secure Sessions with any operating system running on the Microsoft Azure Virtual Desktop Infrastructure (VDI). - The RPA Bot service runs under the `Local System` account per default. - To use another account, ensure that it has permission to run Windows services. - The RPA Bot service runs processes under user accounts on the same computer or within the same domain. - Use dedicated accounts and a user-naming scheme to differentiate between local users and domain users and between human users and bot users. - User accounts used by the bot to run processes must belong to the `Remote Desktop Users` group and must have permission to establish a local RDP session via the local loopback address 127.0.0.2. - To enable a bot to run more than one (Windows 10, Windows 11) or two (Windows Server) Secure Sessions simultaneously, ensure that a terminal server software with enough licensed users is installed on the computer where the bot is installed. The computer must have enough resources to execute several processes simultaneously: 2 GB or more RAM per session. Although other terminal server software can work, RPA has been validated with the following terminal server software: - [Microsoft Remote Desktop Services](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/overview) - [TSplus MuleSoft RPA Connector](https://www.tsplus-rpa.com/) - Before deploying a run configuration on a bot that has only one licensed Secure Session, do not disconnect the session, instead sign out the specified user. - Do not sign in to a computer where a bot with one licensed Secure Session is running a process. ### File System Permission Requirements RPA Bot needs full write access to some folders that are critical to its functioning. To avoid issues during the setup process and later RPA Bot executions, ensure that: - You install RPA Bot as an administrator If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, ensure you reinstall RPA Bot by running the setup file as an administrator. - RPA Bot has full write access to the following folders and any subfolders and files inside them: - `C:\Program Files\Mulesoft\RPABot` - `C:\ProgramData\Mulesoft\RPABot` - Your environment is not blocking the execution of any RPA process The operating system can block the execution of certain files. Ensure that all executable (`.exe`) files inside the RPA Bot home directory and its subfolders are allowed to run. ### Internet Route Requirements To communicate with RPA Manager, RPA Bot requires you to enter the following Internet route in the **RPA Manager to connect** field on the RPA Bot Configurator pop-up: - `https://[your subdomain].rpa.mulesoft.com` In addition, it is also necessary to open the internally used URL `https://*.cloudfront.net`, which is done typically by your network or security team. See [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration#common-settings) for more information about the RPA Bot Configurator pop-up. ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## See Also - [Installing RPA Bot](https://docs.mulesoft.com/rpa-bot/1.6/installation) --- product: RPA Bot version: 1.7 is-latest-version: true --- # Hardware and Software Requirements > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before installing RPA Bot, ensure that your environment meets the minimum hardware and software requirements. ## Hardware Requirements - For optimal performance, use a dedicated computer for running the RPA Bot. - The following table shows the minimum and the recommended hardware requirements for running one process:
MinimumRecommended

Dual-core 2 GHz CPU (MMX/SSE compatible)

Dual-core 3 GHz CPU (MMX/SSE compatible)

8 GB of RAM

16 GB of RAM

30 GB of disk space

30 GB (SSD) of disk space

To run more than one process in parallel, when using Secure Sessions, you must add 2 GB of RAM plus the RAM needed to run the process for each parallel run to these recommended values. For example, to run two different processes in parallel: - Process 1 requires one GB of RAM and runs 10 times in parallel. - Process 2 requires three GB of RAM and runs five times in parallel. In this case, use the following formula to calculate that you need a computer with a minimum of 63 GB of RAM: ### Unsupported Hardware Configurations - Notebooks with Intel Graphics 520 and 530 ## Software Requirements
SoftwareRequired version

Microsoft .NET Framework

  • 4.5

  • 4.7.2

Operating System

Any of the following:

  • Windows 10 (64 bit)

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).

    • Enterprise LTSC

  • Windows 11

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).

  • Windows Server 2019

  • Windows Server 2022

### System Settings - Display resolution: - Minimum: 1280 x 1080 - Recommended: Full HD 1080p (1920 × 1080) or higher - `Custom scaling` of text and other items on the screen: 100% - `ClearType`: turned off ### Requirements for the Secure Session Technology Secure Sessions are hidden Desktop sessions that run in the background and are accessible only to the bot. An additional advantage of using Secure Sessions is that the bot can multiply itself to run several process instances in parallel. To use Secure Sessions you must ensure that all prerequisites are met and all responsible persons are informed. - You can’t use Secure Sessions with any operating system running on the Microsoft Azure Virtual Desktop Infrastructure (VDI). - The RPA Bot service runs under the `Local System` account per default. - To use another account, ensure that it has permission to run Windows services. - The RPA Bot service runs processes under user accounts on the same computer or within the same domain. - Use dedicated accounts and a user-naming scheme to differentiate between local users and domain users and between human users and bot users. - User accounts used by the bot to run processes must belong to the `Remote Desktop Users` group and must have permission to establish a local RDP session via the local loopback address 127.0.0.2. - To enable a bot to run more than one (Windows 10, Windows 11) or two (Windows Server) Secure Sessions simultaneously, ensure that a terminal server software with enough licensed users is installed on the computer where the bot is installed. The computer must have enough resources to execute several processes simultaneously: 2 GB or more RAM per session. Although other terminal server software can work, RPA has been validated with the following terminal server software: - [Microsoft Remote Desktop Services](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/overview) - [TSplus MuleSoft RPA Connector](https://www.tsplus-rpa.com/) - Before deploying a run configuration on a bot that has only one licensed Secure Session, do not disconnect the session, instead sign out the specified user. - Do not sign in to a computer where a bot with one licensed Secure Session is running a process. ### File System Permission Requirements RPA Bot needs full write access to some folders that are critical to its functioning. To avoid issues during the setup process and later RPA Bot executions, ensure that: - You install RPA Bot as an administrator If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, ensure you reinstall RPA Bot by running the setup file as an administrator. - RPA Bot has full write access to the following folders and any subfolders and files inside them: - `C:\Program Files\Mulesoft\RPABot` - `C:\ProgramData\Mulesoft\RPABot` - Your environment is not blocking the execution of any RPA process The operating system can block the execution of certain files. Ensure that all executable (`.exe`) files inside the RPA Bot home directory and its subfolders are allowed to run. ### Internet Requirements RPA Bot requires a stable internet connection to poll tasks from RPA Manager. During downtime of the service or of the region where RPA Manager runs, the bot can’t receive new tasks until connectivity is reestablished. To communicate with RPA Manager, RPA Bot requires you to enter the following Internet route in the **RPA Manager to connect** field on the RPA Bot Configurator pop-up: - `https://[your subdomain].rpa.mulesoft.com` In addition, it is also necessary to open the internally used URL `https://*.cloudfront.net`, which is done typically by your network or security team. See [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration#common-settings) for more information about the RPA Bot Configurator pop-up. ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## See Also - [Installing RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/installation) --- product: RPA Bot version: 1.6 --- # Installing RPA Bot > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before installing RPA Bot, ensure that your environment meets the minimum hardware and software requirements. After downloading and installing the bot, run the RPA Bot Configurator application to configure its connection and default settings. ## Download and Install RPA Bot Follow these steps to download and install RPA Bot. If it is not possible to install the setup as an administrator, set the User Account Control setting to **Never notify**. Otherwise secure sessions cannot be established and automations will fail. 1. From the **Home** page of RPA Manager, download the latest RPA Bot installer. 2. To start the installation, right-click the setup file and choose **Run as administrator**. 3. Provide the following details: - **RPA Manager connection protocol** The protocol RPA Bot uses to connect with RPA Manager. ![The RPA Bot installer window](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-install-https.png) - **RPA Manager connection address** The RPA Manager servername or address to connect to. This is the same URL you use to access RPA Manager, for example: `https://myInstance.rpa.mulesoft.com/`. ![The RPA Bot installer window asking for the RPA Manager address to use](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-install-rpa-manager.png) - **APIKey for the bot** The API key to use for this bot. Use any of the API keys created in RPA Manager. ![The RPA Bot installer window asking for the APIKey to use](/mulesoft/current/en-us/rpa-bot/1.6/_images/bot-install-api-key.png) If you don’t have any API keys, see [Manage API Keys](https://docs.mulesoft.com/rpa-manager/botmanagement-support#manage-api-keys) for creation instructions. 4. Continue the installation process until finished and restart the system. ## See Also - [Hardware and Software Requirements](https://docs.mulesoft.com/rpa-bot/1.6/hardware-software-requirements) - [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/1.6/configuration) --- product: RPA Bot version: 1.7 is-latest-version: true --- # Installing RPA Bot > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before installing RPA Bot, ensure that your environment meets the minimum hardware and software requirements. After downloading and installing the bot, run the RPA Bot Configurator application to configure its connection and default settings. ## Download and Install RPA Bot Follow these steps to download and install RPA Bot. If it is not possible to install the setup as an administrator, set the User Account Control setting to **Never notify**. Otherwise secure sessions cannot be established and automations will fail. 1. From the **Home** page of RPA Manager, download the latest RPA Bot installer. 2. To start the installation, right-click the setup file and choose **Run as administrator**. 3. Provide the following details: - **RPA Manager connection protocol** The protocol RPA Bot uses to connect with RPA Manager. ![The RPA Bot installer window](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-install-https.png) - **RPA Manager connection address** The RPA Manager servername or address to connect to. This is the same URL you use to access RPA Manager, for example: `https://myInstance.rpa.mulesoft.com/`. ![The RPA Bot installer window asking for the RPA Manager address to use](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-install-rpa-manager.png) - **Bot Name** The display name to show in RPA Manager for this bot. - **APIKey for the bot** The API key to use for this bot. Use any of the API keys created in RPA Manager. ![The RPA Bot installer window asking for the APIKey to use](/mulesoft/current/en-us/rpa-bot/latest/_images/bot-install-api-key.png) If you don’t have any API keys, see [Manage API Keys](https://docs.mulesoft.com/rpa-manager/botmanagement-support#manage-api-keys) for creation instructions. 4. Continue the installation process until finished and restart the system. ## See Also - [Hardware and Software Requirements](https://docs.mulesoft.com/rpa-bot/latest/hardware-software-requirements) - [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration) --- product: RPA Bot version: 1.6 --- # RPA Bot Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bots are software robots that carry out any RPA processes assigned to them. To execute the processes, RPA Bots require a computer where the applications required for the processes are installed, along with execution configurations and instructions, which are the activities created in RPA Builder for each process step. The Bot Management module in RPA Manager enables you to manage your bots. Every bot is registered through an API key. After the installation, the bot connects with RPA Manager at defined intervals. You can then assign licenses and service times to the bot, deploy processes for the bot to execute, and monitor the bot’s status and the results of the process runs it carries out. ## See Also - [Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview) --- product: RPA Bot version: 1.7 is-latest-version: true --- # RPA Bot Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bots are software robots that carry out any RPA processes assigned to them. To execute the processes, RPA Bots require a computer where the applications required for the processes are installed, along with execution configurations and instructions, which are the activities created in RPA Builder for each process step. The Bot Management module in RPA Manager enables you to manage your bots. Every bot is registered through an API key. After the installation, the bot connects with RPA Manager at defined intervals. You can then assign licenses and service times to the bot, deploy processes for the bot to execute, and monitor the bot’s status and the results of the process runs it carries out. ## See Also - [Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview)