Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Creating repositories on the orchestration server and candidate systems

Updated on April 5, 2022

If you are using Deployment Manager on premises, create repositories on the orchestration server and all candidate systems to move your application between all the systems in the pipeline. You can use a supported repository type that is provided in Pega Platform, or you can create a custom repository type.

If you are using Deployment Manager on Pega Cloud Services, default repositories, named "pegacloudcustomerroot" for both the development and production repositories, are provided. If you want to use repositories other than the ones provided, you can create your own.

For more information about creating a supported repository, see Creating a repository.

For more information about creating a custom repository type, see Creating and using custom repository types for Deployment Manager.

When you create repositories, note the following information:

  • You cannot use the Pega repository type to store application artifacts for the following reasons:
    • The Pega repository type points to the temporary folder where the Pega Platform node that is associated with Deployment Manager stores caches. This node might not be persistent.
    • This repository type is suitable onlyfor single node deployments. In multinode deployments, each time a requestor is authenticated, the requestor could be in a different node, and published artifacts are not visible to the repository.
    • At most companies, the security practice is that lower environments should not connect to higher environments. Using a Pega repository typically means that a lower environment can access a higher environment.

      You can only use Pega type repositories if are rebasing your development system to obtain the most recently committed rulesets after merging them.

      You can use file system type repositories if you do not want to use proprietary repositories such as Amazon s3 or JFrog Artifactory.

  • You cannot use the defaultstore repository type to host artifacts or product archives for the production applications. It is a system-managed file system repository; it points to the temporary folder where the Pega Platform node that is associated with Deployment Manager stores caches.
  • Ensure that each repository has the same name on all systems.
  • When you create JFrog Artifactory repositories, ensure that you create a Generic package type in JFrog Artifactory. Also, when you create the authentication profile for the repository on Pega Platform, you must select the Preemptive authentication check box.

After you configure a pipeline, you can verify that the repository connects to the URL of the development and production repositories by clicking Test Connectivity on the Repository rule form.

  • Previous topic Configuring candidate systems
  • Next topic Configuring the development system for branch-based development

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