Contents: [hide]

Overview

Each ProcessMaker workspace utilizes one MySQL database to store internal information about processes, user permissions and reports. Nonetheless, ProcessMaker can also be configured to connect to external databases, allowing an organization to integrate ProcessMaker with other DBMS and business applications which utilize databases.

ProcessMaker can establish database connections to MySQL, PostgreSQL, SQL Server/Sybase and Oracle database. By default, it is only possible to connect to MySQL databases, but the other types of database can be used if the server running ProcessMaker has the client drivers installed and the PHP modules for those databases. See the PostgreSQL, SQL Server/Sybase and Oracle documentation to enable database connections.

If needing to connect to another type of database, it is possible to use PHP's Open Database Connectivity (OBDC) functions in a trigger to connect to that database. See Other Types of Databases.

ProcessMaker automatically detects which database modules for PHP are installed on the server. For example, if the php-pgsql module is installed on the ProcessMaker server, ProcessMaker will offer the option to connect to PostgreSQL databases.

Creating a New Database Connection

To create a new database connection, open the project in which the connection will be used. Then go to right side of the screen where the main toolbox is located. Click on the + icon next to the Database Connections option.

A dialog box will open to define a new database connection:

1. Test Connection. Click on this button to test the connection to the database.

2. Cancel. Click on this button to cancel the creation of a new database connection.

3. Engine. Select the type of database software: MySQL, PostgreSQL, SQL Server or Oracle. Note that ProcessMaker will only offer databases in the dropdown list which have PHP modules installed on the server running ProcessMaker. If using a Sybase database, select SQL Server. If consulting one of the internal ProcessMaker databases, select MySQL.

4. Encode. If using a MySQL or PostgreSQL database, then this field will appear to select the character encoding used in the external database. If consulting one of the internal ProcessMaker databases, select "utf8".

5. Server. Required field. Enter the IP address or domain name where the database source is installed. If the database is located on the same server as ProcessMaker, then enter: 127.0.0.1

6. Database Name. Required field. Enter the name of the database to be consulted. Database names generally aren't case sensitive.

7. Username. Required field. Enter the username to log into the external database.

8. Password. Enter the password (if necessary) to log into the external database.

9. Port. Required field. Enter the port number used by the external database. By default, it is set to 3306 for MySQL, 5432 for PostgreSQL, 1521 for Oracle, and 1433 for SQL Server.

10. Description. Enter a brief description about the database connection.

After filling out the information to connect to an external database, click on "Test Connection" (1 in the figure above). If ProcessMaker can successfully connect to the external database, all testing criteria will be checked:

Click on "Back" (2) to return to the previous window. To save the database connection, click on "Save" (1 in the figure below) and it will be added to the list of existing database connections. A flash message will appear at the top of the window indicating that the connection was saved successfully.

If the connection was unsuccessful, any criteria not fulfilled will be marked with X. For example:

Managing the Database Connections

To manage the database connections inside a project, click on the "Database Connections" option inside the main toolbox

A dialog box will open with a list of the existing database connections and their details:

1. Show ID. Click on this button to display the unique ID for the database connection, which is a 32 hexadecimal number used by ProcessMaker to identify the connection. This number is needed if using the executeQuery() function in a trigger.

2. Type. Shows the database engine used for the connection.

3. Server. Shows the IP address or domain name of the server where the external database is located.

4. Database name. Shows the name of the external database.

5. Description. Displays the description of the connection next to the Database name.

6. Edit. Click to edit the database connection.

7. Delete. Click to delete the connection. A message will appear to confirm the deletion:

Click "Yes" to close the window and return to the list of databases; or click "No" to delete the connection, which will show a flash message confirming the deletion at the top of the window.

8. Pagination control. Use this control to navigate through the pages, which shows 10 connections per page.

9. Search field. Enter text to search among the databases connections.

10. Create. Click to create a new database connection.

MySQL

All the necessary modules should already be installed in order to use an external MySQL database, since those same modules are needed to use the internal databases used by ProcessMaker.

By default, MySQL servers are set up to only receive local connections from the localhost. If ProcessMaker is trying to connect to a MySQL server on another machine, then that server will have to be configured to allow external connections. Edit the my.cnf file of the MySQL server and comment out the line:

# bind-address = 127.0.0.1

Then reload or restart the MySQL server. To check whether MySQL is listening for external connections, in Windows issue the command:

netstat -an

