Types of Services
In a Loftware Enterprise SP environment in which multiple Loftware Application Servers are configured to support distributed services, the following types of services exist. They are displayed in System
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
Note: Facilities and other functionality related to multi-site deployment are available only if your Loftware Enterprise SP license has the Multi-Site property enabled. Some options are displayed only if you are signed in to the headquarters site.
Core services support essential Loftware Enterprise SP functionality and require a connection to the Loftware database to function. All core services support failover, and the following table indicates which services also support load balancing.
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.
| Service Name | Description | Load Balancing Supported |
|---|---|---|
|
Device Driver Service |
This service allows you to install new device drivers in Loftware Enterprise SP. |
Yes |
|
Device Management Service |
This service provides access to configure devices and external integration services. This service is necessary for device management, device configuration, device discovery, and integration management. |
Yes |
|
Document Management Service |
This service supports the creation and management of label templates, applications, business rules, forms, images, layer objects, layouts, reusable objects, or workflow templates, as well as data services, processes, and device connections. |
Yes |
|
Font Management Service |
This service synchronizes installed fonts across all Loftware Application Servers. For information about managing fonts, see Managing Fonts. Important! The Font Management Service should be activated and started on all Loftware Application Servers to ensure consistent fonts. |
Yes (required) |
|
Job Management Service |
This service processes all incoming print requests and print actions within Loftware Enterprise SP. It works with the individual devices to ensure proper job processing to completion. |
Yes |
|
Multi-Site Management Service |
This service supports multi-site deployment of Loftware Enterprise SP. Important! This service should be started on all Loftware Application Servers that are part of a multi-site deployment. |
Yes |
|
Notification Management Service |
This service supports messaging and notifications within Loftware Enterprise SP. This service is necessary for messaging related to Model Status (Auto Refresh), job status, and notification. |
Yes |
|
Object Sync Service |
This service synchronizes objects between the headquarters and facilities in a multi-site deployment of Loftware Enterprise SP. Objects are synchronized only if they are configured for synchronization. Important! This service should be started on all Loftware Application Servers that are part of a multi-site deployment. |
Yes |
|
Remote Site Service |
This service supports remote printing which is comprised of a remote site object and Loftware Print Agent or Remote Print Agent. 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. |
Yes |
|
System Management Service |
This service manages the Loftware Enterprise SP instances and provides the client with security, license management, and access to core system language and font resources. This service is running on all Loftware Application Servers and cannot be deactivated. |
No |
|
System Monitor Service |
This service provides essential monitoring services that due to their nature can only run on a single Loftware Application Server in a distributed services environment at any given time. |
No |
|
Transaction Sync Service |
This service synchronizes transactions between the headquarters and facilities in a multi-site deployment of Loftware Enterprise SP. Important! This service should be started on all Loftware Application Servers that are part of a multi-site deployment. |
Yes |
|
Web Service |
This service provides a SOAP Web Service end point for client computers to access printing functionality. This service supports Web Services integrations, not SOAP Web Service data services. |
Yes |
|
Workflow Management Service |
This service supports the creation and management of workflows. |
Yes |
Devices, data services, integrations, and facility services all support failover, and the following table indicates which services also support load balancing.
For ease of management, each service is also displayed in Data Services
Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information,
| Type of Service | Description | Load Balancing Supported |
|---|---|---|
|
Devices |
This is a device service, which can be managed at the device group level. When a device connection is added to a distributed services environment, it becomes available to all Loftware Application Servers. You do not need to start the service on all servers to make it accessible to all servers, but you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. Device group services do not need to connect to the Loftware database. For information about managing multiple device connections simultaneously, see Manage Multiple Device Services. For information about managing device connections in Devices |
No |
|
Data Service |
This is a data service. When a data service is added to a distributed services environment, it becomes available to all Loftware Application Servers. You do not need to start the service on all servers to make it accessible to all servers, but you must ensure that the service is activated with a Forced proxy on all Loftware Application Servers on which it should be available to run and started on at least one. Data services do not necessarily need to connect to the Loftware database. For information about managing data services in Data Services |
Yes |
|
Integrations |
This is an integration service. When an integration is added to a distributed services environment, it becomes available to all Loftware Application Servers. You do not need to start the service on all servers to make it accessible to all servers, but you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. Integrations do not need to connect to the Loftware database. Tip: Web Services integrations are managed by using the core service named Web Service and are not listed as integration services in the Service Management pane. For information about managing integrations in Integrations |
No |
|
Facilities |
This is a facility service. When a facility is added to a distributed services environment, it becomes available to all Loftware Application Servers. You do not need to start the service on all servers to make it accessible to all servers, but you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. |
No |