Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring access to an automation repository

Updated on January 31, 2022

Configure access to an automation repository that you can share between your Pega Platform environment and the Pega Robot Manager environment. Use this automation repository to store the automation package archives that are generated in your development environment.

Before you begin: The Pega Robotic Automation Package Server stores robotic automation deployment packages that are generated as binary files from Pega Robot Studio. The automation repository stores the component that the Pega development server generates.
  1. In Dev Studio, create a new repository instance:
    1. In the header of Dev Studio, click CreateSysAdminRepository.
    2. Create a repository record. For more information, see Creating a repository.
    3. Specify an authentication profile, and then test connectivity with the repository by clicking Test connection.
  2. Search for the pegarobotics/AutomationPackageRepository instance, and then update the value to reference the identifier of the new repository record.
  3. In Dev Studio for the application that hosts Pega Robot Manager 8.5.1 or later, repeat steps 1 through 2.
    Both your Pega Platform environment server and the Pega Robot Manager instance must point to the same repository.
Result: The Pega environments that host your development activities and Pega Robot Manager deployments now have access to the binary repository.
What to do next: Configure Pega Robot Manager. For more information, see Configuring the Pega Robot Manager host server and authentication profile.
  • Previous topic Verifying automation repository configuration
  • Next topic Configuring the Pega Robot Manager host server and authentication profile

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us