Creating a repository connection

In Designer Studio, click Create > SysAdmin > Repository.

Enter a short description of the repository and the repository name and click Create and open.

In the Definition tab, click Select and select the repository type.

Select the Supported artifacts to filter the lists returned from the repository and control the items that are stored in the repository.

Configure your repository type:

• JFrog Artifactory

  1. In the Host ID field, enter the location of the JFrog deployment.
     Note: Do not include any text after the host address that starts with /artfiactory. For example, if a JFrog deployment is accessed through https://10.35.324.324:8081/artifactory, the value entered in the Host ID field must be https://10.35.324.324:8081.
  2. In the Repository key field, enter the root location on the JFrog server under which all artifacts are stored.
  3. In the Authentication profile field, specify Basic.
  4. In the Security section, configure security.
     • In the Secure Protocol list, select the lowest level of security that can be used. If this minimum level of security is not available, the repository call fails with an error message.
     • In the Truststore field, select or create a truststore record that contains the server certificate to use in the TLS/SSL handshake.
     • In the Keystore field, select or create a keystore record that stores the Pega Platform client's private/public key pair that is used by the server to authenticate the client.

• Amazon S3

  1. In the Bucket field, enter the S3 bucket location where artifacts are stored.
  2. In the Authentication profile field, enter the name of the authentication profile to connect to the repository. To create an authentication profile, click the target icon to the right of the Authentication profile field.
     Note: Do not select the Provide secret access key by reference in clear text check box when creating an authentication profile for a repository. This check box is only used when entering Global Resource Settings, and Global Resource Settings are not supported for repositories.
  3. In the Root path field, enter the location of the root folder on S3.

• File system

  1. In the Resource path field, enter the path under which artifacts are stored on a file system.

  Note: Each node's operating system must detect the resource path in order to import and export artifacts.

• Microsoft Azure

  1. In the Container field, enter the name of the container registry.
  2. In the Authentication profile field, enter or select the authentication profile to connect to the Azure repository. To create an authentication profile, click the target icon to the right of the Authentication profile field.
  3. In the Root path field, enter the location of the root folder in Azure.

• Pega

  Note: The Pega repository type is shown only if you have enabled it. For more information, see Enabling the Pega repository type.
  Note: Do not use Pega repositories if you are using Deployment Manager with multiple pipelines per application version. You receive an error and cannot publish the branch into the application, because you cannot select the pipeline into which you want to publish and merge branches. Instead, use the Merge Branches wizard to start pipelines. For more information, see Submitting a branch into a pipeline.
  1. Host ID — The location of the Pega node. It must start with http:// or https:// and must end with PRRestService. For example: http://10.1.5.207:8181/prweb/PRRestService
  2. Use authentication — Specify whether the repository authenticates the user.
     • Authentication Profile — Specify the authentication profile. If there is no authentication profile, the username must have PRPC:Administrators as an access group.
  3. Security section
     • Secure protocol — Select the lowest level of security that can be used. If this minimum level of security is not available, the repository call fails with an error message.
     • Truststore — Select or create a Truststore record that contains the server certificate to use in the TLS/SSL handshake.
     • Keystore — Select or create a Keystore record that stores the Pega Platform client's private/public key pair that is used by the server to authenticate the client.