Appian RPA robotic processes are powered by Java code contained in a central repository called Nexus. As you create or modify libraries, you'll need to deploy your changes to Nexus for the updates to appear in the Appian RPA Console. This page describes the steps you need to take to deploy code to Nexus.
Administrators can find Nexus configuration settings through the Appian RPA Console.
Depending on your organization's governance, you can set up additional Nexus users to correspond with Appian RPA developer accounts. Alternatively, you can set up a single account for all developers to use to authenticate with Nexus. Note that Nexus credentials are stored locally in a developer's IDE, not within Appian RPA.
For a given method or library, you'll need to deploy the code's binary file to Nexus in order for updates to appear in the console.
When you're ready to deploy, you'll need to compile, package and deploy the Maven project as robot binaries, using the utilities provided by Maven and Eclipse.
We are going to create a "Maven Build" configuration:
If you're using IntelliJ, click Clean and then click deploy in the Maven menu to deploy the changes. Maven will auto-push to the repository using the credentials stored in your settings.xml file.
Note: If you prefer, you can deploy using the command line. Navigate to your robotic process folder and run the command
mvn clean deploy to push the binaries.
On This Page