Skip to main content

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

Deploying the application archives

Updated on April 8, 2022

After you create the application archives, deploy them to your target system. This process is the best way to deploy changes into your staging or production environment, control their activation, and recover from problematic deployments.

The user who imports the archives must have the zipMoveImport and SchemaImport privileges on the target system.
  1. Ensure that you have connectivity to both the target system and to the location where the archives are stored.
  2. Use the prpcServiceUtils command line utility to import the archives to the target system:
    • Deploy the Rules archive by following the steps in Importing rules and data by using a direct connection to the database. Your changes are sent to the system, imported to the database, and ready for activation.
    • Deploy the Data archive. When you deploy the Data archive, you use the same tool that you used to deploy the Rule archive but with different properties. You can roll back these changes if required.
  • Previous topic Deploying application changes to your staging or production environment
  • Next topic Testing the deployment

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