User Interface: Service Management

In a Loftware Enterprise SP environment with distributed services, multiple Loftware Application Servers are configured to interact as peers within the Loftware Enterprise SP environment. You can configure load balancing between Loftware Application Servers and failover of services from one Loftware Application Server to another. You can manage services in relation to these Loftware Application Servers in System System Management > Service Management. Alternatively, you can also manage services for devices, data services, and integrations by using View > Service Management for each data service in Data Services , each device group in Devices Devices , and each integration in Integrations .

Note: The Service Management page is primarily relevant if your Loftware Enterprise SP environment includes two or more Loftware Application Servers installed as a distributed environment. For information about how to create a distributed Loftware Enterprise SP environment, see the Loftware Enterprise SP Installation and Configuration Guide.

Note: In a multi-site deployment A configuration of a Loftware environment that includes Loftware instances located at different sites within the same WAN. In a multi-site deployment, each Loftware instance acts as either a headquarters or a facility. of Loftware Enterprise SP, you can configure high availability using distributed services at headquarters and at facilities. For information on connecting a facility to a load balancer, see Create or Modify a Facility.

Important! In an environment with distributed services, to permit a user to perform administrative tasks related to services you must assign Read and Write permissions for Servers. These permissions must be assigned for each server in Access Control . Examples of administrative tasks related to services include creating a data service, a device connection, an integration, or a facility. Core services can only be configured by the SuperAdmin or SystemAdmin user.

Note: By default, devices configured for use with a remote site are read-only in Loftware Enterprise SP and are managed by the Loftware Print Agent (LPA) or Remote Print Agent (RPA). If you want to manage devices that are configured for use with a remote site instead, see Manage Remote Site Device Services.

Service Properties

The following are the properties of a service, such as core service, a data service, an integration service, or a device group service.

Option	Description	Values
Start/Stop	Whether to start or stop the service. Note: This option is not displayed for a device template An object that includes settings for a device but cannot be started as a service and cannot consume a device seat. You can use Save As to create a device based on the device template..	Start Stop
<Service Name>	The name of the selected service, which may be a core service, device group service, data service, or integration service.
Refresh	Refresh the information shown for the service, including the latest status.
Description	An explanation of the purpose of the service.
Configured Status	Whether the service is running on at least one Loftware Application Server within the environment. For services that can be manually started and stopped, the Start/Stop toggle is enabled.	Started Stopped
Enable By Default	Whether the service is enabled by default on a newly-created Loftware Application Server. Note: System Management Services are always enabled, so this option is not configurable for that type of service.	: Enabled by default : Disabled by default
Concurrent Running Servers	The number of Loftware Application Servers that Loftware Enterprise SP should run the service on concurrently. Important! Selecting a value other than All makes the Priority field active for each instance. Note: This option is omitted from or disabled in services that cannot be load balanced.	All <Number>
Instance configurations	Properties and status for each Loftware Application Server in the environment. Which properties are available and which are configurable vary depending on the service selected.	See the "Instance Configuration Properties" table that follows this section.

Instance Configuration Properties

The following are the properties of a service in relation to a particular Loftware Application Server.

Option	Description
Instance Name	The name of a computer acting as a Loftware Application Server.
Activate	Whether to turn the service on or off for this Loftware Application Server. The result is reflected in the State column.
Proxy	If this Loftware Application Server cannot respond to a request, whether it will forward that request to another Loftware Application Server. Ready: The Loftware Application Server forwards requests to another Loftware Application Server if it cannot respond to them locally. Also, the Loftware Application Server forwards requests if the service requires a connection to the Loftware database and the Loftware Application Server cannot connect. Forced: The Loftware Application Server always forwards requests to another Loftware Application Server. Never: The Loftware Application Server does not forward any requests to another Loftware Application Server. Note: This option exists only for services that accept remote operations directly from client computers.
Priority	The order in which the instance of the service on a particular server should fail over to another server, if available. This option is relevant only if the service is configured for high availability or failover rather than load balancing. Important! If the service supports load balancing, then to display the Priority option you must select a number for Concurrent Running Servers. For each server that you are load balancing and that should run the service under ordinary circumstances, set the Priority to 1. For each server that should act as a standby server and run the service only if another server goes offline, set the Priority to 2 or greater. If the same priority is selected for a service on more than one Loftware Application Server, then the service runs on the first Loftware Application Server that attempts to run it. <Number>: The lower the value, the greater the priority. Tip: If you have multiple standby servers, you can use the priority to control which server acts as the failover target for each service. The order proceeds from the lowest number to the highest number. That is, if a Priority 1 server fails and servers with Priority 2 and Priority 3 are available, then the server with Priority 2 will be used if it is running. If the server with Priority 2 fails, then the server with Priority 3 will be used. When the Priority 1 server comes back online, the service will revert to that server.
State	Whether the service is running on this Loftware Application Server. Started: The service is running on this server. Stopped: The service is not running on this server. Ready: The service is running on this server, but is not actively engaged. For example, this state can occur if the service is running on three servers, but the Concurrent Running Servers is 2. A yellow indicator indicates the service is in standby mode and is normal for non-actively engaged services in a Ready state. Unknown: A problem has occurred. Contact Loftware for assistance.