Administrator manual 0.9 - Revision history

Mcantelon at 21:05, 19 March 2013

2013-03-19T21:05:24Z

Mcantelon: /* Configuration */

2013-03-19T21:03:20Z

Configuration

Mcantelon: /* Configuration */

2013-03-19T21:02:09Z

Configuration

Mcantelon: /* Configuration */

2013-03-19T21:00:58Z

Configuration

Mcantelon: /* Configuration */

2013-03-19T21:00:18Z

Configuration

Mcantelon at 20:59, 19 March 2013

2013-03-19T20:59:53Z

Sevein: /* AtoM server configuration */

2013-03-01T23:17:47Z

AtoM server configuration

Courtney: /* Dashboard administration tab */

2013-02-28T19:00:37Z

Dashboard administration tab

Sevein: /* AtoM server configuration */

2013-02-28T18:54:01Z

AtoM server configuration

Courtney: /* AtoM DIP upload */

2013-02-28T18:52:00Z

AtoM DIP upload

@@ Line 7: / Line 7: @@
 = Configuration =
 Archivematica stores working data in MySQL. Archivematica, by default, creates a user named "demo" with the password "demo", but you may wish to create a new user with a stronger password. Here's how you can create a unique MySQL user for Archivematica and grant it the appropriate permissions if need be.
@@ Line 27: / Line 29: @@
 Finaly, change to the <code>src/dashboard/src</code> directory in the Archivematica source tree and edit <code>settings.py</code>, changing the values in the <code>DATABASES</code> dictionary for <code>USER</code> and <code>PASSWORD</code>.
-= Upgrading =
+== Setting organization code / institution Name ==
 *This is done to add the repository code and name as a PREMIS agent. A command must be issued to modify the SQL database:
 <pre>
@@ Line 204: / Line 204: @@
 :* ICA-AtoM
 * Archivematica does not presently support secured sockets. See Issue 990, Issue 690 Because of this, it's highly recommended to run Archivematica on a secure, isolated network.
 = Questions =

@@ Line 8: / Line 8: @@
 = Configuration =
-Archivematica stores working data in MySQL. Here's how you can create a unique MySQL user for Archivematica and grant it the appropriate permissions if need be.
+Archivematica stores working data in MySQL. Archivematica, by default, creates a user named "demo" with the password "demo", but you may wish to create a new user with a stronger password. Here's how you can create a unique MySQL user for Archivematica and grant it the appropriate permissions if need be.
 Enter the MySQL shell as the "root" user:

@@ Line 23: / Line 23: @@
      mysql> quit
-After specifying the user, you should then set the MySQL credentials for the Archivematica server at: <code>src/archivematicaCommon/etc/dbsettings</code>.
+After specifying the user, you should then set the MySQL credentials for the Archivematica server at: <code>/etc/archivematica/archivematicaCommon/dbsettings</code>.
 Finaly, change to the <code>src/dashboard/src</code> directory in the Archivematica source tree and edit <code>settings.py</code>, changing the values in the <code>DATABASES</code> dictionary for <code>USER</code> and <code>PASSWORD</code>.

@@ Line 16: / Line 16: @@
 Specify a MySQL user (named "archivematica" in this example with a password of "somepassword") with full access to the Archivematica's MySQL database:
-     mysql> GRANT ALL PRIVILEGES ON MCP.* TO 'dashboard'@'127.0.0.1' IDENTIFIED BY 'somepassword';
+     mysql> GRANT ALL PRIVILEGES ON MCP.* TO 'dashboard'@'127.0.0.1'
-     mysql> GRANT ALL PRIVILEGES ON MCP.* TO 'dashboard'@'localhost' IDENTIFIED BY 'somepassword';
+                 IDENTIFIED BY 'somepassword';
      mysql> flush privileges;
      mysql> quit

@@ Line 10: / Line 10: @@
 Archivematica stores working data in MySQL. Here's how you can create a unique MySQL user for Archivematica and grant it the appropriate permissions if need be.
-Enter the MySQL shell:
+Enter the MySQL shell as the "root" user:
      $ mysql -u root -p<root password>

@@ Line 5: / Line 5: @@
 = Installation =
 * [[Installation|Instructions for installing the latest build of Archivematica on your server]]
 = Upgrading =

@@ Line 59: / Line 59: @@
 <pre>
   $ sudo mkdir /home/archivematica/.ssh
-  $ chmod 700 /home/archivematica
+  $ chmod 700 /home/archivematica/.ssh/
   $ sudo vim /home/archivematica/.ssh/authorized_keys // Paste here the contents of id_dsa.pub
   $ chown -R archivematica:archivematica /home/archivematica

@@ Line 25: / Line 25: @@
 The parameters that you'll most likely want to set are <code>url</code>, <code>email</code>, and <code>password</code>. These parameters, respectively, specify the destination AtoM website's URL, the email address used to log in to the website, and the password used to log in to the website.