You should see a line such as:

TCP 127.0.0.1:3306 0.0.0.0:0 LISTENING

In Linux/UNIX, use the command:

netstat -tanp

You should see a line such as:

tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 2270/mysqld

When setting up a Database Connection to an external MySQL database, it is necessary to select the character encoding, such as Latin-1 and UTF-8. To find out the character encoding used by a MySQL database, log into MySQL and change to the database and issue the status command:

mysql -u root -p mysql> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | example_db | +--------------------+ 3 rows in set (0.00 sec) mysql> use example_db; Database changed mysql> status; -------------- mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using readline 5.2 Connection id: 6054 Current database: example_db Current user: root@localhost SSL: Not in use Current pager: stdout Using outfile: Using delimiter: ; Server version: 5.0.51a-24 (Debian) Protocol version: 10 Connection: Localhost via UNIX socket Server characterset: latin1 Db characterset: utf8 Client characterset: latin1 Conn. characterset: latin1 UNIX socket: /var/run/mysqld/mysqld.sock Uptime: 12 days 3 hours 51 min 33 sec

Look for the "client characterset", which is the character set in which ProcessMaker will send queries to the MySQL database. The "Conn. characterset" which is the character set where MySQL will send information back to ProcessMaker.

In the configuration of ProcessMaker's Database Connection, set Encode to the character set used by "Client characterset and "Conn. characterset". ProcessMaker expects the Client and Connection character set to be the same. If they aren't the same, change them to be the same. You can change them temporarily with:

SET NAMES <character-set>;

To change them permanently, add the following lines to my.cnf:

character_set_client = <character-set> character_set_results = <character-set> character_set_connection = <character-set>

Then reload or restart the MySQL server.

PostgreSQL

In order for ProcessMaker to connect to a PostgreSQL database, the PostgreSQL client software and the PHP module "pgsql" have to be installed on the same machine as the ProcessMaker server. If the PostgreSQL database does not use the UTF-8 character set and it contains non-ASCII characters, then see this bug.

If the PostgreSQL database is located on a different server than the ProcessMaker server, remember to configure PostgreSQL to allow for connections from the ProcessMaker server.

Windows

Download the pgInstaller for Windows and install the PostgreSQL client software (and the server as well if you plan on running the PostgreSQL server from the same machine as the ProcessMaker server).

Then go to the directory where you installed PHP and verify that you have the dynamic link libraries php_pgsql.dll and php_pdo_pgsql.dll located in the ext directory. If you used the ProcessMaker Windows Installer, these files can be found at: C:\Program Files\ProcessMaker\php\ext\

Then enable PHP's PostgreSQL modules by opening the PHP configuration file php.ini with a plain text editor. If you used the ProcessMaker Windows Installer, it will be located at: <INSTALL-DIRECTORY>\php\php.ini

Look for the "Windows Extensions" section and uncomment the PostgreSQL modules by removing the semicolon (;) from the beginning of the following lines:

extension=php_pdo_pgsql.dll extension=php_pgsql.dll

Then restart the Apache server to use the new PHP configuration, by either rebooting or by going to the command line (located at Start > All Programs > Accessories > Command Prompt) and issuing the command:

httpd -k restart

To verify that PHP is now using the PostgreSQL modules, create a file named info.php with a bare text editor containing:

<?php
   phpinfo();
?>

and save it to your workflow\public_html\ directory, which generally will be found at: C:\Program Files\ProcessMaker\apps\processmaker\htdocs\workflow\public_html\

Then, open your web browser and direct it to http://localhost/info.php to verify that the pdo_pgsql and pgsql extensions are enabled in PHP.

Then, open ProcessMaker and go to Processes. Open a process and go to DATABASE CONNECTIONS and click on the New link. PostgreSQL should now be an available option under the Engine dropdown box.

GNU/Linux or UNIX

It is best to install the PostgreSQL client and PostgreSQL's PHP module using the repositories of your distribution.

Red Hat/Cent OS/Fedora:
Login as root and issue the commands:

yum install postgresql php-pgsql /etc/init.d/httpd restart

Debian/Ubuntu:
Login as root and issue the commands:

su or sudo -s apt-get install postgresql-client php5-pgsql /etc/init.d/apache2 restart

SUSE/openSUSE:
Login as root and issue the commands:

su or sudo -s zypper install postgresql php5-pgsql rcapache2 restart

