Publishing

Publishing is useful when you want to make a document available, but you do not want others to be able to modify the document. When you publish a document, you maintain control over the source document and can continue to update and make changes to the source that are not visible to users of the publication document. When you are ready to make the new version of the document available to your users, you republish the source document, thereby creating a new version of the publication document.

An example of where this facility is useful is in the use of procedure documents. You want everyone to follow the same procedure, and only want to roll out changes to the procedure when the changes have been thoroughly reviewed and tested. So while your users are using one version of the procedure, you make changes to the source document, and when you are ready, you republish the source document.

Other advantages of publishing are:

Publishing Terminology

Familiarize yourself with the following publishing terms that are used throughout this help.

Source Document
The content of this document is the input for the publishing process.
Publish Template
Instructions for how to publish a document.
Streamlines the steps to publish a document.
A subclass of Document, can be versioned.
Publication Document
New document that is different from the source document.
It might or might not be the same format type as the original source document.
Style Template
Describes the presentation output format of a publication document.
Identifies the recognized input formats and output format.
Can contain additional presentation information that is specific to the Publishing Handler.
Is a Custom object.
Liquent Vista Domain
For publishing using the Rendition Engine, the Liquent Vista Domain is a collection of one or more Rendition Engine and Content Engine servers that use a common publishing database. The Liquent Vista Domain is a separate entity from a Windows domain, and there can be multiple Liquent Vista domains within a FileNet P8 domain.
DITA Open Toolkit
An implementation of the OASIS DITA Technical Committee specification for Darwin Information Typing Architecture (DITA) DTDs and Schemas. The Toolkit transforms DITA content (maps and topics) into deliverable formats. The DITA Rendition Engine runs as a background process in FileNet P8 and does not require a separate server installation.

For more information, see: