Configuring and Managing a Multi-Site Deployment

You can configure a multi-site deployment of Loftware Spectrum. With this approach, a Spectrum instance A Spectrum Application Server and a Spectrum Database Server that are associated with each other by a Spectrum License. at one site A geographical location, such as the location of a Spectrum instance or a remote computer. is synchronized with Spectrum instances at other sites. Unlike a high availability deployment in which all Spectrum Application Servers are peers, a multi-site deployment has a headquarters (HQ) The location of a Spectrum Application Server and Spectrum Database Server that are associated with facilities. These servers must be associated with a Spectrum license for which Usage is set to Production and Multi-Site is set to true. Each HQ can communicate with multiple facilities. By synchronizing, an HQ can replicate objects to facilities and replicate transactional data generated at facilities back to the HQ. that communicates with a facility An object in Spectrum that represents the location of a Spectrum Application Server and Spectrum Database Server that are associated with a headquarters (HQ). These servers must be associated with a Spectrum license for which Usage is set to Facility and Multi-Site is set to true. Each facility can communicate with only one headquarters. By synchronizing, an HQ can replicate objects to facilities and replicate transactional data generated at facilities back to the HQ. or facilities, but the facilities are not aware of each other. Objects such as label templates and devices can be configured at the headquarters and replicated to each facility. Any job data generated at facilities can be replicated to the headquarters.

Note: Facilities and other functionality related to multi-site deployment are available only if your Spectrum license has the Multi-Site property enabled. Some options are displayed only if you are signed in to the headquarters site.

Tip: It is recommended that you install the Spectrum application and database at each facility site before you create the facility object in Spectrum. The name of the root folder in Spectrum must be the same at the headquarters site and at each facility site associated with that headquarters. The headquarters and facility sites must be able to communicate, but facilities are not required to be able to communicate with each other.

Approaches

You can use either of the following approaches when configuring a multi-site deployment. The primary difference between these approaches is whether printing is normally processed by facilities or by the headquarters, and therefore whether a Data Provider Person or process that enters data into a form or other data entry view for a label that was configured by a Designer. A user acting as a Data Provider requires the DOCUMENT_PRINTER role or equivalent permissions. signs in to a facility or the headquarters to print.

Note: In a multi-site deployment A configuration of a Spectrum environment that includes Spectrum instances located at different sites within the same WAN. In a multi-site deployment, each Spectrum instance acts as either a headquarters or a facility. of Spectrum, device connections can be created only at headquarters. They can be replicated to facilities by using synchronization, and they can be changed at facilities if allowed by the configuration. Remote Sites can be created at both headquarters and facilities to enable the use of a Loftware NiceLabel driver. For more information, see Using a Loftware NiceLabel Driver at a Facility.

Processing Print Jobs at Facilities

You can configure a multi-site deployment of Spectrum so that you can primarily manage devices, label templates, and other objects from a headquarters, but process print jobs at facilities for faster performance. The headquarters sends the configuration information required for devices, label templates, and other objects to each facility, and each facility uses that information to process print jobs. Objects that are configured to be synchronized are replicated from the headquarters to facilities. Workflows occur at the headquarters. Job data is generated at the facilities and is replicated to the headquarters.

If a multi-site deployment is configured to process print jobs at facilities, users typically do the following:

A Data Provider Person or process that enters data into a form or other data entry view for a label that was configured by a Designer. A user acting as a Data Provider requires the DOCUMENT_PRINTER role or equivalent permissions. signs in to a facility to print.
A Designer Person who creates and designs label templates, forms, and applications for use by Data Providers. signs in to the headquarters to create and edit label templates. If connectivity with the headquarters is lost, label templates and other objects can be modified at facilities until connectivity with headquarters is restored.
An Administrator configures devices by signing in to the headquarters, and configures data services and integrations by signing in to either headquarters or facilities. Devices are configured at the headquarters, and connection information is entered for the facility. If connectivity with the headquarters is lost, an administrator can modify data services and devices at facilities until connectivity with headquarters is restored.

Processing Print Jobs at Headquarters

You can configure a multi-site deployment of Spectrum so that you can primarily manage devices, label templates, and other objects from a headquarters, and process print jobs via the headquarters to ensure that the most current job transaction data and device connectivity status is maintained at the headquarters. Objects in a synchronized folder are replicated from the headquarters to facilities. Workflows occur at the headquarters. Job data is generated at the headquarters.

If a multi-site deployment is configured to process print jobs at headquarters, users typically do the following:

A Data Provider Person or process that enters data into a form or other data entry view for a label that was configured by a Designer. A user acting as a Data Provider requires the DOCUMENT_PRINTER role or equivalent permissions. signs in to the headquarters to print.
A Designer Person who creates and designs label templates, forms, and applications for use by Data Providers. signs in to the headquarters to create and edit label templates. If connectivity with the headquarters is lost, label templates and other objects can be modified at facilities until connectivity with headquarters is restored.
An Administrator configures devices, data services, and integrations by signing in to the headquarters. Devices are configured at the headquarters, and connection information is entered for the facility. If connectivity with the headquarters is lost, an administrator can modify data services and devices at facilities until connectivity with headquarters is restored.

Tasks

You can configure and manage a multi-site deployment in Access Control . However, a multi-site deployment can also be managed via System System Management , allowing you to delegate the responsibility for managing a multi-site deployment to users who do not have access to Access Control .

In Access Control , you can perform the following tasks related to configuring multi-site deployment:

Create facilities
Specify facilities to sync with a specific folder and types of objects in those folders
Manage whether an individual object can be synchronized
Manage access to facilities by using roles, users, and groups
Start and stop a facility

In System System Management , you can perform the following tasks related to configuring multi-site deployment:

Create facilities
Specify folders and types of objects in those folders to be replicated from headquarters to a facility
Schedule replication of objects from headquarters to a facility
Schedule replication of transactional data used for auditing from a facility to a headquarters
Manually initiate or cancel synchronization and review the status of synchronization