Skip to main content

 –

Installing hotfixes by submitting a request to an active instance

Suggest edit Updated on September 29, 2021

To automate hotfix installation, use the command-line tools. If you have an active instance of Pega Platform, you can install hotfixes by submitting a request to the active instance via a web service.

  1. Configure the common properties of the prpcServiceUtils.properties file.
    Property name Value
    pega.rest.server.urlThe URL for the REST service, specified in the following format:

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

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

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

    pega.rest.proxy.port

    The port for the REST proxy server.

    pega.rest.proxy.username

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

    pega.rest.proxy.password

    The password of the REST proxy operator.

    pega.rest.proxy.domain

    The domain of the REST proxy server.

    pega.rest.proxy.workstation

    The workstation ID for the REST proxy server.

    pega.rest.response.typeThe REST response type, either xml or json. The default value is json. Rollback, restore point, and update access group operations support only json.
    user.temp.dir

    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 install properties of the prpcServiceUtils.properties file.
    Property name Value
    hotfix.operation install
    hotfix.dlFilePath The full path to the hotfix package file.
    hotfix.bypassSchema The default value, false, applies any schema changes automatically. A value of true indicates that you have already manually applied the schema changes.
    hotfix.force Set only at the request of Pegasystems Global Client Support to skip hotfix validations and force the hotfix data into the system.
    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 prpcServiceUtils.properties file.
  4. Run the prpcServiceUtils.bat or prpcServiceUtils.sh 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 serviceConnection.properties 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 prpcServiceUtils.properties.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us