Skip to main content

Storing robotic automation packages in Pega Robot Manager

Suggest edit Updated on October 7, 2021

Make your robotic solution fully compatible with your data storage policy by configuring Pega Robot Manager to use a repository for package binary files.

A repository for automation deployment files (packages) eliminates the need to maintain a local Pega Package Server.

When you publish a package from Pega Robot Studio, Pega Robot Studio sends the package and the associated metadata to Robot Manager, which forwards the package files to the repository of your choice. That repository can be local or cloud-based. When Pega Robot Runtime starts, it receives the package files from the repository by calling Robot Manager.

Important: You can delete a package from Robot Manager. That operation also removes the package from the target repository. For more information, see Deleting a package.

What to do next: Configure a repository for package data and discover more about the repository structure by accessing the following articles:
  1. Configuring a repository for package data

    Comply with your data storage policy by configuring Pega Robot Manager to run a repository for package binary files.

  2. Package repository data model

    Learn more about the topology of the package repository that is controlled by Pega Robot Manager. That repository provides an intuitive folder tree for browsing and managing your package data.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us