Archivematica 1.5 is a legacy release, and these documents are no longer being maintained.


On this page

Technical Requirements

Version 1.5: Operating System requirement: A current Ubuntu LTS version, which at the moment means version 14.04. The 64 bit Server Edition of Ubuntu 14.04.4 is recommended.

We plan to release a version 1.5.1 which will be available on Ubuntu 12.04, 16.04 and CentOS/Redhat 7 (more information available soon).

Archivematica is capable of running on almost any hardware supported by Ubuntu; however, processing large collections will require better hardware.

Archivematica can be installed on a single machine, or across many machines to spread the processing workload. See Advanced.

Installing from packages

Installing from packages is tested for both new installations and upgrading from version 1.4.

Updating from Archivematica 1.4

If you have installed an earlier version Archivematica from packages, it is possible to update your installation without re-installing. The steps are:

Update python

This might be done on your system already, if you have been updating the operating system on an ongoing basis.

apt-get update
apt-get install python-pip

Add source code repositories

sudo add-apt-repository ppa:archivematica/externals
wget -O - | apt-key add -
echo 'deb [arch=amd64] trusty main' >> /etc/apt/sources.list

Update Archivematica Storage Service

Ensure that the default user ‘test’ exists in the Storage Service before updating (create it if it doesn’t). Database migrations may not be correctly applied if not.

sudo apt-get update
sudo apt-get install archivematica-storage-service

Create new Storage Service user

Archivematica Storage Service 0.8.0 introduces a new security feature - each user is assigned an API key. All api interactions with the storage service require the use of an api key, including from the Archivematica Dashboard.

Log into the Storage Service with your existing credentials. Go to the Administration tab, and then select ‘users’ from the menu on the left. Create a new user. Once you have finished creating the new user, copy the api key that is displayed on the ‘edit user’ page. You will need this later after upgrading the Dashboard.

Update Archivematica

It is always a good idea to make a backup of your archivematica database before performing any updates. Exact procedures for updating will depend on your local installation, but a simple example would be to use mysqldump:

mysqldump -u root -p MCP > ~/am_backup.sql

If you do not have a password set for the root user in mysql, you can take out the ‘-p’ portion of that command. If there is a problem during the upgrade process, you can restore your mysql database from this backup and try the upgrade again.

During the update process you may be asked about updating configuration files. Choose to accept the maintainers versions. You will also be asked about updating the database, say ‘ok’ to each of those steps. If you have set a password for the root mysql database user, enter it when prompted. It is better to update the dashboard before updating the mcp components.

sudo apt-get install archivematica-common
sudo apt-get install archivematica-dashboard
sudo apt-get install archivematica-mcp-server
sudo apt-get install archivematica-mcp-client

(Optional) Update Elasticsearch

Archivematica 1.4.1 uses Elasticsearch version 1.4. Archivematica 1.5.0 will work with any version of Elasticsearch from 1.4 to 1.7.5. You do not have to upgrade Elasticsearch when upgrading Archivematica, although we recommend doing so, to make future upgrades easier.

Instructions on how to upgrade can be found on the Elasticsearch website. In general it should be possible to upgrade Elasticsearch on a standard Archivematica machine with the following commands:

sudo /etc/init.d/elasticsearch stop
sudo echo "deb stable main" >> /etc/apt/sources.list
sudo apt-get update
sudo apt-get install elasticsearch
sudo /etc/init.d/elasticsearch start

You will be prompted with questions about modifying configuration files. If you have not made any modifications to your Elasticsearch configuration, it should be safe to use the new versions of the configuration files that come with Elasticsearch.

Restart Services

sudo service uwsgi restart
sudo service nginx restart
sudo /etc/init.d/apache2 restart
sudo service gearman-job-server restart
sudo restart archivematica-mcp-server
sudo restart archivematica-mcp-client
sudo restart fits
sudo freshclam

Note, depending on how your Ubuntu system is set up, you may have trouble restarting gearman with the command in the block above. If that is the case, try this command instead:

sudo restart gearman-job-server

Update Dashboard Configuration

Log into the Archivematica dashboard with your existing credentials. Go to the administration tab, and click on ‘general configuration’ in the menu on the left. You will see a new ‘api key’ property in the Storage Service configuration section. Copy the api key you generated earlier, when creating a new Storage Service user, into this box and click save.

Installing Archivematica 1.5 packages (new install)

Archivematica packages in the past have been hosted on Launchpad, in an Ubuntu PPA (Personal Package Archive). With the 1.5.0 release, there is now a new repository at This has been introduced to allow one central place to store packages for multiple operating systems.

There are some dependencies still hosted on Launchpad, that have not yet been migrated to In a future release, all the requirements will be hosted in one repository, for the time being it is necessary to set up two different sources of packages.

  1. Add the archivematica/externals PPA to your list of trusted repositories (if add-apt-repositories is not available you must install python-software-properties first):
