Important information for using AVEVA Real-Time System as a service

Like any other Windows service, the AVEVA Real-Time System (RTS) service typically always runs in the background.

You can use the Services app to stop and start the service.

You can also use the rts start --as-service and rts stop commands.

Administrator privilege is needed to start and stop RTS as a service.

Tip: Open the shell.bat file with administrator privileges by right-clicking and selecting Run as administrator.

Once the RTS service is running, you can use the rts commands as usual to run sequences, run backfills, schedule sequence runs, and perform other common RTS actions. RTS Console can be used as well.

See RTS Console for more information.

When running RTS as a service, the related processes such as RtServer.exe, ScriptHost.exe, and the AVEVA Process Simulation server (SimCentral.Server.ConsoleServiceHost.exe) all run under the service account and do not have associated console windows.

To view RTS progress, you should monitor the associated log files.

See the following sections for more information:

• Monitor a log file

• Access to AVEVA Process Simulation log files for non-service account users

When running as a service, you typically install RTS in a common location accessible by multiple users, so that anyone who has access to that location can use the shell to run rts commands. That is, even if the RTS service is running under a different service account than the user who is using the rts command, the command-line tool accesses the running service since the service was installed from that installation location.

All rts commands except for the rts start command work the same whether RTS is running as a service or as a process.

When RTS is installed as a service, the rts start command requires the --as-service option to start RTS as a service. Otherwise, RTS starts as a process.