Page History

Note:  Next revision cycle, start building everything into
$HOME/\[app\]-\[version#\] and creating a symlink to $HOME/\[app\] so that there is
no question about what the current, in use, directory is.

...

  1a.  You need the MIT modified version of Alfresco WCM from somewhere.  The name of the file is:
             alfresco-enterprise-tomcat-wcm-mitmods-2.1.1a3.tar.gz
        Note, you can also get this from our subversion repository:
             svn+ssh://svn.mit.edu/alfresco-dev/tags/release/alfresco-enterprise-tomcat-wcm-mitmods-2.1.1a3.tar.gz

  1b.  Log into http://customers.alfresco.com using provided Alfresco username and
   password.   Get a license from:

...

   cd /home/alfresco-\[new version\]
   tar \-xzvf /root/alfresco/alfresco-enterprise-tomcat-wcm-mitmods-2.1.1a3.tar.gz

5. Copy the license to the license directory.

...

6. Set up the dir.root location by adding it to the
   custom-repository.properties file.

   

dir.root=/home/alfresco-

\[new version\]/alf_data

7. Setup MySQL database to be used by this system, if this is a new install.
   If this is an upgrade, backup the database with mysqldump.

...

• On the Alfresco server as root, run "ssh-keygen -t dsa" and accept the default location.  Also, leave the passphrase blank (maybe not the best advice but I want to ensure that the script will not be prompted for a password)
• Copy the generated public key file (~/.ssh/id_dsa.pub) to the remote server (e.g., "scp ~/.ssh/id_dsa.pub REMOTESERVER:")
• Log into the remote (assumed linux) server as the remote user.  (If the user doesn't exist, first log in as root and create the account with "adduser USERNAME")

• Code Block
  If it does not exist, create the remote user's .ssh directory and make sure its permissions are properly set. ("mkdir \~/.ssh" and "chmod 700 \~/.ssh") 

• Append the generated public key file you copied to the end of .ssh/authorized_keys, and make sure its permissions are properly set.  ("cat id_dsa.pub >> ~/.ssh/authorized_keys" and "chmod 600 ~/.ssh/authorized_keys")
• Remove the generated public key file from the remote server ("rm id_dsa.pub")

Example:

 adduser adduser deploy_bot    ###note, this is the WEB SERVER "deploy_bot" account, not the ALFRESCO "deploy_bot" account
 mkdir mkdir /home/deploy_bot/.ssh;
 chown chown deploy_bot /home/deploy_bot/.ssh
 chmod chmod 700 /home/deploy_bot/.ssh;
 cat cat ~/id_dsa.pub >> /home/deploy_bot/.ssh/authorized_keys
 chown chown deploy_bot /home/deploy_bot/.ssh/authorized_keys
 chmod chmod 600 /home/deploy_bot/.ssh/authorized_keys
 rm rm ~/id_dsa.pub
 chmod a+rx /home/www
 chmod chmod a+rx /home/www/sash-server
 chmod chmod a+rx /home/www/sash-server/servers/
 chmod chmod a+rx /home/www/sash-server/servers/alumni/
 chown chown deploy_bot /home/www/sash-server/servers/alumni/webapps
 chown chown deploy_bot /home/www/sash-server/servers/alumni/webapps/ROOT
 

 

• Log out of the remote server
• Test by logging into the Alfresco server as root and running "ssh -l USERNAME REMOTESERVER".  If you get in as the remote user without being prompted for a password, congratulations.   Note: in this step, accept the host key.  This stores the host key in known_hosts and is actually important, since you don't want the deployment script to be prompted to accept or not accept the host key.

...

  11d. Edit $ALF_EXT/web-client-config-custom.xml and change the <deployment> element to include the deployment command(s)

       <commands>
...
                 <command name="deploy-to-someplace" program="bash">
                                             <param>-c</param>
                                             <param>${ALF_HOME}/deploy/deploy-to-someplace.sh</param>
                                     </command>
...
                 </commands>

12. Edit $ALF_EXT/custom-authority-services-context.xml and add any new administrators (e.g. <value>jcalz_admin</value>) to the admin list. 

...