|This content applies solely to Appian RPA, which must be purchased separately from the Appian base platform.|
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 processes.
See System Requirements for the Appian platform.
A resource is the physical or virtual machine where a robotic process executes. At a minimum, resources must have the following configuration:
Additionally, Java 8 or higher must be installed on the resource to run robotic processes. 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.
These requirements are our minimum recommendation to ensure the resource can adequately handle the robotic process execution and interaction with programs and applications on the resource. The agent, which connects the resource to the RPA console, doesn't require significant memory in order to operate.
Make sure that any firewalls have been configured to allow HTTPS/443 traffic from the Appian RPA agents running on your resources to your Appian Cloud site domain. Agents must be able to connect to your Appian Cloud site in order to run robotic processes.
If you customize the domain of your Appian Cloud site, you will need to 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, customers will need to use a certificate issued by a public CA.
Visit Appian Community to learn how to configure a custom domain for your Appian Cloud site.
Appian recommends the following development environment for extending robotic processes via workflow libraries or custom code:
You may be able to use MySQL or MariaDB with Appian RPA. New sites come with MariaDB enabled by default.
Refer to the table below for specific guidelines on which databases are supported for your Appian and Appian RPA versions:
|20.1||Supported for all Appian RPA versions||Unsupported|
|20.2||Supported for all Appian RPA versions||Unsupported|
|20.3||Supported for all Appian RPA versions||Supported for Appian RPA 7.2+|
|20.4||Supported for Appian RPA 7.3+||Supported for Appian RPA 7.3+|
|21.1+||Supported for Appian RPA 7.5+||Supported for Appian RPA 7.5+|
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 its 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.
On This Page