Versions Compared

Version Old Version 12 New Version 13
Changes made by

Paul Hindle

Andrew Hill

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space SCHUD and version 9.3

...

ComponentDescriptionStartUp RequirementsTermination RequirementsLogfiles
Admin ServiceOptimizer Further Detail Core Processes System Monitor

The System Monitor (spsysmon(.exe)) process is used to control the running of the other on-line processes:

  1. it starts up the processes which then run continuously until explicitly terminated,
  2. 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 Admin ServiceOptimizer Overview and Admin ServiceOptimizer System Configuration).

Started manually from the command line, or via a script.

On UNIX: spsysmon is stopped by typing: kill -TERM <PID of spsysmon>
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 UNIX: /var/adm/messages (configurable in /etc/syslog.conf)

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 Admin ServiceOptimizer System Configuration Application Logfiles

Admin ServiceOptimizer Further Detail Core Processes Components FRU ProcessThe 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 sysmonMust be stopped by sysmonSee Admin ServiceOptimizer System Configuration Application Logfiles
Admin ServiceOptimizer Further Detail Core Processes API AgentThe 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 sysmonMust be stopped by sysmonSee Admin ServiceOptimizer System Configuration Application Logfiles
Admin ServiceOptimizer Further Detail Core Processes Gantt RouterThe 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 sysmonMust be stopped by sysmon See Admin ServiceOptimizer System Configuration Application Logfiles

...