We now support PHP 7.3. We have compiled PHP against PostgreSQL 11.

At this time, the memcached extension is not compiling. We will enable this extension in our builds once it is updated for PHP 7.3. Please see Issue #378 for more details.

We now support Apache Maven 3.6. We package it as apache-maven_3, installed in /opt/apache-maven-3.

We also check for updates weekly, and deploy updates during our weekly update roll-outs.

We are updating all managed servers from CentOS 7.5 to CentOS 7.6 this week.

We have not experienced any compatibility issues during our packaging and testing. However, the following guides may assist you in evaluating compatibility:

• CentOS 7.6 Release Notes
• Red Hat Enterprise Linux 7.6 Release Notes

This update includes an updated kernel, so each server will be rebooted as part of the update process. As usual, we will perform these updates during your scheduled maintenance times.

Tomcat 8.0 is now end-of-life.

A supported version of Tomcat, which are currently versions 7.0, 8.5, and 9.0, must be used for any existing application.

We now support in-place Tomcat upgrades to Tomcat 8.5 and above. This capability is available in AOSH through the following commands:

• set_httpd_shared_tomcat_version (for a Multi-Site Tomcat JVM)
• set_httpd_tomcat_std_site_version (for a Standard Tomcat JVM)

After performing the upgrade, please refer to the README.txt file in either /var/opt/apache-tomcat/…/README.txt (for a Multi-Site Tomcat JVM) or /var/www/…/README.txt (for a Standard Tomcat JVM). The README.txt file includes details about the auto-backup files named *.bak along with a generated command you may use to clean-up the backup files.

For all managed servers, we are upgrading to Tomcat 8.5 unless you request otherwise. We will carefully review all *.bak files to maintain any customizations through the upgrade. Applications will be restarted, possibly more than once, during this process. We will communicate with you individually and perform these updates during your usual scheduled maintenance times.

We now support Java 11.

Java 11 may be used for any existing application by updating your profile script to include /opt/jdk-11/profile.sh. See this FAQ for more details on how to change Java versions:

https://aoindustries.com/clientarea/FAQ.ao?category=jvms&page=profile

This is a LTS version and is expected to be supported until September 2023.

In this version, we have switched to the OpenJDK builds. We are no longer using the commercial build from Oracle.

We now support Python 3.6.

Python 3.6 may be used for any existing user or application by updating your profile script to include /opt/python-3.6/profile.sh (for Bourne shells) or /opt/python-3.6/profile.csh (for C shells).

We now support Python 3.4.

Python 3.4 may be used for any existing user or application by updating your profile script to include /opt/python-3.4/profile.sh (for Bourne shells) or /opt/python-3.4/profile.csh (for C shells).

Please note that Python 3.4 End-of-life is 2019-03-16. Please consider going to Python 3.5, Python 3.6, or Python 3.7 now.

We now support Tomcat 9.0 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver 8.0.*.

We now support PHP 7.2. We have compiled PHP against PostgreSQL 10.

We now support PHP 7.0. We have compiled PHP against PostgreSQL 9.4.

We now build with mysqlnd instead of depending on MySQL native libraries.

We have removed the dbase extension from this build. If this extension is required by your application, please Contact Us.

In this build, we have made the following changes to extension versions:

1. memcached extension is now 3.*
2. propro extension is now 2.*
3. raphf extension is now 2.*
4. HTTP extension is now 3.*

Older applications may need to be updated for these extension version changes before switching to PHP 7.0.

For both efficiency and security, we have switched to a more modular build of PHP, where some of the built-in extensions are built as shared libraries, packaged as separate RPMs, and only installed and enabled as-needed on a per-Apache/per-site basis. This means some extensions that were on by default in PHP 5 are now off by default in PHP 7.

We moved the default php.ini file from /opt/php-X.Y/lib/php.ini to /etc/opt/php-X.Y/php.ini, where X and Y are the major and minor versions, respectively.

We have also enabled Scan Directories with a default of /etc/opt/php-7.0/conf.d. For mod_php, this is overridden to /etc/httpd/conf/php[@instance]/conf.d for per-Apache configuration. For CGI, this is overridden to /var/www/site_name/webapps/ROOT/cgi-bin/php.d for per-site configuration.

We now support PostgreSQL 10. We have included the following modules in our build:

1. cube - Used by the earthdistance module.
2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.

We now support PostgreSQL 9.5. We have included the following modules in our build:

1. cube - Used by the earthdistance module.
2. earthdistance - Allows spatial indexing of geographical coordinates - (latitude, longitude) pairs.
3. tsearch2 - Backwards compatibility for applications developed for versions of PostgreSQL prior to 8.3.

Separated our set of reusable servlet filters into their own project. Please see the new ao-servlet-filter project at Downloads.

We now support PHP 5.6 in both 32-bit and 64-bit builds. We have compiled PHP against PostgreSQL 9.4 and MySQL 5.7.

In this build we have switched to the 2.* version of the HTTP extension. Older applications may need to be updated for this change before switching to PHP 5.6.

We now support Tomcat 8.0 in both single-site and multi-site configurations. We have included the latest PostgreSQL JDBC Driver built for Java 8. We have also included the latest MySQL JDBC Driver.

We are now using Stripe for our credit card processing. Sage Payments has served us well over the years and may remain a good option for some merchants, but we are attracted to the more predictable fee structure of Stripe.