-AtoM DIP upload can also use [http://en.wikipedia.org/wiki/Rsync Rsync] as a transfer mechanism. Rsync is an open source utility for efficiently transferring files. The <code>rsync-target</code> parameter is used to specify an Rsync-style target host/directory pairing, "foobar.com:~/dips/" for example. The <code>rsync-command</code> parameter is used to specify rsync connection options, "ssh -p 22222 -l user" for example.
+AtoM DIP upload can also use [http://en.wikipedia.org/wiki/Rsync Rsync] as a transfer mechanism. Rsync is an open source utility for efficiently transferring files. The <code>rsync-target</code> parameter is used to specify an Rsync-style target host/directory pairing, "foobar.com:~/dips/" for example. The <code>rsync-command</code> parameter is used to specify rsync connection options, "ssh -p 22222 -l user" for example. If you are using the rsync option, please see AtoM server configuration below.
 To set any parameters for AtoM DIP upload change the values, preserving the existing format they're specified in, in the "Command arguments" field then click "Save".
@@ Line 31: / Line 31: @@
 Note that in AtoM, the sword plugin (Admin --> qtSwordPlugin) and job scheduling (Admin --> Settings --> Job scheduling) must both be enabled in order for AtoM to receive uploaded DIPs.
-== AtoM server configuration ==
+=== AtoM server configuration ===
-To make possible to send DIPs from Archivematica to the AtoM server, we needed to:
+This server configuration step is necessary to allow Archivematica to log in to the AtoM server without passwords, and only when the user is deploying the rsync option described above in the AtoM DIP upload section.
 Generate SSH keys for the Archivematica user. Leave the passphrase field blank.
@@ Line 42: / Line 44: @@
 </pre>
-Copy the contents of <code>/var/lib/archivematica/.ssh/id_rsa.pub</code> somewhere handy, we will need it later.
+Copy the contents of <code>/var/lib/archivematica/.ssh/id_rsa.pub</code> somewhere handy, you will need it later.
-Now, it's turn to configure the AtoM server so Archivematica can send the DIPs using SSH/rsync. For that purpose, we are going to create an user called <code>archivematica</code> and we are going to assign him a restricted shell with access only to rsync:
+Now, it's time to configure the AtoM server so Archivematica can send the DIPs using SSH/rsync. For that purpose, you will create a user called <code>archivematica</code> and we are going to assign that user a restricted shell with access only to rsync:
 <pre>
@@ Line 53: / Line 55: @@
 </pre>
-Let's add the SSH key that we generated before:
+Add the SSH key that we generated before:
 <pre>

← Older revision		Revision as of 18:52, 28 February 2013
Line 30:		Line 30:

	Note that in AtoM, the sword plugin (Admin --> qtSwordPlugin) and job scheduling (Admin --> Settings --> Job scheduling) must both be enabled in order for AtoM to receive uploaded DIPs.		Note that in AtoM, the sword plugin (Admin --> qtSwordPlugin) and job scheduling (Admin --> Settings --> Job scheduling) must both be enabled in order for AtoM to receive uploaded DIPs.
		+
		+	== AtoM server configuration ==
		+
		+	To make possible to send DIPs from Archivematica to the AtoM server, we needed to:
		+
		+	Generate SSH keys for the Archivematica user. Leave the passphrase field blank.
		+	<pre>
		+	$ sudo -i -u archivematica
		+	$ cd ~
		+	$ ssh-keygen
		+	</pre>
		+
		+	Copy the contents of <code>/var/lib/archivematica/.ssh/id_rsa.pub</code> somewhere handy, we will need it later.
		+
		+	Now, it's turn to configure the AtoM server so Archivematica can send the DIPs using SSH/rsync. For that purpose, we are going to create an user called <code>archivematica</code> and we are going to assign him a restricted shell with access only to rsync:
		+
		+	<pre>
		+	$ sudo apt-get install rssh
		+	$ sudo useradd -d /home/archivematica -m -s /usr/bin/rssh archivematica
		+	$ sudo passswd -l archivematica
		+	$ sudo vim /etc/rssh.conf // Make sure that allowrsync is uncommented!
		+	</pre>
		+
		+	Let's add the SSH key that we generated before:
		+
		+	<pre>
		+	<pre>
		+	$ sudo mkdir /home/archivematica/.ssh
		+	$ chmod 700 /home/archivematica
		+	$ sudo vim /home/archivematica/.ssh/authorized_keys // Paste here the contents of id_dsa.pub
		+	$ chown -R archivematica:archivematica /home/archivematica
		+	</pre>
		+
		+	In Archivematica, make sure that you update the <code>--rsync-target</code> accordingly.<br />
		+	These are the parameters that we are passing to the upload-qubit microservice.<br />
		+	Go to the Administration > Upload DIP page in the dashboard.
		+
		+	Generic parameters:
		+
		+	<pre>
		+	--url="http://atom-hostname/index.php" \
		+	--email="demo@example.com" \
		+	--password="demo" \
		+	--uuid="%SIPUUID%" \
		+	--rsync-target="archivematica@atom-hostname:/tmp" \
		+	--debug
		+	</pre>

	== CONTENTdm DIP upload ==		== CONTENTdm DIP upload ==