Skip to main content

Rolling back hotfixes by submitting a request to an active instance

Suggest edit
Updated on April 12, 2022

If an uncommitted hotfix introduces unwanted changes to your system, you can remove it by rolling it back. If you have an active instance of Pega Platform, you can roll back hotfixes by submitting a request to an active instance via a web service.

To invoke a web service to roll back hotfixes, do the following stepsCaution: You cannot roll back committed hotfixes.Note: Database schema changes associated with a hotfix are not removed when rolling back.
  1. Configure the common properties of the file.
    Property name Value URL for the REST service, specified in the following format:

    http:// <hostname> : <port> / <context> /PRRestService/

    For example: http://myhost:8080/prweb/PRRestService operator name on the target system with access to REST services. password of the specified operator.

    The host name of the REST proxy server. Do not use localhost as the host name.

    The port for the REST proxy server.

    The operator name on the REST proxy server with import and export access.

    The password of the REST proxy operator.

    The domain of the REST proxy server.

    The workstation ID for the REST proxy server. REST response type, either xml or json. The default value is json. Rollback, restore point, and update access group operations support only json.

    Enter the full path to the temporary directory. Leave this blank to use the default temporary directory. For more information about temporary directories, see Temporary files and temporary files directories .

  2. Configure the rollback properties of the file.
    Property name Value
    hotfix.operation rollback
    hotfix.async true or false. The default value, true, executes the hotfix operation asynchronously. The system queues the job and returns a JobID to use to get the job status. A value of false executes the operation synchronously.
  3. Save and close the file.
  4. Run the prpcServiceUtils.bat or script with the hotfix option, for example: prpcServiceUtils.bat hotfix
  5. Optional: Pass one or more arguments:
    prpcServiceUtils script argument Value
    connPropFileThe full path to the file that includes information for multiple targets.
    poolSizeThe thread pool size. Default is 5.
    requestTimeOutHow long the system waits for a response before failing with a time-out error. Default is 300 seconds.
    jobIdFileThe path to the job IDs file that is generated by the asynchronous operation.
    propFileThe full path to the properties file, to override the default
  • Previous topic Rolling back hotfixes from the user interface
  • Next topic Rolling back hotfixes by using a direct connection to the database
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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