NOTE: These instructions are deprecated. See the Thalia Setup and Configuration (Simplified) instructions elsewhere on this Wiki.

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.

Note: When downloading software to install in these instructions, unless
otherwise noted, always download the source code, and avoid binary installers.
Binary installers tend to make inaccurate assumptions about what libraries you
have installed on your system, as well as other problems.

When setting up Thalia servers, be certain to know which servers have which
hostnames, and where they will fit into the cluster stack.  A Thalia cluster
will need 3 layers to the cluster.  While these can all exist on the same
server, this is not recommended.

  1. Configure an Apache SSL/Tomcat server as described in the Apache-SSL instructions.  This is the top layer of the cluster. Extra care must be given to certificates and wildcard DNS entries if the system is going to exist within a multi-stack cluster.
  2. Configure an Alfresco server without WCM components, as described in the Alfresco instructions.  This is the second layer of the stack. Give care to the cluster configuration is this is part of a multi-stack cluster. If needed, do not start the Alfresco instance until after the configuration below, and unpack the alfresco.war file like this: 
    cd $ALF_HOME/tomcat/webapps
mkdir alfresco
cd alfresco
$JAVA_HOME/bin/jar -xvf ../alfresco.war
  3. Configure a MySQL server as described in the MySQL instructions.  This is the bottom layer of the stack. Be certain to configure replication if it is part of a multi-stack cluster.
  4. On the top system in the stack, create directory structure: 
    mkdir /home/www/thalia
mkdir /home/www/thalia/conf
mkdir /home/www/thalia/log
mkdir /home/www/thalia/bulkimage
mkdir /home/www/thalia/tmp
  5. Place the thaliausers.xml file into /home/www/thalia/conf.  Its contents should be similar to: 
    <user-list>
<user><name>iannuzzo</name>
<domain>ADMIN</domain>
</user>
<user><name>colodzin</name>
<domain>ADMIN</domain>
</user>
<user><name>dongq</name>
<domain>ADMIN</domain>
</user>
<user><name>dracus</name>
<domain>ADMIN</domain>
</user-list>
  6. Install ImageMagic  and Ghostscript on the top layer of the stack.
    1. go to www.imagemagick.org and get the source distribution: ImageMagick-6.3.9-6.tar.gz, or get it from the ISDA software repository on Trogdor
    2. unzip and untar ImageMagick-6.3.9-6.tar.gz and cd to ImageMagic-6.3.9-6 directory 
      cd /opt
tar -xzvf /root/ImageMagick-6.3.9-6.tar.gz
cd ImageMagick-6.3.9
    3. by default, the base installation directory is /usr/local. binary files go in /usr/local/bin and library files go in /usr/local/lib. If you want to specify an installationprefix other than /usr/local, you can do it by specify the --prefix=PATH 
      ./configure
make
make install
      ##*For more info, please refer to the Install-unix.txt in the package.
    4. after installation, you should be able to type "convert" command and get the help page.
    5. Go to http://pages.cs.wisc.edu/~ghost/ download ghostscript-8.61.tar.gz and ghostscript-fonts-std-8.11.tar.gz, or get them from the ISDA software repository on Trogdor.
    6. Remove previous ghostscript builds and build ghostscript from source 
      cd /opt
tar -xzvf /root/ghostscript-8.62.tar.gz
cd ghostscript-8.62
./configure
make
make install
cd /usr/local/share/ghostscript/
tar -xzvf /root/ghostscript-fonts-std-8.11.tar.gz
  7. On the second server in the stack, customize the Alfresco installation.
    1. Stop the Alfresco service, if needed. 
      cd /home/alfresco-[version number]-[series]
