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
• Information about events (such as alerts) that occur during the render-request process
• Details about requests that were sent to a different QuarkXPress Server instance after the
first assigned QuarkXPress Server instance was unable to process the request
Within the logs, each QuarkXPress Server instance is identified by its IP address and port
number.
You can export log files in XML (Extensible Markup Language) or comma-separated values
(CSV) format. For more information, see "Exporting log files"
Caching
To increase speed and efficiency, QuarkXPress Server Manager caches information in
memory. If the response to a render request, URL request, or file request is included in the
QuarkXPress Server Manager memory cache, QuarkXPress Server Manager returns the
response from the disk cache instead of sending the request to a QuarkXPress Server
instance. For more information, see "Managing the cache"
Requests that contain a binary parameter and multipart responses are not cached, regardless
of whether global caching or command-specific caching is enabled.
When the QuarkXPress Server Manager server application receives response data from a
QuarkXPress Server instance, QuarkXPress Server Manager can return that response directly
or write it as a file and return the file's URL. The second approach maximizes efficiency
for SOAP-based clients, because SOAP transfers binary data very slowly. Cached response
files have names that begin with "TMP_", and they are removed when they reach the age
specified in the cache settings (see "Managing the cache"). QuarkXPress Server Manager uses
the cache file this way regardless of whether caching is turned on or off; however, you can
override this behavior by setting the responseasurl parameter to false for every request.
Web services
QuarkXPress Server Manager provides a Web services interface that makes it easy for
developers to create applications that use QuarkXPress Server. This Web services interface
provides the same functionality that is available through the QuarkXPress Server HTTP
interface. For more information about the Web services interface, see the QuarkXPress Server
Web Integration Guide.
Working with QuarkXPress Server Manager
The general process for using QuarkXPress Server Manager is as follows:
1
Install QuarkXPress Server Manager software.
2
Launch one or more QuarkXPress Server instances on your network.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 53
QUARKXPRESS SERVER MANAGER