Skip to main content

 –

Packaging an application

Suggest edit Updated on January 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.

  • 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.

  • Packaging an application for migration

    Before you can migrate a new application to a different environment, you must 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.

  • Importing the packaged application

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

  • Multitenancy deployment considerations

    In a multitenancy environment, the shared application components are deployed only to the shared environment, and the tenant-specific components are deployed only to the tenant region.

Did you find this content helpful? YesNo

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us