Difference between revisions of "Install-1.3.0-packages"
Line 115: | Line 115: | ||
* Register your installation for full Format Policy Registry interoperability. | * Register your installation for full Format Policy Registry interoperability. | ||
− | [[Register_1.3|Register Archivematica 1.3]] | + | [[Register_1.3.0|Register Archivematica 1.3.0]] |
== Using AtoM 2.x with Archivematica == | == Using AtoM 2.x with Archivematica == |
Latest revision as of 11:15, 24 October 2014
Installation >> Install 1.3.0 >> Install 1.3.0 packages
Updating from Archivematica 1.2[edit]
If you have installed Archivematica 1.2.0 or 1.2.1 from packages, it is possible to update your installation without re-installing. The steps are:
Update Archivematica Storage Service[edit]
sudo apt-get update sudo apt-get install archivematica-storage-service
Update Archivematica[edit]
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 > ~/am12_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
Restart Services[edit]
sudo service uwsgi restart sudo service nginx restart sudo /etc/init.d/apache2 restart sudo /etc/init.d/elasticsearch restart sudo /etc/init.d/gearman-job-server restart sudo restart archivematica-mcp-server sudo restart archivematica-mcp-client sudo restart fits
Installing Archivematica 1.3.0 packages (new install)[edit]
Archivematica packages are hosted on Launchpad, in an Ubuntu PPA (Personal Package Archive). In order to install software onto your Ubuntu 12.04 or 14.04 system from a PPA:
- Add the archivematica/release 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/release sudo add-apt-repository ppa:archivematica/externals
- Add the ElasticSearch apt repository next (from http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-repositories.html):
sudo wget -O - http://packages.elasticsearch.org/GPG-KEY-elasticsearch | sudo apt-key add -
Then add this line to the bottom of /etc/apt/sources.list
deb http://packages.elasticsearch.org/elasticsearch/0.90/debian stable main
- Update your system to the most recent version of your release (12.04.5 or 14.04.1 at the time of this writing).
- 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
- Install all 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-storage-service 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
- Configure the dashboard and storage service
note:these steps are safe to do on a desktop, or a machine dedicated to Archivematica. They may not be advisable on an existing web server. Consult with your web server administrator if you are unsure.
sudo wget -q https://raw.githubusercontent.com/artefactual/archivematica/stable/1.3.x/localDevSetup/apache/apache.default -O /etc/apache2/sites-available/default sudo rm /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 sudo /etc/init.d/apache2 restart sudo freshclam sudo /etc/init.d/clamav-daemon start sudo /etc/init.d/elasticsearch restart sudo /etc/init.d/gearman-job-server restart sudo start archivematica-mcp-server sudo start archivematica-mcp-client sudo start fits
- 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:
http://localhost:8000 (or use the IP address of the machine you have been installing on).
log in as user: test password: test
- 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.
- 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)
- Register your installation for full Format Policy Registry interoperability.
Using AtoM 2.x with Archivematica[edit]
Archivematica has been successfully tested with AtoM 2.x. The best known configuration is Archivematica 1.3.0 with AtoM deployed from the stable/2.1.x branch. Archivematica has been successfully tested with the qa/2.2.x branch.
Installation instructions for Atom 2 are available on the accesstomemory.org website https://www.accesstomemory.org/en/docs/2.1/ . 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 or qa/2.2.x branch.
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
- 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
These steps are detailed on the DIP Upload page.