Deploying the application archives
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.
Result: For information about allowing automatic schema changes, see
Editing administrator privileges for importing
archives with schema changes into production.
- Ensure that you have connectivity to both the target system and to the location where the archives are stored.
- Use the prpcServiceUtils command line utility to import the archives to the
- 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 by following the steps in Rolling back and committing tracked data. 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