Q++Studio Network Architecture (XV4  64-bit)

Navigation:  Introduction >

Q++Studio Network Architecture (XV4  64-bit)

Previous pageReturn to chapter overviewNext page

 

There are 3 components to the Q++Studio architecture:

 

The workstation on which users use QuarkXPress to create templates and plain information files in the QuarkXPress format, and is also used by Q++Studio to automatically generate complete diaries and calendars.

The file server where QuarkXPress templates and plain information files are saved (but on which QuarkXPress is neither installed nor running).

The database server where the Q++Studio database is located (diary scripts, translations, holidays, slogans, astronomical data, ...). Multiple database servers can be inter-connected (one license is required for each database server).

 

In practice, these 3 components can be mixed in various configurations:

 

Single User

This is the simplest configuration, in which all 3 components are running on the same computer.

Single Site

This is the most common configuration, in which two or more PCs, acting as workstations, are connected via LAN to one PC, which is used as both file server and database server, and all PCs, workstations and servers are located at the same Main Site.

Single Site with Remote Users

This is a variation of the Single Site configuration where, additionally, remote single users, each working on a stand-alone PC, connect to the Main Site database server via the regular internet (WAN), with their individual PCs serving as both workstation and file server.

Multi Site

In this configuration, all 3 Q++Studio components are running on a different PC, and the 2 servers are located at different sites.

 

The database server is located at the Main Site, where the majority of the workstations are also located, to benefit from the speed advantage of LAN connections versus WAN connections, and the main site's file server is located.

 

At the remote multi-user site, two or more PCs, acting as workstations, are connected via LAN to one PC, which is used as remote file server, and these workstations are also connected via the regular internet (WAN) to the database server at the Main Site.

 

The reason why a file server is needed at every physical location is that QuarkXPress files can be very large and are always saved entirely, as opposed to access to and from the database server which can be fine-tuned to only read and write the changes that have occurred, if any. If QuarkXPress worked as a database server does, one could ask to only open page 142 of a 384 page document, make changes to that page 142, and then send back only the modified page 142. Unfortunately this is not the case.

 

The use of an EFS server on each file server alleviates the inconvenience that can arise with your QuarkXPress files being located on different file servers.


Topic 181930 updated on 01-Dec-2018.
Topic URL: https://www.qppstudio.net/webhelp_xv4/index.html?architecture.htm