You do not need to read this guide from cover to cover. Instead, use this guide to quickly
look up information, find out what you need to know, and proceed with your work. Use
the detailed table of contents at the beginning of the guide to find information quickly.
What we're assuming about you
In writing this guide, we assume that you are familiar with your computer and know how
to:
ABOUT THIS GUIDE
• Launch an application
• Open, save, and close files
• Use menus, dialog boxes, and palettes
• Work within a networked computing environment
• Use the mouse, keyboard commands, and modifier keys
Consult the documentation provided with your computer or other resources if you need
more information in any of these areas.
Where to go for help
If you're new to QuarkXPress® Server, or if you want to explore one of its other longstanding
features, consult the following resources:
• A Guide to QuarkXPress Server
• The QuarkXPress Server Web Integration Guide
• Third-party books
• General books about desktop publishing
If your issues are at the system level — saving files, moving files, activating fonts, for
example — consult the documentation resources provided with your computer.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 5
ABOUT THIS GUIDE
Conventions
Formatting conventions highlight information to help you quickly find what you need.
• Bold type style: The names of all dialog boxes, fields, and other controls are set in bold
type. For example: "Click OK."
• References: In descriptions of features, parenthetical references guide you in accessing
those features. For example: "The Find/Change dialog box (Edit menu) lets you find and
replace text."
• Arrows: You will often see arrows (>), which map out the menu path to a feature. For
example: "Choose Edit > Style Sheets to display the Style Sheets dialog box."
• Icons: Although many tools and buttons are referenced by name, which you can see by
displaying ToolTips, in some cases icons are shown for easy identification. For example,
"Click the button on the Measurements palette to center text."
• Cross-platform issues: This application is quite consistent across operating systems. However,
some labels, buttons, key combinations, and other aspects of the application must differ
between Mac OS® and Windows® because of user interface conventions or other factors.
In such cases, both the Mac OS and Windows versions are presented, separated by a slash,
with the Mac OS version presented first. For example, if the Mac OS version of a button
is labeled Select, and the Windows version is labeled Browse, you are directed to "Click
Select/Browse." More complex cross-platform differences are mentioned in notes or
parenthetical statements.
6 | A GUIDE TO QUARKXPRESS SERVER 9.0
Getting started with
QuarkXPress Server
QuarkXPress Server lets you render QuarkXPress projects in a variety of formats.
QuarkXPress Server architecture
GETTING STARTED WITH QUARKXPRESS SERVER
The QuarkXPress Server architecture is shown in the following diagram.
QuarkXPress Server architecture diagram
A GUIDE TO QUARKXPRESS SERVER 9.0 | 7
GETTING STARTED WITH QUARKXPRESS SERVER
Understanding QuarkXPress Server
QuarkXPress Server lets you output customized QuarkXPress layouts in a variety of formats
— including JPEG, Portable Document Format (PDF), and PostScript®— from a centralized
QuarkXPress Server application. To send a request to a QuarkXPress Server application, all
you need to do is enter a URL into your Web browser's address field. For example, the
following URL instructs the QuarkXPress Server application named "QXPServer" to return
the file "MyProject.qxp" as a PDF file:
http://QXPServer:8080/pdf/MyProject.qxp
The QuarkXPress Server application receives these requests, renders (creates) the requested
projects in the requested formats, and then returns the rendered file to the client application
(in this case, the Web browser).
The format of QuarkXPress Server URL requests is described in detail in "Creating URL
requests" and in the QuarkXPress Server Web Integration Guide.
You can also create custom applications that communicate with a QuarkXPress Server
application using HTTP, Simple Object Access Protocol (SOAP), or another protocol. For
more information, see the QuarkXPress Server Web Integration Guide.
You can think of QuarkXPress Server as a special version of QuarkXPress that runs on a
server with the following main differences:
• Instead of accepting input from a keyboard and mouse, QuarkXPress Server accepts input
in the form of URLs and other types of requests.
• Instead of sending a project to a printer, QuarkXPress Server renders (creates) output in a
particular format and sends the rendered file to a client.
Server templates and static projects
QuarkXPress Server can open, render, and serve two types of projects:
• Static projects are QuarkXPress projects that can be rendered and served as-is in a variety
of formats by the QuarkXPress Server application. For example, you might make a product
manual available as a static project and allow customers to download that manual in a
variety of formats.
• Server templates are QuarkXPress projects that can be manipulated by the QuarkXPress Server
application before being rendered and served. For example, you might make a sales piece
available as a server template so that each person who downloads it receives a personalized
copy.
QuarkXPress Server can open QuarkXPress documents, projects, and templates created in
any language edition of QuarkXPress 5.0 or later. QuarkXPress Server can save and export
projects in QuarkXPress 8.x and QuarkXPress 9.x format.
8 | A GUIDE TO QUARKXPRESS SERVER 9.0
GETTING STARTED WITH QUARKXPRESS SERVER
The document pool
QuarkXPress Server reads server templates and static projects from a directory called the
document pool. The document pool can be any directory that is available to
QuarkXPress Server through a file system or an FTP server. You can use any of the following
methods to place files in the document pool:
• Drag the files to the document pool directory.
• Use the Add Files command in the Document Pool screen of the QuarkXPress Server Web
interface.
• Upload the files using FTP to the document pool directory.
• Use Telegraph XTensions® software to upload the files to the document pool from within
QuarkXPress. (For more information about Telegraph XTensions software, see "Telegraph
XTensions software.")
For more information about the document pool, see "The QuarkXPress Server user interface."
QuarkXPress Server can also serve documents from a database, a content management
system, or other sources. Collectively, the document pool and any other source of files to
be served are referred to as document providers.
Projects and layouts
QuarkXPress projects can contain one or more layouts, and only one layout can be rendered
at any given time. If you do not specify a layout when you send a rendering request,
QuarkXPress Server renders the first layout in the project.
Job Jackets and resources
In QuarkXPress, resources are things such as style sheets, colors, H&Js, output styles, and
item styles. Resources are stored in a Job Jackets structure, which can be either embedded
in a project or stored in a separate Job Jackets file.
QuarkXPress Server uses a default Job Jackets file to make a default set of resources available
to all projects handled by QuarkXPress Server, regardless of whether they are included in
the projects and articles you render. You can update this file in two ways:
• Using the QuarkXPress Server Web interface. For more information, see "Job Jackets dialog
box."
•
Using request handlers. For more information, see jobjacket and updateprefsfromjj
the QuarkXPress Server Web Integration Guide.
Once you've downloaded the default Job Jackets file, you can update its resources using
QuarkXPress. For more information, see "Job Jackets" in A Guide to QuarkXPress.
The location of the default Job Jackets file is stored in the QuarkXPress Server preferences
folder. For more information, see "QuarkXPress Server preferences."
A GUIDE TO QUARKXPRESS SERVER 9.0 | 9
GETTING STARTED WITH QUARKXPRESS SERVER
Caching
To maximize efficiency, QuarkXPress Server uses cached versions of all rendered projects
whenever possible. You can configure projects so that they are never cached, so that they
are cached for a particular amount of time, or so that they are rendered every time they
are served.
QuarkXPress Server preferences
When you launch QuarkXPress Server, the application creates preferences files that are
functionally and structurally equivalent to the preferences files created by QuarkXPress.
These preferences files reside in the QuarkXPress Server "Preferences" folder.
QuarkXPress Server also creates a "QuarkXPress Server.prf" file in the "Preferences" folder.
This file contains preference settings that are specific to QuarkXPress Server.
QuarkXPress Server uses these preferences the same way QuarkXPress uses them. If an
XTensions module creates a project in QuarkXPress Server, that project draws its settings
from the QuarkXPress Server preferences just as a new QuarkXPress project draws its settings
from the QuarkXPress preferences.
Preferences files are stored in the following locations:
•
Mac OS: [User]/Library/Preferences/Quark/QuarkXPress Server Renderer
9/
• Windows 2003 and Windows XP when running normally or under a domain user:
C:\Documents and Settings\[user name]\Application Data\Quark\QuarkXPress
Server Renderer 9
• Windows 2003 and Windows XP when running as a service under a local user:
C:\Documents and Settings\Default User\Application
Data\Quark\QuarkXPress Server Renderer 9\
• Windows 2008, when QuarkXPress Server is running as a service under the "local system
user" account: C:\ProgramData\Quark\QuarkXPress Server Renderer 9\
• Windows Vista, when QuarkXPress Server is running as a service under the "local system
Understanding QuarkXPress Server XTensions software
QuarkXPress Server ships with a collection of XTensions software that adds capabilities to
QuarkXPress Server. For example, PDF Export XTensions software lets QuarkXPress Server
serve content in PDF format; Modifier XTensions software lets you retrieve, manipulate,
and reconstruct XML representations of projects; and QuarkCopyDesk® Renderer XTensions
software lets you create QuarkCopyDesk articles. Telegraph XTensions software works with
QuarkXPress to allow designers to name boxes in template files so that those boxes can
be addressed by URLs.
For more information about XTensions software included with QuarkXPress Server, see
"QuarkXPress Server XTensions software" and "Telegraph XTensions software."
The QuarkXPress Server XTensions API
In addition to the XTensions modules included with QuarkXPress Server, developers can
create custom XTensions software that add features. The complete server XTensions
Application Programming Interface (API) documentation is available in the
QuarkXPress Server XTensions Developer's Kit (XDK).
As of version 8.0, the QuarkXPress Server XDK is Unicode-compliant.
The QuarkXPress Server XDK lets you create XTensions modules that provide the following
abilities:
• The ability to register request handlers
12 | A GUIDE TO QUARKXPRESS SERVER 9.0
GETTING STARTED WITH QUARKXPRESS SERVER
• The ability to register project providers
• The ability to register new render formats
• The ability to add items to the list of response properties, cookies, and HTTP header items
• The ability to log messages in log files
• The ability to initiate a new transaction to be processed by the server
• The ability to completely control how projects are processed by the server
In addition, QuarkXPress Server XTensions software can register for the following basic
callbacks:
• Pre-processing
• Content loading
• Layout modification
• Post-processing
• Removing slugs while running the QuarkXPress project renderer
• Analyzing the server after a transaction is complete
• Pre- and post-transaction callback
Configuring QuarkXPress Server for launch
To configure QuarkXPress Server prior to launch, open the file [QuarkXPress Server
application folder]/conf/ServerApp.properties folder) and modify it as follows:
•
To make the server run without loading any network interface, use the -nonetwork option
with the qxpservercore.serverRendererParameters. In this mode, the only
transactions a server can run are those passed to it by another process.
• To control whether renderers are monitored, set
qxpservercore.monitorrenderers.value to true or false.
• To specify the query interval for monitoring renderers, set
qxpservercore.monitorrenderers.queryinterval.value to a value in seconds.
• To specify the number of retries for monitoring renderers, set
qqxpservercore.monitorrenderers.noofretries.value to an integer. If a renderer
process has been attempting to fulfill a request for the specified number of retries (with
the specified query interval in seconds between retries), the renderer monitor recyles that
process.
• To control how many renderers the master process launches, specify a number for
qxpserver.subrenders. Note that the number of renderers you can launch depends on
your license.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 13
GETTING STARTED WITH QUARKXPRESS SERVER
Launching QuarkXPress Server
On Windows, you can install QuarkXPress Server as an application or as a service (Quark
recommends that you always run it as a service). On Mac OS, QuarkXPress Server always
runs as an application.
If you install QuarkXPress Server on Windows as an application, you can launch it using
the Start menu or by double-clicking the "ServerStartup.bat" in the QuarkXPress Server
application folder.
If you want to launch QuarkXPress Server as an application on Windows Server 2008,
Windows Vista, and Windows 7, Quark recommends executing "ServerStartup.bat" as an
administrator.
For information on launching QuarkXPress Server in a separate Tomcat installation, see
"Deploying QuarkXPress Server externally" in the QuarkXPress Server ReadMe.
QuarkXPress Server offers a browser-based user interface instead of a conventional user
interface.
Quitting QuarkXPress Server
To quit QuarkXPress Server on Mac OS, press Control+C.
To quit QuarkXPress Server on Windows, press Control+C or double-click the
"shutdown.bat" file in the QuarkXPress Server application folder.
14 | A GUIDE TO QUARKXPRESS SERVER 9.0
THE QUARKXPRESS SERVER USER INTERFACE
The QuarkXPress Server user interface
QuarkXPress Server offers a browser-based user interface instead of a conventional user
interface. This chapter describes that interface and explains how you can use it to configure
and customize your QuarkXPress Server application and manage your server XTensions
modules.
To view the QuarkXPress Server User Interface, launch a Web browser and enter the URL
http://[server]:[port]/qxpsadmin (where [server] is the IP address or domain
name of the server and [port] is the TCP/IP port on which the server is running). If the
server has realm verification enabled, you will be asked to enter your user name and
password.
Navigation pane
The navigation pane on the left side of the has two areas. The Server Information area
lets you view server information and the transaction log, and the Document Pool area
lets you view the contents of the document pool. You can collapse and expand this pane
with the button at the right end of the Navigation Pane header.
If you click Server Information, the Status Monitor screen displays. The fields in the top
area provide information about the server. The icons in the area below represent the
renderers that are currently running and show which requests are being processed by each
renderer in real time. This screen also shows how many active and idle renderers there
are.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 15
THE QUARKXPRESS SERVER USER INTERFACE
Status Monitor screen
If you click Transaction Log, the Logs screen displays the current transaction log. To
download the active log, including recent crash reports, click Download Logs at the top
of the Logs header.
If you click Show XTensions Information, the XTensions Information screen displays,
allowing yout o view the status of all installed XTensions modules.
If you click Document Pool, the document pool screen displays.
Document Pool screen
To add a file, click Add Files in the header. If you add multiple files at one time, you can
create a folder to put them all into by entering the folder name in the Folder film.
16 | A GUIDE TO QUARKXPRESS SERVER 9.0
THE QUARKXPRESS SERVER USER INTERFACE
Document Pool screen
To delete a file, check its box and then click Delete Files.
To search for a file or folder, use the search field in the header.
To preview a file, Control+click/right-click the file and choose Preview.
To get a file's relative path, double-click the file name.
Administration menu
The administration menu lets you manage QuarkXPress Server.
You do not have to restart the server in GUI mode to set preferences.
General Preferences dialog box
The General Preferences dialog box (Administration > Preferences > General) lets you
set preferences that are not related to rendering. It includes the tabs described in the
following topics.
You can also set general preferences using the setprefs request handler. For more
information, see the QuarkXPress Server Web Integration Guide.
General Preferences — Server
The Server tab (Administration > Preferences > General > Server) includes the following
controls.
Use the Document Root Folder field to specify the location of the document pool.
Putting the document pool on a network connected drive is not recommended, because
this negatively impacts the performance of QuarkXPress Server.
Use the Allow Memory Caching check box to control whether memory is cached.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 17
THE QUARKXPRESS SERVER USER INTERFACE
Use the Max Memory Cache Size field to specify the maximum memory size allocated
to the cache memory. Valid values are from 10MB to 1024MB.
Use the Force Served Documents Closed check box to control whether QuarkXPress Server
closes projects from the document pool after it renders them, regardless of the Telegraph
XTensions software setting. Uncheck this box to keep such projects open on the server.
Use the Default Renderer Type drop-down menu to specify the default rendering format
for the server.
• EPS Document: Returns an Encapsulated PostScript (EPS) file.
• JPEG: Returns a JPEG file.
• PDF: Returns a PDF file.
• PNG: Returns a Portable Network Graphics (PNG) file.
• PostScript: Returns a PostScript file.
• QCDDOC: Returns a QuarkCopyDesk article.
• QuarkXPress Document: Returns a QuarkXPress project.
• Raw Custom: Returns a file in internal QuarkXPress format for use by server XTensions
software developers.
• RLE Raw Custom: Returns a file in internal QuarkXPress format (compressed using Run
Length Encoding) for use by server XTensions software developers.
• SWF: Returns a SWF (Flash) file.
Use the Scale field to specify the default scale percentage at which QuarkXPress Server
should render projects.
Use the Disable QXD Return check box to specify whether QuarkXPress Server can return
QuarkXPress projects to clients.
General Preferences — Log
The Log tab (Administration > Preferences > General > Log) includes the following
controls.
Use the Log Document Problems check box to specify whether to include problem
descriptions in transaction log files. The "Log" folder inside the QuarkXPress Server
application folder contains three log files:
• QuarkXPress Server Fatal Log.log: This log lists all fatal errors.
• QuarkXPress Server Log.log: The log for the Java process. This log contains source
code-level logging information that can be useful in troubleshooting.
• QuarkXPress Server Transaction Log.log: This log lists all transactions and all errors.
Detailed application logging is enabled for these log files only if it is enabled in the
"log4j.xml" file.
18 | A GUIDE TO QUARKXPRESS SERVER 9.0
THE QUARKXPRESS SERVER USER INTERFACE
To log detailed transaction timing data, check Log Timing Data.
Logged problems include the following:
• Missing Fonts: If fonts are missing from a project that has been requested for rendering,
a one-line description of each missing font is added to the error log. If QuarkXPress Server
receives a request to render a project and does not have access to the fonts required by the
project, it uses the fonts specified in the Fonts tab of the Preferences dialog box
(Administration > Preferences > General). If these fonts are also unavailable,
QuarkXPress Server substitutes Helvetica (Mac OS) or Arial (Windows). This behavior is
the same as it is in QuarkXPress.
• Missing Pictures
• Missing SXTs: If a required server XTensions module is missing when a rendering request
is received, a one-line description of each missing module is added to the error log. If the
name of the missing module is not returnable, the XTensions module ID number is
returned.
• Text Encoding/Character Set Problems: If text is sent to a text box in the template and
the system does not have access to the correct font glyph, the issue is logged. The log data
indicates the character set that the system attempted to convert. For example, the log
entry might show that a request for Japanese characters was sent to an English project.
Information about missing fonts and missing pictures is also recorded in the
"QuarkXPressServerRenderer.log" file. This file also contains detailed timing information,
including the transaction UID for each transaction. This log file can be found here:
•
Mac OS: [drive]/Users/[user name]/Library/Logs/Quark
•
Windows: C:\Users\talyn\AppData\Quark\Log
To download all logs to a non-server computer, click Show Transaction Log in the
QuarkXPress Server Web interface, then click Download Logs on the upper right.
General Preferences — Email
QuarkXPress Server can automatically notify someone by e-mail when the checked-out
QLA license is about to expire. The Email tab (Administration > Preferences > General
> Email) lets you specify where such e-mail messages should be sent.
Use the Server field to specify the domain name or IP address of the e-mail server that
QuarkXPress Server should use to send messages (for example, mail.quark.com).
Use the Port field to specify the port number of the e-mail server that QuarkXPress Server
should use to send messages. Valid values are from 0 to 255.
Use the From to specify the source e-mail address the QuarkXPress Server application
should use to send messages (for example, QXPSserver1@quark.com).
Use the To to specify the e-mail address to which the QuarkXPress Server application
should send messages (for example, QXPServerAdmin@quark.com).
A GUIDE TO QUARKXPRESS SERVER 9.0 | 19
THE QUARKXPRESS SERVER USER INTERFACE
General Preferences — Authentication
The Authentication tab (Administration > Preferences > General > Authentication)
includes the following controls.
Check Authenticate For Admin Requests to enable the Username and Password fields.
These fields let you control access to administrative parameters and features. You can enter
up to 32 characters.
Renderer Preferences dialog box
Use the renderer Preferences dialog box (Administration > Preferences > Renderer) to
set up default preferences for use when projects are created in QuarkXPress Server. It
includes the tabs described in the following topics.
Many of these preferences come into play only when you create a project in QuarkXPress
Server, either using a construct request or through a request handled by a custom
QuarkXPress Server XTensions module.
You can also set renderer preferences using the setrendererprefs request handler. For
more information, see the QuarkXPress Server Web Integration Guide.
In versions of QuarkXPress Server prior to 9.0, these resources were accessed through the
Document Controls submenu.
Preferences — Display
The Display pane (Administration > Preferences > Renderer > Display) includes the
following controls.
Use the Color TIFFs drop-down list to specify the color depth of screen previews created
for color TIFFs when they are imported.
Use the Gray TIFFs drop-down list to specify the resolution of screen previews created for
grayscale TIFFs when they are imported.
Choose a profile that corresponds to your monitor from the Monitor Profile drop-down
menu, or choose Automatic. Profiles can be placed in the "Profiles" folder in the
Some URL parameters require Boolean arguments. For such parameters, valid values include
1 or 0, true or false, y or n, and yes or no.
You can also send requests to QuarkXPress Server using the HTTP GET and POST protocols
and using XML with XSLT. For more information about these approaches, see the
QuarkXPress Server Web Integration Guide.
Understanding QuarkXPress Server namespaces
QuarkXPress Server namespaces differentiate among types of requests that are otherwise
identical. For example, consider the following three URLs:
http://QXPServer:8080/project1.qxp
http://QXPServer:8080/pdf/project1.qxp
http://QXPServer:8080/postscript/project1.qxp
These requests are identical, except each uses a different namespace (in italic). (The first
request does not specify a namespace, but this simply means the project is to be rendered
using the server's default render type.)
Namespaces can be used to determine the format in which a rendered project is returned,
as indicated above, but they can also be used to direct a request to XTensions software
that performs other functions. For example, if you use Modifier XTensions software's xml
namespace, Modifier XTensions software can return an XML representation of the project.
Looking up a namespace
The QuarkXPress Server Web Integration Guide lists the namespaces for every
QuarkXPress Server function. There is no single list of namespaces because some functions
do not require a particular namespace or are available in multiple namespaces. To determine
which namespace you want to use:
Open the QuarkXPress Server Web Integration Guide.
1
Choose Complete API List from the QuarkXPress Server Functions menu at the top of
2
the page.
Click the link for the render type you want or the function you want to use. (The link
3
might be a dynamic publishing process, a renderer, or a request handler.) The page
corresponding to that render type or function displays.
Locate the Namespace row. If the render type or function has an associated namespace,
4
that namespace is listed here.
Third-party XTensions can add their own namespaces. For information about a third-party
namespace, see the documentation for the XTensions module that adds that namespace.
30 | A GUIDE TO QUARKXPRESS SERVER 9.0
Understanding QuarkXPress Server parameters
Parameters let you control the details of how a request is executed. For example, you can
use the page parameter to create a request that returns only the third page of a project:
http://QXPServer:8080/jpeg/project1.qxp?page=3
You can include multiple parameters in the same request; simply separate them with an
ampersand (&). For example, here's a new version of the above URL that returns page three
Replace 61399 with 61400 (or any port on which Tomcat will be listening for secure
5
connections).
Save and close "server.xml."
6
Open the "ServerApp.properties" file (in the "conf" folder) and enter the port number from
7
step 5 for qxpswebserver.port.
This change means QuarkXPress Server client applications can use HTTPS. For example,
the URL for a QuarkXPress Server user would be as follows: https://[server
name]:[port]/.
Enabling HTTP and HTTPS
To enable HTTP and HTTPS:
USING SSL
Open the "conf" folder in your QuarkXPress Server folder.
For more information, see the QuarkXPress Server Web Integration Guide.
PDF Filter XTensions software
PDF Filter XTensions software allows QuarkXPress Server to render a QuarkXPress project
as a PDF file. To render QuarkXPress projects as PDF files when PDF is not the
QuarkXPress Server default render type, use the PDF namespace, as follows:
QUARKXPRESS SERVER XTENSIONS SOFTWARE
http://[server]:[port]/pdf/[projectname]
For information about PDF preferences, see "Preferences — PDF." To take advantage of more
detailed preferences, create a PDF output style and use that output style when rendering
projects as PDF files.
For information about the parameters for exporting in this format, see the
QuarkXPress Server Web Integration Guide.
Modifier XTensions software
Modifier XTensions software lets clients perform all of the following tasks using XML:
• Modify the properties of pictures in a QuarkXPress project
• Modify the text in text boxes within a QuarkXPress project
• Modify the properties of text boxes and picture boxes in a QuarkXPress project
• Create and delete picture boxes and text boxes in a QuarkXPress project
• Import text or text strings into text boxes within a QuarkXPress project
• Import pictures into picture boxes within a QuarkXPress project
• Save modified QuarkXPress projects in any supported format to any location on the network
(and also in the QuarkXPress Server document pool)
• Create and delete pages
• Create and delete layers
A GUIDE TO QUARKXPRESS SERVER 9.0 | 39
QUARKXPRESS SERVER XTENSIONS SOFTWARE
• Move items within layers
• Create and delete tables
• Modify tables and their contents
• Create QuarkCopyDesk articles and components
• Create lines, anchored boxes, and Bézier boxes
• Create lists
• Group and ungroup boxes
• Divide layouts into sections
To use Modifier XTensions software, a client creates an XML file indicating the actions to
be taken and sends that XML file to the QuarkXPress Server application, where Modifier
XTensions software reads the XML and makes the requested changes. Clients can use a
single XML file or string to manipulate multiple documents and boxes.
For more specific information about Modifier XTensions software, and for the Modifier
DTD, see the QuarkXPress Server Web Integration Guide.
Modifier XTensions software supports both GET and POST functionality.
Modifier XTensions software supports XML containing code that uses Unicode UTF-8 and
UTF-16 encodings. Use the encoding attribute of the XML declaration to specify an
encoding, as you would with any other XML file.
Using Modifier XTensions software
To use Modifier XTensions software:
Create a QuarkXPress project. Note the IDs or names of any text and picture boxes you
1
want to manipulate.
Upload the project to the QuarkXPress Server document pool.
2
Create XML that describes the changes you want, as described in "Creating XML for Modifier
3
XTensions software."
Send the XML to the server in one of the following ways:
4
• Put the XML in a file on the server and then use a URL to point to the file, as follows:
http://server:port/namespace/path/projectname?modify=file:[absolute
path to XML file on server or relative path to XML file on server
relative to the document pool]
Clients can also send XML in the form of a POST request.
Creating XML for Modifier XTensions software
All XML used with Modifier XTensions software uses the Modifier DTD. This DTD is
documented in full in the QuarkXPress Server Web Integration Guide.
In general, the structure for addressing items in a particular layout is as follows:
<PROJECT>
<LAYOUT>
<ID NAME="[name of layout]">
<[Item being addressed]>
<[Parameters of item]>
</[Item being addressed]>
</LAYOUT>
</PROJECT>
For more information, see the QuarkXPress Server Web Integration Guide.
Layer XTensions software
QUARKXPRESS SERVER XTENSIONS SOFTWARE
You can use QuarkXPress Server Layer XTensions software to control the visibility of
specific layers in a rendered QuarkXPress project. You can also add layers, delete layers,
edit layer attributes, and control whether layers are rendered.
When you use the getdocinfo namespace, QuarkXPress Server returns information about
items on all of the layers in the QuarkXPress project, including layers that are not visible.
Clients can use the layer parameter to specify a layer (even a hidden layer) to be rendered.
For example, the URL http://QXPServer:8080/doc.qxp?layer=layer1 renders only
the layer named "layer1" in the project named "doc.qxp."
Clients can specify more than one layer in a single URL. For example, the URL
http://QXPServer:8080/doc.qxp?layer=layer1,layer2 renders the layers named
"layer1" and "layer2."
For information about layer preferences, see "Preferences — Layers." For information about
the parameters for this feature, see the QuarkXPress Server Web Integration Guide.
If Suppress Output is selected for a layer, QuarkXPress Server does not render that layer
when producing PDF, EPS, or PostScript files.
InteractiveDesignerSXT Server XTensions software
InteractiveDesignerSXT XTensions software allows QuarkXPress Server to render both Print
and Interactive layouts in QuarkXPress projects as SWF (Flash) files. If you render a Print
layout as an SWF file, you can use the right and left arrow keys to navigate between pages
in the SWF file.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 41
QUARKXPRESS SERVER XTENSIONS SOFTWARE
To render an Interactive layout in a QuarkXPress project as a SWF file when SWF is not
the QuarkXPress Server default render type, use the SWF namespace, as follows:
If you have edited the project since you last saved it, QuarkXPress prompts you to save
the project.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 47
TELEGRAPH XTENSIONS SOFTWARE
Upload Template dialog box
Choose a server from the Server drop-down menu. This drop-down menu includes the
2
servers listed in the QuarkXPress Server pane of the Preferences dialog box
(QuarkXPress/Edit menu).
If you specified a directory path for the server, that path automatically displays in the
3
Directory Path field. If you did not specify a directory path in the preferences, this field
remains blank. This path defaults to the document pool directory specified in
QuarkXPress Server.
If you are uploading to QuarkXPress Server, and you have configured that server to require
4
authentication, enter a valid user name and password in the User Name and Password
fields. (If the QuarkXPress Server application does not require authentication, leave these
fields empty.)
To specify authentication information for a QuarkXPress Server application, choose
Administration > Preferences > General in the QuarkXPress Server Web interface, check
Authenticate for Admin Requests box and enter a user name and password.
To indicate which protocol to use for uploading, click HTTP or HTTPS.
5
Enter the port for QuarkXPress Server in the Port field.
6
To collect and upload fonts used by the project, check Fonts.
7
To collect and upload pictures used by the project, check Pictures. This will upload high-
8
or low-resolution pictures that are linked to or embedded in the project.
If picture files are missing or have been modified since they were imported into the project,
an alert displays. For more information about missing or modified picture files, see
"Uploading missing or modified pictures."
48 | A GUIDE TO QUARKXPRESS SERVER 9.0
TELEGRAPH XTENSIONS SOFTWARE
Click OK.
9
If you check Fonts, an alert reminds you of possible restrictions regarding copying font
software. Click OK to continue uploading the project with the fonts, click Do Not Collect
Fonts to upload the project without the fonts, or click Cancel to stop the upload.
The Upload Status window displays a progress bar that displays the status of the upload.
When the upload is complete, a message notifies you whether the project uploaded
successfully.
Uploading missing or modified pictures
If the picture files linked to the project are missing or have been modified since they were
imported into the project, an alert displays at upload. Choose from among the following
options:
• To continue the upload with low-resolution versions of the pictures, click OK.
• To stop the upload, click Cancel.
• To locate missing pictures or update modified pictures, click List Pictures.
If you click List Pictures, the Missing/Modified Pictures dialog box displays:
• To view a picture in the project, select the picture's name in the list and click Show.
• To locate a missing picture file, select it and click Update. The Find dialog box displays.
Locate and choose the appropriate file, and then click Open.
• To update a modified picture file, click Update. Every instance of the modified picture in
the project is updated.
• When OK displays in the Status column for each picture, click Collect. If the status of
any picture is still Missing or Modified when you click Collect, that picture file will not
be uploaded, but a low-resolution preview will remain in the project.
• To stop the upload and return to the project window, click Cancel.
A GUIDE TO QUARKXPRESS SERVER 9.0 | 49
QUARKXPRESS SERVER MANAGER
QuarkXPress Server Manager
QuarkXPress Server Manager is a server application that efficiently routes rendering requests
in an environment that uses one or more QuarkXPress Server applications.
QuarkXPress Server Manager uses load-balancing methods to determine which server in
the QuarkXPress Server pool can best process a document request, and uses caching to
improve speed and efficiency. QuarkXPress Server Manager also provides failsafe capability
by reliably resubmitting failed requests, either to the same QuarkXPress Server instance
or to a different one (depending on the error message returned by the server instance).
QuarkXPress Server does not require QuarkXPress Server Manager, but a QuarkXPress Server
Manager server can coordinate multiple QuarkXPress Server applications so that they work
together with maximum speed, reliability, and availability.
QuarkXPress Server Manager also provides a Web services interface that allows developers
to use QuarkXPress Server features without having to use the HTTP interface.
To configure a QuarkXPress Server Manager server application, you must use the
QuarkXPress Server Manager client application. The topics below explain how the
QuarkXPress Server Manager client application works and provide examples for using it.
Understanding QuarkXPress Server Manager
Before you begin, take time to review the topics below so that you understand how this
chapter is structured and how you can get the most out of it.
Load balancing
Load balancing ensures that each rendering request is sent to a server that is likely to be
able to handle it quickly. QuarkXPress Server Manager lets you use choose from three
load-balancing settings:
• Random: Each rendering request is sent to a random server.
50 | A GUIDE TO QUARKXPRESS SERVER 9.0
QUARKXPRESS SERVER MANAGER
• Round robin: Requests are sent to servers in a set order. For example, if you have three
QuarkXPress Server instances and QuarkXPress Server Manager receives ten rendering
requests, the requests are distributed as follows:
QuarkXPress Server instance usedRequest
11
22
33
14
25
36
17
• Dynamic: The QuarkXPress Server Manager server considers file size and throughput
requirements for each request. For example, assume the following series of requests is sent
to QuarkXPress Server Manager in an environment that uses two QuarkXPress Server
instances:
SizeRequest
8MB1
1MB2
2MB3
The first request is assigned to server #1, and the second request is assigned to server #2.
When the third request arrives, QuarkXPress Server Manager checks the loads that the two
servers are already handling and assigns the task to the server with the smallest load — in
this case, server #2.
If a request fails because a server stops responding or because of a "File Not Found" error,
QuarkXPress Server Manager does not resubmit that request to that server.
The Dynamic setting is typically the most efficient setting for environments with more
than one QuarkXPress Server instance.
For information about choosing a load-balancing setting, see "Controlling load balancing."
Developers can implement their own load-balancing systems; for more information, see
the QuarkXPress Server Web Integration Guide.
Request timeout interval
QuarkXPress Server Manager attempts to send each request to a QuarkXPress Server instance
that can promptly handle that request. However, in some situations a QuarkXPress Server
A GUIDE TO QUARKXPRESS SERVER 9.0 | 51
QUARKXPRESS SERVER MANAGER
instance might be unable to process a request in a reasonable amount of time (for example,
if the server is working on a large rendering job, or if the server computer has stopped
functioning). If you specify a certain period of time as the request timeout interval,
QuarkXPress Server Manager will wait for the response until that period of time elapses,
and then send the request to a different QuarkXPress Server instance. This ensures that a
request does not get "lost" if its assigned QuarkXPress Server instance does not become
available promptly.
For information about setting a request timeout interval, see "Using other global settings."
If a client request fails despite being sent to multiple QuarkXPress Server instances,
QuarkXPress Server sends the end user a customizable error message or exception so that
the end user can appropriately handle the failure. A QuarkXPress Server Manager server
can also automatically send e-mail to an administrator in the event of a problem; for more
information, see "Generating automatic e-mail messages."
Determining QuarkXPress Server instance availability
QuarkXPress Server Manager uses two methods to determine the availability of a
QuarkXPress Server instance: ping and ping document.
Ping
QuarkXPress Server Manager periodically sends a ping request to all of its QuarkXPress Server
instances to determine whether they are available. Ping requests use the following format:
http://[Server]:[Port]/getprocessid
Ping document
QuarkXPress Server Manager periodically sends a render request to all of its QuarkXPress
Server instances to determine whether they can render a document. Ping document requests
use the following format:
http://[Server]:[Port]/[PingDocumentName.qxp]
You can specify the document to be used for this render request. To avoid long ping
document rendering times, use a simple document.
You can specify the interval between pings and ping documents in the Other Settings
pane in the Global Settings pane of the QuarkXPress Server Manager window (see "Using
other global settings").
Logging
QuarkXPress Server Manager logs all interactions with QuarkXPress Server instances.
QuarkXPress Server Manager log files contain the following information:
• Render requests
• QuarkXPress Server responses
52 | A GUIDE TO QUARKXPRESS SERVER 9.0
QUARKXPRESS SERVER MANAGER
• 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:
Install QuarkXPress Server Manager software.
1
Launch one or more QuarkXPress Server instances on your network.
2
A GUIDE TO QUARKXPRESS SERVER 9.0 | 53
QUARKXPRESS SERVER MANAGER
Launch the QuarkXPress Server Manager Console server application (see Starting the Manager
3
server application").
Launch the QuarkXPress Server Manager client application (see Starting the Manager
4
client application").
Using the QuarkXPress Server Manager client application, connect to a QuarkXPress Server
5
Manager server (see "Starting QuarkXPress Server Manager").
Use the Manage QuarkXPress Server pane of the QuarkXPress Server Manager window
6
to add QuarkXPress Server instances and specify information about those servers (see
"Configuring QuarkXPress Server instances").
Configure logging options, caching options, a load-balancing method, proxy server settings,
7
automatic e-mail settings, and various other settings in the Global Settings pane of the
QuarkXPress Server Manager window (see "Controlling load balancing," "Using a proxy
server," "Generating automatic e-mail messages," and "Using other global settings").
As necessary, export and delete logs using the Manage Logs pane of the
8
QuarkXPress Server Manager window (see "Managing logs").
As necessary, delete cache items and clear the QuarkXPress Server Manager server cache
9
using the Manage Cache pane of the QuarkXPress Server Manager window (see "Managing
the cache").
Starting QuarkXPress Server Manager
You can use one copy of the QuarkXPress Server Manager client application to administer
multiple copies of the QuarkXPress Server Manager server application (but only one at a
time). Each QuarkXPress Server Manager server can handle multiple QuarkXPress Server
instances.
QuarkXPress Server Manager diagram
54 | A GUIDE TO QUARKXPRESS SERVER 9.0
QUARKXPRESS SERVER MANAGER
Starting the Manager server application
To launch the QuarkXPress Server Manager server application:
•
Mac OS: Open the QuarkXPress Server Manager/Server folder inside the applications
folder and double-click "QXPSMServerStart.command."
• Windows (if you have not installed QuarkXPress Server Manager as a service): Choose Start >
Programs > QuarkXPress Server Manager 9 > Start QuarkXPress Server Manager.
Alternatively, open the "Server" folder in the QuarkXPress Server Manager application
folder and double-click the "QXPSMServerStart.bat" file as an admnistrator.
You can access API documentation in HTML format by navigating to
http://[server]:[port], where [server] identifies the computer on which
QuarkXPress Server Manager is running and [port] identifies the port it is running on.
Starting the Manager client application
To launch the QuarkXPress Server Manager client application:
•
Mac OS: Open the QuarkXPress Server Manager/Client folder inside the applications
folder and double-click the "QuarkXPress Server Manager Client" icon.
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
•
qxpsm_responseasurl: By default, QuarkXPress Server Manager writes responses as
temporary files in the cache folder and returns a URL to the client. This approach prevents
the performance degradation that can result from sending binary data using SOAP. However,
you might want QuarkXPress Server Manager to return the response directly if you are
creating an application that processes that response (simple or multipart) with its own
logic. To make QuarkXPress Server Manager send a response to the browser rather than
the URL of the temporary files in the cache, set this value to false. (Note that setting this
value to false might result in decreased performance.)
•
qxpsm_responseredirect: If you use servlet methodology to send a request to
QuarkXPress Server Manager with qxpsm_responseasurl=true, QuarkXPress Server
Manager returns a frameset page with one or more frames. If the response is not multipart,
the frameset contains a single page with a URL pointing to a response file in the temporary
cache. This can be problematic if, for example, you want to use the returned URL as an
image link in an HTML page. In such situations, submit the request with both
qxpsm_responseredirect=true and qxpsm_responseasurl=true. If you do this,
QuarkXPress Server Manager returns the URL of the rendered file in the temporary cache
instead of returning a frameset page. Note, however, that if the request results in a multipart
response (such as the response returned by the boxes parameter), QuarkXPress Server
Manager ignores the qxpsm_responseredirect=true parameter and returns the frameset
page.
•
qxpsm_servername: By default, the target QuarkXPress Server instance for each request
is determined by the QuarkXPress Server Manager server's load-balancing system. To send
a request to a specific QuarkXPress Server instance, set this parameter to the name or IP
address of that QuarkXPress Server instance. Note that if you use this parameter with an
IP address, you must also submit the port number using the qxpsm_serverport parameter.
•
qxpsm_serverport: If you use the qxpsm_servername parameter with an IP address,
supply the corresponding port number as this parameter's value.
•
qxpsm_timeout: This parameter lets you specify a timeout (in milliseconds) for a specific
request. If this parameter is absent or set to 0, the global timeout value is used. To disable
timeout for a request, use the value –1.
•
qxpsm_usecache: If you set this value to false, the request will be rendered regardless of
whether it is cached and regardless of whether caching is enabled at the global level.
•
qxpsm_username: The value of this parameter, if supplied, is used as the "Admin User"
value when the request is forwarded to a QuarkXPress Server instance.
•
qxpsm_userpassword: The value of this parameter, if supplied, is used as the "Admin
User" password when the request is forwarded to a QuarkXPress Server instance. Default
value is null, which means no password information. If this is not null, you must also
provide qxpsm_username.
74 | A GUIDE TO QUARKXPRESS SERVER 9.0
Glossary
Document pool: The document pool contains the projects that are available for rendering.
By default, the document pool is a collection of discrete files or folders in a specific,
identified folder located on the local server or on a connected network drive. When some
type of external document provider (such as a content management system or database)
is used, projects are not stored in the local document pool.
Document provider: The document provider is the source for projects that
QuarkXPress Server renders. The most basic document provider is the local document
pool. Other document providers can be enabled through the creation of Server XTensions
software, which establish a virtual file system. Server XTensions software can register for
control of a specified range of the QuarkXPress Server namespace. When a project is
requested from this range, server XTensions software retrieves the file from the specified
source and hands it to the server. Examples of document providers include content
management systems such as a standard database,or a live data feed from an HTTP agent.
GLOSSARY
Layout: A layout is a sequence of same-sized pages in a QuarkXPress project. A project can
contain one or more layouts. A layout is functionally equivalent to a QuarkXPress document
in QuarkXPress 5 and earlier.
Project: A QuarkXPress project is a file created by QuarkXPress. A project can contain one
or more layouts.
Rendering: Rendering is the process of generating a file in a particular format (such as
JPEG, EPS, or PDF) from a QuarkXPress layout.
Rendering type: The rendering type is the format in which QuarkXPress Server can render
QuarkXPress layouts. Some rendering types, such as JPEG and PNG, can be displayed in a
Web browser, while others must be saved to the hard drive.
Server XTensions Software (SXT): Server XTensions software is XTensions software written
specifically for QuarkXPress Server. For more information, see the QuarkXPress Server
XTensions Developer's Kit.
Renderer: A renderer is a process launched by QuarkXPress Server to help process rendering
requests. Renderers reside on the same server as QuarkXPress Server and share the same
memory and preferences. When renderers are launched, QuarkXPress Server becomes a
load-balancing "master server," passing incoming requests to renderers for faster response