Managing background processes during upgrades and patches
This content applies to environments that are running Pega Platform 8.2.x and earlier. Background processes are automatically managed during upgrades and patches for clients running Pega Platform 8.3.x and later.
To ensure that Pega Cloud Services applies a software patch successfully, the client must stop the following types of background processes before the patch application and then restart them afterwards:
- Agents
- Job schedulers
- Queue processors
- Listeners
- Clients using Pega DSM only: Data flows
Following Pega Platform 8.2 and earlier software upgrade or patch applications, as well as after Pega Cloud Services environment infrastructure upgrades, Pega automatically restarts Pega agents and listeners that you manually stopped. See the following detailed sections for stopping and then restarting Pega queue processors, job schedulers, and DSM dataflows after you receive notification that the patch application is complete.
Stopping agents
To stop the agents that are currently running, complete the following steps:
- In the navigation panel of Admin Studio, click .
- Select all agents by selecting the check box at the top of the Agents table.
- Click Stop.
Disabling jobs
To disable jobs that are currently running, complete the following steps:
- In the navigation panel of Admin Studio, click .
- For each job enabled, in the State column, click Override.
Stopping queue processor rules
To disable Queue processors that are currently running, complete the following steps:
- In the navigation panel of Admin Studio, click .
- For each Queue processor running, in the State column, click Stop.
Stopping active listeners
To stop active listeners, complete the following steps:
- In the navigation panel of Admin Studio, click to display the Listeners table, which displays all of the configured listeners.
- In the top right corner of the Active listeners table, click Stop all.
Clients using DSM only: Stopping data flows
To stop all of the active data flows complete the following steps:
- In the navigation panel of Dev Studio, click .
- To stop batch processing data flows, click the Batch processing tab. For all of the dataflows in this page, in the Action column, select Pause.
- To stop real-time processing data flows, click the Real-time processing tab. For all of the dataflows in this page, in the Action column, select Pause.
Restarting background processes after a patch
After the client receives confirmation from Pega that a patch has been applied to their environment and the services are up and running, the client must restart the background processes that they stopped to allow the patch to be applied.
To restart these background processes you stopped, see the applicable section.
Enabling jobs
To enable jobs that are currently disabled, complete the following steps:
- In the navigation panel of Admin Studio, click .
- For each job disabled, in the State column, click Revert.
Restarting queue processor rules
To restart Queue processors, complete the following steps:- In the navigation panel of Admin Studio, click .
- For each Queue processor you want to restart, in the State column, click Start.
Restarting listeners
To restart configured listeners, complete the following steps:
- In the navigation panel of Admin Studio, to display the Listeners table, click .
- In the top right corner above the Listeners table, in the Start / restart listener pulldown, select Start or Restart by type.
- Place your cursor in the box below the Start / restart listener pulldown and press the down arrow key.
- Choose the type of listener to restart and click Apply.
- Repeat steps 3 and 4 for the other types of configured listeners.
- Optional: Click the refresh icon to see all Active listeners,
- Select each listener to restart and click Restart.
For more information, see Restarting a listener.
A listener successfully starts on the node type that is specified in its configuration; when you restart all configured listeners in a batch, each listener attempts to restart on all nodes. For information purposes, Pega Platform returns exception errors for listeners attempting to restart on node types that do not match the listener configuration.
Clients using Pega DSM only: Resuming data flows
To resume all of the data flows that you paused, complete the following steps:
- In the navigation panel of Dev Studio, click .
- To resume batch processing data flows, click the Batch processing tab. For all of the dataflows in this page, in the Action column, select Resume.
- To resume real-time processing data flows, click the Real-time processing tab. For all of the dataflows in this page, in the Action column, select Resume.