Page History

unmigrated-wiki-markupNOTE: 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.

...

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:

...

Code Block
cd

...

$ALF_HOME/tomcat/webapps

...


mkdir alfresco
cd alfresco
$JAVA_HOME/bin/jar -xvf ../alfresco.war

...

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.

...

On the top system in the stack, create directory structure:
Code Block

...

mkdir /home/www/thalia

...

mkdir /home/www/thalia/conf

...

mkdir /home/www/thalia/log

...

mkdir /home/www/thalia/bulkimage

...

mkdir /home/www/thalia/tmp

...

Place the thaliausers.xml file into /home/www/thalia/conf. Its contents

...

should be similar to:
Code Block

...

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

...

Install ImageMagic and Ghostscript on the top layer of the stack.
...
1. 1. go to www.imagemagick.org and get the source distribution:
...
1. 1. ImageMagick-6.3.
...
1. 1. 9-
...
1. 1. 6.tar.gz
...
1. 1. , or get it from the ISDA software repository on Trogdor
  2. unzip and untar
...
1. 1. ImageMagick-6.3.
...
1. 1. 9-6.tar.gz and cd to ImageMagic-6.3.
...
1. 1. 9-6 directory
    Code Block
    cd /opt tar -xzvf /root/ImageMagick-6.3.9-6.tar.gz cd ImageMagick-6.3.9
  2. by default, the base installation directory is /usr/local. binary
...
1. 1. files go in /usr/local/bin and library files go in /usr/local/lib. If
...
1. 1. you want to specify an installationprefix other than /usr/local, you
...
1. 1. can do it by specify the --prefix=PATH
...
1. 1. Code Block
    ./configure make make install
    ##*For
     6d. ./configure (specify the path here if necessary. Please note that
         the binary files should be in the system path)
     6e. make; make install
...
1. 1. more info, please refer to the Install-unix.txt in the package.
...
1. 1. after installation, you should be able to type "convert" command and
...
1. 1. get the help page.
  2. 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.
...
1. 2. Remove previous ghostscript builds and build ghostscript from source
    Code Block
    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
