Alfresco Repository

Install Alfresco

This step is not needed if you already have an Alfresco installation.

If you do not already have an Alfresco installation, Armedia recommends Alfresco Enterprise 5.1 or higher.  You can download the enterprise installer and acquire a license file from the Alfresco support web site; you will need an Alfresco support user account.

To integrate ArkCase with Alfresco Records Management module, you must also download and install the records management module; be sure to download the appropriate module version for your Alfresco version.

Alfresco support web site:

Alfresco documentation (including installation guide):

If you install Alfresco using the default installer, be sure to start the installation as the user that should run the Alfresco process; for example, if you install as root, Alfresco will run as root user.  Armedia recommends creating a normal user account, then run the installer as that user.

Configure Alfresco

Sign into Alfresco Share using the Alfresco administrator account.

  • Create an ordinary site called acm.
    • Click the Sites dropdown in the top menu bar, then “Create Site”.
    • Choose the Collaborative site type.
    • acm for site name, acm for url
    • Click OK.
  • If you installed the records management module, then create the records management site (not needed if your records managers have already created the records management site).
    • Click the Sites dropdown in the top menu bar, then “Create Site”.
    • Choose the Records Management site type.
    • Click OK.

Create the ArkCase folder structure:

  • If Records Management is installed, then in the Records Management site, open the file plan, and create a category folder “ACM”.  In the ACM folder, create category folders “Complaints” and “Case Files”.
  • In the acm site, open the Document Library and create these folders:
    • Case Files
    • Complaints
    • Expenses
    • Tasks
    • Timesheets
    • User Profile

On Linux, the Alfresco startup script should look something like this; make sure the bolded portions are correct for your system.


  • #!/bin/sh
  • # Starts, stops, and restarts Alfresco for ACM
  • #
  • # chkconfig: 345 89 11
  • # description: Starts and stops Alfresco for ACM
  • ALFRESCO_DIR=”/opt/alfresco-5.1
  • case $1 in
  •     start)
  •         echo “Starting Alfresco for ACM”
  •         su – $ALFRESCO_USER -c “cd $ALFRESCO_DIR ; ./ start”
  •         ;;
  •     stop)
  •         echo “Stopping Alfresco for ACM”
  •         su – $ALFRESCO_USER -c “cd $ALFRESCO_DIR ; ./ stop”
  •         ;;
  •     restart)
  •         $0 stop
  •         sleep 10
  •         $0 start
  •         ;;
  •     *)
  •         echo “Usage: $0 {start|stop|restart}” >&2
  •         exit 1
  •         ;;
  • esac

Logrotate (Linux hosts only)

Unfortunately, by default Tomcat’s catalina.out file is never truncated or removed, and ordinarily you have to shutdown Alfresco to clean it.  On Linux hosts with logrotate enabled, Armedia uses the following method to manage the size of the catalina.out file, with no Alfresco restarts needed.

Create the file ‘/etc/logrotate.d/alfresco’ with this content:


  • /opt/app/acm/alfresco-5.1/tomcat/logs/catalina.out {
  •   copytruncate
  •   daily
  •   rotate 7
  •   compress
  •   missingok
  •   size 5M
  • }


Ensure the path to the catalina.out is correct.  Then create or update a cron schedule for the root user:

  • sudo crontab –u root -e

Add a line like this:

  • 30 2 * * * /usr/sbin/logrotate -f /etc/logrotate.d/alfresco

When you finish updating this crontab, run this command to verify the crontab was updated:

  • sudo crontab –l

The output should include the line you just added, to run the logrotate script at 2:30 AM each day.  Of course the cron expression can be updated to your taste.