Page History

Wiki MarkupNote:    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.

...

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/thalia/conf.  Most up-to-date thaliausers.xml contents are here.

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>

...

     6a. go to www.imagemagick.org and get the source distribution:
ImageMagick-6.3.2-9.tar.gz

     6b. unzip and unstar ImageMagick-6.3.29.tar.gz and cd to ImageMagic-6.3.29
         directory

     6c. 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 in step 6d.

...

     7a. Stop the Alfresco service, if needed.

Wiki Markup&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; cd           cd /home/alfresco-\[version number\]-\[series\] &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ]
          ./alfresco.sh stop &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ps aux \| grep stop
          ps aux | grep alfresco

          Repeat the ps command until the Alfresco processes terminate.

...

         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  -->

      7e. Add an admin account to the Alfresco custom-authority-services-context.xml
          file.  The file is located at:

...

8.  On the top server in the stack, run the BuildThaliaDomain tool to create
    domains.  **Note that this assumes that alfresco is running on :8080. On dev instance it is not. Please check chart in Thalia environments and workflow

Wiki Markup&nbsp;&nbsp;&nbsp;&nbsp; cd      cd /home/qing/dist &nbsp;&nbsp;&nbsp;&nbsp;
     $JAVA_HOME/bin/java \ -classpath ./lib \ -jar \ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
      BuildThaliaDomain.jar \ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \
      http://`hostname`:8080/alfresco \ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \[DOMAIN NAME\]\
      [DOMAIN NAME]

    Where [DOMAIN NAME] is the domain to configure (such as test, hst, psb,
    etc). For a list of all domains to be set up, see Thalia Domains Wiki Markup&nbsp;&nbsp;&nbsp; Where \[DOMAIN NAME\] is the domain to configure (such as test, hst, psb, &nbsp;&nbsp;&nbsp; etc). For a list of all domains to be set up, see [Thalia Domains|https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/display/ZEST/Thalia+Domains]

9.  Upload the thalia-ime.war file to /home/apache-tomcat-5.5.23/webapps.

Wiki Markup&nbsp;&nbsp;&nbsp;     9a. Copy the thalia.war file from either the deploy repository (pending) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or from
        or from thali-dev.mit.edu:/home/apache-tomcat/webapps to &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \[newserver\to
        [newserver]:/home/apache-tomcat/webapps as BOTH thalia.war and &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and
        ROOT.war.

    9b. If this is a production server, move the current web.xml file to
        web.xml.original, and web.xml.production to web.xml.

...