Core Processes

On This Page:

Process Overview

Related Pages:

Application Logfiles

Process Overview

There are 4 main process types. The table below shows an overview of the startup, termination and logfile requirements of each. Each entry links through to a page that describes that process in more detail and gives an example of the syntax for calling that process.

Component	Description	StartUp Requirements	Termination Requirements	Logfiles
System Monitor	The System Monitor (spsysmon(.exe)) process is used to control the running of the other on-line processes: it starts up the processes which then run continuously until explicitly terminated, it detects if any of those processes terminates and can automatically re-start a process a configurable number of times, and it terminates the processes in a controlled way (e.g. at the end of the on-line day) One System Monitor runs if the server is non-distributed. If the server is distributed, one System Monitor runs as a Master and others run as Slaves	All environment variables and database parameters required by processes under spsysmon's control must be set correctly (see sections ServiceOptimizer Overview and ServiceOptimizer System Configuration). Started manually from the command line, or via a script.	On Windows: spsysmon is stopped by typing `CTRL-C` or by clicking on the close (X) button. spsysmon will then signal all of the processes under its control to make them terminate tidily - this may take a few minutes to complete.	On Windows: System event log The OS system log is a log of the more important events, which are a subset of information logged to the application log in a form that a system administrator would find useful. The information stored in the system log can usually be accessed using standard operating system provided tools. See also Application Logfiles.
FRU Process	The FRU process (spfru(.exe)) is the main ServiceOptimizer process which, for a single FRU, books, schedules and dispatches jobs. It also monitors and reports jeopardy conditions. One FRU process is run for each FRU.	Must be started by sysmon	Must be stopped by sysmon	See Application Logfiles.
API Agent	The API Agent (spapiagent(.exe)) is the routing process for ServiceScheduling API clients. It connects API clients to the correct FRU process and collates results back from multiple FRUs.	Must be started by sysmon	Must be stopped by sysmon	See Application Logfiles.
Gantt Router	The Gantt Router (spganttrouter(.exe)) is the point of contact for ServiceGANTT clients to connect to ServiceOptimizer. It processes the user's login information and then connects to an FRU Process.	Must be started by sysmon	Must be stopped by sysmon	See Application Logfiles.

Important

Each ServiceOptimizer process must be restarted on a regular basis. Failure to do so can result in data corruption. Please see appropriate sections for rules and details on how to set this up.

Note that it is possible to run multiple instances of ServiceOptimizer on a single Server to support multiple environments, each with its own database. Consult ServicePower support to set this up.

Note that, for each ServiceOptimizer executable, passing the -h command line parameter will give a help (usage) message informing the user of command line arguments.