9.0
Table Of Contents
- Contents
- About this Guide
- Getting started with QuarkXPress Server
- The QuarkXPress Server user interface
- Navigation pane
- Administration menu
- General Preferences dialog box
- Renderer Preferences dialog box
- Preferences — Display
- Preferences — Input Settings
- Preferences — Font Fallback
- Preferences — Open and Save
- Preferences — Fonts
- Preferences — EPS
- Preferences — PDF
- Preferences — Project General Settings
- Preferences — Print Layout Settings
- Preferences — Print Layout Measurements
- Preferences — Paragraph
- Preferences — Character
- Preferences — Trapping
- Preferences — Color Manager
- Preferences — Layers
- Preferences — Full Res Preview
- Job Jackets dialog box
- Check Out License dialog box
- Creating URL requests
- Modifying layouts with XML
- Using SSL
- QuarkXPress Server XTensions software
- Telegraph XTensions software
- QuarkXPress Server Manager
- Understanding QuarkXPress Server Manager
- Working with QuarkXPress Server Manager
- Starting QuarkXPress Server Manager
- Request handler binding
- Configuring QuarkXPress Server instances
- Managing the cache
- Managing logs
- Controlling load balancing
- Using a proxy server
- Generating automatic e-mail messages
- Using other global settings
- Saving a server configuration
- Exporting a server configuration
- Using custom error messages
- Sending requests from a browser
- Glossary
- Legal notices
- Index
Quark License Administrator
To prevent unauthorized use, QuarkXPress Server requires the presence of a Quark® License
Administrator (QLA) server to launch. QuarkXPress Server follows the configuration and
control rules that are enforced by QLA. For more information about QLA, see the QLA
documentation included with QuarkXPress Server.
Master-renderer environment
Requests for project renders are stored in a connection queue. The requests in the rendering
queue can be processed by a single QuarkXPress Server application, or by a master
QuarkXPress Server application and several renderers (additional instances of
QuarkXPress Server). The master QuarkXPress Server application launches the available
number of renderers and then passes the requests in the connection queue to those
renderers as they become available. The number of renderers available for launch is
determined by the number of licenses available from the QLA server.
The master QuarkXPress Server process and all of the renderers it launches share the
following elements:
• The same application preferences (each renderer has its own preferences files, but
QuarkXPress Server keeps them synchronized)
• The same document cache in memory
• The same memory cache
• The same server XTensions modules (a separate instance of each XTensions module runs
with each renderer)
• The same server document pool (if defined in the QuarkXPress Server preferences or if a
document provider is used in place of the document pool)
If a renderer unexpectedly quits, the master QuarkXPress Server restarts the renderer
without requiring any action from you.
Changing logging levels in "log4j.xml"
You can change the logging levels for QuarkXPress Server. Options include ERROR, INFO,
WARN, DEBUG, and TRACE.
•
ERROR = includes messages that indicate disrupted and failed requests.
•
INFO = includes messages that indicate the state of services.
•
WARN = includes non-critical service error messages
•
DEBUG = includes messages that indicate server resource usage.
•
TRACE = includes messages according to activity related to requests.
Refer to Java documentation for more information about logging levels.
To change logging levels:
A GUIDE TO QUARKXPRESS SERVER 9.0 | 11
GETTING STARTED WITH QUARKXPRESS SERVER