8.0

Table Of Contents
Overview
Welcome to the QuarkXPress® Server Web Integration Guide (WIG). The WIG describes the
QuarkXPress Server interface and includes sample applications that demonstrate how to build a solution
that integrates with QuarkXPress Server or QuarkXPress Server Manager.
Supported interfaces
The WIG describes two separate interfaces:
HTTP: Provides the ability to interact with the server using URLs that contain calls or point to
XML files that contain calls. Client applications can be written in any language that supports
HTTP requests.
Web services: Provides the ability to interact with the server via Web services using the
QuarkXPress Server Manager object model. Client applications can be written in Java™, .NET,
or any other programming language that can consume SOAP-based Web services.
Note:
If you want to develop a custom load balancer or a custom application in Java using the WIG Object
Model, JDK™ 1.5 is required.
Note:
If you want to use Web Objects in ASP.NET / Visual C#®, the .NET 1.1/2.0 framework with
development environment (Visual Studio®) is required.
The Dynamic Publishing Process (DPP)
Dynamic Publishing Process (DPP) is the process in which QuarkXPress Server opens a project, loads
content, modifies a layout, examines the project, converts data into a particular render type, and then
closes the project.
The process has the following different stages:
Pre-Processing Stage: During this stage an initial setup of the project is done, such as create style
sheets, color, or H&J rules.
Content Loading Stage: During this stage dynamic content is loaded into the boxes in the
QuarkXPress project.
Layout Modification Stage: QuarkXPress Server modifies the layout of the project during this
stage. For example, QuarkXPress Server changes the angle of the boxes by 30 degrees.
Post-Processing Stage: In this stage no modifications to the project are made. QuarkXPress
Server examines the constructed project and performs bookkeeping tasks.
WIG vs. XTensions® Developer Kit (XDK)
The WIG allows Web developers to build client-side applications that use the features available in
QuarkXPress Server. The XDK allows software developers to implement features that are not available
in QuarkXPress Server, such as server-side processing and application-specific services. Note that the
Page 1

Summary of content (304 pages)