Note |
---|
This is |
Wiki Markup |
{note}
This is Joe's modified version of [ document|ISDA:Alfresco Install].{note} \\ \\document. It describes how to install Alfresco WCM plus local MIT modifications. Note that this document describes only version 2.1.1 Enterprise. |
Wiki Markup |
---|
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
...
indicated,
...
always
...
download
...
the
...
tomcat
...
tarball,
...
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.
...
1.
...
get
...
the
...
Alfresco
...
software:
...
1a. You need the MIT modified version of Alfresco WCM from somewhere. The name of the file is:
alfresco-enterprise-tomcat-wcm-mitmods-2.1.1.tar.gz
...
1b. Log into http://customers.alfresco.com
...
using provided Alfresco username and
password. Get a license from:
Wiki Markup |
---|
\[Company Home\] - \[Downloads\] - \[Limited Downloads\] |
...
Such as:
enterprise-network-developer-unlimited.lic
...
Store the software in a convenient temporary directory on the system
receiving the install, such as /tmp/alfresco
...
or
...
/root/alfresco.
...
2.
...
If
...
this
...
system
...
is
...
currenlty
...
in
...
use
...
as
...
an
...
Alfresco
...
server,
...
suspend
...
any
services directly dependent upon Alfresco (such as Thalia IME),
...
and
...
then
suspend Alfresco itself.
2a. Suspend any services directly dependent upon Alfresco, such as Thalia
IME. This is highly dependent upon what that service is.
2b. Suspend Alfresco.
Wiki Markup |
---|
cd /home/alfresco-\[current version\]
./alfresco.sh stop |
...
2c.
...
Scan
...
the
...
process
...
list
...
to
...
see
...
when
...
the
...
Alfresco
...
processes
...
finish
shutting down and terminate. Repeat until no alfresco processes are left.
ps aux | grep alfresco
This may take some time to do. If it takes longer then 5 minutes, kill
the process directly.
Wiki Markup |
---|
kill \-9 \[process number\] |
...
2d.
...
Back
...
up
...
the
...
current
...
repository,
...
and
...
copy
...
the
...
backup
...
to
...
a
...
backup
...
storage
server.
3. Prepare the home directories. If this system had previous installations of
Alfresco, move the previous repository stores and database to a backup
location. Then create the home directories.
Wiki Markup |
---|
cd /home
mkdir /home/alfresco-\[new version\]
mkdir /home/alf_data |
...
If this is going to be a clustered machine, create the cluster directories.
Wiki Markup |
---|
mkdir /home/alf_data/cluster-A
mkdir /home/alf_data/cluster-B
mkdir /home/alf_data/cluster-\[repeat for each stack in cluster\]
mkdir /home/alf_data/replication |
...
4.
...
Unpack
...
the
...
software
...
into
...
the
...
correct
...
directory.
...
Wiki Markup |
---|
cd /home/alfresco-\[new version\]
tar \-xzvf /root/alfresco/alfresco-enterprise-tomcat-wcm-mitmods-2.1.1.tar.gz |
...
5.
...
Copy
...
the
...
alfresco.sh
...
file
...
from
...
the
...
ISDA
...
software
...
repository
...
to
...
the
...
new
Alfresco home directory.
Wiki Markup |
---|
scp \[krb-id\]@\[software-repository\]:alfresco.sh /home/alfresco-\[new-version\] |
...
Edit the alfresco.sh
...
file
...
to
...
use
...
the
...
local
...
file
...
paths.
...
6.
...
Copy
...
the
...
license
...
to
...
the
...
license
...
directory.
...
Wiki Markup |
---|
cp /root/alfresco/enterprise-network-developer-unlimited.lic \
/home/alfresco-\[new version\]/tomcat/shared/classes/alfresco/extension/license |
...
7.
...
Set
...
up
...
the
...
dir.root
...
location
...
by
...
adding
...
it
...
to
...
the
custom-repository.properties
...
file.
...
dir.root=/home/alfresco-2.1.1-enterprise/alf_data
...
8.
...
Setup
...
MySQL
...
database
...
to
...
be
...
used
...
by
...
this
...
system,
...
if
...
this
...
is
...
a
...
new
...
install.
...
If this is an upgrade, backup the database with mysqldump.
8a. Login to MySQL server as root and connect to the MySQL database
8b. If this is a new install, create a new database and setup a user.
8b1. Create the database.
create database alfresco; Where alfresco is the name of the
database to create
8b2. Grant permissions to user.
grant all on alfresco.* to 'username'@'localhost'
...
identified
...
by
'password'
...
with
...
grant
...
option;
grant all on alfresco.* to 'username'@'localhost.localdomain'
...
identified by 'password'
...
with
...
grant
...
option;
Replace the database, password and user names as needed, to match
the alfresco server. Select a password that will be secure.
9. If this is going to be the second independent instance of Alfresco on a
server, then edit the files:
$ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/alfresco-shared.properties
...
$ALF_HOME/tomcat/webapps/alfresco/WEB-INF/classes/alfresco/web-client-config-wcm.xml
...
Alter the option avm.remote.port
...
to
...
have
...
a
...
unique
...
port
...
number,
...
and
...
the
ports for RMI and JMX.
10. Edit the virtualization server properties file and change the server address.
vi virtual-tomcat/conf/alfresco-virtserver.properties
...
Edit alfresco.virtserver.domain
...
to
...
have
...
the
...
IP
...
address
...
of
...
the
...
server
receiving the Alfresco software:
alfresco.virtserver.domain=18-92-1-223.ip.alfrescodemo.net
...
11. Note: you do not need to upgrade TinyMCE or edit any jsp files.
12. If this is going to be a clustered system, move or alter the following
files to make a cluster configuration.
12a. Move the following files in
$ALF_HOME/tomcat/share/classes/alfresco/extension
...
cp replicating-content-services-context.xml.sample
...
\
replicating-content-services-context.xml
...
cp ehcache-custom.xml.sample.cluster
...
ehcache-custom.xml
...
12b. Select an ID for the cluster ID, and alter the following properties
in the custom-repository.properties
...
file.
cluster.id=A
...
dir.root=/home/
...
export # Set to an appropriate local, usually a SAN mount
dir.root.replicated=$
...
{dir.root}/replication
...
...
dir.contentstore=${dir.root}
...
/contentstore
...
dir.contentstore.replicated=$
...
{dir.root.replicated}
...
/contentstore
...
dir.contentstore.deleted=$
...
{dir.root}/contentstore.deleted
...
...
dir.auditcontentstore=${dir.root}
...
/audit.contentstore
...
dir.indexes
...
=
...
$
...
{dir.root}
...
/lucene-indexes
...
dir.indexes.lock
...
=
...
$
...
{dir.indexes}
...
/locks
...
index.recovery.mode
...
=
...
AUTO
index.tracking.cronExpression=0/5
...
*
...
*
...
*
...
*
...
?
system.bootstrap.config_check.strick
...
=
...
true
...