Skip to main content


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

Configuring a repository to ingest customer data

Updated on August 3, 2022

This content applies only to Pega Cloud environments

Configure a repository for storing the manifest file and data files that you want to ingest into your Pega Customer Decision Hub.

  • If your system is deployed in a Pega Cloud services environment, configure your SFTP application to point to your S3 file repository as the root directory for file destination paths.
    The Pega Cloud services team defines the S3 file repository for your system in advance. For more information, see .
  • If your system is deployed in a third-party cloud, perform the following actions:
    1. Create a repository.
      For instructions, see Creating a repository.
      Note:

      If the repository that you create is to be shared across environments, you must manually update the root path to identify the environment. For example, if the same repository is to be shared by the development and QA environments:

      • Create folders named Dev and QA in the SFTP root folder.
      • Update the root path in the repository rule.

      The following figure shows how a Dev folder is defined as the root path for the repository in the QA environment, for non-Pega Cloud implementations:

      Sample repository configuration with a root path configured to Dev folder
      Repository configuration window in Dev Studio with the Root path field set to Dev
    2. Configure your SFTP application to point to your S3 file repository as the root directory for file destination paths.

    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.

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

    Close Deprecation Notice
    Contact us