1. On the second server in the stack, customize the Alfresco installation.
  ...
  1. 1. Stop the Alfresco service, if needed.
      ...
      Code Block
      cd /home/alfresco-
  ...
  1. 1. [version number
  ...
  1. 1. ]-
  ...
  1. 1. [series
  ...
  1. 1. ]
  ...
  1. 1. ./alfresco.sh stop
  ...
  1. 1. ps aux
  ...
  1. 1. | grep alfresco
  ...
  1. 1. - Repeat the ps command until the Alfresco processes terminate.
  ...
  1. 1. Edit contentModel.xml and add the Thalia admin property definition.
  ...
  1. 1. It is located in the following directory:
      Code Block
  ...
  1. 1. $ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model
  ...
  1. 1. In the block containing <type name="cm:person">, and before the
  ...
  1. 1. </properties> line, add:
      Code Block
  ...
  1. 1. <property name="cm:isAdmin">
  ...
  1. 1. <type>d:text</type>
  ...
  1. 1. </property>
  ...
  1. 1. Put our custom model (includes thaliaModel.xml and thalia-model-
  ...
  1. 1. context.
  ...
  1. 1. xml) in the extension folder.
  ...
  1. 1. Use the one from either the deploy
  ...
  1. 1. repository or from thalia-dev.
  ...
  1. 1. Edit permissionDefinitions.xml and add the Thalia permissionGroup
  ...
  1. 1. definitions to the permission group definition block.
  ...
  1. 1. Be certain not
  ...
  1. 1. to split a block of code.
  ...
  1. 1. It is located in directory:
      Code Block
  ...
  1. 1. $ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model
  ...
  1. 1. - The new block should be inserted after:
        ...
        Code Block
        <permissionGroup name="Execute" allowFullControl="false" expose="false">
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ExecuteContent" />
  ...
  1. 1. - </permissionGroup>
  ...
  1. 1. - The additional block should be:
        ...
        Code Block
        
  ...
  1. 1. - <permissionGroup name="ThaliaWrite" allowFullControl="false"
  ...
  1. 1. - expose="false">
  ...
  1. 1. - <includePermissionGroup type="sys:base" permissionGroup="Write"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base" permissionGroup="Read"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="AddChildren"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base" permissionGroup="Delete"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ExecuteContent"/>
  ...
  1. 1. - </permissionGroup> <permissionGroup name="ThaliaRead"
  ...
  1. 1. - allowFullControl="false"
  ...
  1. 1. - expose="false">
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ReadProperties"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ReadChildren"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ReadContent"/>
  ...
  1. 1. - </permissionGroup>
  ...
  1. 1. - <permissionGroup name="ThaliaDownload" allowFullControl="false"
  ...
  1. 1. - expose="false">
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ReadProperties"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ReadChildren"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ReadContent"/>
  ...
  1. 1. - <includePermissionGroup type="sys:base"
  ...
  1. 1. - permissionGroup="ExecuteContent"/>
  ...
  1. 1. - </permissionGroup>
  ...
  1. 1. - 
  ...
  1. 1. Add an admin account to the Alfresco custom-authority-services-context.xml
  ...
  1. 1. file.
  ...
  1. 1. The file is located at:
      ...
      Code Block
      $ALF_HOME/tomcat/shared/classes/alfresco/extension
  ...
  1. 1. - In the <property name="adminUsers"> block, add the following line
  ...
  1. 1. - before the </properties> line:
        Code Block
  ...
  1. 1. - <value>thaliaAdmin</value>
  ...
  1. 1. - If the file is not there, import it from the ISDA software and file repsoitory
  ...
  1. 1. - or another 2.1 E machine.
  ...
  1. 1. - Alternatively, add this line to the
  ...
  1. 1. - file located at:
        Code Block
  ...
  1. 1. - $ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco
  ...
  1. 1. - /authority-services-context.xml
    2. If this is going to be part of a cluster, do the Alfresco cluster
  ...
  1. 1. configuration now, per the Alfresco Cluster setup instructions.
  ...
  1. 1. Update the user files, and start the Alfresco service.
  ...
  1. 1. Code Block
      chown -R repos:repos /home/repos cd $ALF_HOME
  ...
  1. 1. ./alfresco.sh start
  ...
  1. Log in as the Alfresco Admin user, and add the thaliaAdmin and
  ...
  1. guestUser users.
  ...
  1. Check the passwords for these users on the Thalia
  ...
  1. server (top server in the stack). Use the Web interface web tool in
  ...
  1. Alfresco to do this.
    ...
    1. 1. Also create a guest user account. User name is guestuser, and the
    ...
    1. 1. password is in the
    ...
    1. 1. /home/apache-tomcat-5.5.23/webapps/ROOT/WEB-INF/web.xml file.
    ...
    1. On the top server in the stack, run the BuildThaliaDomain tool to create
    ...
    1. domains.
    ...
    1. ...
      Code Block
      cd /home/qing/dist
    ...
    1. $JAVA_HOME/bin/java
    ...
    1. -classpath ./lib
    ...
    1. -jar \
    ...
    1. BuildThaliaDomain.jar \
    ...
    1. http://`hostname`:8080/alfresco \
    ...
    Wiki Markup
        Where \[DOMAIN NAME\] is the domain to configure (such as test, hst, psb,     etc).
    ...
    1. [DOMAIN NAME
    ...
    1. ]
      - Where [DOMAIN NAME] is the domain to configure (such as test, hst, psb, etc).
    1. Upload the thalia-ime.war file to /home/apache-tomcat-5.5.23/webapps.
    ...
    1. 1. Copy
    ...
    1. 1. the
    ...
    1. 1. thalia.war
    ...
    1. 1. file
    ...
    1. 1. from
    ...
    1. 1. either
    ...
    1. 1. the
    ...
    1. 1. deploy
    ...
    1. 1. repository
    ...
    1. 1. (pending)
    ...
    1. 1. or
    ...
    1. 1. from
    ...
    1. 1. thali-dev.mit.edu:/home/apache-tomcat/webapps
    ...
    1. 1. to
    ...
    1. 1. [newserver
    ...
    1. 1. ]:/home/apache-tomcat/webapps
    ...
    1. 1. as
    ...
    1. 1. BOTH
    ...
    1. 1. thalia.war
    ...
    1. 1. and
    ...
    1. 1. ROOT.war.
    ...
    1. 1. If this is a production server, move the current web.xml file to
    ...
    1. 1. web.xml.original, and web.xml.production to web.xml.
    ...
    1. 1. Change the passwords for the users admin and thaliaAdmin on both the
    ...
    1. 1. Alfresco repository and the Thalia IME server.
    ...
    1. Set the domain specific metadata mapping
    ...
    1. Upload the rmoldlog.py file to /root, and add the following line to
    ...
    1. /var/spool/cron/root:
      ...
      Code Block
      30 2 * * * /root/rmoldlog.py > /loc/logs/rmlog.
    ...
    1. log  2>&1 &

Child pages

Versions Compared

Old Version 2

New Version Current

Key