| The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply. |
This page describes the recommended minimum configurations for running Appian RPA, as well as other considerations to make sure your environment is well-suited to successfully execute robotic tasks.
See System Requirements for the Appian platform.
A host machine is the physical or virtual machine where a robotic task executes. At a minimum, host machines must have the following configuration:
Additionally, Java 8 must be installed on the host machine to run robotic tasks. When choosing which Java version to install, ensure to choose either 32-bit or 64-bit so it is the same as the version your operating system is using.
Note: These requirements are our minimum recommendation to ensure the host machine can adequately handle the robotic task execution and interaction with programs and applications on the host machine. The agent, which connects the host machine to the RPA console, doesn't require significant memory in order to operate.
Make sure any firewalls are configured to allow HTTPS/443 traffic from the Appian RPA agents running on your host machines to your Appian Cloud site domain. Agents must be able to connect to your Appian Cloud site in order to run robotic tasks.
If you customize the domain of your Appian Cloud site, you must provide signed certificates issued by a public Certificate Authority (CA) for Appian RPA to work properly. If you use a signed certificate issued by a private CA, Appian RPA breaks and throws TLS/SSL exceptions.
Appian Cloud doesn't impose restrictions on whether to use public or private certificates. However, RPA customers must use a certificate issued by a public CA.
Learn how to configure a custom domain for your Appian Cloud site.
Appian recommends the following development environment for extending robotic tasks via workflow libraries or custom code:
The host machine requires a web browser with a graphical interface (GUI) for any browser actions. Headless browsers aren't supported.
You may be able to use MySQL or MariaDB with Appian RPA. New sites come with MariaDB enabled by default.
If you are a self-managed customer using RPA on Appian Kubernetes, you may only use Maria DB.
Self-Managed RPA customers using Appian on Kubernetes need to bring their own MariaDB for RPA
Visit System Requirements to learn more about which databases are supported for your version of Appian.
Appian RPA is a capability of the Appian platform, but Appian RPA releases are independent from the rest of the platform. This release process allows for more rapid development so you get access to new features, bug fixes, and improvements faster. Some of these updates may rely on feature availability in the Appian platform. Therefore, if you're using an older version of the Appian platform, Appian RPA may not be able to take advantage of all the latest capabilities.
Appian RPA is backwards compatible with the Appian platform. In other words, each new Appian RPA release works for available versions of Appian back to 20.1.
Appian RPA System Requirements