sudo apt-get update
sudo apt-get install python-software-properties
sudo add-apt-repository ppa:archivematica/externals
  1. Add to your list of trusted repositories
sudo wget -O - | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] trusty main" >> /etc/apt/sources.list'
  1. Add the ElasticSearch apt repository next:
sudo wget -O - | sudo apt-key add -
sudo sh -c 'echo "deb stable main" >> /etc/apt/sources.list'
  1. Update your system to the most recent 14.04 release. This step will also fetch a list of the software from the PPAs you just added to your system.
sudo apt-get update
sudo apt-get upgrade
  1. Install the storage service package
sudo apt-get install -y archivematica-storage-service
  1. Configure the storage service
sudo rm -f /etc/nginx/sites-enabled/default
sudo ln -s /etc/nginx/sites-available/storage /etc/nginx/sites-enabled/storage
sudo ln -s /etc/uwsgi/apps-available/storage.ini /etc/uwsgi/apps-enabled/storage.ini
sudo service uwsgi restart
sudo service nginx restart
  1. Install the Archivematica packages (each of these packages can be installed separately, if necessary). Say YES or OK to any prompts you get after entering the following into terminal:
sudo apt-get install archivematica-mcp-server
sudo apt-get install archivematica-mcp-client
sudo apt-get install archivematica-dashboard
sudo apt-get install elasticsearch
  1. Configure the dashboard
