Administer > Server performance tuning > Scheduled processes

Scheduled processes

You can start RAD applications, known as scheduled processes, as unattended background processes. Scheduled processes are also known as background agents, schedulers, processors, and background tasks. Scheduled processes run at set intervals and check for specific conditions before executing a RAD application. Each scheduled process has one or more schedule records that determine the conditions that must be met for the RAD application to run. You can start scheduled processes from the Scheduler form.

Note: There can be only one kmupdate process running at any time. Starting more than one kmupdate process causes unpredictable behavior on the search engine server.

List of scheduled processes

By default, Service Manager provides the following scheduled processes:

Scheduler Name Runs as Process Name or Names Description
KMUpdate KMUpdate This process checks for update records and sends them to the index
SLA sla This process monitors service level agreements and processes alerts.
Sync sync This process identifies orphan processes that were shut down improperly and frees up any resources they are using before stopping them.
agent agent This process manages charts from stored queries.
alert.processor alert This process manages Incident Management log messages and alerts.
availability.startup availability This process manages asset availability and updates outage statistics.
change.startup change This process manages change events.
contract contract This process manages contract events.
event.startup event This process manages asynchronous incoming events from the Eventin Queue.
gie.startup gie This is a legacy process from earlier versions of Service Manager that manages incoming Prim Events.
inactive.startup inactive

If using the SM applications earlier than version 9.32, this process automatically logs off users who are inactive for a period of time.

If using the SM applications version 9.32 or later, this process is obsolete. A new inactivity timer mechanism is used, which no longer requires this process. Note that this new mechanism requires your SM server, applications, and web client to upgrade to version 9.32 or later. As long as your applications is earlier than version 9.32, the old mechanism is used.

linker.startup linker This process manages related calls to closed incidents.
lister.startup lister This process manages global variables in the globallist file.
marquee marquee This process manages static marquee messages.
ocm.startup ocm This process manages request events.
printer.startup despooler This process manages server-side print requests.
problem problem This process manages IM alerts and messages.
report.startup report This process manages Report Writer reports and importing and exporting of reports.
scauto.startup scautod This process manages incoming and outgoing ServiceCenter Automate connections.

 

 

Related topics

Add an agent to the startup agent record

Configure the alert periodic schedule record

Create an anubis agent record

Create an anubis schedule record

Restart stopped background processes automatically

Start a scheduled process

Stop a process