...
12b. Select an ID for the cluster ID, and alter the following properties
in the custom-repository.properties file.
cluster.id=A
dir.root=/home/export # Set to an appropriate local, usually a SAN mount
dir.root.replicated=${dir.root}/replication
dir.contentstore=${dir.root}/contentstore
dir.contentstore.replicated=${dir.root.replicated}/contentstore
dir.contentstore.deleted=${dir.root}/contentstore.deleted
dir.auditcontentstore=${dir.root}/audit.contentstore
dir.indexes = ${dir.root}/lucene-indexes
dir.indexes.lock = ${dir.indexes}/locks
index.recovery.mode = AUTO
index.tracking.cronExpression=0/5 * * * * ?
system.bootstrap.config_check.strick = true
13. Configure the deployment script.
13a. Edit ${ALF_HOME}/deploy/deploy.sh
(Right now, only Joe can probably set this up properly)
There are four environment variables we care about.
Set DEPLOY_SERVER to the fully qualified hostname of the remote machine to which you want to deploy. (e.g., "export DEPLOY_SERVER=isda-ist1.mit.edu")
Set TOMDIR to the path to the directory on the remote machine to which you want to deploy. (e.g., "export TOMDIR=/home/apache-tomcat-5.5.23/webapps/ROOT")
Set DEPLOY_USER to the username for an Alfresco account that has read access to the web project to be deployed. (e.g., "export DEPLOY_USER=deploy_bot") This should also be the name of the user on the remote server with ssh login access.
Set DEPLOY_PASSWORD to the Alfresco password for the DEPLOY_USER user. (e.g., "export DEPLOY_PASSWORD=deploy_bot_password_or_something")
13b. As root, install the proper id_dsa.pub in the ~/.ssh directory... the one corresponding to ${DEPLOY_USER}@${DEPLOY_SERVER}.