Rolling back a problematic deployment
In the event of a problematic deployment, the first goal is to prevent further issues from occurring. Then you can roll back the deployment and restore your system to a state that was previously known to be working.
Do the following steps:
Result: Roll back the data instances that you changed to their
previous version. To roll back data changes, use the prpcServiceUtils command line
utility. For more information, see Rolling back and committing tracked data. This
process replaces those modified data instances with their prior definition, rolling back
your data changes to the last known, good state.
- Ensure that no new operators can access the problematic application. You can temporarily disable access to the entire system. For more information, see How to temporarily disallow new interactive logins with a Dynamic System Setting.
- Roll back the problematic rules changes. You can roll back changes by updating the access group for your application and specifying the previous version of your application.
Previous topic Activating the release for all users Next topic Packaging a release on your development environment