The Site Manager can be configured using different XML files. The names of these files are defined in the editor.properties file. The files are a small bootstrap file (editor.startup.configuration) necessary for some settings before the actual start of the editor, and the XML files for the customization of the editor. The following use cases are supported:

When a user is member of more than one group, for which specific configuration files exist, then the system chooses an arbitrary group for which the configuration file is taken. So, it is good practice, to have only one group for each user for which a configuration file exists. If this is no option, you can define your own selection scheme as described in this manual.

The files are evaluated in a specific order:

No <ConfigGroups> element used

<ConfigGroups> element used

Be aware, that you need to define a file in editor.configuration in both cases, even if it will not be used in the second case, otherwise an error occurs.

Example for a configuration without a <ConfigGroups> element

You have made the following settings in editor.properties:

      editor.startup.configuration=editor-startup.xml
editor.configuration=editor.xml
group.configuration=editor-group-{0}.xml
user.configuration=editor-user-{0}.xml

    

A user named "Axel" who is only member of the group "editors" logs in and the following configuration files are applied in the shown order:

Example for a configuration with a <ConfigGroups> element

You have made the following settings in editor.properties:

      editor.startup.configuration=editor-startup.xml
editor.configuration=editor.xml
group.configuration=editor-group-{0}.xml
user.configuration=editor-user-{0}.xml

    

And these settings in editor-startup.xml:

      <ConfigGroups>
   <ConfigGroup name="editors">
      <Configuration name="common"/>
      <Configuration name="editor"/>
   </ConfigGroup>
</ConfigGroups>

    

The same user as before logs in and the following configuration files are applied in the shown order:

How files merge

All elements which can occur only once - due to the coremedia-editor.dtd - will be overwritten by the settings of the succeeding configuration file. The following elements use inheritance:

Example:

The interesting parts of the editor.xml look as follows:

      <Bundle name="first/bundle"/>
<SpellChecker enabled="true"/>
<Documents>
  <Document type="Article">
    <Property name="Headline" editorClass="FirstClass"/>
  </Document>
</Documents>
<DocumentTypes>
  <DocumentType name="Article">
    <PropertyType name="Editor">
      <Validator class="NotEmpty"/>
      <Initializer class="SetChiefEditor"/>
    <PropertyType/>
  </DocumentType>
</DocumentTypes>


    

The interesting parts of the group specific editor definition look as follows:

      <Bundle name="second/bundle"/>
<SpellChecker enabled="false"/>
<Documents>
  <Document type="Image">
    <Property name="Caption" editorClass="SecondClass"/>
  </Document>
</Documents>
<DocumentTypes>
  <DocumentType name="Article">
    <PropertyType name="Editor">
      <ModelClass class="MyModel"/>
      <Initializer class="SetEditor"/>
    <PropertyType/>
  </DocumentType>
</DocumentTypes>

    

Applying both editor definitions will result in the following behavior:

See Section 5.2, “Configuration Possibilities in the XML Files” for a detailed description of the properties.

You can either use locally stored files for each client or administrate these files centrally on the Content Server and deliver them to the clients.

Note

Not mandatory: You only need to do this configuration if you want to use group or user specific configuration files or if you want to administrate the files centrally on the Content Server. Otherwise, the following files in the folder <CoreMediaInstall>/properties/corem are used by default:

• editor-startup.xml

• editor.xml

Caution

Configure in the following file:

• editor.properties

Defining the XML configuration files

Defining user or group specific configuration files

Example:

Note

Note, that you can define multiple configuration files for a specific group, which will be evaluated in a specific order. See the Site Manager Developer Manual for a description of the XML element <ConfigGroups> for details.

Administrating the XML files on the server

        grant codeBase "http://localhost/servlets/fileservlet" {
    .
    .
    permission java.io.FilePermission 
    "properties${/}corem${/}editor.xml", "read";
    permission java.io.FilePermission 
    "properties${/}corem${/}editor-CVD.xml", "read";
};