User Interface: Facilities
If your Loftware Enterprise SP license and your permissions permit, you can create a facility An object in Loftware that represents the location of a Loftware Application Server and Loftware Database Server that are associated with a headquarters (HQ). These servers must be associated with a Loftware 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. object in Loftware Enterprise SP to manage a facility site.
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.
When you select a facility from the Facilities page in System
General
Property | Description |
---|---|
Facility Location |
Required. A description of the physical location of the facility. The Facility Location is a comment intended to assist administrators and is not used by Loftware Enterprise SP to identify or connect to the facility. |
Facility URL |
Required. The URL of the Loftware Application Server at the facility. The URL should include an http:// or https:// prefix, either an IP address or a DNS name, and a port, but not the path to Loftware Enterprise SP within the Loftware Application Server. Examples The following example includes a typical non-secured access port. http://www.example.com:8080 The following example includes a typical secured access port. https://www.example.com:8443 |
Facility Response URL |
The URL to connect to the load balancer that manages the facility. If the facility is not managed by a load balancer, leave this box blank. The URL should include an http:// or https:// prefix, either an IP address or a DNS name, and a port, but not the path to Loftware Enterprise SP within the Loftware Application Server. Examples The following example includes a typical non-secured access port. http://www.example.com:8080 The following example includes a typical secured access port. https://www.example.com:8443 |
Print From HQ |
Whether print jobs originating from the facility should be processed by a Loftware Application Server at the headquarters or at the facility. This property can have the following values:
|
Configuration Sync
Area |
Description |
---|---|
Frequency |
When to replicate synchronized objects from headquarters to the facility. The following options are available for scheduling synchronization:
|
Folders |
Which folders and types of objects to replicate from headquarters to the facility. For each folder that you select, you can specify which types of objects in that folder to synchronize and whether to recursively synchronize all subfolders within the folder. The following controls allow you to specify folders and types of objects to be synchronized:
|
Transaction Sync
Area |
Description |
---|---|
Frequency |
When to replicate transactional data used for auditing from the facility to headquarters. The following options are available for scheduling synchronization:
|
Dialog Boxes
Dialog | Description |
---|---|
Properties |
|
View > Configuration Sync |
Controls for initiating and canceling the replication of synchronized objects from headquarters to the facility, and information reported about recent synchronizations. Note: A synchronization takes effect on each object individually. You can cancel a synchronization that is in progress, preventing any more objects from being synchronized. However, canceling a synchronization does not undo the effects on objects already processed during that synchronization. The following commands are available:
The following information is displayed about each synchronization:
|
View > Transaction Sync |
Controls for initiating and halting the replication of transactional data The following commands are available:
The following information is displayed about each synchronization:
|