After installing, verify that the pgsql and pdo_pgsql modules are enabled in PHP with the command:

php -m

Then, open ProcessMaker in a web browser. Go to PROCESSES and open a process. Then, go to DATABASE CONNECTIONS and click on the New link. PostgreSQL should now be an available option in the Engine dropdown box.

Microsoft SQL Server

To connect ProcessMaker to SQL Server databases, follow the instructions according to your environment:

Windows

To connect ProcessMaker to a remote or local MSSQL installation on a Windows server, follow the steps below:

1. Download the php_dblib.dll freeTDS dll taking into account your system's architecture and PHP version.
For instance, ProcessMaker 3.0.1.8 (current latest version) works with PHP 5.5 Thread Safe, therefore, depending on the system architecture (X86 or x64), download one of the marked options.

2. Place the php_dblib.dll file into the /PHP/ext directory (depending on the installation) located at:

Bitnami Installation:
<INSTALLATION-DIRECTORY>/Bitnami/processmaker-3.0.1.8-0/php/ext

Self-Installer Installation:
<INSTALLATION-DIRECTORY>/Users/USERNAME/AppData/Roaming/ProcessMaker-3_X_X_X/php/ext

3. Then, open the php.ini file located at:

Bitnami Installation:
<INSTALLATION-DIRECTORY>/Bitnami/processmaker-3.0.1.8-0/php

Self-Installer Installation:
<INSTALLATION-DIRECTORY>/Users/USERNAME/AppData/Roaming/ProcessMaker-3_X_X_X/php

To enable the mssql extension, add the following line under the "Dynamic Extensions" section:

extension=php_dblib.dll

Next, restart the Apache server to use the new PHP configuration. This can be done in several ways:

  1. Using the Microsoft Windows Services console: Open a command line (Start > All Programs > Accessories > Command Prompt) and type:

    services.msc

    The Services console will open, search for the service processmakerApache and click on the "Restart" option.

    The Service Control will restart the Apache service.

  2. Using the Bitnami ProcessMaker Stack Manager Tool: (Only if ProcessMaker was installed with the Bitnami installer) Open the manager tool by going to Start > All Programs > Bitnami ProcessMaker > and select Bitnami ProcessMaker Stack Manager Tool. Go to the Manage Servers tab, select Apache Web Server and click on the "Restart" button.

  3. Using only the Command Prompt: Open a command line (Start > All Programs > Accessories > Command Prompt) and go to the Apache directory inside the ProcessMaker folder. For instance, for a Bitnami Installation on the C: disk, the directory will be:

    cd c:\Bitnami\processmaker-3.0.1.8-0\apache2\bin

    The Apache service created during the ProcessMaker installation is named "processmakerApache". Therefore, execute the following command (that includes the name of the service) to restart the Apache service.

    httpd -n processmakerApache -k restart

Finally, log into ProcessMaker and open a process. Go to Database Connections and click on the New link. The option Microsoft SQL Server should now be available under the Engine dropdown box.

Fill the rest of the fields according to the description in the Creating a New Database Connection section.

Finally, click on the "Test Connection" option. If the configuration is correct, all marks will turn green in the "Testing Server Connection" dialog.

If a problem occurs, see the Possible Configuration Issues section.

Possible Configuration Issues

Microsoft SQL Server Option is Missing

If for some reason the SQL Server option does not appear in the list of Database Connections, verify that PHP is now using the mssql extension. Login into ProcessMaker and select the Admin tab. Click the PHP Information option under "Settings" and scroll down searching for the mssql extension section that is usually between the "myhash" and "mysql" sections.

If the section is missing, restart the server system to apply the recent changes.

Destination Port Unreachable

If the "Test Connection" option is clicked, the following dialog displays:

Verify that the MSSQL remote server is allowing remote connections. Open the SQL Server Configuration Management, click on SQL Server Configuration Manager, go to Protocols for SQLExpress and make sure the TCP/IP is enabled. The TCP/IP option allows other computers to connect with MSSQL through IP. If not, right click on it and choose Enable.

Check if the port is the correct one by right-clicking on TCP/IP and selecting Properties. In the "TCP/IP Properties" dialog, select the IP Addresses tab and scroll down to IPAII. Make sure TCP Dynamic Ports is blank and that TCP Port is set to 1433.

Last, ensure that the SQL Server is running under the Network Service mode by going to SQL Server Services. Right-click on SQL Server and select "Properties".

