Toggle navigation

ProcessMaker Image Guide

Version 3.2

Websoft9 ProcessMaker is a pre-configured, ready to run image for running ProcessMaker on Alibaba Cloud.

ProcessMaker is an open source, workflow management software suite, which includes tools to automate your workflow, design forms, create documents, assign roles and users, create routing rules, and map an individual process quickly and easily. It’s relatively lightweight and doesn’t require any kind of installation on the client computer. This file describes the requirements and installation steps for the server.

Application Software(ProcessMaker3.2)
Software directory: /data/wwwroot/processmaker

Application Server(PHP7.0,APACHE2.4)
PHP Configuration File: /etc/php/7.0/apache2/php.ini
Apache Vhost Configuration File: /etc/apache2/sites-available
Apache Log Files:/var/log/apache2

Database install directory: /usr/share/mysql
Database data directory: /data/mysql
Database Configuration File: /etc/mysql/mysql.conf.d/mysqld.cnf
PhpMyAdmin install directory: /usr/share/phpmyadmin
Kown more from MySQL User Guide

After the installation of Image,please verify it

  • Login on Alibaba Cloud console,get you Internet IP Address
  • Open you Chrome or Firefox on your local PC,visit the http://Internet IP Address/
  • If verify successfully,you can enter the Start Installation page of this Image
  • If no response from browser,please check the Security Group settings to ensure that port 80 is been allowed

Using Chrome or Firefox to visit: http://Internet IP Address/ to start the application installation process.It is recommended to complete two steps before the installation:

  • Domain resolution if you want to use (Add an A record to the Internet IP Address of Server from your Domain Control Panel)
  • Modify the MySQL password of Root through PhpMyAdmin

Then access the installation page by domain directly and complete the installation wizard for the following steps:

  1. Visit http://Internet IP Address or http://yourdomain to enter the start page of installation
  2. Click the “Next” for the next steps
  3. Fill in the  MySQL Database configuration(Default MySQL password of root is 123456) and click “Next”  button
  4. Fill in the Workspace Configuration section,and and click “Filish”  button
  5. Then you will receive feedback on successful installation below
  6. Click the “OK” to login interface
  7. Log in to backend of ProcessMaker below:

Three usernames and passwords are required for application installation, application using, andapplication maintenance:

1、ResourceSpace:Username and password is set by youself when installation,
Backend URL:http://Internet IP Address/sysworkflow/en/neoclassic/login/login
2、MySQL Database:Default username and password is root/123456,
Control Panel URL:http://Internet IP Address/phpmyadmin
3、Linux Server:Username is root,Password is set by youself when buying.You can reset the password through console and restart the Server if you have forgotten it.Please Using the Putty for Remote and WinSCP for SFTP

Plugins allow additional functionality and interface customization into ProcessMaker. The main goal of plugins is to add new features to ProcessMaker.

To see the list of plugins installed in ProcessMaker, go to the ADMIN menu and click on Plugins tab in the left sidebar:

To import a new plugin, click on the “Import” button in the toolbar. Then, select a plugin’s tar file to upload to ProcessMaker.

The current status of a plugin is displayed as Enabled or Disabled in the Plugin Manager list. When disabled, the plugin can not be used.

Routine backup (archives) of the database and application setup is essential to ensure failover is smooth.

Backup is based on the server snapshot automatic backup and manual local backup in two ways, both of which have their own advantages and disadvantages, it is recommended to use together

Automatic Backup by Snapshot of Server

IaaS provider have the “snapshot” function for Server, the snapshot is for the server disk. Snapshot tool can record the specified point in time the hard disk data, all backed up, and can achieve a key recovery.

If you have an automatic snapshot of the disk settings, the following scenes you can be more calm face:

  • Work a few days of the results, was mistakenly deleted
  • Hackers damage your site
  • The content has been messed up

Done a snapshot backup, a key to restore to the backup point of time state. That is, on-site reduction, very good function.

Different cloud vendor snapshot settings slightly different, specific reference:

Manual Backup

You can use Manual Backup as following steps:

  1. Download the entire software directory(/data/wwwroot/procesmaker) by SFTP or other tools
  2. Visit http://< Internet IP Address >/phpMyAdmin,login in to the phpMyAdmin Panel
  3. Select your database,then Export it
  4. Click “go” button for backup process,and then download the SQL backup file

