Managing background processes during upgrades and patches

Stopping agents

To stop the agents that are currently running, complete the following steps:

1. In the navigation panel of Admin Studio, click Resources Agents .
2. Select all agents by selecting the check box at the top of the Agents table.
3. Click Stop.

Disabling jobs

To disable jobs that are currently running, complete the following steps:

1. In the navigation panel of Admin Studio, click Resources Jobs .
2. 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:

1. In the navigation panel of Admin Studio, click Resources Queue processors .
2. For each Queue processor running, in the State column, click Stop.

Stopping active listeners

To stop active listeners, complete the following steps:

1. In the navigation panel of Admin Studio, click Resources Listeners to display the Listeners table, which displays all of the configured listeners.
2. 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:

1. In the navigation panel of Dev Studio, click Configure Decisioning Decisions Data Flows .
2. 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.
3. 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:

1. In the navigation panel of Admin Studio, click Resources Jobs .
2. For each job disabled, in the State column, click Revert.

Restarting queue processor rules

1. In the navigation panel of Admin Studio, click Resources Queue processors .
2. For each Queue processor you want to restart, in the State column, click Start.

Restarting listeners

To restart configured listeners, complete the following steps:

1. In the navigation panel of Admin Studio, to display the Listeners table, click Resources Listeners .
2. In the top right corner above the Listeners table, in the Start / restart listener pulldown, select Start or Restart by type.
3. Place your cursor in the box below the Start / restart listener pulldown and press the down arrow key.
4. Choose the type of listener to restart and click Apply.
5. Repeat steps 3 and 4 for the other types of configured listeners.
6. Optional: Click the refresh icon to see all Active listeners,
7. 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:

1. In the navigation panel of Dev Studio, click Configure Decisioning Decisions Data Flows .
2. 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.
3. 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.