Versions Compared

Version Old Version 5 New Version Current
Changes made by

Paul Hindle

Andrew Hill (Deactivated)

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.4

In the template below, <instance> is the OS user (account) under which ServiceOptimizer is running.

If the system monitor restarts a component (or finds that it has itself been restarted), it will first move all the component log files (including optimizer log files) from the previous incarnation of that component into a subdirectory of the directory containing the logs:

...

The following parameters deal with the archiving of logfiles - see Admin ServiceOptimizer System Configuration Application Logfiles for further details

ParameterDescription

Application logfile control

mon_archive_dir

Directory (folder) under which ServiceOptimizer application log files are archived.

mon_archive_logs

Determines whether logs from previous runs of the server will be saved. 'YES' will save logs, 'NO' will not.

mon_pci_archive_timeout

Time in seconds to wait for remote archiving to complete. 

In a distributed ServiceOptimizer instance, archiving could take a long time. The command sent from the master System Monitor to the slave System Monitor to trigger archiving on the slave has this specific reply timeout (used instead of mon_pci_command_timeout). 

Note that this parameter must be greater than or equal to the value for mon_pci_command_timeout or the System Monitor will not start.