Edit the Common Configuration Layer

The Content Store package installs a skeleton configuration layer in /etc/escenic/engine/common. This folder tree contains configuration files that you can use as a basis for your host configurations. All the property settings in these files are commented out, and you need to uncomment and set values in some of the files.

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

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 Store are stored (multimedia files - video, audio, images, Word documents, PDF files and so on). You should set this to:
```
filePublicationRoot=/var/lib/escenic/engine/
```
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 Stibo DX support staff, plus information about the type of this Content Store instance. This identifier is used for error and usage reporting. For production installations you must use the following format:
```
customerId=prod@customer-id
```
where customer-id is an identifier for your organization - your domain name for example:
```
customerId=prod@mycompany.com
```
You can optionally prefix the customer ID with a qualifier of some kind if you have multiple installations and separate reporting is considered useful. You might, for example, replace prod@mycompany.com with prod@dailynews.mycompany.com on some hosts and prod@weeklymag.mycompany.com on others.

For non-production instances, you can replace the prod instance type identifier with another identifier of your choice, such as test or staging.

Reporter components that are installed with the Content Store automatically send reports about the Stibo DX software running at your site. The reported information includes:
- Which versions of the Content Store and its plug-ins are running at your site.
- The number of active CUE users (reported once an hour)
This information is very valuable to Stibo DX support engineers and helps with the diagnosis of reported errors and performance problems. It is also used in the calculation of support and maintenance charges. For this reason your are required to set this property on all Content Store installations and to configure your firewall so that reports can be delivered (see below).

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.
Open /etc/escenic/engine/common/neo/io/managers/ContentManager.properties for editing, and make sure the following properties are uncommented and set correctly:
dataConnector
Must be set as follows:
```
dataConnector=/connector/DataConnector
```