On the properties dialog, check if the option "Built in account" is in Network Service mode.

Changes won't take effect until the SQLExpress service is restarted.

If there is still a problem, make sure the TCP port 1433 is not blocked by the firewall.

MS-SQL Connection Refused

If the "Test Connection" option is clicked, the following dialog displays:

Notice that MSSQL has two methods of authentication: Windows Authentication and SQL Server Authentication. ProcessMaker uses the SQL Server Authentication method to establish a connection.

Therefore, the user must choose the login method. If unsure, open the SQL Server Management Studio, right-click on Security, select Login and look for the user specified in the connection.

Right-click on the user and choose "Properties". Verify that the credentials provided are the right ones in the "Login Properties" dialog.

After that, verify the user settings by going to Status. Check if the option "Permission to connect to database engine" is Grant and if "Login" is Enabled.

Database Does Not Exist

If the "Test Connection" option is clicked, the following dialog displays:

Verify that the user specified is the owner or has permission to access the database. To verify this, open the SQL Server Management Studio, right-click on the database and choose "Properties".

On the Database Properties dialog, check if the specified user is the owner of the database.

Linux/UNIX

ProcessMaker servers running on Linux/UNIX can access Microsoft SQL Server or Sybase databases by installing FreeTDS. Most distributions provide FreeTDS and a PHP extension for SQL Server or Sybase. If your distribution doesn't provide a package for FreeTDS, see these instructions to compile FreeTDS from the source code.

If planning on executing stored procedures on the SQL Server database, edit the FreeTDS configuration file, which is generally found at /etc/freetds/freetds.conf

Edit the following lines to specify the IP address and port of server where SQL Server is installed and the TDS version number:

host = xxx.xxx.xxx.xxx port = 1433 tds version = 8.0

Red Hat/CentOS/Fedora

Install FreeTDS and the php-mssql package using yum:

yum install freetds php54w-mssql

Then, edit the /etc/php.ini file to enable the mssql extension:

extension=mssql.so Note that if using CentOS version 6.0 or later, follow RHEL/Centos version 6.0 instructions

Finally, restart Apache:

/etc/init.d/httpd restart

The Microsoft SQL Server will be added in the list of Database Connections:

For older versions of Red Hat/CentOS which don't contain a php-mssql package, see these instructions to manually compile FreeTDS and PHP's mssql extension.

Debian/Ubuntu

If using Debian 6 (Squeeze) or Ubuntu 9.10 (Karmic Koala) or later, login as root (or use sudo) to install FreeTDS and the php5-sybase package (which will work for MS SQL Server as well). Then, restart apache:

apt-get install freetds-bin php5-sybase /etc/init.d/apache2 restart

If using Debian 5 (Lenny), install the freetds-common package instead:

apt-get install freetds-common php5-sybase /etc/init.d/apache2 restart

For older versions of Debian and Ubuntu, compile FreeTDS from source.

SUSE/openSUSE

SUSE/openSUSE does not provide a PHP package to access MS SQL Servers, so freeTDS and the mssql PHP extension will have to be compiled from source.

First, install the unixOBDC package and the tools for compiling:

zypper install unixOBDC gcc make

Then, download the source code for the latest stable version of freeTDS. Decompress the code and configure and compile it:

tar xzf freetds-stable.tgz cd freetds-0.82/ ./configure -with-unixODBC=/usr/lib make make install

Install the php5-devel package (which contains the phpize command):

zypper install php5-devel

Next, check which version of PHP you are using:

php -i

Then, download the source code for your version of PHP to a local directory. Decompress the code, switch to the ext/mssql directory and compile the mssql extension. Note that the following commands will only compile the mssql extension and insert it into your existing installation of PHP without altering anything else:

tar xzf php-5.3.3.tar.gz cd php-5.3.3/ext/mssql phpize ./configure make make install

Then, configure PHP to use the new extension by editing the PHP configuration files:

vi /etc/php5/apache2/php.ini vi /etc/php5/cli/php.ini

In both files, add the line:

extension=mssql.so

Finally, restart Apache to be able to use the new mssql.so extension:

rcapache2 restart

If the SQL Server Database Does Not Use UTF-8 Encoding

Some issues might arise if the SQL Server database does not use the UTF-8 character set and it contains non-ASCII characters, because ProcessMaker is designed to use UTF-8. This means:

