This section describes how to set the JVM properties.

• (Windows) At a command prompt, enter the following:

  Set JAVA_OPTS=-Ddir.root=e:/alfresco/data

• (Linux) At a command prompt, enter the following:

  export JAVA_OPTS==Ddir.root=/srv/alfresco/data

You can use a combination of global properties and system properties for certain customizations. For example, if you wish to distribute a system that has a core set of properties overridden but need to customize the last few for each installation.

1. Activate the properties in the <classpathRoot>/alfresco-global.properties file.
2. Set all common defaults for your system.
3. On each installation, add the final configuration values. For example:

   -Ddb.username=alfresco
   -Ddb.password=alfresco 
   -Dindex.tracking.cronExpression='0/5 * * * * ?' 
   -Dindex.recovery.mode=AUTO 
   -Dalfresco.cluster.name=ALFRESCO_DEV

1. To output detailed Ehcache usage information, set the following logging category to DEBUG:

   org.alfresco.repo.cache.EhCacheTracerJob

2. To target specific caches, you can append the cache name or package, for example:

   org.alfresco.repo.cache.EhCacheTracerJob.org.alfresco

3. Open to the <configRoot>\alfresco\scheduled-jobs-context.xml file.
4. Locate the following bean:

   ehCacheTracerJob

   Override this bean to change the trigger schedule.

5. Uncomment the scheduler property to activate the trigger.

   When ehCacheTracerJob is triggered, the job will collect detailed cache usage statistics and output them to the log/console, depending on how logging has been configured for the server.

6. To ensure that caches use statistics, set the statistics property for all caches.

   statistics="true"

   Use the cluster cache sample file or copy the default cache configuration file into the <extensions> directory.

This section describes enabling versioning for all content in the repository.

1. Open the data dictionary <configRoot>\alfresco\model\contentModel.xml.
2. Search for the <type>: <type name="cm:content">
3. Immediately after the closing </properties> tag, insert the following lines:

   <type name="cm:content">
      <properties>
      ...
      </properties>
      <mandatory-aspects>
         <aspect>cm:versionable</aspect>
      </mandatory-aspects>
   </type> 

4. Save the file.
5. Restart the Alfresco server.

This section describes how to disable versioning for all content in the repository.

1. Open the alfresco-global.properties file.
2. Add the following property:

   version.store.enableAutoVersioning=false

   When this property is set to false, the VersionableAspect will not respond to any events; even if the aspect is present, it will not create versions.

3. Save the global properties file.
4. Restart the Alfresco server.

This section describes the replication steps for the MySQL database.

1. Open a MySQL command prompt on the master server.
2. Grant the slave permission to replicate:

   GRANT REPLICATION SLAVE ON *.* TO <slave_user> IDENTIFIED BY '<slave_password>'

3. If the master is not using the binary update log, add the following lines to my.cnf (Linux) or my.ini (Windows) configuration file on the master, and restart the server:

   [mysqld]
   log-bin
   server-id=1

   Note: By convention, server-id for the master is usually server-id 1, and any slaves from 2 onwards, although you can change this. If the master is already using the binary update log, either note the offset at the moment of the backup (the next step), or use the RESET MASTER statement to clear all binary logs and immediately begin the backup. You may want to make a copy of the binary logs before doing this if you need to use the binary logs to restore from backup.
4. Make a backup of the database.

   This will be used to start the slave server. You can skip this step if you use the LOAD DATA FROM MASTER statement, but first review the following comments about locking the master.

5. Add the following to the configuration file on the slave:

   master-host=master-hostname
   master-user=slave-user
   master-password=slave-password
   server-id=2

   The slave user and slave password are those to which you set when you granted REPLICATION SLAVE permission on the master. The server-id must be a unique number, different to the master or any other slaves in the system. There are also two other options: master-port, used if the master is running on a non-standard port (3306 is default), and master-connect-retry, a time in seconds for the slave to attempt to reconnect if the master goes down. The default is 60 seconds.

   Restore the data from the master, either as you would normally restore a backup or with the statement LOAD DATA FROM MASTER. The latter will lock the master for the duration of the operation, which could be quite lengthy, so you may not be able to spare the downtime.