Create the Common Configuration Layer

The Content Engine package installed in the Unpack Content Engine Components step contains a skeleton configuration layer. This is a folder tree containing configuration files that you can use as a basis for your configurations. All the property settings in these files are commented out. To create a configuration, you copy this tree to the location specified in your bootstrap layer (e.g. /etc/escenic/engine/common) and edit the contents to set the properties you need. You will find the skeleton configuration layer located in /opt/escenic/engine/siteconfig/config-skeleton.

On your assembly-host, while logged in as escenic:

  1. Copy the skeleton configuration layer to /etc/escenic/engine/common:

    $ cp -r /opt/escenic/engine/siteconfig/config-skeleton/* /etc/escenic/engine/common/
  2. Copy the delivered security configuration files to /etc/escenic/engine/common

    $ cp -r /opt/escenic/engine/security/ /etc/escenic/engine/common/
  3. Open /etc/escenic/engine/common/ServerConfig.properties for editing, and make sure the following properties are present, uncommented and set correctly for your site:

    databaseProductName

    The name of the database you are using. Currently allowed values are:

    • MySQL

    filePublicationRoot

    The path of the folder in which all binary files served by the Content Engine are stored (multimedia files - video, audio, images, Word documents, PDF files and so on). You should set this to:

    filePublicationRoot=/var/lib/escenic/publications/

    The path you specify must include a trailing slash.

    webPublicationRoot

    The URL root you want to be used for all your publications. For example http://my-company.com/. The URLs of your publications are formed by appending the publication name to this string. This property is in general used only for development purposes. In production, it is often the case that each publication has its own root URL.

    customerId

    The name of your organization, or some other name that will clearly identify your installation to Escenic support staff. Reporter components that are installed with the Content Engine automatically send reports about the Escenic software running at your site. The reported information includes:

    • Which versions of the Content Engine and its plug-ins are running at your site.

    • The number of active Content Studio users (reported once an hour)

    This information is very valuable to Escenic support engineers and helps with the diagnosis of reported errors and performance problems.

    The reporter components sends their reports to Google Analytics. In order for this to work, your firewalls must allow outgoing traffic on port 80 to http://www.google-analytics.com.

  4. Open /etc/escenic/engine/common/connector/ReadConnector.properties for editing, and make sure the following property is uncommented and set correctly:

    dataSourceName

    Must be set as follows:

    dataSourceName=java:comp/env/jdbc/ECE_READ_DS

    This is the name of the read database pool that you defined when installing the application server (see Install Application Server).

    Do not modify any of the other settings in this file.

  5. Open /etc/escenic/engine/common/connector/UpdateConnector.properties for editing, and make sure the following property is uncommented and set correctly:

    dataSourceName

    Must be set as follows:

    dataSourceName=java:comp/env/jdbc/ECE_UPDATE_DS

    This is the name of the update database pool that you defined when installing the application server (see Install Application Server).

    Do not modify any of the other settings in this file.

  6. Open /etc/escenic/engine/common/neo/io/managers/ContentManager.properties for editing, and make sure the following properties are uncommented and set correctly:

    readConnector

    Must be set as follows:

    readConnector=/connector/ReadConnector
    updateConnector

    Must be set as follows:

    updateConnector=/connector/UpdateConnector