Configuring the development system
Version:
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:
-
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.
-
Click
. -
In the Owning Ruleset field, enter Pega-DevOps-Foundation.
-
In the Setting Purpose field, enter RMURL.
-
Click Create and open.
-
On the Settings tab, in the Value field, enter the URL of the orchestration server. Use this format: http://hostname:port/prweb/PRRestService.
-
Click Save.
-
-
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.
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.
-
Log in to the application.
-
In the Designer Studio header, click the name of your application, and then click Definition.
-
In the Built-on application section, click Add application.
-
In the Name field, press the Down arrow key and select the name of the target application.
-
In the Version field, press the Down arrow key and select the target application version.
-
Click Save.
-
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.
-
In the Designer Studio header, click the name of your application, and then click Definition.
-
In the Application rulesets section, click the Open icon for each ruleset that you want to lock.
-
Click Lock and Save.
-
-
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.
-
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.
-
Create a new Pega repository type. For more information, see Creating a repository connection.
-
In the Host ID field, enter the URL of the development system.
-
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).
-