The source code of PM is written in UTF-8 and produces UTF-8 HTML pages.
  • The source code of PM is written in UTF-8, and produces UTF-8 HTML pages.
  • The character set for the Apache server needs to be in UTF-8.
  • The AJAX requests using JSON encode are in UTF-8.
  • The collation in MySQL for ProcessMaker databases is in UTF-8.

In other words, these four components need to be in UTF-8 for everything to work: source code, Apache server, interactive data and database fields.

Solving Issues with UTF-8 Characters

To display Unicode data from SQL server, it is recommended to:

Setup FREETDS in Linux/UNIX

To avoid permissions problems with the freetds.conf file, it is recommended to give the freetds.conf file world read permissions. For example:

chmod +r /etc/freetds/freetds.conf

Make the environment variable FREETDSCONF point to the location of the freetds.conf file. At the beginning of the Apache service script (which is located at /etc/init.d/httpd in Red Hat/Cent OS/Fedora and at /etc/init.d/apache2 in Debian/Ubuntu/SuSE), add the following line:

export FREETDSCONF=/etc/freetds/freetds.conf

Finally, in the global section of the freetds.conf file, change the following lines to:

tds version = 7.0 client charset = UTF-8

Note: The TDS Version may change according to the version of the database engine with which the server is trying to communicate. For more information, please visit the freetds guide page.

Change MSSQLResultSet.php

Once freetds is getting all data in UTF-8, the code is no longer needed to convert all fields to UTF-8. Remove the lines 123-133 from the MSSQLResultSet.php file, which is located at:

/gulliver/thirdparty/creole/drivers/mssql/MSSQLResultSet.php

Collation Database Configuration

Usually when trying to execute queries that contain the character ñ, an error will occur. If searching in fields, the result will be NULL.

The problem is that the database collation in ProcessMaker is configured with UTF-8. To make that work, data must be transformed using PHP's mb_convert_encoding() function to convert from the character set used by the SQL Server database to UTF-8. If converting from ISO-8859-1, which is the most commonly used character set in Windows, the utf8_encode() and utf8_decode() functions can be used.

For example, the following trigger code converts from UTF-8 to ISO-8859-1 to send queries to an SQL Server database and then it converts the search results from ISO-8859-1 to UTF-8, so the results can be displayed in a grid field in ProcessMaker:

$idMssql  = '11609821854ca4355344560009542371'; //change UID for database connection to SQL Server
$group = utf8_decode(@@SelectedGroup);        //convert from UTF-8 to ISO-8859-1
$rows = executeQuery("SELECT FIRST_NAME + ' ' + LAST_NAME from TABLE_EMPLOYEES
   where GROUP = '$group' and COMPANY in ('5','4','3','1')"
, $idMssql);
 
//place search results in a grid field named "EmployeesGrid" which has the rows firstName and lastName,
//which will be displayed in a subsequent DynaForm:
@=EmployeesGrid = array();
for ($i = 1; $i <= count($rows); $i++) {
   //use utf8_encode() to convert from ISO-8859-1 to UTF-8:
   @=EmployeesGrid[$i] = array(
      'firstName' => utf8_encode($rows[$i]['FIRST_NAME']),
      'lastName' => utf8_encode($rows[$i]['LAST_NAME'])
   );
}

Oracle

In order to connect to an Oracle database, Oracle's client software must be installed on the same server running ProcessMaker. If the Oracle database does not use the UTF-8 character set and it contains non-ASCII characters, then see this bug.

Note: If using Oracle Instant Client to connect to an Oracle database, make sure to use the same version of Instant Client as the Oracle Database. The following SQL command can be used to find the version of the database: SELECT version FROM V$INSTANCE

Cent OS

Note: This database connection has been tested only with Oracle v. 12.c in CentOS installations.

Oracle provides instructions and RPM packages to install its Instant Client in Linux, which can be downloaded for free at:

http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html

If ProcessMaker is running on a 32 bit system, download Instant Client for Linux x86. For a 64 bit system, download Instant Client for Linux x86-64. For an AMD system, download Instant Client for Linux AMD64 (32-bit and 64-bit). Make sure to download the version of Instant Client Basic or Basic-Lite which matches your version of Oracle. It is also recommended to download the SQL*Plus and SDK packages, but it is not necessary.

Then follow the steps below to install and configure Instant Client in Linux, depending upon whether using a Red Hat or a Debian based system.

Install Instant Client

