To accomplish this task, it needs an IS server to exist (usually called "ServiceStatus?") which the various services post status information to. Note that the various services learn the name of the IS server (and IS object within) to which they are to publish status information via the "-status" command line arguments. For example, the ArchivingService may be started with the option:
-status ServiceStatus.ArchivingService
Note that the ServiceStatusGUI can cope even if the ServiceStatus? IS server is absent when it starts up, as it keeps an eye out for its later arrival.