Overview

Follow these instructions to install ProcessMaker 2.0 - 2.5 on top of a LAMP (Linux, Apache, MySQL, PHP) stack in OpenSUSE 11.2 or later. If using an older version of OpenSUSE, MySQL will have to be upgraded to at least version 5.1.6. If installing ProcessMaker 2.8 or later, see these instructions.

Before installing checking the installation requirements. After installation, see Additional Server Configuration.

ProcessMaker Installation

Follow the steps listed below to install ProcessMaker in SuSE/OpenSUSE.

Step 1: Install MySQL, PHP and Apache

If the LAMP stack isn't already installed, open a shell by going to Applications > Accessories > Terminal. At the command line, login with administrative powers (or as root if its password was set):

sudo -s  or  su    
   Enter password

In OpenSUSE 11.2:

Install Apache, MySQL and PHP and all their necessary modules:

zypper install apache2 php5 php5-mysql apache2-mod_php5 mysql mysql-client mysql-community-server \
   php5-soap php5-mbstring php5-gd php5-mcrypt php5-ldap php5-curl php5-xml php5-soap php5-cli

Set MySQL to automatically start as a service at bootup and turn on the service:

chkconfig --add mysql
rcmysql start

Then, set up a secure installation of mysql, by setting a root password and removing the "test" database:

mysql_secure_installation

Set Apache to automatically start as a service at bootup and turn on the service:

chkconfig --add apache2
rcapache2 start

Make sure that the apache2 and mysql services will start on bootup. They should be listed as "on" for the runlevel on which your installation of OpenSuSE runs, which is generally level 5:

# chkconfig -l | grep -E "apache2|mysql"
apache2                   0:off  1:off  2:off  3:on   4:off  5:on   6:off
mysql                     0:off  1:off  2:on   3:on   4:off  5:on   6:off

Check that Apache and PHP are working correctly, by adding an index.php file:

vi /srv/www/htdocs/index.php

Put this code in the file and save it:

Then, open a web browser on the server and enter the address:

http://localhost

Information about PHP should appear in the browser window, indicating that PHP is working correctly.

In OpenSUSE 13.1:

Install Apache, MySQL and PHP and all their necessary modules:

zypper install apache2 apache2-mod_php5 mysql-community-server-client mysql-community-server \
   php5 php5-mysql php5-soap php5-mbstring php5-gd php5-mcrypt php5-ldap php5-curl php5-soap

OpenSUSE 13.1 has MariaDB installed by default. The above command will will uninstall MariaDB and replace it with MySQL. If wanting to keep MariaDB and use it instead of MySQL, then use the command:

zypper install apache2 php5 php5-mysql apache2-mod_php5 php5-soap php5-mbstring \
   php5-gd php5-mcrypt php5-ldap php5-curl php5-soap

Set MySQL/MariaDB to automatically start as a service at bootup and turn on the service:

chkconfig --add mysql
service mysql start

Then, set up a secure installation of MySQL/MariaDB, by setting a root password and removing the "test" database:

mysql_secure_installation

Set Apache to automatically start as a service at bootup and turn on the service:

systemctl enable apache2.service
service apache2 start

Install PhpMyAdmin

In addition, phpMyAdmin can be installed to easily view the MySQL databases used by ProcessMaker inside a web browser.

Step 2: Configuring PHP Settings

Enable the php5 module for Apache:

a2enmod php5

If using PHP 5.3 and later, then no configuration of PHP is required. If using PHP 5.2 which is used in OpenSUSE 11.1 and earlier, then PHP's configuration file php.ini needs to be edited to increase the memory limit for each session.

Edit PHP's configuration file php.ini with a plain text editor, which is located at:

/etc/php5/apache2/php.ini

Each ProcessMaker session needs a minimum of 128MB RAM to run properly, so set the memory_limit to 128M or greater:

memory_limit = 128M

Note: The value set for the memory_limit in php.ini should be the same value set in the System interface (or in the env.ini file).

If the php.ini file has been modified, make sure that file_uploads and short_open_tag have been enabled:

file_uploads = On
short_open_tag = On

If planning on uploading large files, as Input Documents while running processes, the max_post_size and upload_max_filesize should be increased to more than the default 2MB. For instance, if planning on uploading files as large as 24MB, then:

post_max_size = 24M
upload_max_filesize = 24M

Step 3: Download & Extract ProcessMaker

Go to http://sourceforge.net/projects/processmaker/files and download the latest version of ProcessMaker. The versions are numbered according to the pattern MAJOR.MINOR-REVISION, such as 2.0.45. Beta versions will have the word "beta" appended to the version number.

After the download has finished, decompress the tarball in the directory where ProcessMaker will be installed. ProcessMaker can be installed in any directory which is not publicly accessible to the internet (so do NOT install it in /var/www), but it is generally installed in /opt, since it is not an optional program which doesn't come from the standard repositories:

tar -C /opt -xzvf processmaker-2.X-X.tar.gz  

Verify that ProcessMaker was correctly decompressed:

ls /opt/processmaker

The processmaker directory should contain the following contents:

gulliver     processmaker      rbac        shared
LICENSE.txt  processmaker.bat  README.txt  workflow

Set file permissions

Then, issue the following commands as the "root" user so that ProcessMaker can access the necessary files when run by the Apache server:

cd /opt/processmaker
chmod -R 770 shared workflow/public_html
cd /opt/processmaker/workflow/engine/
chmod -R 770 config content/languages plugins xmlform js/labels
chown -R wwwrun:www /opt/processmaker

If installing ProcessMaker 2.5.0 or later, also give write permissions to generate Output Documents:

cd /opt/processmaker/gulliver
chmod -R 770 js thirdparty/html2ps_pdf/cache

Step 4: MySQL Configuration

The MySQL "root" user should already have all the necessary privileges to setup the ProcessMaker databases. If planning on using a MySQL user other than "root" to set up the ProcessMaker databases, grant a MySQL user superuser privileges to create and update databases.

Login to MySQL:

mysql -u root -p

Enter the root password for MySQL.

Once in MySQL, give the user which will be running ProcessMaker superuser privileges to create create and modify MySQL databases:

mysql> grant all on *.* to 'USER'@'localhost' identified by 'PASSWORD' with grant option;