Open a terminal in the server where ProcessMaker is installed and login as root (or use the sudo) in order to install the following packages needed by Oracle Instant Client:

yum install php-pear php-devel zlib zlib-devel bc libaio glibc yum groupinstall "Development Tools"

Copy the Oracle Instant Client package files to the current directory and then issue the following command to install them:

rpm -ivh oracle-instantclient*

If using a 64 bit version of Instant Client, then create symbolic links so the Instant Client can be found:

ln -s /usr/include/oracle/11.2/client64 /usr/include/oracle/11.2/client ln -s /usr/lib/oracle/11.2/client64 /usr/lib/oracle/11.2/client

(Make sure to change 11.2 to match your version of Instant Client.)

Then set the LD_LIBRARY_PATH variable to indicate where the Instant Client library is located. For a 64 bit system, issue the following command

echo "export LD_LIBRARY_PATH=/usr/lib/oracle/11.2/client64/lib" > /etc/profile.d/oracle.sh

For a 32 bit system:

echo "export LD_LIBRARY_PATH=/usr/lib/oracle/11.2/client/lib" > /etc/profile.d/oracle.sh

(Make sure to change 11.2 to match your version of Instant Client.)

Then also set the LD_LIBRARY_PATH for the current session:

source /etc/profile.d/oracle.sh

Install PDO_OCI

Download the PDO_OCI-1.0.tgz file and decompress it with the following commands:

wget http://wiki.processmaker.com/sites/default/files/PDO_OCI-1.0.tgz tar -xzvf PDO_OCI-1.0.tgz

Then, configure PHP to use PDO_OCI:

cd PDO_OCI-1.0 phpize ./configure --with-pdo-oci=instantclient,/usr,11.2

Make sure to change 11.2 to match your version of Instant Client. Then compile and install the PDO_OCI module:

make make install cd ..

Then, include the module in PHP and restart Apache so the module can be used:

echo "extension=pdo_oci.so" > /etc/php.d/pdo_oci.ini service httpd restart

Finally, check whether the PDO_OCI module was installed and included in PHP:

php -i | grep oci

The following line should appear in the output:

PDO drivers => oci, mysql

Install OCI8

Use the pear command to download the OCI8 source code and then decompress it:

pear download pecl/oci8 tar -xvf oci8-1.4.9.tgz

(Change 1.4.9 to the version of OCI8 which was downloaded by pear.) Then, configure how the code will be compiled:

cd oci8-1.4.9 phpize ./configure --with-oci8=shared,instantclient,/usr/lib/oracle/11.2/client64/lib

(Change 11.2 to your version of Instant Client. For 32 bit systems, remove 64.)

Then, compile and install:

make make install

Then, include OCI8 in PHP and restart Apache to be able to use the new module:

echo "extension=oci8.so" >> /etc/php.d/oci8.ini service httpd restart

Finally, check whether it was installed and included correctly:

php -i | grep oci8

The output should include lines like the following:

/etc/php.d/oci8.ini, oci8 oci8.connection_class => no value => no value oci8.default_prefetch => 100 => 100 oci8.events => Off => Off oci8.max_persistent => -1 => -1

Checking the Oracle installation

After installing an Oracle client and the OCI8 and PDO_OCI extensions in PHP, then login to ProcessMaker and go to the DESIGNER menu and open process for editing. Click on the Database Connections tab and create a new connection. In the Engine dropdown box, there should be an Oracle option:

Oracle Troubleshooting

Check the Apache error log file for startup errors.

Temporarily set display_error=On in php.ini so script errors are displayed. Switch it back off when finished for security reasons.

Chapter 9 of The Underground PHP and Oracle Manual contains information about common connection errors and discusses alternative ways to set environment variables.

Oracle's SQL*Plus command line tool can be downloaded from the [www.oracle.com/technetwork/database/features/instant-client/index-100365.html Instant Client] page to help resolve environment and connection problems. Check whether SQL*Plus can connect and then ensure the Environment section (not the Apache Environment section) of phpinfo.php shows the equivalent environment settings.

The following testoci8.php script can be used to check whether the OCI8 extension works with Oracle. Create the testoci8.php file at the location <install-directory>/workflow/public_html/testoci8.php with the following contents:

<?php
//change the username, password, machine, domain and address:
$conn = oci_connect('username', 'password', 'mymachine.mydomain/mydatabase');
 
