Note: Next revision cycle, start building everything into
Wiki Markup
$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.
...
7a. Stop the Alfresco service, if needed.
cd cd /home/alfresco-\[version number\]-\[series\]
] Wiki Markup
./alfresco.sh stop
ps aux \| grep stop
ps aux | grep alfresco
Repeat the ps command until the Alfresco processes terminate.
...
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
cd cd /home/qing/dist
Wiki Markup
$JAVA_HOME/bin/java \ -classpath ./lib \ -jar \
\
BuildThaliaDomain.jar \
\
http://`hostname`:8080/alfresco \
\[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 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|https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/display/ZEST/Thalia+Domains] Wiki Markup
9. Upload the thalia-ime.war file to /home/apache-tomcat-5.5.23/webapps.
9a. Copy the thalia.war file from either the deploy repository (pending)
or from Wiki Markup
or from thali-dev.mit.edu:/home/apache-tomcat/webapps to
\[newserver\to
[newserver]:/home/apache-tomcat/webapps as BOTH thalia.war and
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.
...