(use ‘mysql.exe’ on Windows platform and ‘./mysql’ on Linux based platforms)

Deploy the new version of the sample reports.

With this deployment, a new version of the sample reports are released to insure compressed times with a big quantity of audit data. Let’s start with tasks:

Extract ‘reports.zip’ in the ‘data-integration’ folder. ‘report.zip’ contains 5 files with ‘prpt’ extension, each one containing one Pentaho Reporting Designer report. By default, and to let the report production simpler, are saved in the default folder: ‘data-integration’.

For the PostgreSQL platform: check if the ‘alfresco’ user of the database has password equal to ‘alfresco’. If yes, jump to the next task otherwise you have to update the connection in all the prpt reports. To update the password of all the prpt reports, follow that tasks:

For each prpt report in the ‘data-integration’ folder, execute what is described below.

Open the prpt report, one by one, with the Pentaho Reporting Designer.

Click on the ‘Data’ tab on the top right of the interface.

Right click on the JDBC:AAAR_DataMart in the Data sets.

Select ‘Edit Datasource’.

Select the ‘AAAR_DataMart’ in the left list. Pay attention to select the PostgreSQL one because two connections are defined: one for PostgreSQL and one for Mysql.

Click on the pencil.

Modify the password.

(OPTIONAL) If you want to test the connection remember that it could fail even if the password it’s correct because you could need the JDBC library in the ‘lib/jdbc’ folder of your Pentaho Reporting Designer installation.

Save the report.

Remember to repeat the tasks for all the prpt reports.

For the MySql platform: check if the ‘root’ user of the database has password equal to ‘root’. If yes, jump to the next task otherwise you have to update the connection in all the prpt reports. To update the password of all the prpt reports, follow that tasks:

For each prpt report in the ‘data-integration’ folder, execute what is described below.

Open the prpt report, one by one, with the Pentaho Reporting Designer.

Click on the ‘Data’ tab on the top right of the interface.

Right click on the JDBC:AAAR_DataMart in the Data sets.

Select ‘Edit Datasource’.

Select the ‘AAAR_DataMart’ in the left list. Pay attention to select the MySql one because two connections are defined: one for PostgreSQL and one for Mysql.

Click on the pencil.

Modify the password.

(OPTIONAL) If you want to test the connection remember that it could fail even if the password it’s correct because you could need the JDBC library in the ‘lib/jdbc’ folder of your Pentaho Reporting Designer installation.

Save the report.

Remember to repeat the tasks for all the prpt reports.

That’s all!

Now everything is ok to process again the audit data in the same way it is described here.

In the Alfresco wiki is described the backup and restore strategy but is not so clear how to do it in detail. In this post is shared a practical way to perform a restore of a backuped Alfresco in the way I like: a list of commands and tasks to execute… simpler to understand, to do and to test.

In this example is supposed that Alfresco is installed in ‘/opt/alfresco’ folder and the DBMS used is PostgreSQL. The restore strategy supposes that the backup is done as a “cold backup” described in this ‘Alfresco backup script‘ post.

Let’s start…

First of all proceed to stop alfresco.

service alfresco stop

Supposing the DBMS runs using the ‘postgres’ user, proceed as first task to restore the PostgreSQL database.

Digit CTRL+d to exit from the shell. Supposing the DBMS backup is stored in the ‘alfresco_postgres.tar’ file conforming to the backup strategy described here, let’s go ahead with the restoring of the database.

pg_restore -d alfresco alfresco_postgres.tar
exit

Now it’s time to restore the ‘alf_data’ folder with documents and indexes. Also in this case is supposed that the files are stored in a ‘alfresco_data.tgz’ file conforming to the backup strategy described here.

cd /opt/alfresco
mv alf_data alf_data.old
tar zxvf alfresco_data.tgz

That’s all!
Now it’s time to start again Alfresco and use it normally.

In the Alfresco wiki is described the backup and restore strategy but is not so clear how is defined a script and how to do it more exactly. To be more precise the backup strategy could be a “cold backup” or a “hot backup”. In this post is shared a practical way to perform a “cold backup” in the way I like: a list of commands and tasks to execute… simpler to understand, to do and to test.

In this example is supposed that Alfresco is installed in ‘/opt/alfresco’ folder and the DBMS used is PostgreSQL. The script is developed to have a 10 days backup history. If in your case is requested more or less than 10 days you can simply modify the ‘NUM_DUMP’ variable.

Exit with CTRL+X and confirm saving. Let’s go ahead defining permits and preparing the repository folder. Talking about the repository folder here is presented an example but in practical cases is suggested to mount an external file system used specifically for backup purpose.

Now everything is set and it’s time to activate the crontab to perform automatic backup, probably during the night time. Please, observe that the user used to run Alfresco is named ‘alfresco’ (do not run it as root) and the crontab is performed as ‘alfresco’ user with ‘-u alfresco’.

sudo crontab -u alfresco -e

.

00 01 * * * /opt/alfresco/alfrescoBackup.sh /opt/alfresco/backup

In this example the cold backup of Alfresco is performed at 01:00 am. To read more about crontab see here.

In this post is shared the installation of Liferay 6.1.1 Community Edition GA2 on Ubuntu 12.04 LTS 64bit with Apache Tomcat 7.0.35 and PostgreSQL 8.4.15. The purpose installation is not the bundle one but the more “robust” alternative for an enterprise configuration.

Creation of a Virtual Machine with Ubuntu 12.04 LTS – 64bit – Desktop

For development purpose you should create your own environment on a virtual machine useful to customizations and tests. Of course if you are in a production environment you can jump directly to the next paragraph talking about the JDK installation.

In this case we use the Oracle VirtualBox as virtualization product but nothing should happen if you prefer VMPlayer or other solutions.

As first step, create the virtual machine with at least 2Gb RAM and start it using the ‘ubuntu-12.04.1-desktop-amd64.iso’ file. During the installation you receive some easy questions, driving you in the installation task.

Below some suggestions:

Admit downloading and installation of third party software and update during installation.

Machine name: liferay

Password: liferay

Launch update manager and reboot (more times until no update or errors). This task is not mandatory but suggested.