Creating a repository connection

Create connections between Pega Platform and repositories to provide centralized storage, versioning, and metadata support for your application artifacts.

To create a repository, your access group must have the PegaRULES:RepositoryAdministrator role.

1. In Designer Studio, click Create > SysAdmin > Repository.

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

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

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

5. Configure your repository type:

   • JFrog Artifactory

     1. In the Host ID field, enter the location of the JFrog deployment.
     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. Optional: In theSecurity 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 name field, enter the S3 bucket location where artifacts are stored.
     2. In the Root path field, enter the location of the root folder on S3.
     3. In the Access key id field, enter the access key ID that you obtained from the Cloud service vendor.
     4. In the Secret access key field, enter the secret access key that you obtained from the Cloud service vendor.

   • File system

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

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

   • Pega

     The Pega repository type is shown only if you have enabled it. For more information, see Enabling the Pega repository type.

     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. Optional. 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. Optional. 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.

6. Click Test connectivity to verify the credentials.
7. Click Save.

Open topic with navigation