Follow these instructions to install ProcessMaker 2.0 - 2.5 in Red Hat Enterprise Linux (RHEL)/CentOS 5 or later. If installing, ProcessMaker 2.8 or later, see these instructions. Before installing ProcessMaker, see the Installation Requirements. After installation, see Additional Server Configuration.
Step 1: Configure SELinux
If ProcessMaker is installed in the /opt directory, it is necessary to either configure SELinux to allow Apache to read/write to the directory where ProcessMaker is installed or simply disable SELinux.
To configure SELinux, so that Apache can read/write to the /opt/processmaker directory. first login as "root" and issue the following commands from the terminal:
restorecon -R -v /opt/processmaker
Then, configure Apache so it is able to send email:
If needing to run ProcessMaker on any port other than the default ports of 80, 443, 488, 8008, 8009 and 8443, then SELinux needs to be configured to allow another port to be used. For example, if using port 8080:
SELinux causes so many problems, that it often easier to simply disable it. To permanently disable SELinux, edit the SELinux configuration file:
In the config file, set the following parameter:
Then, restart the server, so SELinux will be permanently disabled.
If needing to temporarily disable SELinux, in order to debug a problem, login as the "root" user and issue the command:
To temporarily enable SELinux:
Step 2: Installing Apache, MySQL and PHP
If Apache, MySQL or PHP are not already installed, then switch to the root user:
Enter the root password
Then use yum to install Apache, MySQL and PHP:
Follow the instructions on the screen to install the Apache web server.
Next, install the PHP modules needed by ProcessMaker:
php-mcrypt is not in CentOS's standard repositories. However, it is in Fedora's EPEL repository.
Install the EPEL Repo:
For 32 bit:
For 64 bit:
Then it is possible to execute:
After changing the PHP configuration, restart the Apache service (or reboot the machine).
To check if all the PHP modules were installed, run the following command:
In addition, phpMyAdmin can be installed to easily view the MySQL databases used by ProcessMaker inside a web browser. For some versions of RHEL/CentOS, phpMyAdmin will need to be manually installed.
Step 3: Configuring PHP Settings
If using PHP 5.3 and later, then no configuration of PHP is required. If using PHP 5.2 which is used in Red Hat/CentOS 5.10 and earlier, then PHP's configuration file php.ini needs to be edited to increase the memory limit for each session.
Open the php.ini file with a plain text editor, which is located at:
Each ProcessMaker session needs a minimum of 128MB RAM to run properly, so set the memory_limit to 128M or greater:
If the php.ini file has been modified, make sure that file_uploads and short_open_tag have been enabled:
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:
upload_max_filesize = 24M
Step 4: Download & Extract ProcessMaker
Go to http://sourceforge.net/projects/processmaker/files and download a recent version of ProcessMaker. The versions are numbered according to the pattern MAJOR.MINOR.REVISION, such as 2.0.45. Download the processmaker-2.X.X.tar.gz file.
Note: Some older versions of ProcessMaker offered rpm files, but it is recommended to install from the tar.gz file if planning on installing in a directory other than /opt or doing an additional installation of ProcessMaker.
It is recommended to install ProcessMaker under the /opt directory, since it is an add-in application which doesn't come from the standard repositories. Nonetheless, ProcessMaker can be installed in any directory, except directories such as /var/www which are publicly accessible to the internet, since that would be a security hole.
Download the latest ProcessMaker tarball from http://sourceforge.net/projects/processmaker/files and save it to the server where ProcessMaker will be installed. Use the tar command to decompress the tar.gz file in the /opt directory (or where ever installing ProcessMaker):
This will create a new processmaker directory, containing all the ProcessMaker files and subdirectories.
Set File Permissions
After installing the ProcessMaker files either from the RPM package or from the tarball, make the following subdirectories writable for the "apache" user, so ProcessMaker can write to certain directories:
chmod -R 770 shared workflow/public_html
chmod -R 770 config content/languages plugins xmlform js/labels
chown -R apache:apache /opt/processmaker
If installing ProcessMaker 2.5.0 or later, also give write permissions to generate Output Documents:
chmod -R 770 js thirdparty/html2ps_pdf/cache
Step 5: MySQL Configuration
Before using MySQL, use mysql_secure_installation to set up a secure database environment. Login as the "root" user and issue the following command:
Then follow the wizard to configure MySQL:
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MySQL to secure it, we'll need the current password for the root user. If you've just installed MySQL, and you haven't set the root password yet, the password will be blank, so you should just press enter here.
Enter the MySQL root password:
Enter current password for root (enter for none): OK, successfully used password, moving on...
Then it is possible to change the MySQL root password:
Setting the root password ensures that nobody can log into the MySQL root user without the proper authorization.
You already have a root password set, so you can safely answer 'n'.
Change the root password? [Y/n] n ... skipping.
Then, it will ask about removing anonymous users:
By default, a MySQL installation has an anonymous user, allowing anyone to log into MySQL without having to have a user account created for them. This is intended only for testing, and to make the installation go a bit smoother. You should remove them before moving into a production environment.
Remove anonymous users? [Y/n] y ... Success!
Then it will ask about disabling root login:
Normally, root should only be allowed to connect from 'localhost'. This ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] y ... Success!
Then, it is possible to change the MySQL database name:
By default, MySQL comes with a database named 'test' that anyone can access. This is also intended only for testing, and should be removed before moving into a production environment.
Remove test database and access to it? [Y/n] y - Dropping test database... ... Success! - Removing privileges on test database... ... Success!
Finally, reload privileges tables:
Reloading the privilege tables will ensure that all changes made so far will take effect immediately.
Reload privilege tables now? [Y/n] y ... Success!
All done! If you've completed all of the above steps, your MySQL installation should now be secure.
Thanks for using MySQL!
User other than root
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, then follow the steps below to grant a MySQL user superuser privileges to create and update databases. Login to MySQL:
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:
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.
MySQL Configuration Issues
Setting the root Password
If MySQL doesn't have a root password, set one for better security:
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:
Then, MySQL needs to be started as a service:
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:
Step 6: Apache Configuration
Copy ProcessMaker's sample configuration for Apache to conf.d directory:
Edit the ProcessMaker configuration file pmos.conf:
Modify the file to fit your environment:
# the ServerName with you own subdomains.
#processmaker virtual host
<VirtualHost your_ip_address >
DirectoryIndex index.html index.php
Allow from all
RewriteRule ^.*/(.*)$ sysGeneric.php [NC,L]
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"
AddOutputFilterByType DEFLATE text/html
Note: If using Apache 2.4 (which is found in Red Hat/CentOS 7.0), then change the following line from:
Replace your_ip_adress 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 file 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:
#processmaker virtual host
<VirtualHost 192.168.1.100 >
DirectoryIndex index.html index.php
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:
#processmaker virtual host
<VirtualHost *:8080 >
DirectoryIndex index.html index.php
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 Apache configuration file found at /etc/httpd/conf/httpd.conf.
ProcessMaker needs to use the expires, rewrite, deflate and vhost_alias modules in the Apache 2 web server. Check to see whether these modules are enabled, by opening the Apache configuration file found at /etc/httpd/conf/httpd.conf. The following 4 lines should be found in the list of Apache modules to load:
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule deflate_module modules/mod_deflate.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
Note: If using Apache 2.4 (which is found in CentOS/Red Hat 7.0), either include the filter module:
Or remove the following line from pmos.conf:
After adding the web site pmos.conf and enabling modules, it is necessary to restart the Apache web server:
Apache Configuration Issues
Setting Apache as Service
If Apache is not already running as a service, then configure it to automatically start as a service when booting up:
No ServerName Warning
If a similar warning message appears when restarting Apache:
Then, the ServerName needs to be set for Apache. Edit the httpd.conf file and add the line:
For instance, if running ProcessMaker from the local machine, then:
If running ProcessMaker off a port other than the default port 80, then add the following line to the httpd.conf file:
For instance, if running ProcessMaker from the local machine at port 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:
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.
If a firewall blocks traffic on non-standard ports, the port needs to be unblocked so it can be used by ProcessMaker. For example, if using an IPTables firewall, the following commands unblock the port 8080:
iptables-save | tee /etc/sysconfig/iptables
service iptables restart
Step 7: Setting up ProcessMaker
Once all ProcessMaker configurations were set up, 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 at port 8080, go to: http://127.0.0.1:8080
Then in the web browser, use the installation wizard to complete the installation.
Step 8: 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.
Execution of cron.php
Errors during Installation
Depending on the errors found in the installation log file, check the following files:
The Apache configuration file:
The ProcessMaker web site configuration file for Apache:
The PHP configuration file:
The MySQL configuration file:
The ProcessMaker configuration file where components are installed:
The ProcessMaker configuration file for database connections:
The ProcessMaker redirection to login screen:
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.