$stid = oci_parse($conn, 'select table_name from user_tables');
oci_execute($stid);
echo "<table>\n";
while (($row = oci_fetch_array($stid, OCI_ASSOC+OCI_RETURN_NULLS)) != false) {
    echo "<tr>\n";
    foreach ($row as $item) {
        echo " <td>".($item !== null ? htmlentities($item, ENT_QUOTES) : "&nbsp;")."</td>\n";
    }
    echo "</tr>\n";
}
echo "</table>\n";
?>

Make sure to modify the connection credentials to suit your database. Then open a web browser and go to the address:

http://<processmaker-address>/testoci8.php

For example, if ProcessMaker is installed at the address 192.168.0.1 on port 8080, then go to:

http://192.168.0.1:8080/testoci8.php

The tables in the Oracle database should be listed on the page. Make sure to delete the testoci8.php file when done testing.

Other Types of Databases

If using another type of database that ProcessMaker does not support, then it is possible to connect to that database using PHP's database extensions inside a trigger. Many types of databases have their own specialized functions such as oci_connect() or mysql_connect(), but almost all databases and spreadsheets also support the Open Database Connectivity (ODBC) protocol.

Unfortunately, database connections created in triggers can not be used like normal Database Connections in ProcessMaker. In order to be queried like a normal database, using the SQL Connection and SQL properties in DynaForm fields, first the results of the database query will have to be stored as an associative array of associative arrays in the $_SESSION superglobal variable, so they can be accessed by DynaForm fields.

ODBC

The specialized PHP functions for each type of database are generally easier to use, but PHP's ODBC functions offer a standardized way to connect to any data source.

Installing ODBC

Before trying to use ODBC in PHP, make sure that the odbc module is installed in PHP, by going to the command line and issuing the command:

php -m

If "odbc" doesn't appear in the list of modules, then it will need to be installed:

Debian/Ubuntu:

apt-get install unixodbc php5-odbc

Red Hat/CentOS/Fedora:

yum install unixODBC unixODBC-devel php-odbc

SUSE/OpenSUSE:

yast2 -i php5-odbc

Windows:
The ODBC module should be installed by default in PHP.

Using ODBC in Triggers

First, establish a connection to the database with obdc_connect() (or obdc_pconnect() for a persistent connection):

resource odbc_connect( string $dsn, string $user, string $password [, int $cursor_type])

The first parameter is the data source name, which contains the custom parameters needed to connect to different types of databases. It might contain something like:

"Driver={DRIVER-NAME};Server=SERVER-URL;Database=DB-NAME;"

but it varies widely. See this list of connection strings.

Populating a Textbox

To set the value of a DynaForm textbox, fire the trigger before the DynaForm which queries the database using ODBC and then sets the value of the case variable for the textbox.

For example, to query a Visual FoxPro database and set the value of a textbox named "ClientName":

$dns = "Driver={Microsoft Visual FoxPro Driver};SourceType=DBC;SourceDB=c:\somepath\contacts.dbc;Exclusive=No";
$con = obdc_connect($dns, "", "");
if ($con !== false) {
   $res = odbc_exec($con, "SELECT FIRSTNAME, LASTNAME FROM CLIENTS WHERE CLIENT_ID='ARG29'");
   if ($row = odbc_fetch_array($res))
      @@ClientName = $row['FIRSTNAME'] . ' ' . $row['LASTNAME'];
}

Populating a Grid

To populate a DynaForm grid, create an associative array of associative arrays and assign it to the case variable for the grid. The keys in the associative arrays must be the same as the names of the grid fields, so use AS in the SQL query to rename the fields from the table if they don't match the field names in the grid.

For example, this trigger uses OBDC to connect to an Access database and populate a DynaForm grid named "ProductsGrid" which has the fields "serialNo", "productTitle", "description" and "listPrice":

$dns = "Driver={Microsoft Access Driver (*.mdb)};Dbq=c:\somepath\Products.mbd";
$con = obdc_connect($dns, "someuser", "p4sSw0rd");
if ($con !== false) {
   $aProducts = array();
   $cnt = 1;
   $sql = "SELECT SERIAL AS serialNo, TITLE AS productTitle, DESC AS description,
      PRICE AS listPrice FROM PRODUCTS WHERE CATEGORY='current'"
;
   $res = odbc_exec($con, $sql);
 
   while ($row = (odbc_fetch_array($res)))
      $aProducts[$cnt++] = $row;
 
   @@ProductsGrid = $aProducts;
}
else {
   G::SendMessageText("Unable to connect to Access database!", "ERROR");
}