Replace USER with the name of your MySQL user and PASSWORD with the password for that user. (If that user doesn't already exist, he/she will be automatically created with the above grant command. If you are running ProcessMaker on a different server than your MySQL server, then replace localhost with the domain name or IP address of the server where ProcessMaker is located.

Exit MySQL:

mysql> exit;

MySQL Configuration Issues

Setting the root Password

If MySQL doesn't have a root password, set one for better security:

mysqladmin -u root password PASSWORD

If you have forgotten the root password, see these instructions to reset it.

Starting as a Service

When logging into MySQL, if the following error message appears:

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Then, MySQL needs to be started as a service:

service mysqld start

If MySQL was installed from its Red Hat/CentOS package, it should automatically start as a service on bootup. If not, then use use chkconfig to add it as a service:

 chkconfig --levels 345 mysqld on

Step 5: Apache Configuration

Edit the ProcessMaker configuration file to fit your environment:

 vi /opt/processmaker/etc/pmos.conf

Replace your_ip_address and your_processmaker_domain with the IP address and domain name used by your ProcessMaker server:

# Please change the ip address with your server ip address and
  # the ServerName with you own subdomains.
  NameVirtualHost your_ip_address
  #processmaker virtual host
  <VirtualHost your_ip_address >
    ServerName "your_processmaker_domain"
    DocumentRoot /opt/processmaker/workflow/public_html
    DirectoryIndex index.html index.php
    <Directory  "/opt/processmaker/workflow/public_html">
       AddDefaultCharset UTF-8
       AllowOverRide none
       Options FollowSymlinks
       Order allow,deny
       Allow from all
       RewriteEngine on
       RewriteRule ^.*/(.*)$ sysGeneric.php [NC,L]
       ExpiresActive On
       ExpiresDefault "access plus 1 day"
       ExpiresByType image/gif "access plus 1 day"
       ExpiresByType image/png "access plus 1 day"
       ExpiresByType image/jpg "access plus 1 day"
       ExpiresByType text/css "access plus 1 day"
       ExpiresByType text/javascript "access plus 1 day"
       AddOutputFilterByType DEFLATE text/html
    </Directory>
  </VirtualHost>

Note: If using Apache 2.4 (which is found in OpenSUSE 13.1 and later), then change the following line from:

    Allow from all

To:

    Require all granted

Replace your_ip_address with the IP number or domain name of the server running ProcessMaker. If only planning on running and accessing ProcessMaker on your local machine, then use the IP address "127.0.0.1". If using ProcessMaker on a machine whose IP address might change (such as a machine whose IP address is assigned with DHCP), then use "*", which represents any IP address. If not using the standard port 80, then it is necessary to also specify the port number.

If your DNS or /etc/hosts has a defined domain for ProcessMaker, then use that domain for your_processmaker_domain. Otherwise, use the same IP address for your_processmaker_domain as was used for your_ip_address.

For example, if running ProcessMaker on a server at address 192.168.1.100 with a DNS at 123.456.7.89:

 NameVirtualHost 192.168.1.100
  #processmaker virtual host
  <VirtualHost 192.168.1.100 >
    ServerName "123.456.7.89"
    DocumentRoot /opt/processmaker/workflow/public_html
    DirectoryIndex index.html index.php
    <Directory  "/opt/processmaker/workflow/public_html">
    ...

For example, if ProcessMaker is installed in the /user/fred directory on your local machine at port 8080 with an dynamic IP assigned by DHCP:

NameVirtualHost *:8080
  #processmaker virtual host
  <VirtualHost *:8080 >
    ServerName "*"
    DocumentRoot /user/fred/processmaker/workflow/public_html
    DirectoryIndex index.html index.php
    <Directory  "/user/fred/processmaker/workflow/public_html">
    ...

Note: It is also possible to define the virtual host for ProcessMaker directly in the Apache configuration by inserting the above VirtualHost definition in the file /etc/apache2/apache2.conf.

After editing pmos.conf, add it to Apache's list of sites which are available for serving:

cp /opt/processmaker/etc/pmos.conf /etc/apache2/conf.d/pmos.conf

ProcessMaker needs to use the expires, rewrite, deflate and vhost_alias modules in the Apache 2 web server. All these modules are included in openSUSE's apache2 package, but only expires is enabled by default.

To enable the other Apache modules from the graphical interface, open the YaST2 Control Center and go to ' System > /etc/sysconfig Editor > Network > WWW > Apache2 > APACHE_MODULES. Make sure that expires is in the list of modules and add: rewrite deflate vhost_alias

To enable the other Apache modules from the command line:

vi /etc/sysconfig/apache2

Search for the APACHE_MODULES variable and edit its list of modules to include expires, rewrite, deflate and vhost_alias. For example:

APACHE_MODULES="actions alias auth_basic authn_file authz_host authz_groupfile authz_default authz_user autoindex
cgi dir env expires include log_config mime negotiation setenvif ssl userdir php5 deflate vhost_alias rewrite"

After adding the web site pmos.conf and enabling modules, it is necessary to restart the Apache web server:

rcapache2 restart

Apache Configuration Issues

Non-standard Port

If running ProcessMaker off a port other than the default port 80, then add the following line to the file /etc/apache2/listen.conf:

Listen <IP-ADDRESS>:<PORT>

For instance, if running ProcessMaker from the local machine at port 8080:

Listen 127.0.0.1:8080

Or simply:

Listen 8080

Note: If Apache is using the default port 80, then configure other programs (like Skype) to not use port 80. Check whether a program is currently listening on port 80 with the command:

netstat -tanp

To configure Skype to stop listening on port 80, press CTRL+O or go to Tools > Options. Under the Advanced section of the "Options" dialog box, go to the "Connection" section and enter an alternative port for Use port [ ] for incoming connections.

No VirtualHosts Warning

If you see one of the following messages when reloading or restarting Apache:

[warn] NameVirtualHost 12.34.56.78:80 has no VirtualHosts
[warn] NameVirtualHost *:0 has no VirtualHosts
[warn] NameVirtualHost *:80 has no VirtualHosts

Then, comment out or delete the following lines in the file /etc/apache2/listen.conf:

NameVirtualHost 12.34.56.78:80
NameVirtualHost *:80
NameVirtualHost *

Step 6: Setting up ProcessMaker

Open a web browser and enter the IP address (and port number if not using the default port 80) where ProcessMaker is installed. For instance, if ProcessMaker is installed at the address 192.168.10.100, then go to: http://192.168.10.100
If using ProcessMaker which is installed locally on port 8080, go to: http://127.0.0.1:8080

Then in the web browser, use the installation wizard to complete the installation.

Step 7: Additional Configuration

Additional aspects of ProcessMaker may need to be configured. See Additional Server Configuration and the Configuration section of the wiki. Most installations of ProcessMaker need to configure the following:

Setting the Time Zone

In ProcessMaker version 2.0.29 and later, the default time zone for the ProcessMaker server is set in the env.ini configuration file. If using a previous version of ProcessMaker, see Default Time Zone.

Configuring Email

If planning on sending out email notifications or enabling users to recover forgotten passwords, then see Email - Settings to configure ProcessMaker to use an email server.

Execution of cron.php

If planning on using email notifications, events or the case scheduler, then the server running ProcessMaker has to be configured to periodically execute the cron.php file. See Executing cron.php.

Errors during Installation

If an error occurs during the installation, check the installation log file:
/shared/log/install_log.log
It will generally be found at:
/opt/processmaker/shared/log/install_log.log

Depending on the errors found in the installation log file, check the following files:
The Apache configuration file:
/etc/apache2/apache2.conf
The ProcessMaker web site configuration file for Apache:
/etc/apache2/conf.d/pmos.conf
The PHP configuration file:
/etc/php5/apache2/php.ini
The MySQL configuration file:
/etc/my.cnf
The ProcessMaker configuration file where components are installed:
/workflow/engine/config/paths_installed.php
The ProcessMaker configuration file for database connections:
/shared/sites/workflow/db.php
The ProcessMaker redirection to login screen:
/processmaker/workflow/public_html/index.html

If the following error appears at the login screen:

This error indicates that the installer was unable to access the MySQL databases to install the translations. Make sure that the MySQL port (which is 3306 by default) isn't blocked by a firewall and MySQL is configured to accept connections from the server running processmaker. If that doesn't work, then ask for help on the forum.