Publishing assets

Publishing objects in object store

Publication Document

Description

Represents a document generated by the publish operation.

Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies

For all publication documents:

  • Publish Template, Style Template, and Output Folder specified in the Publication Info (this information is in XML format and used during republish of the source document)

For published documents only:

  • Document referenced by the OwnerDocument property, if not null
  • Document referenced by the SourceDocument (Publication Source) property, if not null
  • Folder referenced by the PublishingSubsidiaryFolder property for an HTML document, if not null

See also Common dependencies between objects.

Environment-specific data Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying users and groups. For more information, see Permission.
Notes

Typically, a publication document does not need to be deployed.

If you do deploy a publication document, note that a relationship exists between the publication document and the source document from which it was generated. You must deploy both the source and publication documents, as well as the Publish Template and Style Template that was used if republish is to be done.

Publish Request

Description Represents a request to publish a document.
Deployment Mechanism

Not applicable

Dependencies Not applicable
Environment-specific data Not applicable
Notes A publish request is a short-lived object that is created when a Publish action is executed on a document. When the action has finished processing, the request is deleted. Therefore, you should not deploy publish request objects.

Publish Style Template

Description Specifies the output format for publishing a document and, for PDF format, optional parameters.
Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies

See Common dependencies between objects.

Environment-specific data

Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying users and groups. For more information, see Permission.

Notes

The Publishing Extensions AddOn includes two default publish style templates. If you modify these templates, you must deploy the updated templates to the destination environment.

NOTE Delete the default publish style templates in the destination environment before importing the updated templates.

Publish Template

Description Specifies the publishing instructions for the publish action such as security, property settings, location, and type of publish operation including what style template, if any, is to be used.
Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies

The destination folder for the publication document that is specified in the publish template

The following assets, if they are specified in the publish template:

  • Publish style template
  • Event actions for publish and for republish
  • Publication document class
  • Security policy
  • Any specific permissions to be applied to the publication document

See Common dependencies between objects.

Environment-specific data Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying users and groups. For more information, see Permission.
Notes

The Publishing Extension AddOn does not include any default publish templates. Therefore, you must deploy all publish templates for your application.

Source Document

Description

Represents a document whose content is used to create a published document.

Deployment Mechanism
  1. Enterprise Manager export tool: See Create export files.
  2. FileNet Deployment Manager conversion tool: See Convert objects for import.
  3. Enterprise Manager import tool: See Import converted objects.
Dependencies None
Environment-specific data Any object exported from an object store contains a set of basic permissions that controls access to that object. These permissions contain environment-specific information identifying users and groups. For more information, see Permission.
Notes

Typically, a source document does not need to be deployed.

If you do deploy a source document, note that a relationship exists between the source document and the publication document that is generated from it. You must deploy both the source and publication documents, as well as the Publish Template and Style Template that was used if republish is to be done.

Publishing objects in GCD

Publishing configuration

Description Contains the configuration settings for a publishing operation.
Deployment Mechanism Content Engine does not support export and import of this type of object. You must re-create the object in the destination environment.
Dependencies

Not applicable

Environment-specific data Not applicable
Notes None

Rendition Engine connection

Description Represents site-specific connection data for a Rendition Engine that is referenced by a publishing configuration.
Deployment Mechanism Content Engine does not support export and import of this type of object. You must re-create the object in the destination environment.
Dependencies

Not applicable

Environment-specific data Not applicable
Notes

None

DITA publishing objects

DITA Open Toolkit

Description Provides a information development solution for publishing that is based on the Darwin Information Typing Architecture (DITA).
Deployment Mechanism

Content Engine does not support the export and import of the DITA Open Toolkit. Instead, you must install and configure the toolkit in the destination environment.

Dependencies Not applicable.
Notes DITA publishing uses publish templates, publish style templates, and rendition engine connections that are described earlier in this topic.

DITA Rendition Engine connection

Description Represents site-specific connection data for a DITA Rendition Engine that is referenced by a publishing configuration. (A DITA Rendition Engine is one that uses a DITA Open Toolkit deployment for publishing documents.)
Deployment Mechanism Content Engine does not support export and import of this type of object. You must re-create the object in the destination environment.
Dependencies

Not applicable

Environment-specific data Not applicable
Notes

None