Windows Service Configuration
During the installation of FlowForce Server on a Windows operating system, it is possible to configure the following settings:
•How FlowForce Server should start up as a Windows service: automatic, on demand, delayed automatic, or disabled.
•The operating system user account to be used by FlowForce Server as a Windows service: Local System, Local Service, Network Service, or Other User.
•If FlowForce Server is configured to run as Other User, you can set the username and password of this user, similar to how this is done in the Windows Services management console.
If you select Other User, the user account (or the group which it is a member of) must have read/write access to C:\ProgramData\Altova. Otherwise, this will result in failure of the installation or startup. Note also that if you select Other User to run the services, the account needs the following privileges: Adjust memory quotas for a process (SeIncreaseQuotaPrivilege) and Replace a process level token (SeAssignPrimaryTokenPrivilege). These privileges can be granted in the Windows applet Local Security Policy in the subtree Local Policies/User Rights Assignment. Local Security Policy can be accessed via the Start menu search box.
These privileges are only required for the main FlowForce service, not for FlowForceWeb. Importantly, the file access rights are required for both.
The settings listed above can also be configured for FlowForce Web Server.
The settings have the same meaning as when you change the service properties from the Windows Services management console.
To define the settings above during installation, click the relevant tab (FlowForce Server or FlowForce Web Server) on the installation dialog box. Click Change next to Service configuration.
If you need to change these settings after installation, open the Windows Services management console, and then change the properties of the required service from there. To open the Windows Services management console, open a command line window and type Services.msc.