2020

Table Of Contents
USING QUARKXPRESS SERVER
Set the value of QXPSM_OUTPUT_DIR to the output location. For example:
QXPSM_OUTPUT_DIR= "c:\output"
Execute the file “Generate.command”/”Generate.bat”. The resulting output uses 3.
the following structure.
To use the generated artifacts: 4.
Copy the contents of [output location]/_server/conf to [QXPSM
application folder]/Server/conf .
Copy the contents of [output location]/_server/lib to [QXPSM
application folder]/Server/lib .
Restart QuarkXPress Server Manager.
Compatible client side web-service stubs, for both Java and .NET can be found
at [output location]/_client/stubs
Understanding ManagerSDK.xml
“ManagerSDK.xml” is used to generate client SDK classes for QuarkXPress Server
requests. Each element in “ManagerSDK.xml” corresponds to a request handler, a
render type, or an element in the schema.
A client SDK class is generated for each element in the XML. Each property in the
schema and each parameter of the request handler or render type also corresponds
to a unique element in the XML.
A Class variable is generated for each property, as follows.
<Class>: One element for each SDK class generated. The class generated is
derived from QRequest. Attributes are:
name: The name of the generated class.
namespace: The namespace recognized by QuarkXPress Server when this
request class is translated into a QuarkXPress Server request.
description: A description of the class. Unless this value is null, the
description forms the header of the generated class and is included in the
generated API docs.
alias: The alias to be used as an element name if this request class is
serialized to XML. For example, when the Project class is serialized to
XML, the element used is Project.
194 | A GUIDE TO QUARKXPRESS SERVER 2020