In Appian RPA, you'll use your Appian username and an API key to authenticate with the Maven repository built into the RPA Console. If the robotic process needs any dependency that is neither public nor Appian RPA's, such as a utility library, this dependency should be within the dependencies repository, since the platform resolves them in the following order: In this example, replace repo_url with the real URL of the Maven repository included in your Appian RPA installation. jidoka-repo jidoka repo_url true true jidoka repo_url true true training repo_url default You'll need the path to your Console repository.

The repositories don't need to be separate.

one to deploy the binaries of the robotic processes you develop.one to have access to the Appian RPA API.You need to configure the Maven repositories for Appian RPA to work properly. In this section, we describe what each part of the code does and provide examples for how this file should appear. Configure MavenĪfter you download Maven and confirm it's the correct version, configure the settings.xml file to work with Appian RPA. Appian recommends adding the bin folder to the Path system variable, so that the Maven command can be executed from any directory on the computer.Īfter you download and unzip the Maven file, use the command mvn -version in the terminal to check your installed version of Maven. The only thing to do is unzip it in the desired folder on your machine. We recommend downloading the ZIP file containing the binaries. Maven is a free software that developers must have installed on their Appian RPA development machine. But if you prefer to set up Maven on your own, you can use this page to guide you through that process. Remember that by using the Configurator, Maven configuration (including the settings.xml) is done automatically. This page discusses how to set up Maven to develop and deploy robotic processes. You'll need to set up your local development environment to build, modify, and debug your robotic processes.

Maven settings xml