Skip to main content


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

Packaging an application

Updated on December 22, 2021

To migrate a new application to a different environment, you must package the application before you can import it to the new environment.

Pega Government Platform Implementation Guide Pega Government Platform Implementation Guide Pega Government Platform Implementation Guide Pega Government Platform Implementation Guide

Merging application changes

If you develop your application features in separate branches, use the Merge Branches wizard to merge the branches before you package the application. The wizard shows any merge conflicts so that you can correct them before you merge the branches.

Additionally, the Pega 1:1 Operations Manager application allows business users to make controlled changes in a Business Operations Environment (BOE), and test the changes in a production environment within boundaries defined by your organization's IT department. For more information, see Revision management.

Packaging an application for migration

Before you migrate a new application to a different environment, package the relevant data instances and rulesets into a product rule. The product rule is an instance of Rule-Admin-Product, which Pega Platform refers to as the RAP file.

Before you begin: If you develop your application features in separate branches, merge the branches. For more information, see Developing applications, merging branches, and deploying changes in a distributed development environment.
  1. In the header of Dev Studio, click ConfigureApplicationDistributionPackage to start the Application Packaging wizard.
    For more information about using the wizard, see Packaging your application in a product rule.
  2. Complete each page of the Application Packaging wizard.
  3. On the last page of the wizard, click Preview.
  4. Review the contents of the generated RAP file.
  5. If you want to make any changes, on the last page of the wizard, click Modify.
  6. When you have completed your review of the RAP file, click Export.
    Result: The wizard creates a .zip file in the ServiceExport directory on the current application server node.

Importing the packaged application

To deploy a new application to a different environment, import the .zip file that contains the packaged application to the new environment.

Before you begin: Package the relevant data instances and rulesets into a product rule. For more information, see Packaging an application for migration.
  1. In the header of Dev Studio, click ConfigureApplicationDistributionImport.
  2. Use the Import wizard to import the target .zip file. For more information, see Importing rules and data from an archive by using a wizard.

    For information about how to swap the database connection pointers to your production database after importing an application to a production environment, see the Pega Platform Update Guide at Install Pega Platform.

Tags

Pega Government Platform 8.7

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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