Page History

Note: Next revision cycle, start building everything intounmigrated-wiki-markup
$HOME/\[app\]-\[version#\] and creating a symlink to $HOME/\[app\] so that there -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

...

.

...

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.

...

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

...

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-

...

Wiki Markup
The system super users can self-register in any domain by going to https://\[domain\].thalia.mit.edu/resttest.jsp and click on the super user self reg button.

...

list>
Install ImageMagic on the top layer of the stack.

...

...
1. 1. go to www.imagemagick.org and get the source distribution:
    ImageMagick-6.3.2-9.tar.
...
1. 1. gz
...
1. 1. unzip and unstar ImageMagick-6.3.2.tar.gz and cd to ImageMagic-6.3.2
...
1. 1. directory
...
1. 1. by default, the base installation directory is /usr/local. binary files
...
1. 1. go
...
1. 1. in
...
1. 1. /usr/local/bin
...
1. 1. and
...
1. 1. library
...
1. 1. files
...
1. 1. go
...
1. 1. in
...
1. 1. /usr/local/lib.
...
1. 1. If
...
1. 1. you
...
1. 1. want
...
1. 1. to
...
1. 1. specify
...
1. 1. an
...
1. 1. installationprefix
...
1. 1. other
...
1. 1. than
...
1. 1. /usr/local,
...
1. 1. you
...
1. 1. can
...
1. 1. do
...
1. 1. it
...
1. 1. by
...
1. 1. specify
...
1. 1. the
...
1. 1. --prefix=PATH
...
1. 1. in
...
1. 1. step
...
1. 1. 6d.
...
1. 2. ./configure
...
1. 1. (specify
...
1. 1. the
...
1. 1. path
...
1. 1. here
...
1. 1. if
...
1. 1. necessary.
...
1. 1. Please
...
1. 1. note
...
1. 1. that
...
1. 1. the
...
1. 1. binary
...
1. 1. files
...
1. 1. should
...
1. 1. be
...
1. 1. in
...
1. 1. the
...
1. 1. system
...
1. 1. path)
...
1. 2. make;
...
1. 1. make
...
1. 1. install
  2. for more info,
...
1. 1. please
...
1. 1. refer
...
1. 1. to
...
1. 1. the
...
1. 1. Install-unix.txt
...
1. 1. in
...
1. 1. the
...
1. 1. package
  2. after installation,
...
1. 1. you
...
1. 1. should
...
1. 1. be
...
1. 1. able
...
1. 1. to
...
1. 1. type
...
1. 1. "convert"
...
1. 1. command
...
1. 1. and
...
1. 1. get
...
1. 1. the
...
1. 1. help
...
1. 1. page.
...
2. On the second server in the stack, customize the Alfresco installation.
  1. Stop the Alfresco service.
    cd /home/alfresco-
...
1. 1. version
...
1. 1. number
...
1. 1. -
...
1. 1. series
...
...
1. 1. ./alfresco.sh stop
...
1. 1. ps aux | grep
...
1. 1. 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:
...
...
1. 1. /home/alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/
...
1. 1. model
...
1. 1. In the block containing <type name="cm:person">, and before the
...
1. 1. </properties> line, add:
...
...
1. 1. <property name="cm:isAdmin">
...
1. 1. <type>d:text</type>
...
1. 1. </
...
1. 1. property>
...
1. 1. Put our custom model (includes thaliaModel.xml and
...
1. 1. thalia-model-
    context.mxl) in the extension folder.
...
1. 1. Use the one from either the deploy
    repository or from thalia-dev.
  2. 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:
...
...
1. 1. /home/alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/
...
1. 1. model
...
1. 1. The additional block should be:
...
...
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>
...
1. 1. <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. </
...
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. </
...
1. 1. permissionGroup>
...
1. 1. Add an admin account to the Alfresco authority-services-context.xml
...
1. 1. file.
...
1. 1. The file is located at:
...
...
1. 1. /home/alfresco/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/
...
...
1. 1. In the <property name="adminUsers"> block, add the following line
...
...
1. 1. before
...
1. 1. the
...
1. 1. </properties>
...
1. 1. line:
    <value>thaliaAdmin</value>
  2. Start the Alfresco service.
    cd /home/alfresco-
...
1. 1. version
...
1. 1. number
...
1. 1. -
...
1. 1. series
...
...
1. 1. ./alfresco.sh
...
1. 1. start
...
1. 1. Log in as the Alfresco Admin user, and add the thaliaAdmin and
...
1. 1. guestUser users.
...
1. 1. Check the passwords for these users on the Thalia
...
1. 1. server (top server in the stack).
...
1. 1. Use the Web interface web tool in
...
1. 1. Alfresco to do this
...
1. 1. .
...
...
1. On the top server in the stack, run the BuildThaliaDomain tool to create
...
1. domains.
...
...
1. cd /home/qing/dist
...
1. $JAVA_HOME/bin/java -classpath ./lib -jar \
...
1. BuildThaliaDomain.jar \
Wiki Markup
      \[alfresco repository location\]\
Wiki Markup
      \[DOMAIN NAME\]      Where \[DOMAIN NAME\] is the domain to configure (such as test, hst, psb,
    etc).
   For example, to create the TEST domain on isda-thalia6 do:
$JAVA_HOME/bin/java -classpath ./lib -jar BuildThaliaDomain.jar http://isda-thalia6.mit.edu:8080/alfresco TEST

  Please be aware that the jar file was compiled using java6, so if the JAVA_HOME points to a location older than java6, it will not work.
You can run the jar file from any server to manage any domain in any alfresco repository. You just need to specify the alfresco repository address as the first argument.
9. Upload the thalia-ime.war file to /home/apache-tomcat-5.5.23/webapps.
10. Set the domain specific metadata mapping
11. run cronjob to clean up the log, tmp, and bulkimage directories.  :
...
1. http://`hostname`:8080/alfresco \
  DOMAIN NAME
  Where DOMAIN NAME is the domain to configure (such as test, hst, psb,
  etc).
2. 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.
3. Set the domain specific metadata mapping
4. Upload the rmoldlog.py file to /root, and add the following line to
...
1. /var/spool/cron/root:
...
...
1. 30 2 * * * /root/rmoldlog.py > /loc/logs/rmlog.
...
1. log 2>&1 &

Child pages

Versions Compared

Old Version 5

New Version 6

Key