Deployment Manual / 4.2.3 Properties for the Publisher

Advanced Search

Deployment Manual / Version 2107

Table Of Contents

4.2.3 Properties for the Publisher

In the properties given below, some properties take a different form when using CoreMedia Multi-Master Management. In that case, an index number is used to indicate the publication target that is configured using this property value. The index numbers are consecutive integers starting with 1 and running up to the number of publication targets.

`publisher.autoextend.latest-approved-version`
Type	java.lang.Boolean
Default	false
Description	This property affects the automatic extension of publication sets. The default behavior ("false") is as follows: If the referenced content item is not published yet, publish its earliest approved version. If the referenced content item is already published, do nothing If set to "true", not the earliest but the latest (= newest) approved version is published.
`publisher.autoextend.max-failures`
Type	java.lang.Integer
Default	0
Description	The maximum number of implicitly added content items and folders whose publication may fail before no further content items and folders may be added implicitly. If set to 0 (the default), the publisher never stops adding content items and folders.
`publisher.autoextend.update-linked-documents`
Type	java.lang.Boolean
Default	false
Description	This property affects the automatic extension of publication sets. By default, ("false") only direct linked and approved content items are added to the publication set. If set to "true", all linked content items are recursively added to the publication set. The recursion stops when a version is already published and may lead to surprisingly large publication sets. Setting updateLinkedDocuments implicitly also sets latestApprovedVersion.
`publisher.connection-timeout-seconds`
Type	java.lang.Integer
Default	300
Description	The timeout in seconds for the connection to the Master Live Server ior.
`publisher.destroy-intermediate-versions`
Type	java.lang.String
Default	strict
Description	Whether intermediate content item versions between two publications will be destroyed or not on the Content Management Server. Example for dumb mode: Version 1 of content item A was published. In the meantime, the versions 2, 3, 4 and 5 have been created. When you now publish version 5, the versions 2, 3, 4 are destroyed and only version 1 and 5 remain on the Content Server. Old flags true and false are supported, too. false maps to off while true maps to strict. Available Modes off Turns destruction of intermediate versions off. dumb Simply destroys all versions between the currently published one and the previously published one; if you run into performance issues on publication or you do not use a multi-site set up this should be chosen. Mind that for multi-site set up this setting might break translation states. strict Destroys all versions between the currently published one and the previously published one, but only if the versions are not referenced by master/masterVersion properties. This ensures that for a multi-site set up your translation state will be valid. This setting is recommended for multi-site set ups.
`publisher.destroy-older-versions-on-live-servers`
Type	java.lang.Boolean
Default	true
Description	Whether older published versions should be destroyed ("true") on the Master Live Server. That is, only two published versions (the current and the one before) of each content item remain on the Master Live Server. Only change if you have a valid reason.
`publisher.enable-bypass-previews`
Type	java.lang.Boolean
Default	true
Description	Whether publication previews bypass ("true") or not ("false") the publication queue for faster response times.
`publisher.local.domain`
Type	java.lang.String
Default
Description	The domain for logging in locally to the Content Management Server.
`publisher.local.password`
Type	java.lang.String
Default	publisher
Description	The password for logging in locally to the Content Management Server.
`publisher.local.user`
Type	java.lang.String
Default	publisher
Description	The user name for logging in locally to the Content Management Server.
`publisher.priority`
Type	java.util.Map<java.lang.String,java.lang.Integer>
Default
Description	Priorities of publications requested through: guiEditor: 60 uapi: 40 generator: 40 jpython: 20 importer: 20 utility: 20 unknown: 20
`publisher.target`
Type	java.util.List<hox.corem.server.publish.PublisherConfigurationProperties$Target>
Default
Description	target is a list-valued property. You configure it with publisher.target[0].name, for example. Values other than "0" are only required for the multi-master feature, that is publication to different Master Live Servers. Target has the following properties: name Value: java.lang.String Default: Description: The permanent and unique name of the publication target. Once set, it should never be changed, as this name is used for target identification in the APIs and in JMX. displayName Value: java.lang.String Default: Description: The display name is shown to users when no localized information about a publication target is available; display names, too, should be unique, but they may well change to better illustrate the current uses of a publication target. user Value: java.lang.String Default: publisher Description: The URL where the publisher can obtain the IOR of the Master Live Server. password Value: java.lang.String Default: publisher Description: The password for logging in to the Master Live Server. domain Value: java.lang.String Default: Description: The domain for logging in to the Master Live Server. iorUrl Value: java.lang.String Default: Description: The URL where the publisher can obtain the IOR of the Master Live Server. folders Value: java.lang.String Default: Description: The base folders that are assigned to a publication target. This property typically references exactly one top-level folder, either by name or by its numerical ID. If more than one site is generated from a single Live Server, multiple top-level folders may be given, separated by commas. When indicating a folder by name, that name is blocked for rename operations on the top-level folder. Once you have assigned a folder to a publication target, it must not be reassigned to another target. Doing so would result in inconsistencies between Content Management Server and Master Live Server.

Table 4.9. Publisher Properties

Search Results

Table Of Contents