sudo rm -f /etc/apache2/sites-enabled/*default* [this might change]
sudo wget -q -O /etc/apache2/sites-available/default.conf
sudo ln -s /etc/apache2/sites-available/default.conf /etc/apache2/sites-enabled/default.conf
sudo /etc/init.d/apache2 restart
sudo freshclam
sudo /etc/init.d/clamav-daemon start
sudo /etc/init.d/elasticsearch restart
sudo service gearman-job-server restart
sudo start archivematica-mcp-server
sudo start archivematica-mcp-client
sudo start fits

If you have trouble with the gearman command try this as an alternative:

sudo restart gearman-job-server
  1. Test the storage service. The storage service runs as a separate web application from the Archivematica dashboard. Go to the following link in a web browser and log in as user test with the password test: http://localhost:8000 (or use the IP address of the machine you have been installing on)
  2. Create a new administrative user in the Storage service. The storage service has its own set of users. In the User menu in the Administrative tab of the storage service, add at least one administrative user, and delete or modify the test user. After you have created an administrative user, copy its API key to your clipboard.
  3. Test the dashboard. You can login to the Archivematica dashboard and finish the installation in a web browser: http://localhost (again, use the IP address of the machine you have been installing on). When prompted, enter the URL of the Storage Service, the name of the administrative user, and that user’s API key.
  4. Register your installation for full Format Policy Registry interoperability.

Install from source

Installing from source has been tested using ansible scripts. Ansible installations have been tested for new installations but are not fully tested for upgrades.

Instructions coming soon.

Install for CentOS/Redhat

Archivematica version 1.5.1 and higher support installation on CentOS/Redhat.


Extra repos:

Some repositories need to be installed in order to fullfill the installation procedure:

  • Extra packages for enterprise linux
sudo yum install -y epel-release
  • Elasticsearch
sudo -u root rpm --import
sudo -u root bash -c 'cat << EOF > /etc/yum.repos.d/elasticsearch.repo
name=Elasticsearch repository for 1.7 packages
  • Archivematica
sudo -u root bash -c 'cat << EOF > /etc/yum.repos.d/archivematica.repo

Service depencencies

Common services like elasticsearch, mariadb and gearmand should be installed and enabled before the archivematica install. It can be done with:

sudo -u root yum install -y java-1.8.0-openjdk-headless elasticsearch mariadb-server gearmand
sudo -u root systemctl enable elasticsearch
sudo -u root systemctl start elasticsearch
sudo -u root systemctl enable mariadb
sudo -u root systemctl start mariadb
sudo -u root systemctl enable gearmand
sudo -u root systemctl start gearmand

Install Archivematica Storage Service

  • First, we install the packages:
sudo -u root yum install -y python-pip archivematica-storage-service
  • After the package is installed, we need to populate the sqlite database, and collect some static files used by django. Those tasks must be run as “archivematica” user.
sudo -u archivematica bash -c " \
set -a -e -x
source /etc/sysconfig/archivematica-storage-service
cd /usr/share/archivematica/storage-service
/usr/lib/python2.7/archivematica/storage-service/bin/python migrate
/usr/lib/python2.7/archivematica/storage-service/bin/python collectstatic --noinput
  • And now, we enable and start the archivematica-storage-service and it’s nginx frontend
sudo -u root systemctl enable archivematica-storage-service
sudo -u root systemctl start archivematica-storage-service
sudo -u root systemctl enable nginx
sudo -u root systemctl start nginx


The storage service will be avaliable at http://<ip>:8001

Installing Archivematica Dashboard and MCP Server

  • First, install the pacakges:
sudo -u root yum install -y archivematica-common archivematica-mcp-server archivematica-dashboard
  • Create user and mysql database with:
sudo -H -u root mysql -hlocalhost -uroot -e "DROP DATABASE IF EXISTS MCP; CREATE DATABASE MCP CHARACTER SET utf8 COLLATE utf8_unicode_ci;"
sudo -H -u root mysql -hlocalhost -uroot -e "CREATE USER 'archivematica'@'localhost' IDENTIFIED BY 'demo';"
sudo -H -u root mysql -hlocalhost -uroot -e "GRANT ALL ON MCP.* TO 'archivematica'@'localhost';"
  • And as archivematica user, run migrations:
sudo -u archivematica bash -c " \
set -a -e -x
source /etc/sysconfig/archivematica-dashboard
cd /usr/share/archivematica/dashboard
/usr/lib/python2.7/archivematica/dashboard/bin/python syncdb --noinput
  • Start and enable services:
sudo -u root systemctl enable archivematica-mcp-server
sudo -u root systemctl start archivematica-mcp-server
sudo -u root systemctl enable archivematica-dashboard
sudo -u root systemctl start archivematica-dashboard
  • Reload nginx in order to load the dashboard config file:
sudo -u root systemctl reload nginx


The dashboard will be avaliable at http://ip:81

Installing Archivematica MCP client

  • First, we need to add some extra repos with the MCP Client dependencies:
  • Archivematica supplied external packages:
sudo -u root bash -c 'cat << EOF > /etc/yum.repos.d/archivematica-extras.repo
  • Nux multimedia repo
rpm -Uvh
  • Forensic tools repo
rpm -Uvh
  • Then, install the package:
sudo -u root yum install -y archivematica-mcp-client
  • The MCP Client expect some programs in certain paths, so we put things in place:
sudo cp /usr/bin/clamscan /usr/bin/clamdscan
sudo ln -s /usr/bin/7za /usr/bin/7z

After that, we can enable and start services

sudo -u root systemctl enable archivematica-mcp-client
sudo -u root systemctl start archivematica-mcp-client
sudo -u root systemctl enable fits-nailgun
sudo -u root systemctl start fits-nailgun

Finalizing installation

The dashboard will be available on port 81, and the storage service on port 8001. You will need to complete the installation by opening up the dashboard in a web browser, and filling in the form you are presented with. On the 2nd page of the installer, you are asked for information about the storage service. You will need to log into the storage service and find the api key that was generated for your user (in admin->users).


Each service have a configuration file in /etc/sysconfig/archivematica-packagename


If IPv6 is disabled, Nginx may refuse to start. If that is the case make sure that the listen directives used under /etc/nginx are not using IPv6 addresses like [::]:80.


Docker installations are experimental at this time- instructions coming soon.


The recommended way to install Archivematica for development is with Ansible and Vagrant. For instructions on how to install Archivematica from a virtual machine, see the Ansible & Vagrant Installation instructions on the Archivematica wiki.


Installing across multiple machines

It is possible to spread Archivematica’s processing load across several machines by installing the following services on separate machines:

  • Elasticsearch
  • gearman
  • mySQL

For help, send an email to Archivematica tech mailing list.

Firewall requirements

When installing Archivematica on multiple machines, all the machines must be able to reach each other on the following ports:

  • http, mysqld, gearman, nfs, ssh

Using AtoM 2.x with Archivematica

Archivematica 1.5 has been tested with and is recommended for use with AtoM versions 2.2. AtoM version 2.2 or higher is required for use with the hierarchical DIP functionality; see Arrange a SIP from backlog.

Installation instructions for Atom 2 are available on the documentation. When following those instructions, it is best to download Atom from the git repository (rather than use one of the supplied tarballs). When checking out Atom, use the head of either the stable/2.1.x, stable/2.2.x or qa/2.3.x branch (integration with qa branch is experimental).

Once you have a working AtoM installation, you can configure dip upload between Archivematica and Atom. The basic steps are:

  • Update atom dip upload configuration in the Archivematica dashboard
  • Confirm atom-worker is configured on the Atom server (copy the atom- worker.conf file from atom source to /etc/init/)
  • Enable the Sword Plugin in the AtoM plugins page
  • Enable job scheduling in the AtoM settings page (AtoM version 2.1 or lower only)
  • Confirm gearman is installed on the AtoM server
  • Configure ssh keys to allow rsync to work for the archivematica user, from the Archivematica server to the Atom server
  • Start gearman on the Atom server
  • Start the atom worker on the AtoM server