Production as a service: Overview
FYI, the Installation Guide, SCG, Upgrade Guide, AND Checklist for Support Issues document refer to this topic by name. So don't change or delete it without fixing those docs.
Production as a service can start one or more instances of the Production module. When Production is started by the service, it is, by default, not allowed to interact with the user interface. Its primary intention is to start the Production module automatically, with production tasks that do not require any user interaction.
Installation
Please refer to the instructions provided in DOCUMENTS 7 Installation Guide.
Configuration
Configure the service according to these instructions.
Further adjustments are made by editing the ReadSoft Production service properties using the Windows dialog:
-
-
The service can be set to run automatically. (This is usually done by the installation program.)
-
Specify how the Production service logs on to ensure the correct users have the correct rights. (This is required if Windows authentication is enabled.)
-
Further changes are made in the RSProductionService.exe.config.behaviour file.
Execution and logging
Production service events are logged. See Checking on production tasks that are running as services.
When set to run automatically, the service starts after reboot, and the Production module starts to run. ReadSoft Production as a service does not require user attention. If the Production module crashes or stops, it is restarted automatically. The error is logged here:
-
In the folder. (Select menu > > ( >) >.)
-
In ServicesLog.html.
When a production task is executed in a Production service, all deployed versions of the task are executed consecutively. If a solution was deployed more than once, there will be several versions of the solution and its specifications. This means that all instances that match the production task will be processed, regardless of what version they belong to. 
Example:
Troubleshooting Windows services