Discovering Ports and Debugging

If unsure which port number is being used by a database, use the nmap command to discover the port. This program is installed by default on most Linux/UNIX distributions, but it needs to be installed in Windows.

If the database is located on the same machine as the ProcessMaker server, issue the command:

nmap localhost

If the database is on another server, enter the domain name or IP address where it is located. For example:

nmap 192.168.1.229

nmap will list the ports which are currently being used by the server. If the database service is activated and it's port isn't blocked by a firewall, then a port number should be listed for the database:

Starting Nmap 6.00 ( http://nmap.org ) at 2015-02-05 12:03 BOT Nmap scan report for no-name-229.colosa.net (192.168.1.229) Host is up (0.0094s latency). Not shown: 990 closed ports PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 80/tcp open http 111/tcp open rpcbind 389/tcp open ldap 631/tcp open ipp 1521/tcp open oracle 3306/tcp open mysql

If a port number isn't listed for the database, then go to the server where the database is installed and make sure that it is being run as a service:

MySQL:

Red Hat/Cent OS/Fedora:

Login as root (or use sudo) and issue the command:

# service mysqld status mysqld (pid 1703) is running...

To see a list of all services:

service --status-all

Debian/Ubuntu:

Login as root (or use sudo) and issue the command:

# service mysql status Server version 5.5.41-0+wheezy1 Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 3 days 1 hour 59 min 33 sec Threads: 1 Questions: 19041 Slow queries: 0 Opens: 716 Flush tables: 1 Open tables: 205 Queries per second avg: 0.071.

To see a list of all services:

service --status-all

Windows:

Open the command prompt (go to Start > Run and enter: cmd) and enter the following command to see a list of all running services:

net start

To see the status of MySQL:

sc query mysql-service-name

For example, to see the status of MySQL installed by the automatic ProcessMaker Installer:

C:\> sc query ProcessMakerMysql SERVICE_NAME: ProcessMakerMysql TYPE : 10 WIN32_OWN_PROCESS STATE : 4 RUNNING (STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0

PostgreSQL:

Red Hat/Cent OS/Fedora:

Login as root (or use sudo) and issue the command:

# service postgresql status postmaster (pid 3498) is running...

For recent versions, it may be necessary to specify the version number:

# service postgresql-9.4 status postmaster (pid 3498) is running...

To see a list of all services:

service --status-all

Debian/Ubuntu:

Login as root (or use sudo) and issue the command:

# service postgresql status Running clusters: 9.1/main

To see a list of all services:

service --status-all

Windows:

Open the command prompt (go to Start > Run and enter: cmd) and enter the following command to see a list of all running services:

net start

To see the status of PostgreSQL:

sc query postgresql-service-name

Oracle:

Linux/UNIX:

Oracle uses the dbstart and dbstop commands (which are located in the $ORACLE_HOME/bin directory) to start and stop the database, although a service script can be added in the /etc/init.d/ directory. Likewise, it uses the lsnrctl start and lsnrctl stop commands to start and stop the listener and isqlplusctl start and isqlplusctl stop to start and stop SQL*Plus.

To see the status of the Oracle database, use the following command (located in the $ORACLE_HOME/bin directory):

chkdb_status

Windows:

Open the command prompt (go to Start > Run and enter: cmd) and enter the following command to see a list of all running services:

net start

Oracle creates a service for its listener and for its database:

sc query OracleOraDB12Home1TNSListener sc query OracleDatabaseX

For example, to see the status of an Oracle database named "ORCL" and the listener:

C:\> sc query OracleServiceORCL SERVICE_NAME: OracleServiceORCL TYPE : 10 WIN32_OWN_PROCESS STATE : 4 RUNNING (STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0 C:\> sc query OracleOraDB12Home1TNSListener SERVICE_NAME: OracleOraDB12Home1TNSListener TYPE : 10 WIN32_OWN_PROCESS STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0

MS SQLServer:

Windows:

Open the command prompt (go to Start > Run and enter: cmd) and enter the following command to see a list of all running services:

net start

Oracle creates a service for its listener and for its database:

sc query MSSQLSERVER

For example:

C:\> sc query MSSQLSERVER SERVICE_NAME: MSSQLSERVER TYPE : 10 WIN32_OWN_PROCESS STATE : 4 RUNNING (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0