Management and Administration > K2 Server > K2 Server | Send feedback |
The K2 Server is the principle server for running the processes that are deployed by the various designers. Each installed K2 Server must be individually licensed and can be deployed in Stand Alone, Distributed (Single Server), clustered or load balanced (Multiple K2 Servers).
Server configuration is performed by means of a configuration file, but certain other system settings are required as well. These include setting up the service account, creating a unique e-mail and mailbox for the Service Account. The K2 Server requires a unique service account and appropriate privileges to ensure that it is able to access system resources for operational purposes.
Any changes made to the configuration file will only take affect after the K2 Server has been restarted.
The K2 Server is also referred to as Host Server as a number of services are hosted within the K2 Server; they include:
The K2 Server will run in two specific modes namely as a service or in console mode. Running as a service is for normal operations and console mode is either for debugging or for development purposes. For example, the developer license will only allow the K2 Server to run tin console mode. For more information on licensing see the following: K2 Platform Licensing
The K2 Server requires specific pre-requisites to functions, see the pre-requisites here Prerequisites for the K2 Server role.
The K2 Service for normal operations must be run as a service. see the following: Configuring Log on as a Service Rights
For distributed environments, Kerberos can be used however K2 Pass-Through Authentication is the preferred alternative for small to medium scale implementations.