Robotic processes are highly customized to suit your business's key use cases. Developers play an essential role in creating, configuring, and deploying robotic processes in Appian RPA. This page describes the steps to set up your local development environment so all components are communicating properly for efficient development.
Appian RPA's robotic processes are written in Java, so you need some knowledge of general programming and Java to develop robotic processes. We also recommend that you're familiar with the technologies and techniques most frequently used in Java programming. To manage your Java code, it's recommended to use a version control system like Git.
It is also highly recommended that you have some experience working in an integrated development environment (IDE) like Eclipse or IntelliJ or, at least, a code editor. To package and deploy robotic processes, you need some knowledge of Maven commands.
Familiarize yourself with Appian RPA's architecture to understand how components integrate and communicate with each other. To get the most out of this page, we recommend you have some knowledge of Appian RPA terms and concepts.
Each robotic processes runs under the strictest security protocols, using encrypted communications (SSL) and protecting resources by using profiles and permissions.
The following diagram shows how a developer fits into the Appian RPA ecosystem to develop and manage robotic processes.
A developer uses the Appian RPA Console to configure robotic processes and monitor the results. To execute a robotic process, the developer may also need to set up resources. To establish communication with the Console, a resource must have an agent installed and running on it. Each of these components is essential in setting up your development environment to test your robotic processes.
Learn more about the Appian RPA Console.
Learn more about how to setup and use resources.
Learn more about how to setup and use an agent.
Appian recommends the following development environment for creating robotic processes:
To properly deploy code and test robotic processes, you'll also need to access the repository and identify resources.
Appian RPA uses Maven to store robotic process artifacts. As you develop robotic process code, you'll deploy your changes to the central repository.
The repository is an essential component because the necessary dependencies to develop and operate your robotic processes are stored here. You will deploy your robotic process in this repository when it's finished, making it available for the console and enabling it to be managed or sent to the agent to run on the resource.
You can find your Maven API key from the Appian RPA Console. Click Settings > Refresh Maven Key and copy the value. Note that this is the only time you'll be able to view and copy this specific key.
Starting with this release, Appian RPA no longer uses Nexus as its default code repository. You can still use Nexus as your code repository when you upgrade to Appian 20.3. However, if you choose to use the local Appian RPA console repository, you'll need to complete a few manual steps.
In Appian RPA, you deploy, configure, and execute robotic processes on one or several resources. A resource is a computer, piece of equipment, or virtual machine in which robots can run. As you set up your development environment, it can be helpful for you to also identify the resources where you'll develop, test, and ultimately deploy your robotic processes.
Although you could use the same machine to develop and execute robotic processes, it is recommended that the resource where the robot code is written is different from the resource that the robotic process runs on. The robotic process interacts with the keyboard, mouse, and clipboard in the same way as a human user would, making it more difficult to debug the robot if it runs on the development environment. Having a separate resource for testing executions allows you to observe the execution and debug from your development environment more easily.
Appian RPA is compatible with the main virtualization systems, such as Citrix, VMware or VirtualBox.
Before you get started, check that your environment is set up appropriately. Below, we'll check the Java JDK version, as well as the Maven version and its integration in Eclipse.
As already noted, regardless of what operating system runs in the machine in which your robots will execute, any environment with Java version 1.8 or higher installed will be enough for you to develop your robotic processes.
You might find that javac is not available in the Path system's environment variable. In such case, you should use the command
java --version instead, provided you have a JDK installed. Alternatively, you can navigate to the JDK installation folder and locate the javac executable file.
To check your Maven version, enter the command
This command shows information about the Maven version and what Java version you have installed, and their paths, as well as other information about the operating system.
Verify that Eclipse is properly integrated and set up with Java and Maven:
Now let's check the Maven integration in Eclipse:
It is important that the proper version (3.0 or higher) and the proper installation folder of Maven are set up. In the example above, the installation folder is /usr/share/maven.
With your environment set up and configured, you're ready to get started developing robotic processes in Appian RPA.
On This Page