Publishing PageSeeder data to print, the Web or both

Task config

The Universal Ant PS Config is used to centralize common configuration parameters and to maintain transparency about the config in use.


   <ps:config name="[name]" file="[file]">
     <entry key="[key]" value="[value]"/>


nameThe name of the config - set to "default" if not specified.No
fileThe path of a file containing the properties to load.No
load-defaultWhether to load the default properties from PageSeeder (only applicable if script is run within PageSeeder publisher) - default "true".No


Entries can also be specified individually using the inner element

<entry key="[key]" value="[value]">

Each entry will overwrite any existing one with the same name.


Simplest case:

<ps:config />

 Reading properties from file:

<ps:config file="" />

Named configuration:

<ps:config name="A" file="" />
<ps:config name="B" file="" />

Overridding file properties:

<ps:config file="" >
  <entry key="scheme" value="https"/>


The task will add a list of properties to the current project. Each property can be accessed using the following pattern: 


where [config] is the name of the config (if none was specified, "default" is used) and [property] is the name of the property.


Below are the names of properties created by the PS config. They correspond to the old ps-* Ant properties except where 'new property' is specified.

jsessionidthe user's jsessionid in PageSeeder
hostthe webSiteAddress from PageSeeder
portthe webSitePort from PageSeeder
servlet.prefixthe servletPrefix from PageSeeder
site.prefixthe sitePrefix PageSeeder
group.idid of group initiating the publish (e.g. 12)
group.namename of group initiating the publish (e.g. acme-demo)
group.folderpath of default group folder

/ps/acme/demo of default group folder with no site prefix

group.schemescheme of default group folder (e.g. https) - new property
group.hosthost of default group folder
group.portport of default group folder (e.g. 80)
group.templatestyle owner of group/default group for URI (e.g. acme) - previously ps-style-owner
custom.foldercustomFolder name from (e.g. acmedefault)
workingpath to local unique working folder for this group/document
working.rootpath to root for all local working folders
documents.rootpath to PageSeeder documents folder (only if Publish Engine is installed on PageSeeder server).
web.rootpath to the root for the ps-publisher webapp
engine.urlthe external URL used to contact the Publish Engine (e.g.
session.folderA unique folder name for the current PS user session to copy result files to (i.e. ${ps-webRoot}/session/${ps-sessionfolder} )

The following parameters are only passed when a Document is being published (not when a Group is being published and not when the document is in the Loading Zone):

uri.idURI id (e.g. 123)
uri.schemeURI scheme (e.g. http)
uri.hostURI host (e.g.
uri.portURI port (e.g. 80)
uri.pathURI path

/ps/acme/demo/minutes/2006-12-08.xml path without prefix

/acme/minutes/demo/2006-12-08.xml path without group prefix

uri.folderURI folder

/ps/acme/demo/minutes folder with /ps prefix

/acme/demo/minutes folder without group prefix

uri.filenameFilename (e.g.  2006-12-08.xml) without extension (e.g.  2006-12-08)
uri.extensionFile extension (e.g.  xml)
uri.document.typePSML document type (e.g. book)

The following parameters are only passed when a Document in the Loading Zone is being published.

upload.pathdocument path

upload.folderdocument folder

upload.filenameFilename (e.g.  2006-12-08.xml) without extension (e.g.  2006-12-08)
upload.extensionFile extension (e.g.  xml)
upload.confirmedIf script is run before displaying the Upload confirmation then false, otherwise true.

The following parameters are only passed when the current user is logged in:

usernameThe current user's username (e.g.  jsmith)
user.idThe current user's ID (e.g 123)
user.firstnameThe current user's first name (e.g.  John)
user.surnameThe current user's surname (e.g.  Smith)

The following properties can only be set manually:

passwordThe password used to connect to PageSeeder


To see the list of configuration properties while running a script, you can either use the DEBUG or VERBOSE mode (developer only) or use the echo properties Ant task  <echoproperties />


Created on , last edited on