Skip to main content


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

Migrate Application from Source Prod Environment

Updated on November 21, 2022

+

This content applies to On-premises, Client-managed cloud and Pega Cloud environments

Create, Export, and Import your RAP

In your source system, create a RAP of your production application or pre-prod application for migration.  Use your source production application or as close to your existing production application as possible.  

Export the RAP to your on-premises file system.  Then log into your Pega Cloud development environment and import your RAP.  Your rulesets are updated to the target GA version upon import.

For more information, see:

Best Practices When Using RAP Files

When using the Import Wizard in Dev Studio to import a RAP file, the default maximum file size is 1 GB.  If your RAP file is larger than 1 GB, create more than one file, each of which is smaller than 1 GB.  

When importing more than one RAP file, any rules that have dependencies on other rules must be imported after the rules on which they depend.

If the Pega database schema has been modified (such as by adding additional columns or other custom database objects) the schema in the Pega Cloud environment must be modified to match it before importing the RAP file.  Raise a Cloud Change ticket (CC) to execute the custom DDL scripts manually.  Attach the scripts to the CC.  After Pega runs the scripts, the RAP file can be imported into the Pega Cloud environment without errors.

Before importing the RAP file, set the AutoDBSchemaChanges dynamic system setting to True to enable schema changes at the system level.

  1. In Dev Studio, search for AutoDBSchemaChanges.
  2. In the dialog box that appears for the search results, click AutoDBSchemaChanges.
  3. On the Settings tab, in the Value field, enter true.
  4. Click Save.

Pega Cloud uses a PostgreSQL database.  If you have converted from another type of database, do not apply the DDL when importing the RAP file.

If the RAP file contains rules (such as Connect-SQL) that connect to an external database, exclude the database rules from the RAP file.  Create the database rules manually, and reconfigure them, after importing the rest of the RAP file.

If the RAP file contains rules that connect to external sources other than databases, there are two basic options for how to import the files without getting errors:

  1. Establish a connection to the external source. After the connection is established successfully, import the rules related to the connection to the external source.  For more information about each specific type of connection see: Integrating Pega applications with external systems
  2. Exclude the connection rules from the RAP file.  Create them manually, and reconfigure them, after importing the rest of the RAP file.

 

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