Before upgrade you should put the site down for maintenance and always Backup your code, data and config files.

  1. Go to ProcessMaker SourceForge page and download the processmaker-3.x.tar.gz file.
  2. Decompress the processmaker-3.2.x.tar.gz file, overwriting the existing processmaker directory
    Warning: DO NOT delete the old processmaker directory and then copy the new processmaker directory into the same place, because all the essential configuration information and all the uploaded input documents and attached files from the old installation will be lost. Instead, decompress the file so it will overwrite any existing files but won’t effect any other files 
  3. Edit the MySQL configuration file, which is named my.cnf
    Make sure that the following line appears in the MySQL configuration file:

  4. Go to the ProcessMaker installation directory and run the processmaker upgrade command from the command line.
  5. Login as root (or use the sudo -i command), then run the following command:
    cd /data/wwwroot/processmaker
    ./processmaker upgrade
  6. Changing the Apache Configuration,To change the configuration, edit the pmos.conf file where the ProcessMaker Virtual
  7. Upgrade the Databases:After upgrading the ProcessMaker source code, the MySQL database(s) used by ProcessMaker need to be upgraded as well.
  8. Run the processmaker database-upgrade command from the command line with the name of the workspace included at the end. Execute the command for each workspace of the ProcessMaker installation.
    cd /data/wwwroot/processmaker
    ./processmaker database-upgrade workflow
  9. Run the processmaker flush-cache database command from the command line with the name of the workspace included at the end. Execute the command for each workspace of the ProcessMaker installation.
    cd /data/wwwroot/processmaker
    ./processmaker flush-cache 
  10. Migrating the List of Cases:To move these cases to their corresponding tables, execute the processmaker migrate-new-cases-lists command. Then, execute the processmaker database-generate-self-service-by-value command to move the unassigned cases to a separate table in the database.
    cd /data/wwwroot/processmaker
    ./processmaker migrate-new-cases-lists
    ./processmaker database-generate-self-service-by-value 
  11. After the upgrading process, copy the main env.ini file that is located in the following file path by default:

    And paste it inside each workspace’s folder at:


The upgrade solution is from:

ProcessMaker 3.2 is available by default in English, but translation files for additional languages can be installed.

Read more:

Websoft9 Mantis Image have installed the phpMyadmin

Following is the step for access phpMyadmin

  1. Open Chrome or Firefox on your local PC
  2. visit the http://Internet IP Address/phpMyAdmin,you can enter the login page
  3. select you language,Username:root,Password:123456
  4. Click the button “Go”

You can use the command to manage the services for Server.Please choose the corresponding command mode according to different types of operating system

Ubuntu Linux

Apache http service

~# systemctl start httpd
~# systemctl stop httpd
~# systemctl restart httpd
~# systemctl reload apache2 #Configuration file

MySQL  service

~# systemctl start mysqld
~# systemctl stop mysqld
~# systemctl restart mysqld


~# a2dismod ModuleName  #disable Apache2 module
~# a2enmod ModuleName    #enable Apache2 module
~# a2ensite Configuration      #enable vhost configuration
~# a2dissiteConfiguration      #disable vhost configuration

When install new extension from back-end it will not successful,may be the permissions of file and folder is not appropriate,you should change it

Web site root permissions to follow:
file 644,folder 755 ,Permissions Users and groups www-data
If there is a file permissions problem, execute the following three commands:

chown -R www-data.www-data /data/wwwroot/processmaker
find /data/wwwroot/default/processmaker -type d -exec chmod 755 {} \;
find /data/wwwroot/default/processmaker -type f -exec chmod 644 {} \;

Modify the /etc/php/7.0/apache2/php.ini file to increase the allowed size for uploads:

; Maximum size of POST data that PHP will accept.
post_max_size = 16M
; Maximum allowed size for uploaded files.
upload_max_filesize = 16M

then,restart the apache

# systemctl restart httpd

The PHP configuration file allows you to configure the modules enabled, the email settings or the size of the upload files. It is located at /etc/php/7.0/apache2/php.ini.

There are some PHP settings that need to be sufficient to install.

e.g The values for PHP.ini below are suggested values only.

  • memory_limit – Minimum: 256M Recommended: 1G or better
  • upload_max_filesize – Minimum: 20M
  • post_max_size – Minimum: 20M
  • max_execution_time: At Least 120 Recommended: 300

After modifying the PHP configuration file, restart both Apache and PHP-FPM for the changes to take effect:

# systemctl restart httpd

If you receive the message “Maximum execution time of 30 seconds exceeded”.You may also like to extend the max_execution_time for PHP and you can modify it by two methods below

Method one: edit your /etc/php/7.0/apache2/php.ini

; Maximum execution time of each script, in seconds
; Note: This directive is hardcoded to 0 for the CLI SAPI
max_execution_time = 90
; Maximum amount of time each script may spend parsing request data. It's a good
; idea to limit this time on productions servers in order to eliminate unexpectedly
; long running scripts.

After modifying the PHP configuration file, restart both Apache and PHP-FPM for the changes to take effect:

# systemctl restart httpd

Method two: edit your .htaccess:

<IfModule mod_php5.c>
php_value max_execution_time 90