Skip to main content
LinkedIn
Copied!

Stage 1: Preparing your Pega Cloud development environment

After you complete the “Getting Started” steps, you are ready to migrate your application to your Pega Cloud Services environment.

Create, Export, and Import your RAP

In your on-premises system, create a RAP of your application for migration.  See Setting up and packaging your release.

Export the RAP to your on-premises file system.  Then log into your Pega Cloud Services development environment and import your RAP. 

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 script(s) manually.  Attach the script(s) to the CC.  After Pega runs the script(s), 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 in Pega Cloud with external systems (https://community.pega.com/knowledgebase/articles/pega-cloud/cloud/integrating-pega-applications-pega-cloud-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.

Testing your application in the Pega Cloud environment

Now that your application is running in your Pega Cloud development environment, begin your testing.  To ensure your application is working as expected now that it is in the cloud environment and your modernizations are complete, run your full set of regression and functional testing.  For information on testing, see Testing Your Application in the Phase 2:  Application Upgrade article.

There may be a number of changes required when moving from running the application in the on-premises setup to running in the Pega Cloud environment, including:

  • All the on-premises references to other external systems – email listeners, services, connectors, and so on – must be changed to work in your Pega Cloud Services environment. 
  • Users must have appropriate access to the applications in the Pega Cloud Services environment. 
  • If you have upgraded from an older version of Pega Platform, you must implement the latest, strongest security features.

As issues are found, they should be fixed in the development environment only. 

Test, make changes, and retest until your developers feel the application runs smoothly.  As described in the Deployment Manager documentation, be sure to gather all your changes in a RuleSet or branch. 

Continue this process until the application is running smoothly in the development environment.

Create test data to use in the Development environment.  If you have existing test data that you would like to use in the Development environment, use the Work Packaging wizard to move the data.  This process is very similar to using a RAP file to move application rules.  For more information, see:  Creating a product rule of test case data by using the Package Work wizard

 

Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us