Configuration of multi-site publishing means configuration of the publication targets. For each target the
Content Management Server needs a set of properties which have to be defined
in the WEB-INF/properties/corem/publisher.properties file. You have to replace
<n> with a consecutive number for each property set, starting with 1.
It is possible to change the publication target configuration after the first start of the server and even if the server is running.
| Property | Description |
|---|---|
publisher.target.<n>.user | The user which is used by the publisher to log in to the Master Live Server. |
publisher.target.<n>.domain | The domain of the user which is used by the publisher to log in to the Master Live Server. |
publisher.target.<n>.password | The password of the user which is used by the publisher to log on the
Master Live Server. Make sure, that you change
the password of the existing user publisher on the Master Live Server or that you newly create this user on
the Master Live Server. |
publisher.target.<n>.ior.url | The URL where the publisher can obtain the IOR of the Master Live Server. |
publisher.target.<n>.name | The permanent and unique name of the publication target. This name is used for target identification in the APIs and in JMX. Changing this name may lead to unexpected failures in clients that are not properly stopped, changed, and restarted. |
publisher.target.<n>.display.name | 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. |
publisher.target.<n>.folders |
The property folders 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. For example, the following configuration line would be correct:
It specifies three folders that are mapped to a single target, one of which is the folder with ID 5173. Listing folders numerically can be helpful when a folder must be renamed, but should not leave its publication target. 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 3.4. Properties used to configure Multi-Site Management
![[Warning]](../common/images/warning.png) | Warning |
|---|---|
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.
When you configure base folders by name, a top-level folder of that name may not be renamed and no other
top-level folder may be renamed to assume that name. This stops users from reassigning top-level folder
accidentally. When you want to rename top-level folders that belong to a publication target, configure them
using their numeric id in the file |
 |  |  |
 |