After you configure the orchestration server and all your candidate systems, configure additional settings so that you can create pipelines if you are using branches in a distributed or non-distributed branch-based environment.

To configure the development system, complete the following steps:

1. On the development system (in nondistributed environment) or the main development system (in a distributed environment), create a dynamic system setting to define the URL of the orchestration server, even if the orchestration server and the development system are the same system.

   1. Click CreateRecordsSysAdminDynamic System Settings.

   2. In the Owning Ruleset field, enter Pega-DevOps-Foundation.

   3. In the Setting Purpose field, enter RMURL.

   4. Click Create and open.

   5. On the Settings tab, in the Value field, enter the URL of the orchestration server. Use this format: http://hostname:port/prweb/PRRestService.

   6. Click Save.

2. On either the development system (in a non-distributed environment) or the remote development system (in a distributed environment), use the New Application wizard to create a new development application that developers will log in to.

   This application allows development teams to maintain a list of development branches without modifying the definition of the target application.

3. On either the development system or remote development system, add the target application of the pipeline as a built-on application layer of the development application.

   1. Log in to the application.

   2. In the Designer Studio header, click the name of your application, and then click Definition.

   3. In the Built-on application section, click Add application.

   4. In the Name field, press the Down arrow key and select the name of the target application.

   5. In the Version field, press the Down arrow key and select the target application version.

   6. Click Save.

4. On either the development system or remote development system, lock the application rulesets to prevent developers from making changes to rules after branches have been merged.

   1. In the Designer Studio header, click the name of your application, and then click Definition.

   2. In the Application rulesets section, click the Open icon for each ruleset that you want to lock.

   3. Click Lock and Save.

5. To publish branches to a development system to start a branch to merge, configure a Pega repository.

   It is recommended that you merge branches by using the Merge Branch wizard. However, you can publish a branch to the remote development system to start a deployment. Publishing a branch when you have multiple pipelines per application is not supported.

   1. On either the development system or remote development system, in Designer Studio, enable Pega repository types.

      For more information, see Enabling the Pega repository type.

   2. Create a new Pega repository type. For more information, see Creating a repository connection.

   3. In the Host ID field, enter the URL of the development system.

   4. Ensure that the default access group of the operator that is configured for the authentication profile of this repository points to the pipeline application on the development system (in a nondistributed environment) or source development system (in a distributed environment).