https://wiki.umiacs.umd.edu/adapt/api.php?action=feedcontributions&user=Shake&feedformat=atomAdapt - User contributions [en]2024-03-28T20:30:00ZUser contributionsMediaWiki 1.39.6https://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2939Ace:Audit Manager Installation Guide2019-07-25T18:32:41Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
* https://ace.umiacs.io<br />
* or https://gitlab.com/chronopolis/audit-control-environment/-/releases<br />
* or https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases/1.14.1<br />
<br />
Previous versions can be found at:<br />
* https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace-am.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Ace:Audit_Manager_User_Guide|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Main&diff=2938Ace:Main2019-07-25T18:31:41Z<p>Shake: </p>
<hr />
<div>ACE (Auditing Control Environment) is a system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.<br />
<br />
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. <br />
<br />
Anyone wishing to audit their files with ACE only needs to install an Audit Manager locally to manage their files. The ADAPT project runs a publically available IMS at ims.umiacs.umd.edu that any group may freely use.<br />
<br />
{| width="75%" style="margin-left: 75px;"<br />
| '''Audit Manager''' || '''Integrity Management Service'''<br />
|-<br />
| [[Ace:Audit Manager Installation Guide|Download Audit Manager]] || [[Ace:Ace IMS System|System Documentation]]<br />
|-<br />
| [[Ace:Audit Manager User Guide|User Guide]] || [http://ims.umiacs.umd.edu:8080/ace-ims/IMSWebService IMS Webservice]<br />
|-<br />
| [http://groups.google.com/group/ace-devel Discussion List] || [[Ace:Validating Witness and Tokens|Validating Tokens and Witnesses]]<br />
|-<br />
| [[Ace:Audit Manager Upgrading|Upgrade Audit Manager]] || [http://groups.google.com/group/ace-ims-witness?hl=en IMS Witness Google Goup]<br />
|- <br />
| [[Ace:AM Config Reference|AM Configuration Options]] || [http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness IMS Witness UMIACS listserv]<br />
|-<br />
| [[Ace:Comparing Collections|Comparing Collections]] || [[Ace:IMS Installation| IMS Installation Guide]]<br />
|-<br />
| '''Resources'''<br />
|-<br />
| [https://gitlab.com/chronopolis/audit-control-environment Gitlab Project Repo]<br />
|-<br />
| [[Ace:Devel Pages|Development Documentation]]<br />
|-<br />
| [[Ace:Webstart Client|Auditor Application]] || <br />
|-<br />
| [http://digitalcommons.uconn.edu/libr_pubs/39/ Step by Step installation instructions]<br />
|}<br />
<br />
<br />
'''Papers and Presentations'''<br />
<br />
* Smorul, M., Song, S., and JaJa, J. An Implementation of the Audit Control Environment(ACE) to Support the Long Term Integrity of Digital Archives. in DigCCurr 2009. 2009: University of North Carolina.[[media:DigCCurr2009_060909.pdf|pdf]] presentation [[media:Smorul-digccurr09.ppt|ppt]]<br />
* ACE Presentation at Archiving 2007 (5/07) [[media: ACE-Archiving2007.ppt|ppt]]<br />
* Song, S. and JaJa, J. ACE: A Novel Software Platform to Ensure the Integrity of Long Term Archives. in Archiving 2007. 2007: IS&T. [[media:rad71E67.pdf|pdf]]<br />
<br />
Development of the ACE Version1.0 release was partially sponsored by the US National Archives and Records Administration. The basic research on ACE was partially sponsored under a DIGARCH grant from NSF/Library of Congress.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Update_Audit_Manager&diff=2937Ace:Update Audit Manager2019-07-10T15:59:45Z<p>Shake: </p>
<hr />
<div>Updating previous versions of ACE.<br />
<br />
<br />
; 1. Note the version you are running.<br />
Login to your installation and note the current version you are running at the bottom of the web site.<br />
<br />
; 2. Stop tomcat.<br />
Run TOMCAT/bin/shutdown.sh or TOMCAT/bin/shutdown.bat<br />
<br />
; 3. Remove old version. <br />
Delete the ace war file(ace-am.war) and directory(ace-am) in TOMCAT/webapps. it may be named begin with an uppercase A as in Ace-am.<br />
<br />
; 4. Install latest webapp.<br />
Place the latest war file from https://ace.umiacs.io/ in the webapps directory. If your previous version was named Ace-am rather than ace-am you will need to rename the war file appropriately.<br />
<br />
; 5. Download database updates.<br />
On the download page above, save all the appropriate updates.sql file. For example, if you are upgrading from 1.0 to 1.2.1, you will need to download 1.0-1.1.update.sql and 1.1-1.2.updates.sql. <br />
<br />
; 6. Update database.<br />
Connect to mysql and update the ace database. execute each sql script in order. For example, run 1.0-1.1.update.sql before 1.1-1.2.updates.sql, etc... <br />
<br />
<pre><br />
[root@loach ~]# mysql -Daceam <br />
Reading table information for completion of table and column names<br />
You can turn off this feature to get a quicker startup with -A<br />
<br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 648<br />
Server version: 5.0.45 Source distribution<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> source 1.0-1.1.update.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> source 1.1-1.2.updates.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.01 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> quit<br />
Bye<br />
</pre><br />
<br />
; 7. Restart tomcat.<br />
Run TOMCAT/bin/startup.sh(unix) or TOMCAT/bin/startup.bat (windows) and point your web browser at the audit manager. You should see the latest version listed at the bottom of the page.<br />
<br />
The ACE download page will have copies of the context and ace-am.sql files. If you are updating, you do not need new versions of these files.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2936Ace:Audit Manager Installation Guide2019-07-10T15:59:05Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
* https://ace.umiacs.io<br />
* or https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.14.1<br />
* or https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases/1.14.1<br />
<br />
Previous versions can be found at:<br />
* https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace-am.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Ace:Audit_Manager_User_Guide|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2935Ace:Audit Manager Installation Guide2019-07-10T15:58:38Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
* https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.14.1<br />
* or https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases/1.14.1<br />
* or https://ace.umiacs.io<br />
<br />
Previous versions can be found at:<br />
* https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace-am.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Ace:Audit_Manager_User_Guide|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2934Main Page2019-07-10T15:58:02Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><br />
<ul><br />
<li>[[Ace|Integrity Management (ACE)]]<br />
<li>[[WarcManager|Warc Management Utility]]<br />
<li>[https://gitlab.umiacs.umd.edu/adapt/ingestion-tools RESTful Bag server Implementation]</ul></td><br />
<td><ul><br />
<li>[[Webarc:Main|Web Archive Indexing]]<br />
<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
'''ACE Development Infrastructure'''<br />
* current release https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.14.1<br />
* releases https://gitlab.umiacs.umd.edu/adapt/ace/tags<br />
* public source repository https://gitlab.umiacs.umd.edu/adapt/ace<br />
* CI testing https://gitlab.umiacs.umd.edu/adapt/ace/pipelines<br />
* CI development builds http://adaptci01.umiacs.umd.edu/resource/ace<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Current: https://gitlab.umiacs.umd.edu/adapt/ace/issues<br />
<br />
'''ACE V 1.10 (4/22)'''<br />
* Bug Fix for a deadlock when connection to the IMS was lost<br />
<br />
'''ACE V 1.9 (1/14)'''<br />
* Frontend UI improvements,<br />
* Backend threading improvements when ingesting tokens and auditing collections<br />
<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2933Main Page2019-05-13T16:22:22Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><br />
<ul><br />
<li>[[Ace|Integrity Management (ACE)]]<br />
<li>[[WarcManager|Warc Management Utility]]<br />
<li>[https://gitlab.umiacs.umd.edu/adapt/ingestion-tools RESTful Bag server Implementation]</ul></td><br />
<td><ul><br />
<li>[[Webarc:Main|Web Archive Indexing]]<br />
<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
'''ACE Development Infrastructure'''<br />
* current release https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.13<br />
* releases https://gitlab.umiacs.umd.edu/adapt/ace/tags<br />
* public source repository https://gitlab.umiacs.umd.edu/adapt/ace<br />
* CI testing https://gitlab.umiacs.umd.edu/adapt/ace/pipelines<br />
* CI development builds http://adaptci01.umiacs.umd.edu/resource/ace<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Current: https://gitlab.umiacs.umd.edu/adapt/ace/issues<br />
<br />
'''ACE V 1.10 (4/22)'''<br />
* Bug Fix for a deadlock when connection to the IMS was lost<br />
<br />
'''ACE V 1.9 (1/14)'''<br />
* Frontend UI improvements,<br />
* Backend threading improvements when ingesting tokens and auditing collections<br />
<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2932Ace:Audit Manager Installation Guide2019-05-02T16:23:46Z<p>Shake: Fix broken link</p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
* https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.13<br />
* or https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases/1.13<br />
<br />
Previous versions can be found at:<br />
* https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace-am.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Ace:Audit_Manager_User_Guide|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2931Ace:Audit Manager Installation Guide2019-05-02T16:22:35Z<p>Shake: Update links</p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
* https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.13<br />
* or https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases/1.13<br />
<br />
Previous versions can be found at:<br />
* https://obj.umiacs.umd.edu/obj/bucket/ace/view/releases<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace-am.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Main&diff=2930Ace:Main2018-05-14T21:51:31Z<p>Shake: </p>
<hr />
<div>ACE (Auditing Control Environment) is a system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.<br />
<br />
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. <br />
<br />
Anyone wishing to audit their files with ACE only needs to install an Audit Manager locally to manage their files. The ADAPT project runs a publically available IMS at ims.umiacs.umd.edu that any group may freely use.<br />
<br />
{| width="75%" style="margin-left: 75px;"<br />
| '''Audit Manager''' || '''Integrity Management Service'''<br />
|-<br />
| [[Ace:Audit Manager Installation Guide|Download Audit Manager]] || [[Ace:Ace IMS System|System Documentation]]<br />
|-<br />
| [[Ace:Audit Manager User Guide|User Guide]] || [http://ims.umiacs.umd.edu:8080/ace-ims/IMSWebService IMS Webservice]<br />
|-<br />
| [http://groups.google.com/group/ace-devel Discussion List] || [[Ace:Validating Witness and Tokens|Validating Tokens and Witnesses]]<br />
|-<br />
| [[Ace:Audit Manager Upgrading|Upgrade Audit Manager]] || [http://groups.google.com/group/ace-ims-witness?hl=en IMS Witness Google Goup]<br />
|- <br />
| [[Ace:AM Config Reference|AM Configuration Options]] || [http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness IMS Witness UMIACS listserv]<br />
|-<br />
| [[Ace:Comparing Collections|Comparing Collections]] || [[Ace:IMS Installation| IMS Installation Guide]]<br />
|-<br />
| '''Resources'''<br />
|-<br />
| [https://gitlab.umiacs.umd.edu/adapt/ace Gitlab Project Repo]<br />
|-<br />
| [[Ace:Devel Pages|Development Documentation]]<br />
|-<br />
| [[Ace:Webstart Client|Auditor Application]] || <br />
|-<br />
| [http://digitalcommons.uconn.edu/libr_pubs/39/ Step by Step installation instructions]<br />
|}<br />
<br />
<br />
'''Papers and Presentations'''<br />
<br />
* Smorul, M., Song, S., and JaJa, J. An Implementation of the Audit Control Environment(ACE) to Support the Long Term Integrity of Digital Archives. in DigCCurr 2009. 2009: University of North Carolina.[[media:DigCCurr2009_060909.pdf|pdf]] presentation [[media:Smorul-digccurr09.ppt|ppt]]<br />
* ACE Presentation at Archiving 2007 (5/07) [[media: ACE-Archiving2007.ppt|ppt]]<br />
* Song, S. and JaJa, J. ACE: A Novel Software Platform to Ensure the Integrity of Long Term Archives. in Archiving 2007. 2007: IS&T. [[media:rad71E67.pdf|pdf]]<br />
<br />
Development of the ACE Version1.0 release was partially sponsored by the US National Archives and Records Administration. The basic research on ACE was partially sponsored under a DIGARCH grant from NSF/Library of Congress.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Comparing_Collections&diff=2929Ace:Comparing Collections2018-05-14T21:50:34Z<p>Shake: /* Step 2: Add the Peer User to A Local ACE */</p>
<hr />
<div>The ACE AM allows you to compare collections to an external manifest. This is useful when you want to compare sites that have replicated data, or to verify all data was successfully loaded during ingestion.<br />
<br />
There are two ways to compare collection, first is to register peer ACE AM installations and automatically compare collections as part of an audit. The second from an external data file containing digests and filenames.<br />
<br />
==Peer Comparisons==<br />
<br />
Comparing collections with a Peer site is a multi-step process which allows your ACE instance to query a peer ACE's digests for a given collection. First a user is needed at the Peer site for your ACE to be able to query for file digests. Then the Peer site needs to be registered in your local ACE. Finally, comparisons can be done by either manually issuing a comparison or by adding a PeerCollection to your Collection which you wish to compare.<br />
<br />
===Step 1: Create a Peer User===<br />
<br />
At the remote site, a User needs to be created in order for your ACE to have access to the remote ACE. The comparisons run through a series of HTTP requests, and as such it is recommended to only use a minimal set of Roles for the Peer User.<br />
<br />
A User can be created by browsing to the Accounts servlet (/Users).<br />
<br />
[[Image:Peer_roles.png||Minimal User Roles]]<br />
<br />
===Step 2: Add the Peer User to A Local ACE===<br />
<br />
Once a user is created for you at the Peer Site, your ACE needs to store the credentials. This can be done on the PartnetSite servlet (/PartnerSite) which can be found by browsing with:<br />
* Status (Collection): Compare Collection<br />
** Partner: Add New<br />
<br />
[[Image:Add_partner.png||Add Partner Dialogue]]<br />
<br />
===Step 3a: Manually Selecting the Collection===<br />
<br />
After the user setup is complete and your ACE AM can communicating with the Peer ACE AM, a manual collection comparison can be done through the CompareCollection Servlet.<br />
<br />
This is the same servlet as in Step 2. After selecting a Partner Site to compare against, a listing of collections will be shown which you can compare against.<br />
<br />
* Note: If the credentials are not correct, you will be able to see an Exception in the aceam.log<br />
* Note: There is currently a bug where if a PartnerSite has a large amount of collections, not all will be shown.<br />
<br />
===Step 3b: Registering a PeerCollection with a Local Collection===<br />
<br />
If you wish to have collections compared automatically when auditing, you simply need to go to the Collection Settings and select the 'Add Peer' dialogue. This then follows the same process as the manual selection. Once a collection has been chosen, it will be persisted to the ACE AM database and used to compare against during audits.<br />
<br />
<br />
==Manually Compare==<br />
<br />
Manually comparing collections is a two step process. First a source list of digests and filenames needs to be generated. The second step is to load that list into an AM installation for comparison. To manually compare collections between AM installations, you would download the digest list from the first installation, then upload the list to the second for comparison.<br />
<br />
===Step 1: Generate Digest List===<br />
<br />
The format of the list is a simple, SHA-256 digest, followed by one or more spaces or tabs, then the path to the file in the collection.<br />
<br />
Example source list.<br />
<pre><br />
01348875911b94af38b35f304dcd75348f437734696e26b40fd868eecd687d35 /state/data/state/state-2007-10-ARC/state-20071001-aud-000000.arc.gz<br />
365fe0af21237b750258f6b8c48b25964d0dd5c7d612748eff2f6526f43682bb /state/data/state/state-2007-10-ARC/state-20071001-aud-000001.arc.gz<br />
893298b40da08a1b9ce0c7994c8f2717cedb23d046936c8e24bd62655ca1962b /state/data/state/state-2007-10-ARC/state-20071001-aud-000002.arc.gz<br />
ba7cce400971bd56377e2d79a21192c63e0328e7651728345c49ebf35fb4999d /state/data/state/state-2007-10-ARC/state-20071001-aud-000003.arc.gz<br />
9827832cdfd4a9565422e41fd334eb09a23c835772184936ffebabb147eb5b8a /state/data/state/state-2007-10-ARC/state-20071001-aud-000004.arc.gz<br />
3d55a5b19dd6133e598fb29ff89444fb05196863c21d8773a03dbe16c0b42615 /state/data/state/state-2007-10-ARC/state-20071001-aud-000005.arc.gz<br />
ea0880b33fb9b237299c7e92578f4881c820b93e3d130a5818e3b3a3e90b8872 /state/data/state/state-2007-10-ARC/state-20071001-aud-000006.arc.gz<br />
45b632a3de7ca7c38a916242d78cedce6f11004cef99e4642194a48651db597f /state/data/state/state-2007-10-ARC/state-20071001-aud-000007.arc.gz<br />
bca0a7d6f78b9d46196bb502ef31782d0b3ea5a075ca61691bdd0a2ffc3cfd24 /state/data/state/state-2007-10-ARC/state-20071001-aud-000008.arc.gz<br />
4ec209a01449552454b57d82e12c0848982010ebd7f36e4ac3206576819531cf /state/data/state/state-2007-10-ARC/state-20071001-aud-000009.arc.gz<br />
c4ed9102ba6e8f0ea5f9bfeb06318b3db2230733c5fd9a22b18405dcfe820a7f /state/data/state/state-2007-10-ARC/state-20071001-aud-000010.arc.gz<br />
b6f97b66eff760a3bbef4e7895be9432fa4dfcb206d42d789c5ecfb4343eadc1 /state/data/state/state-2007-10-ARC/state-20071001-aud-000011.arc.gz<br />
ab3f8d618e51032418a3285fd24687f7a2a006cd546de43e575c72b1fed727e4 /state/data/state/state-2007-10-ARC/state-20071001-aud-000012.arc.gz<br />
</pre><br />
<br />
Directories '''must''' be separated by a /. This is different from Windows where directories are separated by a \.<br />
<br />
The Audit Manager is able to supply a list of digests for a collection or directory. <br />
# From the status page, select the collection you wish to generate a list for<br />
# Click on more..., then 'Download Digests'. You will see a list of digests and filenames in the correct format. You can right-click and save the list to your hard drive.<br />
<br />
===Step 2: Upload to ACE===<br />
<br />
From the status screen, select the collection you wish to compare. Click the 'more...' link to bring up the drop down menu, then click 'Compare Collection'. You will see the following screen. Click on 'Browse' and select the name of the file you saved your digest link into during step 1. Click submit.<br />
<br />
[[Image:Compare-1.png|400px]]<br />
<br />
<br />
If everything in the file you submitted matches the selected collection, you will see the following summary showing no differences.<br />
<br />
[[Image:Compare-3.png|400px]]<br />
<br />
<br />
If, for some reason there are differences, then your screen may look something like the following:<br />
<br />
[[Image:Compare.png|400px]]<br />
<br />
There are four different ways in which collections may differ.<br />
<br />
;Files in original collection, but not in supplied<br />
:This is a list of files that appear in the collection being monitored by ACE, but do not appear in the uploaded file.<br />
;Files in supplied file, but not original collection<br />
:These are files that appear in the uploaded list, but not in the collection monitored by ACE.<br />
;Files with different names, but same digests<br />
:These are files which have the same content, but only differ in directory or name. This is seen when files are renamed and moved across different operating systems.<br />
;Files with same names, but different digests<br />
:These are files that have the same directory and name, but have different content. Most likely seen during a bad replication.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=File:Add_partner.png&diff=2928File:Add partner.png2018-05-14T21:50:12Z<p>Shake: </p>
<hr />
<div></div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Comparing_Collections&diff=2927Ace:Comparing Collections2018-05-14T21:50:02Z<p>Shake: </p>
<hr />
<div>The ACE AM allows you to compare collections to an external manifest. This is useful when you want to compare sites that have replicated data, or to verify all data was successfully loaded during ingestion.<br />
<br />
There are two ways to compare collection, first is to register peer ACE AM installations and automatically compare collections as part of an audit. The second from an external data file containing digests and filenames.<br />
<br />
==Peer Comparisons==<br />
<br />
Comparing collections with a Peer site is a multi-step process which allows your ACE instance to query a peer ACE's digests for a given collection. First a user is needed at the Peer site for your ACE to be able to query for file digests. Then the Peer site needs to be registered in your local ACE. Finally, comparisons can be done by either manually issuing a comparison or by adding a PeerCollection to your Collection which you wish to compare.<br />
<br />
===Step 1: Create a Peer User===<br />
<br />
At the remote site, a User needs to be created in order for your ACE to have access to the remote ACE. The comparisons run through a series of HTTP requests, and as such it is recommended to only use a minimal set of Roles for the Peer User.<br />
<br />
A User can be created by browsing to the Accounts servlet (/Users).<br />
<br />
[[Image:Peer_roles.png||Minimal User Roles]]<br />
<br />
===Step 2: Add the Peer User to A Local ACE===<br />
<br />
Once a user is created for you at the Peer Site, your ACE needs to store the credentials. This can be done on the PartnetSite servlet (/PartnerSite) which can be found by browsing with:<br />
* Status (Collection): Compare Collection<br />
** Partner: Add New<br />
<br />
[[Image:add_partner.png||Add Partner Dialogue]]<br />
<br />
===Step 3a: Manually Selecting the Collection===<br />
<br />
After the user setup is complete and your ACE AM can communicating with the Peer ACE AM, a manual collection comparison can be done through the CompareCollection Servlet.<br />
<br />
This is the same servlet as in Step 2. After selecting a Partner Site to compare against, a listing of collections will be shown which you can compare against.<br />
<br />
* Note: If the credentials are not correct, you will be able to see an Exception in the aceam.log<br />
* Note: There is currently a bug where if a PartnerSite has a large amount of collections, not all will be shown.<br />
<br />
===Step 3b: Registering a PeerCollection with a Local Collection===<br />
<br />
If you wish to have collections compared automatically when auditing, you simply need to go to the Collection Settings and select the 'Add Peer' dialogue. This then follows the same process as the manual selection. Once a collection has been chosen, it will be persisted to the ACE AM database and used to compare against during audits.<br />
<br />
<br />
==Manually Compare==<br />
<br />
Manually comparing collections is a two step process. First a source list of digests and filenames needs to be generated. The second step is to load that list into an AM installation for comparison. To manually compare collections between AM installations, you would download the digest list from the first installation, then upload the list to the second for comparison.<br />
<br />
===Step 1: Generate Digest List===<br />
<br />
The format of the list is a simple, SHA-256 digest, followed by one or more spaces or tabs, then the path to the file in the collection.<br />
<br />
Example source list.<br />
<pre><br />
01348875911b94af38b35f304dcd75348f437734696e26b40fd868eecd687d35 /state/data/state/state-2007-10-ARC/state-20071001-aud-000000.arc.gz<br />
365fe0af21237b750258f6b8c48b25964d0dd5c7d612748eff2f6526f43682bb /state/data/state/state-2007-10-ARC/state-20071001-aud-000001.arc.gz<br />
893298b40da08a1b9ce0c7994c8f2717cedb23d046936c8e24bd62655ca1962b /state/data/state/state-2007-10-ARC/state-20071001-aud-000002.arc.gz<br />
ba7cce400971bd56377e2d79a21192c63e0328e7651728345c49ebf35fb4999d /state/data/state/state-2007-10-ARC/state-20071001-aud-000003.arc.gz<br />
9827832cdfd4a9565422e41fd334eb09a23c835772184936ffebabb147eb5b8a /state/data/state/state-2007-10-ARC/state-20071001-aud-000004.arc.gz<br />
3d55a5b19dd6133e598fb29ff89444fb05196863c21d8773a03dbe16c0b42615 /state/data/state/state-2007-10-ARC/state-20071001-aud-000005.arc.gz<br />
ea0880b33fb9b237299c7e92578f4881c820b93e3d130a5818e3b3a3e90b8872 /state/data/state/state-2007-10-ARC/state-20071001-aud-000006.arc.gz<br />
45b632a3de7ca7c38a916242d78cedce6f11004cef99e4642194a48651db597f /state/data/state/state-2007-10-ARC/state-20071001-aud-000007.arc.gz<br />
bca0a7d6f78b9d46196bb502ef31782d0b3ea5a075ca61691bdd0a2ffc3cfd24 /state/data/state/state-2007-10-ARC/state-20071001-aud-000008.arc.gz<br />
4ec209a01449552454b57d82e12c0848982010ebd7f36e4ac3206576819531cf /state/data/state/state-2007-10-ARC/state-20071001-aud-000009.arc.gz<br />
c4ed9102ba6e8f0ea5f9bfeb06318b3db2230733c5fd9a22b18405dcfe820a7f /state/data/state/state-2007-10-ARC/state-20071001-aud-000010.arc.gz<br />
b6f97b66eff760a3bbef4e7895be9432fa4dfcb206d42d789c5ecfb4343eadc1 /state/data/state/state-2007-10-ARC/state-20071001-aud-000011.arc.gz<br />
ab3f8d618e51032418a3285fd24687f7a2a006cd546de43e575c72b1fed727e4 /state/data/state/state-2007-10-ARC/state-20071001-aud-000012.arc.gz<br />
</pre><br />
<br />
Directories '''must''' be separated by a /. This is different from Windows where directories are separated by a \.<br />
<br />
The Audit Manager is able to supply a list of digests for a collection or directory. <br />
# From the status page, select the collection you wish to generate a list for<br />
# Click on more..., then 'Download Digests'. You will see a list of digests and filenames in the correct format. You can right-click and save the list to your hard drive.<br />
<br />
===Step 2: Upload to ACE===<br />
<br />
From the status screen, select the collection you wish to compare. Click the 'more...' link to bring up the drop down menu, then click 'Compare Collection'. You will see the following screen. Click on 'Browse' and select the name of the file you saved your digest link into during step 1. Click submit.<br />
<br />
[[Image:Compare-1.png|400px]]<br />
<br />
<br />
If everything in the file you submitted matches the selected collection, you will see the following summary showing no differences.<br />
<br />
[[Image:Compare-3.png|400px]]<br />
<br />
<br />
If, for some reason there are differences, then your screen may look something like the following:<br />
<br />
[[Image:Compare.png|400px]]<br />
<br />
There are four different ways in which collections may differ.<br />
<br />
;Files in original collection, but not in supplied<br />
:This is a list of files that appear in the collection being monitored by ACE, but do not appear in the uploaded file.<br />
;Files in supplied file, but not original collection<br />
:These are files that appear in the uploaded list, but not in the collection monitored by ACE.<br />
;Files with different names, but same digests<br />
:These are files which have the same content, but only differ in directory or name. This is seen when files are renamed and moved across different operating systems.<br />
;Files with same names, but different digests<br />
:These are files that have the same directory and name, but have different content. Most likely seen during a bad replication.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=File:Peer_roles.png&diff=2926File:Peer roles.png2018-05-14T21:47:55Z<p>Shake: </p>
<hr />
<div></div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Comparing_Collections&diff=2925Ace:Comparing Collections2018-05-14T21:44:19Z<p>Shake: </p>
<hr />
<div>The ACE AM allows you to compare collections to an external manifest. This is useful when you want to compare sites that have replicated data, or to verify all data was successfully loaded during ingestion.<br />
<br />
There are two ways to compare collection, first is to register peer ACE AM installations and automatically compare collections as part of an audit. The second from an external data file containing digests and filenames.<br />
<br />
==Peer Comparisons==<br />
<br />
Comparing collections with a Peer site is a multi-step process which allows your ACE instance to query a peer ACE's digests for a given collection. First a user is needed at the Peer site for your ACE to be able to query for file digests. Then the Peer site needs to be registered in your local ACE. Finally, comparisons can be done by either manually issuing a comparison or by adding a PeerCollection to your Collection which you wish to compare.<br />
<br />
===Step 1: Create a Peer User===<br />
<br />
At the remote site, a User needs to be created in order for your ACE to have access to the remote ACE. The comparisons run through a series of HTTP requests, and as such it is recommended to only use a minimal set of Roles for the Peer User.<br />
<br />
A User can be created by browsing to the Accounts servlet (/Users).<br />
<br />
===Step 2: Add the Peer User to A Local ACE===<br />
<br />
Once a user is created for you at the Peer Site, your ACE needs to store the credentials. This can be done on the PartnetSite servlet (/PartnerSite) which can be found by browsing with:<br />
* Status (Collection): Compare Collection<br />
** Partner: Add New<br />
<br />
===Step 3a: Manually Selecting the Collection===<br />
<br />
After the user setup is complete and your ACE AM can communicating with the Peer ACE AM, a manual collection comparison can be done through the CompareCollection Servlet.<br />
<br />
This is the same servlet as in Step 2. After selecting a Partner Site to compare against, a listing of collections will be shown which you can compare against.<br />
<br />
* Note: If the credentials are not correct, you will be able to see an Exception in the aceam.log<br />
* Note: There is currently a bug where if a PartnerSite has a large amount of collections, not all will be shown.<br />
<br />
===Step 3b: Registering a PeerCollection with a Local Collection===<br />
<br />
If you wish to have collections compared automatically when auditing, you simply need to go to the Collection Settings and select the 'Add Peer' dialogue. This then follows the same process as the manual selection. Once a collection has been chosen, it will be persisted to the ACE AM database and used to compare against during audits.<br />
<br />
<br />
==Manually Compare==<br />
<br />
Manually comparing collections is a two step process. First a source list of digests and filenames needs to be generated. The second step is to load that list into an AM installation for comparison. To manually compare collections between AM installations, you would download the digest list from the first installation, then upload the list to the second for comparison.<br />
<br />
===Step 1: Generate Digest List===<br />
<br />
The format of the list is a simple, SHA-256 digest, followed by one or more spaces or tabs, then the path to the file in the collection.<br />
<br />
Example source list.<br />
<pre><br />
01348875911b94af38b35f304dcd75348f437734696e26b40fd868eecd687d35 /state/data/state/state-2007-10-ARC/state-20071001-aud-000000.arc.gz<br />
365fe0af21237b750258f6b8c48b25964d0dd5c7d612748eff2f6526f43682bb /state/data/state/state-2007-10-ARC/state-20071001-aud-000001.arc.gz<br />
893298b40da08a1b9ce0c7994c8f2717cedb23d046936c8e24bd62655ca1962b /state/data/state/state-2007-10-ARC/state-20071001-aud-000002.arc.gz<br />
ba7cce400971bd56377e2d79a21192c63e0328e7651728345c49ebf35fb4999d /state/data/state/state-2007-10-ARC/state-20071001-aud-000003.arc.gz<br />
9827832cdfd4a9565422e41fd334eb09a23c835772184936ffebabb147eb5b8a /state/data/state/state-2007-10-ARC/state-20071001-aud-000004.arc.gz<br />
3d55a5b19dd6133e598fb29ff89444fb05196863c21d8773a03dbe16c0b42615 /state/data/state/state-2007-10-ARC/state-20071001-aud-000005.arc.gz<br />
ea0880b33fb9b237299c7e92578f4881c820b93e3d130a5818e3b3a3e90b8872 /state/data/state/state-2007-10-ARC/state-20071001-aud-000006.arc.gz<br />
45b632a3de7ca7c38a916242d78cedce6f11004cef99e4642194a48651db597f /state/data/state/state-2007-10-ARC/state-20071001-aud-000007.arc.gz<br />
bca0a7d6f78b9d46196bb502ef31782d0b3ea5a075ca61691bdd0a2ffc3cfd24 /state/data/state/state-2007-10-ARC/state-20071001-aud-000008.arc.gz<br />
4ec209a01449552454b57d82e12c0848982010ebd7f36e4ac3206576819531cf /state/data/state/state-2007-10-ARC/state-20071001-aud-000009.arc.gz<br />
c4ed9102ba6e8f0ea5f9bfeb06318b3db2230733c5fd9a22b18405dcfe820a7f /state/data/state/state-2007-10-ARC/state-20071001-aud-000010.arc.gz<br />
b6f97b66eff760a3bbef4e7895be9432fa4dfcb206d42d789c5ecfb4343eadc1 /state/data/state/state-2007-10-ARC/state-20071001-aud-000011.arc.gz<br />
ab3f8d618e51032418a3285fd24687f7a2a006cd546de43e575c72b1fed727e4 /state/data/state/state-2007-10-ARC/state-20071001-aud-000012.arc.gz<br />
</pre><br />
<br />
Directories '''must''' be separated by a /. This is different from Windows where directories are separated by a \.<br />
<br />
The Audit Manager is able to supply a list of digests for a collection or directory. <br />
# From the status page, select the collection you wish to generate a list for<br />
# Click on more..., then 'Download Digests'. You will see a list of digests and filenames in the correct format. You can right-click and save the list to your hard drive.<br />
<br />
===Step 2: Upload to ACE===<br />
<br />
From the status screen, select the collection you wish to compare. Click the 'more...' link to bring up the drop down menu, then click 'Compare Collection'. You will see the following screen. Click on 'Browse' and select the name of the file you saved your digest link into during step 1. Click submit.<br />
<br />
[[Image:Compare-1.png|400px]]<br />
<br />
<br />
If everything in the file you submitted matches the selected collection, you will see the following summary showing no differences.<br />
<br />
[[Image:Compare-3.png|400px]]<br />
<br />
<br />
If, for some reason there are differences, then your screen may look something like the following:<br />
<br />
[[Image:Compare.png|400px]]<br />
<br />
There are four different ways in which collections may differ.<br />
<br />
;Files in original collection, but not in supplied<br />
:This is a list of files that appear in the collection being monitored by ACE, but do not appear in the uploaded file.<br />
;Files in supplied file, but not original collection<br />
:These are files that appear in the uploaded list, but not in the collection monitored by ACE.<br />
;Files with different names, but same digests<br />
:These are files which have the same content, but only differ in directory or name. This is seen when files are renamed and moved across different operating systems.<br />
;Files with same names, but different digests<br />
:These are files that have the same directory and name, but have different content. Most likely seen during a bad replication.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Upgrading&diff=2924Ace:Audit Manager Upgrading2017-06-26T19:10:47Z<p>Shake: /* Database Files */</p>
<hr />
<div>==Upgrade Instructions==<br />
There are three steps to upgrading the audit manager, these are upgrading the application code, upgrading the underlying database, and finally updating any configuration files if necessary. The procedure for upgrading is listed below<br />
<br />
These instructions are current for version 1.3. Links to all previous versions of ace are available on the [https://gitlab.umiacs.umd.edu/adapt/ace/tags software page]<br />
<br />
; 1. Note the version you are currently running<br />
: Point your web browser at your ACE AM installation and look for the version at the bottom. If should look something like 1.2.2, or 1.3..<br />
; 2. Stop the Audit Manager/Tomcat<br />
: Run TOMCAT/bin/shutdown.sh to stop tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/shutdown.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0<br />
<br />
; 3. Apply database patches<br />
: Connect to your mysql database and apply any listed patches in order. You will need to apply all patches starting with your current version (see step 1) *in order*. See the table at the bottom of this page for a list of what patches you need. <br />
<br />
: To apply the patchec, connect to your database and issue the command 'source patchfile.sql' for each patch file you need to run.<br />
<br />
:Here's an example of what you will see. Depending on which patches you are applying, your screen will look different.<br />
<pre><br />
[user@loach ~]$ mysql aceam -u aceam -p <br />
Enter password: <br />
Reading table information for completion of table and column names<br />
You can turn off this feature to get a quicker startup with -A<br />
<br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 88<br />
Server version: 5.0.45 Source distribution<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> source 1.2-1.3.updates.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.01 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> <br />
</pre><br />
<br />
<br />
; 4. Upgrade the ACE AM code<br />
: Remove the existing ACE installation files and directories located at TOMCAT/webapps/ace-am and TOMCAT/webapps/ace-am.war.<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/webapps/ace-am*<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/work/Catalina/localhost/ace-am/<br />
:Place a copy of the latest ace-am.war file in TOMCAT/webapps/<br />
[toaster@loach ~/aceam]$ cp /tmp/ace-am.war apache-tomcat-6.0.18/webapps/<br />
: The latest version can be downloaded [http://narademo.umiacs.umd.edu/aceam/current/ace-am.war here]<br />
; 5. Update any configuration settings. (Versions prior to 1.3)<br />
: In your TOMCAT/conf/Catalina/localhost/ace-am.xml file, you may need to add some settings. This is only needed if you are upgrading from 1.2.2 or earlier.<br />
<br />
: Check the following line in your configuration file to ensure the database connection uses UTF-8.<br />
&lt;Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
<br />
: If your url does not contain the character encoding, you will need to add it if you want to use UTF-8 characters.<br />
<br />
: There is a sample configuration file available [http://narademo.umiacs.umd.edu/aceam/current/ace-am.xml here]<br />
; 6. Restart ACE.<br />
: Run TOMCAT/bin/startup.sh to restart tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/startup.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0_07<br />
<br />
==Database Files==<br />
Database patches required to bring ace database up to date can be found in the most recent version of ACE, located [https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.12 here]</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Upgrading&diff=2923Ace:Audit Manager Upgrading2017-06-26T19:10:06Z<p>Shake: /* Upgrade Instructions */</p>
<hr />
<div>==Upgrade Instructions==<br />
There are three steps to upgrading the audit manager, these are upgrading the application code, upgrading the underlying database, and finally updating any configuration files if necessary. The procedure for upgrading is listed below<br />
<br />
These instructions are current for version 1.3. Links to all previous versions of ace are available on the [https://gitlab.umiacs.umd.edu/adapt/ace/tags software page]<br />
<br />
; 1. Note the version you are currently running<br />
: Point your web browser at your ACE AM installation and look for the version at the bottom. If should look something like 1.2.2, or 1.3..<br />
; 2. Stop the Audit Manager/Tomcat<br />
: Run TOMCAT/bin/shutdown.sh to stop tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/shutdown.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0<br />
<br />
; 3. Apply database patches<br />
: Connect to your mysql database and apply any listed patches in order. You will need to apply all patches starting with your current version (see step 1) *in order*. See the table at the bottom of this page for a list of what patches you need. <br />
<br />
: To apply the patchec, connect to your database and issue the command 'source patchfile.sql' for each patch file you need to run.<br />
<br />
:Here's an example of what you will see. Depending on which patches you are applying, your screen will look different.<br />
<pre><br />
[user@loach ~]$ mysql aceam -u aceam -p <br />
Enter password: <br />
Reading table information for completion of table and column names<br />
You can turn off this feature to get a quicker startup with -A<br />
<br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 88<br />
Server version: 5.0.45 Source distribution<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> source 1.2-1.3.updates.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.01 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> <br />
</pre><br />
<br />
<br />
; 4. Upgrade the ACE AM code<br />
: Remove the existing ACE installation files and directories located at TOMCAT/webapps/ace-am and TOMCAT/webapps/ace-am.war.<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/webapps/ace-am*<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/work/Catalina/localhost/ace-am/<br />
:Place a copy of the latest ace-am.war file in TOMCAT/webapps/<br />
[toaster@loach ~/aceam]$ cp /tmp/ace-am.war apache-tomcat-6.0.18/webapps/<br />
: The latest version can be downloaded [http://narademo.umiacs.umd.edu/aceam/current/ace-am.war here]<br />
; 5. Update any configuration settings. (Versions prior to 1.3)<br />
: In your TOMCAT/conf/Catalina/localhost/ace-am.xml file, you may need to add some settings. This is only needed if you are upgrading from 1.2.2 or earlier.<br />
<br />
: Check the following line in your configuration file to ensure the database connection uses UTF-8.<br />
&lt;Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
<br />
: If your url does not contain the character encoding, you will need to add it if you want to use UTF-8 characters.<br />
<br />
: There is a sample configuration file available [http://narademo.umiacs.umd.edu/aceam/current/ace-am.xml here]<br />
; 6. Restart ACE.<br />
: Run TOMCAT/bin/startup.sh to restart tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/startup.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0_07<br />
<br />
==Database Files==<br />
Database patches required to bring ace database up to date can be found in the most recent version of ACE, located [https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace here]</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2922Ace:Audit Manager Installation Guide2017-04-21T17:04:41Z<p>Shake: /* Quick Setup */</p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.11<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace-am.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2921Ace:Audit Manager Installation Guide2017-04-21T17:04:18Z<p>Shake: /* Files */</p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace-am.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.11<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2920Ace:Audit Manager Installation Guide2017-03-28T17:19:52Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.8 or later http://java.sun.com<br />
* Tomcat 7.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.11<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2919Ace:Audit Manager Installation Guide2016-11-29T17:59:16Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.7 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.11<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Release_Guidlines&diff=2918Ace:Release Guidlines2016-11-28T21:33:06Z<p>Shake: /* Git Release */</p>
<hr />
<div>The tests should be performed prior to an ACE release. As many of these as possible should be included in the maven/hudson configs for automated testing. <br />
<br />
Prior to release testing, please make sure all bugs/features for that version have been completed on Redmine. https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/roadmap. Update maven version and footer version prior to creating a release package.<br />
<br />
=Source Testing=<br />
<br />
# export a clean copy of the 'svn export https://subversion.umiacs.umd.edu/ace/trunk ace-test'<br />
# 'mvn package' in root, and make sure the build succeeds.<br />
<br />
=Clean deploy testing=<br />
# Create a new database using the current ace ace-am.sql file.<br />
# From your build, deploy the war file in ace-am/target/ace-am-XXX.war <br />
<br />
=Upgrade testing=<br />
# Grab the previous ace release, install the schema and war file<br />
# register the test collection.<br />
# shutdown instance, run update sql file, drop in new war file<br />
# Check error log for errors, check display for major feature changes, run test audit on existing colleciton, register new collection.<br />
<br />
=Releasing=<br />
When you have fully tested everything, use maven to generate the current release and update the current project with the next snapshot.<br />
# Run mvn release:prepare in the root project<br />
# upload the two new binary versions in ace-dist/target to redmine.<br />
# export the source in the tags/ace-xxx version, tar/gz it and upload to redmine<br />
<br />
= Releasing with Git and UMObj =<br />
<br />
===Git Brancing===<br />
# git checkout -b release-$VERSION<br />
# mvn versions:set -DnewVersion=$VERSION-RELEASE<br />
# check pom.xml<br />
# find . -type f -name '*.versionsBackup' -delete<br />
# git commit -a -m 'Bump $VERSION release'<br />
# mvn package && test war and deployment<br />
# git checkout master<br />
# git merge --no-ff release-$VERSION<br />
# git tag -a ace-$VERSION<br />
# git archive --format=tar.gz --prefix=ace/ master > ace-$VERSION-src.tar.gz<br />
# git checkout develop<br />
# git merge --no-ff release-$VERSION<br />
# mvn versions:set -DnewVersion=$(VERSION + 1)-SNAPSHOT<br />
# find . -type f -name '*.versionsBackup' -delete<br />
# git commit -a -m 'Bump $(VERSION + 1) snapshot'<br />
# git push --atomic origin master develop<br />
<br />
=== UMObj ===<br />
<br />
Releases are now stored on umobj, and uploading is simple.<br />
<br />
# Prepare the keys needed for uploading to the adapt group<br />
<pre><br />
export OBJ_ACCESS_KEY_ID="ADAPT_KEY"<br />
export OBJ_SECRET_ACCESS_KEY="ADAPT_KEY"<br />
export OBJ_SERVER="obj.umiacs.umd.edu"<br />
</pre><br />
<br />
# Copy the dist and releases to umobj<br />
<pre><br />
[ace] $ cpobj ace-$VERSION-src.tar.gz ace:/releases/$VERSION/<br />
100% | ...<br />
[ace] $ cpobj ace-dist/target/ace-dist-$RELEASE-bin.tar.gz ace:/releases/$VERSION/<br />
100% | ...<br />
[ace] $ cpobj ace-dist/target/ace-dist-$RELEASE-bin.zip ace:/releases/$VERSION/<br />
100% | ...<br />
</pre></div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=WarcManager&diff=2917WarcManager2016-09-29T19:07:58Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The Warc Manager is a tool to help archives quickly browse, search, and analyze archives of web crawl data. The manager is lightweight database web application which indexes and provides a nice browsing interface to a collection of warc data.<br />
<br />
<br />
* Source Code Repository: https://gitlab.umiacs.umd.edu/adapt/warc-utils<br />
* <strike>Nightly builds: http://adaptci01.umiacs.umd.edu:8080/job/WARC%20Manager%202/</strike><br />
<br />
=Searching=<br />
<br />
The warc manager offers two ways to search collections.<br />
<br />
[[Image:searchpage.png]]<br />
<br />
1. If you know the page you want to view, start typing the full URL into the search box starting with 'http'. You will see a drop-down box containing URL's that match what you have typed. Clicking on any of them will load details for the URL.<br />
<br />
2. <nowiki>Type a search string and click 'Search'. Optionally you can add wildcards to your search. For example, entering '*.html' will search for all URL's ending in .html. Some common searches are listed below</nowiki>:<br />
* <nowiki>*.html</nowiki> - search for all files ending in '.html'<br />
* <nowiki>http://www.somesite.com*</nowiki> - View all URL's for www.somesite.com<br />
* <nowiki>http://www.somesite.com/*.html</nowiki> - view all '.html' files on somesite.com.<br />
<br />
==Search Results==<br />
[[Image:searchresults.png|thumb|Search Results]]<br />
<br />
The search results show all matching URL's along with some statistics about that url. Double clicking on any row will load details for any url.<br />
<br />
* First Crawl - The earliest crawl date for the url.<br />
* Last Crawl - The most recent crawl date for the url.<br />
* Harvested - Lists the total number of times a page appears in the archive. This includes duplicates and revisits<br />
* Unique - Shows how many unique copies of the page exist in the archive. <br />
<br />
==URL Details==<br />
[[Image:urldetails.png|thumb|URL Details]]<br />
The url details page shows detailed information for any URL in the collection. If there are multiple copies or different versions of a URL they will be listed in the left-hand column. Clicking on any entry will load details for that URL.<br />
<br />
If you are accessing a URL that contains a html page (As opposed to an image) the warc manager will attempt to extract all links contained in that page and populate the table on the lower right. links that appear in the archive are shown in black, missing links are red. You can double-click on any page in the table to view details for that url. If the URL is not an html file (ie, image) the link table will remain empty. <br />
<br />
Clicking on the 'Download File' link will allow you to download the selected page from the archive.<br />
<br />
=Installation=<br />
<br />
The installation consists of a few simple steps. <br />
<br />
Before you begin, you will need to download:<br />
* Apache Tomcat: http://tomcat.apache.org<br />
* MySQL jdbc connector: http://dev.mysql.com/downloads/connector/j/<br />
* context.xml, schema.sql, and the warc webapp from: http://adaptvm01.umiacs.umd.edu:8080/jenkins/job/Warc%20Manager%202/<br />
<br />
1. Create database and setup permissions.<br />
mysql> create database webarc;<br />
mysql> grant all on webarc.* to webarc@localhost identified by 'PASSWORD';<br />
mysql> use webarc;<br />
mysql> source schema.sql;<br />
2. Install tomcat and JDBC driver<br />
$ tar -xf apache-tomcat-6.0.32.tar.gz<br />
$ cp mysql-connector-java-5.0.7-bin.jar apache-tomcat-6.0.32/lib<br />
3. Install and configure the Warc Manager<br />
$ cp warc-webapp-1.0-SNAPSHOT.war apache-tomcat-6.0.32/webapps/warc.war<br />
$ mkdir -p apache-tomcat-6.0.32/conf/Catalina/localhost<br />
$ cp context.xml apache-tomcat-6.0.32/conf/Catalina/localhost/warc.xml <br />
* edit apache-tomcat-6.0.32/conf/Catalina/localhost/warc.xml and make sure the password under the resource line is the same as you specified above:<br />
<br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20" <br />
maxIdle="10" maxWait="-1" name="jdbc/warcdb" '''password="PASSWORD"''' testOnBorrow="true"<br />
type="javax.sql.DataSource" url="jdbc:mysql://localhost/webarc" username="webarc"<br />
validationQuery="SELECT 1"/><br />
<br />
Add the following line after the resource line.<br />
<Parameter name="ingest.url" value="http://localhost:8080/warc/rest/ingest"/><br />
<br />
4. Start Tomcat<br />
$ apache-tomcat-6.0.32/bin/startup.sh<br />
<br />
=Indexing Web Content=<br />
<br />
The Warc Manager is able to index warc data stored on the same server that the manager is running on. To index warc files, you will need to know the directory on the server where they reside.<br />
<br />
1. From the main screen, click 'Ingest Files'. You will see the ingest file screen.<br />
<br />
[[Image:ingestfiles.png]]<br />
<br />
2. Enter the following information:<br />
* Server Directory - The directory on the warc manager where warc files are stored. The scan will recursively search for any files ending in 'warc.gz'<br />
* Select Collection / New Collection: If you want to load these files into an existing collection, select it from the drop down box. Otherwise, type in the name of a new collection or label for these warc files.<br />
<br />
3. Click 'Scan Directory' When you are ready to index warc files. You can return to the scan page any time to view the progress of your upload.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2916Ace:Audit Manager Installation Guide2016-09-29T19:05:59Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.7 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.10<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Main&diff=2915Ace:Main2016-09-29T19:04:26Z<p>Shake: </p>
<hr />
<div>ACE (Auditing Control Environment) is a system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.<br />
<br />
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. <br />
<br />
Anyone wishing to audit their files with ACE only needs to install an Audit Manager locally to manage their files. The ADAPT project runs a publically available IMS at ims.umiacs.umd.edu that any group may freely use.<br />
<br />
{| width="75%" style="margin-left: 75px;"<br />
| '''Audit Manager''' || '''Integrity Management Service'''<br />
|-<br />
| [[Ace:Audit Manager Installation Guide|Download Audit Manager]] || [[Ace:Ace IMS System|System Documentation]]<br />
|-<br />
| [[Ace:Audit Manager User Guide|User Guide]] || [http://ims.umiacs.umd.edu:8080/ace-ims/IMSWebService IMS Webservice]<br />
|-<br />
| [http://groups.google.com/group/ace-devel Discussion List] || [[Ace:Validating Witness and Tokens|Validating Tokens and Witnesses]]<br />
|-<br />
| [[Ace:Audit Manager Upgrading|Upgrade Audit Manager]] || [http://groups.google.com/group/ace-ims-witness?hl=en IMS Witness Google Goup]<br />
|- <br />
| [[Ace:AM Config Reference|AM Configuration Options]] || [http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness IMS Witness UMIACS listserv]<br />
|-<br />
| || [[Ace:IMS Installation| IMS Installation Guide]]<br />
|-<br />
| '''Resources'''<br />
|-<br />
| [https://gitlab.umiacs.umd.edu/adapt/ace Gitlab Project Repo]<br />
|-<br />
| [[Ace:Devel Pages|Development Documentation]]<br />
|-<br />
| [[Ace:Webstart Client|Auditor Application]] || <br />
|-<br />
| [http://digitalcommons.uconn.edu/libr_pubs/39/ Step by Step installation instructions]<br />
|}<br />
<br />
<br />
'''Papers and Presentations'''<br />
<br />
* Smorul, M., Song, S., and JaJa, J. An Implementation of the Audit Control Environment(ACE) to Support the Long Term Integrity of Digital Archives. in DigCCurr 2009. 2009: University of North Carolina.[[media:DigCCurr2009_060909.pdf|pdf]] presentation [[media:Smorul-digccurr09.ppt|ppt]]<br />
* ACE Presentation at Archiving 2007 (5/07) [[media: ACE-Archiving2007.ppt|ppt]]<br />
* Song, S. and JaJa, J. ACE: A Novel Software Platform to Ensure the Integrity of Long Term Archives. in Archiving 2007. 2007: IS&T. [[media:rad71E67.pdf|pdf]]<br />
<br />
Development of the ACE Version1.0 release was partially sponsored by the US National Archives and Records Administration. The basic research on ACE was partially sponsored under a DIGARCH grant from NSF/Library of Congress.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2914Main Page2016-09-29T19:01:43Z<p>Shake: /* Overview */</p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><ul><li>[[Ace|Integrity Management (ACE)]]<li>[[WarcManager|Warc Management Utility]]<li>[https://scm.umiacs.umd.edu/redmine/adapt/projects/ingestion RESTful Bag server Implementation]</ul></td><br />
<td><ul><li>[[Webarc:Main|Web Archive Indexing]]<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
'''ACE Development Infrastructure'''<br />
* current release https://gitlab.umiacs.umd.edu/adapt/ace/tags/ace-1.10<br />
* releases https://gitlab.umiacs.umd.edu/adapt/ace/tags<br />
* public source repository https://gitlab.umiacs.umd.edu/adapt/ace<br />
* CI testing and development builds http://adaptci01.umiacs.umd.edu/resource/ace<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Current: https://gitlab.umiacs.umd.edu/adapt/ace/issues<br />
<br />
'''ACE V 1.10 (4/22)'''<br />
* Bug Fix for a deadlock when connection to the IMS was lost<br />
<br />
'''ACE V 1.9 (1/14)'''<br />
* Frontend UI improvements,<br />
* Backend threading improvements when ingesting tokens and auditing collections<br />
<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2913Main Page2016-09-29T18:59:17Z<p>Shake: /* Overview */</p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><ul><li>[[Ace|Integrity Management (ACE)]]<li>[[WarcManager|Warc Management Utility]]<li>[https://scm.umiacs.umd.edu/redmine/adapt/projects/ingestion RESTful Bag server Implementation]</ul></td><br />
<td><ul><li>[[Webarc:Main|Web Archive Indexing]]<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
'''ACE Development Infrastructure'''<br />
* releases https://gitlab.umiacs.umd.edu/adapt/ace/tags<br />
* public source repository https://gitlab.umiacs.umd.edu/adapt/ace<br />
* CI testing and development builds http://adaptci01.umiacs.umd.edu/resource/ace<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Current: https://gitlab.umiacs.umd.edu/adapt/ace/issues<br />
<br />
'''ACE V 1.10 (4/22)'''<br />
* Bug Fix for a deadlock when connection to the IMS was lost<br />
<br />
'''ACE V 1.9 (1/14)'''<br />
* Frontend UI improvements,<br />
* Backend threading improvements when ingesting tokens and auditing collections<br />
<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2912Main Page2016-05-24T20:22:57Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><ul><li>[[Ace|Integrity Management (ACE)]]<li>[[WarcManager|Warc Management Utility]]<li>[https://scm.umiacs.umd.edu/redmine/adapt/projects/ingestion RESTful Bag server Implementation]</ul></td><br />
<td><ul><li>[[Webarc:Main|Web Archive Indexing]]<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
'''ACE Development Infrastructure'''<br />
* releases https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/files<br />
* public source repository https://gitlab.umiacs.umd.edu/adapt/ace<br />
* CI testing and daily builds https://adaptci01.umiacs.umd.edu/<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Old: https://scm.umiacs.umd.edu/redmine/adapt/<br />
* Current: https://gitlab.umiacs.umd.edu/adapt/ace/issues<br />
<br />
'''ACE V 1.10 (4/22)'''<br />
* Bug Fix for a deadlock when connection to the IMS was lost<br />
<br />
'''ACE V 1.9 (1/14)'''<br />
* Frontend UI improvements,<br />
* Backend threading improvements when ingesting tokens and auditing collections<br />
<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2911Main Page2016-05-24T20:22:01Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><ul><li>[[Ace|Integrity Management (ACE)]]<li>[[WarcManager|Warc Management Utility]]<li>[https://scm.umiacs.umd.edu/redmine/adapt/projects/ingestion RESTful Bag server Implementation]</ul></td><br />
<td><ul><li>[[Webarc:Main|Web Archive Indexing]]<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
'''ACE Development Infrastructure'''<br />
* releases https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/files<br />
* public source repository https://gitlab.umiacs.umd.edu/adapt/ace<br />
* CI testing and daily builds https://adaptci01.umiacs.umd.edu/<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Old: https://scm.umiacs.umd.edu/redmine/adapt/<br />
* Current: https://gitlab.umiacs.umd.edu/adapt/ace/issues<br />
<br />
'''ACE V 1.10 (4/22)'''<br />
* Bug Fix for a deadlock when connection to the IMS was lost<br />
<br />
'''ACE V 1.9 (1/14)'''<br />
* Frontend UI improvements,<br />
* Backend threading improvements when ingesting tokens and auditing collections<br />
<br />
'''ACE V 1.6 (2/3)'''<br />
* Token store exporting, improved db storing<br />
* Frontend UI improvements, <br />
* Build system (maven) changes<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2910Main Page2016-05-24T20:16:16Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><ul><li>[[Ace|Integrity Management (ACE)]]<li>[[WarcManager|Warc Management Utility]]<li>[https://scm.umiacs.umd.edu/redmine/adapt/projects/ingestion RESTful Bag server Implementation]</ul></td><br />
<td><ul><li>[[Webarc:Main|Web Archive Indexing]]<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
<br />
'''ACE Development Infrastructure'''<br />
* public source repository https://adapt.umiacs.umd.edu/gitlab/adapt/ace<br />
* CI testing and daily builds https://adaptci01.umiacs.umd.edu/<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Old: https://scm.umiacs.umd.edu/redmine/adapt/<br />
* Migrating To: https://adapt.umiacs.umd.edu/gitlab/groups/adapt<br />
<br />
<br />
'''Undergrad positions available'''<br />
* The ADAPT project is hiring undergrad programmers to work on a variety of projects<br />
* Learn more on our [[Employment]] page<br />
<br />
'''ACE V 1.6 (2/3)'''<br />
* Token store exporting, improved db storing<br />
* Frontend UI improvements, <br />
* Build system (maven) changes<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Ace V 1.5 Released (6/25)'''<br />
* Source Released under BSD License<br />
* Resource migration<br />
* Lots of internal refactoring, dependency restructuring<br />
<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Release_Guidlines&diff=2909Ace:Release Guidlines2016-01-14T21:02:00Z<p>Shake: Add git release instructions</p>
<hr />
<div>The tests should be performed prior to an ACE release. As many of these as possible should be included in the maven/hudson configs for automated testing. <br />
<br />
Prior to release testing, please make sure all bugs/features for that version have been completed on Redmine. https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/roadmap. Update maven version and footer version prior to creating a release package.<br />
<br />
=Source Testing=<br />
<br />
# export a clean copy of the 'svn export https://subversion.umiacs.umd.edu/ace/trunk ace-test'<br />
# 'mvn package' in root, and make sure the build succeeds.<br />
<br />
=Clean deploy testing=<br />
# Create a new database using the current ace ace-am.sql file.<br />
# From your build, deploy the war file in ace-am/target/ace-am-XXX.war <br />
<br />
=Upgrade testing=<br />
# Grab the previous ace release, install the schema and war file<br />
# register the test collection.<br />
# shutdown instance, run update sql file, drop in new war file<br />
# Check error log for errors, check display for major feature changes, run test audit on existing colleciton, register new collection.<br />
<br />
=Releasing=<br />
When you have fully tested everything, use maven to generate the current release and update the current project with the next snapshot.<br />
# Run mvn release:prepare in the root project<br />
# upload the two new binary versions in ace-dist/target to redmine.<br />
# export the source in the tags/ace-xxx version, tar/gz it and upload to redmine<br />
<br />
=Git Release=<br />
# mvn versions:set to $RELEASE<br />
# git add all pom.xml<br />
# git commit<br />
# git tag -a ace-$RELEASE -m 'ace-$RELEASE'<br />
# git archive --format=tar.gz --prefix=ace/ master > ace-$RELEASE-src.tar.gz<br />
# mvn versions:set to next snapshot<br />
# git add all pom.xml<br />
# git commit<br />
# git push</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=WarcManager&diff=2908WarcManager2014-12-05T20:26:41Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The Warc Manager is a tool to help archives quickly browse, search, and analyze archives of web crawl data. The manager is lightweight database web application which indexes and provides a nice browsing interface to a collection of warc data.<br />
<br />
<br />
* Source Code Repository: https://subversion.umiacs.umd.edu/warc-utils/<br />
* Nightly builds: http://adaptci01.umiacs.umd.edu:8080/job/WARC%20Manager%202/<br />
<br />
=Searching=<br />
<br />
The warc manager offers two ways to search collections.<br />
<br />
[[Image:searchpage.png]]<br />
<br />
1. If you know the page you want to view, start typing the full URL into the search box starting with 'http'. You will see a drop-down box containing URL's that match what you have typed. Clicking on any of them will load details for the URL.<br />
<br />
2. <nowiki>Type a search string and click 'Search'. Optionally you can add wildcards to your search. For example, entering '*.html' will search for all URL's ending in .html. Some common searches are listed below</nowiki>:<br />
* <nowiki>*.html</nowiki> - search for all files ending in '.html'<br />
* <nowiki>http://www.somesite.com*</nowiki> - View all URL's for www.somesite.com<br />
* <nowiki>http://www.somesite.com/*.html</nowiki> - view all '.html' files on somesite.com.<br />
<br />
==Search Results==<br />
[[Image:searchresults.png|thumb|Search Results]]<br />
<br />
The search results show all matching URL's along with some statistics about that url. Double clicking on any row will load details for any url.<br />
<br />
* First Crawl - The earliest crawl date for the url.<br />
* Last Crawl - The most recent crawl date for the url.<br />
* Harvested - Lists the total number of times a page appears in the archive. This includes duplicates and revisits<br />
* Unique - Shows how many unique copies of the page exist in the archive. <br />
<br />
==URL Details==<br />
[[Image:urldetails.png|thumb|URL Details]]<br />
The url details page shows detailed information for any URL in the collection. If there are multiple copies or different versions of a URL they will be listed in the left-hand column. Clicking on any entry will load details for that URL.<br />
<br />
If you are accessing a URL that contains a html page (As opposed to an image) the warc manager will attempt to extract all links contained in that page and populate the table on the lower right. links that appear in the archive are shown in black, missing links are red. You can double-click on any page in the table to view details for that url. If the URL is not an html file (ie, image) the link table will remain empty. <br />
<br />
Clicking on the 'Download File' link will allow you to download the selected page from the archive.<br />
<br />
=Installation=<br />
<br />
The installation consists of a few simple steps. <br />
<br />
Before you begin, you will need to download:<br />
* Apache Tomcat: http://tomcat.apache.org<br />
* MySQL jdbc connector: http://dev.mysql.com/downloads/connector/j/<br />
* context.xml, schema.sql, and the warc webapp from: http://adaptvm01.umiacs.umd.edu:8080/jenkins/job/Warc%20Manager%202/<br />
<br />
1. Create database and setup permissions.<br />
mysql> create database webarc;<br />
mysql> grant all on webarc.* to webarc@localhost identified by 'PASSWORD';<br />
mysql> use webarc;<br />
mysql> source schema.sql;<br />
2. Install tomcat and JDBC driver<br />
$ tar -xf apache-tomcat-6.0.32.tar.gz<br />
$ cp mysql-connector-java-5.0.7-bin.jar apache-tomcat-6.0.32/lib<br />
3. Install and configure the Warc Manager<br />
$ cp warc-webapp-1.0-SNAPSHOT.war apache-tomcat-6.0.32/webapps/warc.war<br />
$ mkdir -p apache-tomcat-6.0.32/conf/Catalina/localhost<br />
$ cp context.xml apache-tomcat-6.0.32/conf/Catalina/localhost/warc.xml <br />
* edit apache-tomcat-6.0.32/conf/Catalina/localhost/warc.xml and make sure the password under the resource line is the same as you specified above:<br />
<br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20" <br />
maxIdle="10" maxWait="-1" name="jdbc/warcdb" '''password="PASSWORD"''' testOnBorrow="true"<br />
type="javax.sql.DataSource" url="jdbc:mysql://localhost/webarc" username="webarc"<br />
validationQuery="SELECT 1"/><br />
<br />
Add the following line after the resource line.<br />
<Parameter name="ingest.url" value="http://localhost:8080/warc/rest/ingest"/><br />
<br />
4. Start Tomcat<br />
$ apache-tomcat-6.0.32/bin/startup.sh<br />
<br />
=Indexing Web Content=<br />
<br />
The Warc Manager is able to index warc data stored on the same server that the manager is running on. To index warc files, you will need to know the directory on the server where they reside.<br />
<br />
1. From the main screen, click 'Ingest Files'. You will see the ingest file screen.<br />
<br />
[[Image:ingestfiles.png]]<br />
<br />
2. Enter the following information:<br />
* Server Directory - The directory on the warc manager where warc files are stored. The scan will recursively search for any files ending in 'warc.gz'<br />
* Select Collection / New Collection: If you want to load these files into an existing collection, select it from the drop down box. Otherwise, type in the name of a new collection or label for these warc files.<br />
<br />
3. Click 'Scan Directory' When you are ready to index warc files. You can return to the scan page any time to view the progress of your upload.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Main&diff=2907Ace:Main2014-11-24T17:36:22Z<p>Shake: </p>
<hr />
<div>ACE (Auditing Control Environment) is a system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.<br />
<br />
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. <br />
<br />
Anyone wishing to audit their files with ACE only needs to install an Audit Manager locally to manage their files. The ADAPT project runs a publically available IMS at ims.umiacs.umd.edu that any group may freely use.<br />
<br />
{| width="75%" style="margin-left: 75px;"<br />
| '''Audit Manager''' || '''Integrity Management Service'''<br />
|-<br />
| [[Ace:Audit Manager Installation Guide|Download Audit Manager]] || [[Ace:Ace IMS System|System Documentation]]<br />
|-<br />
| [[Ace:Audit Manager User Guide|User Guide]] || [http://ims.umiacs.umd.edu:8080/ace-ims/IMSWebService IMS Webservice]<br />
|-<br />
| [http://groups.google.com/group/ace-devel Discussion List] || [[Ace:Validating Witness and Tokens|Validating Tokens and Witnesses]]<br />
|-<br />
| [[Ace:Audit Manager Upgrading|Upgrade Audit Manager]] || [http://groups.google.com/group/ace-ims-witness?hl=en IMS Witness Google Goup]<br />
|- <br />
| [[Ace:AM Config Reference|AM Configuration Options]] || [http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness IMS Witness UMIACS listserv]<br />
|-<br />
| || [[Ace:IMS Installation| IMS Installation Guide]]<br />
|-<br />
| '''Resources'''<br />
|-<br />
| [https://gitlab.umiacs.umd.edu/adapt/ace Gitlab Project Repo]<br />
|-<br />
| [https://scm.umiacs.umd.edu/redmine/adapt/projects/ace Old File and Issue Tracker]<br />
|-<br />
| [[Ace:Devel Pages|Development Documentation]]<br />
|-<br />
| [[Ace:Webstart Client|Auditor Application]] || <br />
|-<br />
| [http://digitalcommons.uconn.edu/libr_pubs/39/ Step by Step installation instructions]<br />
|}<br />
<br />
<br />
'''Papers and Presentations'''<br />
<br />
* Smorul, M., Song, S., and JaJa, J. An Implementation of the Audit Control Environment(ACE) to Support the Long Term Integrity of Digital Archives. in DigCCurr 2009. 2009: University of North Carolina.[[media:DigCCurr2009_060909.pdf|pdf]] presentation [[media:Smorul-digccurr09.ppt|ppt]]<br />
* ACE Presentation at Archiving 2007 (5/07) [[media: ACE-Archiving2007.ppt|ppt]]<br />
* Song, S. and JaJa, J. ACE: A Novel Software Platform to Ensure the Integrity of Long Term Archives. in Archiving 2007. 2007: IS&T. [[media:rad71E67.pdf|pdf]]<br />
<br />
Development of the ACE Version1.0 release was partially sponsored by the US National Archives and Records Administration. The basic research on ACE was partially sponsored under a DIGARCH grant from NSF/Library of Congress.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Devel_Pages&diff=2905Ace:Devel Pages2014-04-29T18:14:16Z<p>Shake: </p>
<hr />
<div>=General=<br />
<br />
* [https://adapt.umiacs.umd.edu/gitlab/groups/adapt Bug Tracker, Source code..]<br />
* [http://groups.google.com/group/ace-devel Discussion List]<br />
* [https://adaptci01.umiacs.umd.edu:8443/job/ace/ Jenkins build tests]<br />
<br />
=Token Store Format=<br />
<br />
Information for creating, parsing and validating Token stores<br />
<br />
* [[Ace:TokenStore|Token Store Format]]<br />
* [[Ace:StorePython|Processing Token Stores in Python]]<br />
<br />
=Audit Manager=<br />
<br />
Developer pages and documentation for the ACE Audit Manager web application<br />
<br />
* [[Ace:JSON Interface|JSON Interface to Audit Manager]]<br />
* [[Ace:Roles|Security Roles]]<br />
* [[Ace:Summary Details|Summary generation]]<br />
* [[Ace:Expanding the Audit Manager|Adding Storage Types]] <br />
* [[Ace:Release Guidlines|Release Guidelines]]<br />
<br />
=Integrity Management Service=<br />
<br />
* [[Ace:IMSPython|Accessing the IMS using python]]<br />
<br />
=Other=<br />
<br />
* [[Ace:Deprecated|Deprecated Pages]]</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2904Ace:Audit Manager Installation Guide2014-04-29T18:10:44Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.7 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
The latest versions of these can be downloaded from:<br />
https://adapt.umiacs.umd.edu/gitlab/adapt/ace/tree/svn/tags/ace-1.8<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Main_Page&diff=2903Main Page2014-04-29T18:08:59Z<p>Shake: </p>
<hr />
<div>=Overview=<br />
The ADAPT project is developing technologies for building a scalable and reliable infrastructure for the long-term access and preservation of digital assets. Over the past years, we've developed numerous tools and have active research in many areas.<br />
<br />
<table width="75%" style="margin-left: 75px;"><br />
<tr><td>'''Open Source Tools'''</td><td>'''Research'''</td></tr><tr><br />
<td valign="top"><ul><li>[[Ace|Integrity Management (ACE)]]<li>[[WarcManager|Warc Management Utility]]<li>[https://scm.umiacs.umd.edu/redmine/adapt/projects/ingestion RESTful Bag server Implementation]</ul></td><br />
<td><ul><li>[[Webarc:Main|Web Archive Indexing]]<li>[[Replication:Main|Replication Monitoring]]<br />
<li>[[Chronopolis|Chronopolis]]</ul><br />
</td></tr></table><br />
<br />
<br />
'''ACE Development Infrastructure'''<br />
* public source repository https://adapt.umiacs.umd.edu/gitlab/adapt/ace<br />
* <strike>Hudson</strike>Jenkins testing and daily builds https://adaptci01.umiacs.umd.edu:8443/job/ace/<br />
* Projects converted from netbeans build to maven3 for easier collaboration<br />
<br />
'''Issue Tracker'''<br />
The adapt project now has an issue tracker to manage releases of our software and track bugs/feature requests.<br />
* Old: https://scm.umiacs.umd.edu/redmine/adapt/<br />
* Migrating To: https://adapt.umiacs.umd.edu/gitlab/groups/adapt<br />
<br />
<br />
'''Undergrad positions available'''<br />
* The ADAPT project is hiring undergrad programmers to work on a variety of projects<br />
* Learn more on our [[Employment]] page<br />
<br />
'''ACE V 1.6 (2/3)'''<br />
* Token store exporting, improved db storing<br />
* Frontend UI improvements, <br />
* Build system (maven) changes<br />
<br />
'''Python tutorials for ACE'''<br />
* [[Ace:IMSPython| Requesting and validating IMS tokens]]<br />
<br />
'''Ace V 1.5 Released (6/25)'''<br />
* Source Released under BSD License<br />
* Resource migration<br />
* Lots of internal refactoring, dependency restructuring<br />
<br />
<br />
'''Conference Videos Online (4/21/09)'''<br />
Videos for the two-day conference, "Partnerships in Innovation II: From Vision to Reality and Beyond" held on October 7- 8, 2008 in College Park, Maryland, USA are now [[Partnerships 2008 Videos|online]]<br />
<br />
=Old Projects=<br />
<ul><li>[[PAWN:Main|Ingestion (PAWN)]]<br />
<li>[[Focus:Main|Format Stewardship (FOCUS)]]<br />
<li>[[TPAP|TPAP]] - Transcontinental persistent archive prototype</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Main&diff=2902Ace:Main2014-04-10T21:05:50Z<p>Shake: </p>
<hr />
<div>ACE (Auditing Control Environment) is a system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.<br />
<br />
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. <br />
<br />
Anyone wishing to audit their files with ACE only needs to install an Audit Manager locally to manage their files. The ADAPT project runs a publically available IMS at ims.umiacs.umd.edu that any group may freely use.<br />
<br />
{| width="75%" style="margin-left: 75px;"<br />
| '''Audit Manager''' || '''Integrity Management Service'''<br />
|-<br />
| [[Ace:Audit Manager Installation Guide|Download Audit Manager]] || [[Ace:Ace IMS System|System Documentation]]<br />
|-<br />
| [[Ace:Audit Manager User Guide|User Guide]] || [http://ims.umiacs.umd.edu:8080/ace-ims/IMSWebService IMS Webservice]<br />
|-<br />
| [http://groups.google.com/group/ace-devel Discussion List] || [[Ace:Validating Witness and Tokens|Validating Tokens and Witnesses]]<br />
|-<br />
| [[Ace:Audit Manager Upgrading|Upgrade Audit Manager]] || [http://groups.google.com/group/ace-ims-witness?hl=en IMS Witness Google Goup]<br />
|- <br />
| [[Ace:AM Config Reference|AM Configuration Options]] || [http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness IMS Witness UMIACS listserv]<br />
|-<br />
| || [[Ace:IMS Installation| IMS Installation Guide]]<br />
|-<br />
| '''Resources'''<br />
|-<br />
| [https://adapt.umiacs.umd.edu/gitlab/adapt/ace Gitlab Project Repo]<br />
|-<br />
| [https://scm.umiacs.umd.edu/redmine/adapt/projects/ace Old File and Issue Tracker]<br />
|-<br />
| [[Ace:Devel Pages|Development Documentation]]<br />
|-<br />
| [[Ace:Webstart Client|Auditor Application]] || <br />
|-<br />
| [http://digitalcommons.uconn.edu/libr_pubs/39/ Step by Step installation instructions]<br />
|}<br />
<br />
<br />
'''Papers and Presentations'''<br />
<br />
* Smorul, M., Song, S., and JaJa, J. An Implementation of the Audit Control Environment(ACE) to Support the Long Term Integrity of Digital Archives. in DigCCurr 2009. 2009: University of North Carolina.[[media:DigCCurr2009_060909.pdf|pdf]] presentation [[media:Smorul-digccurr09.ppt|ppt]]<br />
* ACE Presentation at Archiving 2007 (5/07) [[media: ACE-Archiving2007.ppt|ppt]]<br />
* Song, S. and JaJa, J. ACE: A Novel Software Platform to Ensure the Integrity of Long Term Archives. in Archiving 2007. 2007: IS&T. [[media:rad71E67.pdf|pdf]]<br />
<br />
Development of the ACE Version1.0 release was partially sponsored by the US National Archives and Records Administration. The basic research on ACE was partially sponsored under a DIGARCH grant from NSF/Library of Congress.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2901Ace:Audit Manager Installation Guide2013-06-04T17:32:18Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.7 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
These can be downloaded at the following website:<br />
https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/files<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Upgrading&diff=2900Ace:Audit Manager Upgrading2013-04-12T15:48:52Z<p>Shake: </p>
<hr />
<div>==Upgrade Instructions==<br />
There are three steps to upgrading the audit manager, these are upgrading the application code, upgrading the underlying database, and finally updating any configuration files if necessary. The procedure for upgrading is listed below<br />
<br />
These instructions are current for version 1.3. Links to all previous versions of ace are available on the [https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace software page]<br />
<br />
; 1. Note the version you are currently running<br />
: Point your web browser at your ACE AM installation and look for the version at the bottom. If should look something like 1.2.2, or 1.3..<br />
; 2. Stop the Audit Manager/Tomcat<br />
: Run TOMCAT/bin/shutdown.sh to stop tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/shutdown.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0<br />
<br />
; 3. Apply database patches<br />
: Connect to your mysql database and apply any listed patches in order. You will need to apply all patches starting with your current version (see step 1) *in order*. See the table at the bottom of this page for a list of what patches you need. <br />
<br />
: To apply the patchec, connect to your database and issue the command 'source patchfile.sql' for each patch file you need to run.<br />
<br />
:Here's an example of what you will see. Depending on which patches you are applying, your screen will look different.<br />
<pre><br />
[user@loach ~]$ mysql aceam -u aceam -p <br />
Enter password: <br />
Reading table information for completion of table and column names<br />
You can turn off this feature to get a quicker startup with -A<br />
<br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 88<br />
Server version: 5.0.45 Source distribution<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> source 1.2-1.3.updates.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.01 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> <br />
</pre><br />
<br />
<br />
; 4. Upgrade the ACE AM code<br />
: Remove the existing ACE installation files and directories located at TOMCAT/webapps/ace-am and TOMCAT/webapps/ace-am.war.<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/webapps/ace-am*<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/work/Catalina/localhost/ace-am/<br />
:Place a copy of the latest ace-am.war file in TOMCAT/webapps/<br />
[toaster@loach ~/aceam]$ cp /tmp/ace-am.war apache-tomcat-6.0.18/webapps/<br />
: The latest version can be downloaded [http://narademo.umiacs.umd.edu/aceam/current/ace-am.war here]<br />
; 5. Update any configuration settings. (Versions prior to 1.3)<br />
: In your TOMCAT/conf/Catalina/localhost/ace-am.xml file, you may need to add some settings. This is only needed if you are upgrading from 1.2.2 or earlier.<br />
<br />
: Check the following line in your configuration file to ensure the database connection uses UTF-8.<br />
&lt;Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
<br />
: If your url does not contain the character encoding, you will need to add it if you want to use UTF-8 characters.<br />
<br />
: There is a sample configuration file available [http://narademo.umiacs.umd.edu/aceam/current/ace-am.xml here]<br />
; 6. Restart ACE.<br />
: Run TOMCAT/bin/startup.sh to restart tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/startup.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0_07<br />
<br />
<br />
==Database Files==<br />
Database patches required to bring ace database up to date can be found in the most recent version of ACE, located [https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace here]</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2899Ace:Audit Manager Installation Guide2012-12-13T17:25:49Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.6 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
These can be downloaded at the following website:<br />
https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/files<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Main&diff=2898Ace:Main2012-10-22T20:28:10Z<p>Shake: </p>
<hr />
<div>ACE (Auditing Control Environment) is a system that incorporates a new methodology to address the integrity of long term archives using rigorous cryptographic techniques. ACE continuously audits the contents of the various objects according to the policy set by the archive, and provides mechanisms for an independent third-party auditor to certify the integrity of any object.<br />
<br />
ACE consists of two components, the first an Audit Manager(AM) that checks files locally to ensure they have not been compromised. The second part, the Integrity Management Service (IMS), issues tokens that the AM can use to verify that its local store of file digests has not been tampered with. <br />
<br />
Anyone wishing to audit their files with ACE only needs to install an Audit Manager locally to manage their files. The ADAPT project runs a publically available IMS at ims.umiacs.umd.edu that any group may freely use.<br />
<br />
{| width="75%" style="margin-left: 75px;"<br />
| '''Audit Manager''' || '''Integrity Management Service'''<br />
|-<br />
| [[Ace:Audit Manager Installation Guide|Download Audit Manager]] || [[Ace:Ace IMS System|System Documentation]]<br />
|-<br />
| [[Ace:Audit Manager User Guide|User Guide]] || [http://ims.umiacs.umd.edu:8080/ace-ims/IMSWebService IMS Webservice]<br />
|-<br />
| [http://groups.google.com/group/ace-devel Discussion List] || [[Ace:Validating Witness and Tokens|Validating Tokens and Witnesses]]<br />
|-<br />
| [[Ace:Audit Manager Upgrading|Upgrade Audit Manager]] || [http://groups.google.com/group/ace-ims-witness?hl=en IMS Witness Google Goup]<br />
|- <br />
| [[Ace:AM Config Reference|AM Configuration Options]] || [http://mailman.umiacs.umd.edu/mailman/listinfo/ims-witness IMS Witness UMIACS listserv]<br />
|-<br />
| || [[Ace:IMS Installation| IMS Installation Guide]]<br />
|-<br />
| '''Resources'''<br />
|-<br />
| [https://scm.umiacs.umd.edu/redmine/adapt/projects/ace Files and Issue Tracker]<br />
|-<br />
| [[Ace:Devel Pages|Development Documentation]]<br />
|-<br />
| [[Ace:Webstart Client|Auditor Application]] || <br />
|-<br />
| [http://digitalcommons.uconn.edu/libr_pubs/39/ Step by Step installation instructions]<br />
|}<br />
<br />
<br />
'''Papers and Presentations'''<br />
<br />
* Smorul, M., Song, S., and JaJa, J. An Implementation of the Audit Control Environment(ACE) to Support the Long Term Integrity of Digital Archives. in DigCCurr 2009. 2009: University of North Carolina.[[media:DigCCurr2009_060909.pdf|pdf]] presentation [[media:Smorul-digccurr09.ppt|ppt]]<br />
* ACE Presentation at Archiving 2007 (5/07) [[media: ACE-Archiving2007.ppt|ppt]]<br />
* Song, S. and JaJa, J. ACE: A Novel Software Platform to Ensure the Integrity of Long Term Archives. in Archiving 2007. 2007: IS&T. [[media:rad71E67.pdf|pdf]]<br />
<br />
Development of the ACE Version1.0 release was partially sponsored by the US National Archives and Records Administration. The basic research on ACE was partially sponsored under a DIGARCH grant from NSF/Library of Congress.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2897Ace:Audit Manager Installation Guide2012-09-14T17:34:31Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.6 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp<br />
* ace-am.xml: ace configuration file<br />
<br />
These can be downloaded at the following website:<br />
https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Installation_Guide&diff=2896Ace:Audit Manager Installation Guide2012-09-14T17:33:41Z<p>Shake: </p>
<hr />
<div>The ACE Audit manager is a web portal to monitor the integrity of any collection you specify. The manager will register any new files found in addition to checking the integrity of files in a collection during an audit. <br />
<br />
==Requirements==<br />
Before you begin, you will need to have the following software installed:<br />
* Java 1.6 or later http://java.sun.com<br />
* Tomcat 6.0 or later http://tomcat.apache.org<br />
* MySQL 4.0 or later http://www.mysql.org<br />
* MySQL connector 5.0.7 or better http://www.mysql.com/products/connector/j/<br />
<br />
==Files==<br />
<br />
The following files are needed to install the Audit Manager <br />
* ace.sql : sql tables<br />
* ace-am.war: ace webapp (version 1.4.1 11-20-09)<br />
* ace-am.xml: ace configuration file<br />
<br />
These can be downloaded at the following website:<br />
https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace<br />
<br />
==Quick Setup==<br />
<br />
This is for new installations only. To update, follow the directions [[Ace:Update Audit Manager|here]]<br />
<br />
;1. Create Database : Create a new database called 'aceam', grant permissions and setup table structure.<br />
<pre><br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 2 to server version: 4.1.20<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> create database aceam;<br />
Query OK, 1 row affected (0.01 sec)<br />
<br />
mysql> grant all on aceam.* to 'aceam'@'localhost' identified by 'YOUR_PASSWORD';<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> use aceam;<br />
Database changed<br />
mysql> source ace.sql;<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
ERROR 1146 (42S02): Table 'aceam.ACTIVITY_LOG_ENTRY' doesn't exist<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
Records: 0 Duplicates: 0 Warnings: 0<br />
<br />
mysql> exit<br />
Bye<br />
</pre><br />
<br />
The ace.sql listed is the file from above. Set YOUR_PASSWORD to a password to use for this database. This password is only used to connect the Audit Manager to the database.<br />
<br />
;2. Install Webapp : Install tomcat on your server and verify it's working. Shutdown the server and place a copy of the ace-am.war file in your TOMCAT/webapps directory. Place a copy of the configuration file ace-am.xml in your TOMCAT/conf/Catalina/localhost directory. Open up the configuration file and edit the following setting.<br />
<br />
<pre><br />
<Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
</pre><br />
<br />
Change the password from YOUR_PASSWORD to whatever you used above.<br />
<br />
* Place a copy of the mysql-connector-java-5.0.XX-bin.jar in your TOMCAT/lib directory.<br />
<br />
; 3. Register your first collection : When the monitor starts up, you will see a status screen with no collections.<br />
<br />
* Click ''Add Collection'' from the status screen. <br />
**You should be prompted for a password. Enter 'admin' for both the username and password.<br />
* Enter a descriptive name, and the directory you want to monitor. Choose the type of storage where this directory is located. <br />
**Click ''Configure Storage'' when finished.<br />
* If you selected something other than ''local'' for your storage, a box will appear with additional setting you need to fill out.<br />
* Click ''Save'' when finished.<br />
<br />
; 4. Audit your collection : Click the ''Status'' link at the top of the page. Click on the name of the collection and then click the [[Image:file-audit-start.jpg]] icon in the details box. Your collection will now scan all files and register tokens. Please see the [[Audit Manager User Documentation|User Documentation]] for more details.</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Upgrading&diff=2895Ace:Audit Manager Upgrading2012-09-14T17:32:19Z<p>Shake: </p>
<hr />
<div>==Upgrade Instructions==<br />
There are three steps to upgrading the audit manager, these are upgrading the application code, upgrading the underlying database, and finally updating any configuration files if necessary. The procedure for upgrading is listed below<br />
<br />
These instructions are current for version 1.3. Links to all previous versions of ace are available on the [https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace software page]<br />
<br />
; 1. Note the version you are currently running<br />
: Point your web browser at your ACE AM installation and look for the version at the bottom. If should look something like 1.2.2, or 1.3..<br />
; 2. Stop the Audit Manager/Tomcat<br />
: Run TOMCAT/bin/shutdown.sh to stop tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/shutdown.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0<br />
<br />
; 3. Apply database patches<br />
: Connect to your mysql database and apply any listed patches in order. You will need to apply all patches starting with your current version (see step 1) *in order*. See the table at the bottom of this page for a list of what patches you need. <br />
<br />
: To apply the patchec, connect to your database and issue the command 'source patchfile.sql' for each patch file you need to run.<br />
<br />
:Here's an example of what you will see. Depending on which patches you are applying, your screen will look different.<br />
<pre><br />
[user@loach ~]$ mysql aceam -u aceam -p <br />
Enter password: <br />
Reading table information for completion of table and column names<br />
You can turn off this feature to get a quicker startup with -A<br />
<br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 88<br />
Server version: 5.0.45 Source distribution<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> source 1.2-1.3.updates.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.01 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> <br />
</pre><br />
<br />
<br />
; 4. Upgrade the ACE AM code<br />
: Remove the existing ACE installation files and directories located at TOMCAT/webapps/ace-am and TOMCAT/webapps/ace-am.war.<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/webapps/ace-am*<br />
:Place a copy of the latest ace-am.war file in TOMCAT/webapps/<br />
[toaster@loach ~/aceam]$ cp /tmp/ace-am.war apache-tomcat-6.0.18/webapps/<br />
: The latest version can be downloaded [http://narademo.umiacs.umd.edu/aceam/current/ace-am.war here]<br />
; 5. Update any configuration settings. (Versions prior to 1.3)<br />
: In your TOMCAT/conf/Catalina/localhost/ace-am.xml file, you may need to add some settings. This is only needed if you are upgrading from 1.2.2 or earlier.<br />
<br />
: Check the following line in your configuration file to ensure the database connection uses UTF-8.<br />
&lt;Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
<br />
: If your url does not contain the character encoding, you will need to add it if you want to use UTF-8 characters.<br />
<br />
: There is a sample configuration file available [http://narademo.umiacs.umd.edu/aceam/current/ace-am.xml here]<br />
; 6. Restart ACE.<br />
: Run TOMCAT/bin/startup.sh to restart tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/startup.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0_07<br />
<br />
<br />
==Database Files==<br />
Database patches required to bring ace database up to date can be found in the most recent version of ACE, located [https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace here]</div>Shakehttps://wiki.umiacs.umd.edu/adapt/index.php?title=Ace:Audit_Manager_Upgrading&diff=2894Ace:Audit Manager Upgrading2012-09-14T17:24:22Z<p>Shake: </p>
<hr />
<div>==Upgrade Instructions==<br />
There are three steps to upgrading the audit manager, these are upgrading the application code, upgrading the underlying database, and finally updating any configuration files if necessary. The procedure for upgrading is listed below<br />
<br />
These instructions are current for version 1.3. Links to all previous versions of ace are available on the [https://scm.umiacs.umd.edu/redmine/adapt/projects/list_files/ace software page]<br />
<br />
; 1. Note the version you are currently running<br />
: Point your web browser at your ACE AM installation and look for the version at the bottom. If should look something like 1.2.2, or 1.3..<br />
; 2. Stop the Audit Manager/Tomcat<br />
: Run TOMCAT/bin/shutdown.sh to stop tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/shutdown.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0<br />
<br />
; 3. Apply database patches<br />
: Connect to your mysql database and apply any listed patches in order. You will need to apply all patches starting with your current version (see step 1) *in order*. See the table at the bottom of this page for a list of what patches you need. <br />
<br />
: To apply the patchec, connect to your database and issue the command 'source patchfile.sql' for each patch file you need to run.<br />
<br />
:Here's an example of what you will see. Depending on which patches you are applying, your screen will look different.<br />
<pre><br />
[user@loach ~]$ mysql aceam -u aceam -p <br />
Enter password: <br />
Reading table information for completion of table and column names<br />
You can turn off this feature to get a quicker startup with -A<br />
<br />
Welcome to the MySQL monitor. Commands end with ; or \g.<br />
Your MySQL connection id is 88<br />
Server version: 5.0.45 Source distribution<br />
<br />
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.<br />
<br />
mysql> source 1.2-1.3.updates.sql;<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
Query OK, 0 rows affected (0.01 sec)<br />
<br />
Query OK, 0 rows affected (0.00 sec)<br />
...<br />
...<br />
Query OK, 0 rows affected (0.00 sec)<br />
<br />
mysql> <br />
</pre><br />
<br />
<br />
; 4. Upgrade the ACE AM code<br />
: Remove the existing ACE installation files and directories located at TOMCAT/webapps/ace-am and TOMCAT/webapps/ace-am.war.<br />
[toaster@loach ~/aceam]$ rm -rf apache-tomcat-6.0.18/webapps/ace-am*<br />
:Place a copy of the latest ace-am.war file in TOMCAT/webapps/<br />
[toaster@loach ~/aceam]$ cp /tmp/ace-am.war apache-tomcat-6.0.18/webapps/<br />
: The latest version can be downloaded [http://narademo.umiacs.umd.edu/aceam/current/ace-am.war here]<br />
; 5. Update any configuration settings. (Versions prior to 1.3)<br />
: In your TOMCAT/conf/Catalina/localhost/ace-am.xml file, you may need to add some settings. This is only needed if you are upgrading from 1.2.2 or earlier.<br />
<br />
: Check the following line in your configuration file to ensure the database connection uses UTF-8.<br />
&lt;Resource auth="Container" driverClassName="com.mysql.jdbc.Driver" maxActive="20"<br />
maxIdle="10" maxWait="-1" name="jdbc/aceamdb" <br />
password="ace" username="aceam" <br />
url="jdbc:mysql://localhost/aceam?characterEncoding=UTF-8" <br />
testOnBorrow="true" type="javax.sql.DataSource" validationQuery="SELECT 1"/><br />
<br />
: If your url does not contain the character encoding, you will need to add it if you want to use UTF-8 characters.<br />
<br />
: There is a sample configuration file available [http://narademo.umiacs.umd.edu/aceam/current/ace-am.xml here]<br />
; 6. Restart ACE.<br />
: Run TOMCAT/bin/startup.sh to restart tomcat<br />
[toaster@loach ~/aceam]$ apache-tomcat-6.0.18/bin/startup.sh <br />
Using CATALINA_BASE: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_HOME: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18<br />
Using CATALINA_TMPDIR: /fs/narahomes/toaster/aceam/apache-tomcat-6.0.18/temp<br />
Using JRE_HOME: /opt/jdk1.6.0_07<br />
<br />
<br />
==Database Files==<br />
Database patches required to bring ace database up to version 1.3.<br />
<br />
{| border="1" width="75%" style="margin 10px;"<br />
|-<br />
| Current Version || Database Update Files<br />
|-<br />
| 1.2.2 || [http://narademo.umiacs.umd.edu/aceam/1.3/1.2-1.3.updates.sql 1.2-1.3.updates.sql]<br />
|-<br />
| 1.2.1 || [http://narademo.umiacs.umd.edu/aceam/1.3/1.2-1.3.updates.sql 1.2-1.3.updates.sql]<br />
|-<br />
| 1.2 || [http://narademo.umiacs.umd.edu/aceam/1.3/1.2-1.3.updates.sql 1.2-1.3.updates.sql]<br />
|-<br />
| 1.1 || [http://narademo.umiacs.umd.edu/aceam/1.2/1.1-1.2.updates.sql 1.1-1.2.updates.sql]<br>[http://narademo.umiacs.umd.edu/aceam/1.3/1.2-1.3.updates.sql 1.2-1.3.updates.sql]<br />
|-<br />
| 1.0 || [http://narademo.umiacs.umd.edu/aceam/1.1/1.0-1.1.update.sql 1.0-1.1.update.sql]<br>[http://narademo.umiacs.umd.edu/aceam/1.2/1.1-1.2.updates.sql 1.1-1.2.updates.sql]<br>[http://narademo.umiacs.umd.edu/aceam/1.3/1.2-1.3.updates.sql 1.2-1.3.updates.sql]<br />
|}</div>Shake