Comply with your data storage policy by configuring Pega Robot Manager to run a repository for package binary
files.
As a system administrator or developer, connect your application to a
repository for hosting automation package binaries. Then, configure Robot Manager to point to that repository by specializing an instance
of the pyPackageBinariesRepository rule in your application
layer.
Before you begin: Create an instance of a Repository rule that points to the
file storage system in which you want to store automation package binaries. For more
information, see Creating a repository.
For example, to make your solution compatible with the cloud, you can configure a
JFrog repository to store your package data.
In Dev Studio, click RecordsSysAdminApplication Settings.
Select the pyPackageBinariesRepository application
settings rule, as shown in the following example:
Accessing the pyPackageBinariesRepository rule
Specialize the rule in your application layer:
Click Save As.
In the Context section, specify the owning
ruleset.
Click Create and open.
In the Value per production level section, populate a
Production Level field with the name of the remote
repository for storing automation package binaries, as shown in the following
example:
Connecting Pega Robot Manager to a reposiory for automation package
binaries
Confirm your settings by clicking Save.
In the RuntimeConfig.xml file, set the
UseRobotManagerPackageServer attribute to
true, as shown in the following example:
See the following example for reference:Configuring Pega Robot Manager to control the automation package
repositoryFor more information, see Managing robot configuration remotely.
What to do next: Optionally, learn more about the folder tree that Robot Manager automatically generates in the package repository
as packages are uploaded by accessing the following article:
Previous topic
Storing robotic automation packages in Pega Robot Manager
