Settings.xml

jcr-standalone-derby
jcr-standalone-mssql
jcr-standalone-mysql
jcr-standalone-oracle
jcr-clustered-mysql
jcr-clustered-mssql
jcr-clustered-oracle

This is the directory that contains the XperienCentral release. This directory is actually a temporary directory: After a successful build of XperienCentral, this directory is deleted.

${webmanager.project.basedir}/webmanager-webapps/webmanager-static-webapp/target/webmanager-static-webapp-${project.version}

The location for all the static content (images and style sheets that determine the website’s design).

${webmanager.project.basedir}/webmanager-webapps/webmanager-backend-webapp/target/webmanager-backend-webapp-${project.version}

Contains a reference to the location of the XperienCentral application. Because the setup of the environment is based on .WAR files, this parameter can be disabled. This is done by entering the no-backenddir value

None

For Tomcat: leave it empty. For JBoss: set to: ${webmanager.osgidirectory}/platformbundles

Set the bundledir to ${webmanager.osgidirectory}/platformbundles for deployment on application servers that unpack the application archive to a temporary directory on each startup. JBoss, for example.

${webmanager.backendbasedir}/WEB-INF/siteworks/configuration.xml

/vol/www/mywebsite/configuration/configuration.xml

The reference to XperienCentral’s configuration file. Which license components are available for which host names is determined in this file.

${webmanager.backendbasedir}/WEB-INF/streaming

/vol/www/mywebsite/streaming

The streaming directory contains files uploaded in XperienCentral and that require authorization. These files cannot simply be placed in a public web directory.

smtp.gx.nl

smtp.mywebsite.com

This property contains the SMTP server used to send all outgoing e-mails. Example of e-mails sent by XperienCentral:

• Responses to forms completed on the website
• Newsletters
• Alerts to editors
• Notifications of changed content

classpath:webmanager.properties

This property points to the files used by the Spring framework (see the file <webmanager-root>\webmanager\webapps\backed\WEB-INF\springmvc-servlet.xml). The properties file can be referenced in three ways:

• By referring to the file in the classpath:
  
  <webmanager.springproperties.filename>classpath:webmanager.properties</webmanager.springproperties.filename>

• By setting a Java system property with the name webmanager.configuration.properties that points to the location of the file webmanager.properties if it is located outside of the XperienCentral deployment:
  
  <webmanager.springproperties.filename>file:${webmanager.configuration.properties}</webmanager.springproperties.filename>

• By explicitly pointing to the location of the file on the file system if the properties file is located outside of the XperienCentral deployment, for example:
  
  <webmanager.springproperties.filename>file:/vol/www/mywebsite/condiguration/spring/webmanager.properties</webmanager.springproperties.filename>

${webmanager.backendbasedir}/work/edition-bundles

This property points to the directory containing the XperienCentral plugins.

None

In a clustered environment, each node must have a unique identifier. The best practice is to use the name of the server as the cluster ID so you can easily match the two together.

false

In a clustered environment, you must define each node as either a read/write or read-only node. False means the node is read/write and True means the node is read-only.

localhost

The host for the database.

3306

The port number for the database.

webmanager9

The name of the database used for storing all external data.

root

The name of the user who has database rights.

admin

The database user's password.

localhost


The host name of the database.

3306


The port number of the database.

webmanager9


The name of the database where the JCR data is stored.

root


The user who accesses the database.

admin


The database user's password.