thalia specific server setup

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. 3. Configure a MySQL serveras 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/thalia

mkdir /home/thalia/conf

mkdir /home/thalia/log

mkdir /home/thalia/bulkimage

     mkdir /home/thalia/tmp 5. Place the thaliausers.xml file into /home/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 on the top layer of the stack.

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.2.tar.gz and cd to ImageMagic-6.3.2
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.

6d. ./configure (specify the path here if necessary. Please note that the binary files should be in the system path)

6e. make; make install

6f. for more info, please refer to the Install-unix.txt in the package

6g. after installation, you should be able to type "convert" command and get the help page.

7. On the second server in the stack, customize the Alfresco installation.

7a. Stop the Alfresco service.

cd /home/alfresco-[version number]-[series]

./alfresco.sh stop

ps aux | grep alfresco

Repeat the ps command until the Alfresco processes terminate. 7b. Edit contentModel.xml and add the Thalia admin property definition.
It is located in the following directory:

/home/alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model

In the block containing <type name="cm:person">, and before the

</properties> line, add:

               </property>
7c. Put our custom model (includes thaliaModel.xml and thalia-model-
context.mxl) in the extension folder. Use the one from either the deploy
repository or from thalia-dev.      7d. 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:        /home/alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model
        The additional block should be:           <permissionGroup name="ThaliaWrite" allowFullControl="false"

expose="false">