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
3
Create a new line containing the unique custom error code you defined in step 2. Follow
the custom error code with a tab and then enter the custom text to be returned for that
error.
4
Save and close the file.
This change will not take effect until you quit and restart the QuarkXPress Server Manager
server application.
Sending requests from a browser
Like QuarkXPress Server, QuarkXPress Server Manager lets you send requests from a Web
browser. This capability helps to ensure that you need to make only minimal changes
when you update an application so that it sends requests to a QuarkXPress Server Manager
server instead of a QuarkXPress Server instance.
Assume that a QuarkXPress Server instance expects requests in the following format:
http://[QXPServer]:[port]/[request]?[request_parameters]
If this is the case, a QuarkXPress Server Manager server will expect requests in the following
format:
http://[QXPSManagerServer]:[port]/qxpsm/request/[request]?[request_parameters]
In other words, a QuarkXPress Server Manager server accepts requests in a format that is
similar to the request format used with a QuarkXPress Server instance. That means you
can get the benefits of QuarkXPress Server Manager without having to completely rewrite
your applications.
Additional parameters
In addition to request-specific parameters, QuarkXPress Server Manager accepts the
following request parameters. These parameters can be submitted in the standard
QuarkXPress Server GET format joined by an ampersand (&) with the other parameters in
the body of the request.
•
qxpsm_bypassfileinfo: When QuarkXPress Server Manager receives a request, it executes
a fileinfo request on the document to get the document's size and last-modified date
and time. These values are used for load balancing and for determining whether to serve
the document from the cache. If the value of this parameter is set to true, the fileinfo
request is not made, file size is considered to be zero for load-balancing purposes, and the
document in the cache is considered to have changed.
•
qxpsm_context: Set this value if you need to use it in a custom load balancer.
•
qxpsm_maxtries: This parameter lets you specify a maximum number of retries for a
specific request. If this parameter is absent or set to 0, the global maximum retries value
is used. To disable maximum retries for a request, use the value –1.
•
qxpsm_password: The value of this parameter, if supplied, is used as the "Admin Password"
value when the request is forwarded to a QuarkXPress Server instance.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 73
QUARKXPRESS SERVER MANAGER