Migrating Repositories

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, described on this page.

These steps apply to any Appian RPA developer who has previously developed or deployed a robotic process in the environment. If you are a new Appian RPA developer and have not deployed a robotic process prior to this release, you don't need to complete these steps. Everything is taken care of automatically.

These steps apply only to Appian RPA customers who are migrating from Nexus to the local Appian RPA console repository. If you are continuing to use Nexus or you're a new Appian RPA customer starting with this release, you won't need to make any of the changes listed below.

What's changing?

The repository change requires some manual steps to ensure your code deployment and robotic process executions continue as expected:

This section describes the steps to complete each of these changes.

Update settings.xml

Update settings.xml to use your Appian username and an API key to authenticate with the Maven repository built into the RPA Console.

To find your API key:

  1. Go to the Appian RPA Console.
  2. Click the gear icon and click Refresh Maven Key.
  3. Copy the key that appears. Note that this is the only time you'll be able to view and copy this specific key.
  4. Include your API key in the <servers> section of the settings.xml file:
    1
    2
    3
    4
    5
    
     <server>
     <id>jidoka</id>
     <username>appian_username</username>
     <password>maven_API_key</password>
     </server>
    

See Maven Setup for more details on repository authentication.

Update pom.xml

You'll also need to update the repository URL listed in pom.xml of each robotic process:

  1. Locate the <url> element within the pom.xml file.
  2. Update the URL to point to the updated repository. If using the default repository, you can use the following example, where <mydomain> is your base environment:
    • Old: https://<mydomain>/nexus/content/repository/jidoka/
    • New: https://<mydomain>/rpa/repo
  3. Confirm the rest of the pom.xml file points to the new repo, if the old URL was listed in other spots.

Update the default repository

Administrators need to update the default repository in Appian RPA's settings:

  1. Go to the Appian RPA Console.
  2. Under the Settings tab, click Configuration.
  3. Under Tools Configuration, find the Default repository URL (/ ending) field.
  4. Leave this field blank to use the console repository. To use a Nexus repository, paste the Nexus URL here.
  5. Don't change any of the other fields in this section.
  6. Click Save tools configuration to save your changes.

Migrate your code (including workflow libraries)

Developers will need to migrate their robotic process code and workflow libraries to the console repository. The simplest way to do this is to re-deploy code after the settings.xml file has been updated to reference the new repository. The robotic process's artifacts will be pushed to the new repository so it can be referenced in the console and for each subsequent robotic process execution.

Learn more about deploying code and deploying libraries.

Update workflow libraries in the console

  1. Go the Appian RPA Console.
  2. Click the Robotic processes tab.
  3. Click Workflow libraries workflow-libraries.png in the toolbar.
  4. Click an entry in the List of workflow libraries.
  5. The entry's details appear in the Workflow library editor. Choose Console repository in the Repository menu.
  6. Click Save to save your changes.

Update the robotic process configuration

Finally, you'll need to update existing robotic processes so their configuration references the new repository:

  1. Go the Appian RPA Console.
  2. Click the Robotic processes tab to see the robotic processes you have access to.
  3. In the Actions column for a robotic process, click Configure configure-icon.
  4. At the bottom of the Robotic process configuration page, you'll find the Technical information section.
  5. Choose Console repository in the Repository menu.
  6. Click Save to save your changes.
Open in Github

On This Page

FEEDBACK