Skip to main content

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

Creating the application archives

Updated on December 13, 2021

For each release, you create one or two RAP archives, depending on the changes you made to your application. The user who exports the archives must have the zipMoveExport privilege.

These RAP archives include:

  • The Rules RAP, which contains the Rules portion of your release, instances from Rules- types only, and all rules changes.
  • The Data RAP, which contains the Data portion of your release, instances from Data classes only, and all data changes.

Splitting the release into a Rules RAP and a Data RAP provides you with more control over the deployment and activation of your changes on other systems.

More RAP archives might be created during the development process. Import these RAP archives to a single system from which the Rules RAP and Data RAP will be created. This method provides the greatest level of control over the release by separating the release process from the development process.

  1. Define the RAPs by using the Application Packaging wizard or by copying an existing RAP rule. For more information, see Product rules.
  2. Export each RAP as an archive:
    1. Export the rules. For more information, see Exporting an application, product rule, or ruleset to an archive or repository by using the Export wizard
    2. Provide a standard name for the archive, such as
    3. Store these archives in a standard location to which you have access, and that will be accessible during deployment.
Result: A Rules archive and a Data archive are created as the result of this process.

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

Close Deprecation Notice
Contact us