./alfresco.sh stop
ps aux | grep alfresco
      • Repeat the ps command until the Alfresco processes terminate.
    2. Edit contentModel.xml and add the Thalia admin property definition. It is located in the following directory: 
      $ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model
    3. In the block containing <type name="cm:person">, and before the </properties> line, add: 
      <property name="cm:isAdmin">
       <type>d:text</type>
     </property>
    4. Put our custom model (includes thaliaModel.xml and thalia-model-context.xml) in the extension folder. Use the one from either the deploy repository or from thalia-dev.
    5. Edit permissionDefinitions.xml and add the Thalia permissionGroup definitions to the permission group definition block. Be certain not to split a block of code. It is located in directory: 
      $ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model
      • The new block should be inserted after: 
        <permissionGroup name="Execute" allowFullControl="false" expose="false">
          <includePermissionGroup type="sys:base" permissionGroup="ExecuteContent" />
      </permissionGroup>
      • The additional block should be: 
        <!-- Custom permissions for Thalia -->

           <permissionGroup name="ThaliaWrite" allowFullControl="false"
                 expose="false">
              <includePermissionGroup type="sys:base" permissionGroup="Write"/>
          <includePermissionGroup type="sys:base" permissionGroup="Read"/>
          <includePermissionGroup type="sys:base"
                 permissionGroup="AddChildren"/>
          <includePermissionGroup type="sys:base" permissionGroup="Delete"/>
          <includePermissionGroup type="sys:base"
                 permissionGroup="ExecuteContent"/>
           </permissionGroup>

           <permissionGroup name="ThaliaRead"  allowFullControl="false"
                 expose="false">
             <includePermissionGroup type="sys:base"
                  permissionGroup="ReadProperties"/>
             <includePermissionGroup type="sys:base"
                  permissionGroup="ReadChildren"/>
         <includePermissionGroup type="sys:base"
                  permissionGroup="ReadContent"/>
           </permissionGroup>

           <permissionGroup name="ThaliaDownload" allowFullControl="false"
                expose="false">
              <includePermissionGroup type="sys:base"
                  permissionGroup="ReadProperties"/>
              <includePermissionGroup type="sys:base"
                  permissionGroup="ReadChildren"/>
              <includePermissionGroup type="sys:base"
                  permissionGroup="ReadContent"/>
          <includePermissionGroup type="sys:base"
                  permissionGroup="ExecuteContent"/>
           </permissionGroup>

           <!--  End of custom permissions for Thalia  -->
    6. Add an admin account to the Alfresco custom-authority-services-context.xml file. The file is located at: 
      $ALF_HOME/tomcat/shared/classes/alfresco/extension
      • In the <property name="adminUsers"> block, add the following line before the </properties> line: 
        <value>thaliaAdmin</value>
      • If the file is not there, import it from the ISDA software and file repsoitory or another 2.1 E machine. Alternatively, add this line to the file located at: 
        $ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/authority-services-context.xml
    7. If this is going to be part of a cluster, do the Alfresco cluster configuration now, per the Alfresco Cluster setup instructions.
    8. Update the user files, and start the Alfresco service. 
      chown -R repos:repos /home/repos
cd $ALF_HOME
./alfresco.sh start
  8. Log in as the Alfresco Admin user, and add the thaliaAdmin and guestUser users. Check the passwords for these users on the Thalia server (top server in the stack).  Use the Web interface web tool in Alfresco to do this.
    1. Also create a guest user account.  User name is guestuser, and the password is in the /home/apache-tomcat-5.5.23/webapps/ROOT/WEB-INF/web.xml file.
  9. On the top server in the stack, run the BuildThaliaDomain tool to create domains. 
    cd /home/qing/dist
$JAVA_HOME/bin/java -classpath ./lib -jar \
    BuildThaliaDomain.jar \
    http://`hostname`:8080/alfresco \
    [DOMAIN NAME]
    • Where [DOMAIN NAME] is the domain to configure (such as test, hst, psb, etc).
  10. Upload the thalia-ime.war file to /home/apache-tomcat-5.5.23/webapps.
    1. Copy the thalia.war file from either the deploy repository (pending) or from thali-dev.mit.edu:/home/apache-tomcat/webapps to [newserver]:/home/apache-tomcat/webapps as BOTH thalia.war and ROOT.war.
    2. If this is a production server, move the current web.xml file to web.xml.original, and web.xml.production to web.xml.
    3. Change the passwords for the users admin and thaliaAdmin on both the Alfresco repository and the Thalia IME server.
  2. Set the domain specific metadata mapping
  3. Upload the rmoldlog.py file to /root, and add the following line to /var/spool/cron/root: 
    30 2 * * * /root/rmoldlog.py > /loc/logs/rmlog.log&nbsp; 2>&1 &
  • No labels