How to configure an Apache httpd server as a reverse proxy for the PASOE? - Progress Community

Loading

Skip to Main Content

How to configure an Apache httpd server as a reverse proxy for the PASOE?

This Article explains how to set up a front facing Apache Httpd server, using the mod.proxy directive so that it will act as the public facing side of an application that is using rest services via PASOE, the Progress AppServer.

Jan 31, 2017
Knowledge

Title

How to configure an Apache httpd server as a reverse proxy for the PASOE?

URL Name

How-to-configure-an-Apache-httpd-server-as-a-reverse-proxy-for-the-PASOE

Article Number

000181097

Environment

Product: OpenEdge Version: 11.6, 11.7, 12 OS: All Supported Platforms Other: Apache Httpd, mod.proxy, PASOE

Question/Problem Description

How to set up a front facing Apache Httpd server for the PASOE, using the mod.proxy directive?

How to configure an Apache httpd server as a reverse proxy for the PASOE, so that it will act as the public facing side of an application that is using rest services?

Steps to Reproduce

Clarifying Information

Apache supports an optional module (mod_proxy) that configures the web server to act as a proxy server. We will use this module to forward requests for a particular web application to the PASOE, without having to configure a web connector.

Error Message

Defect Number

Enhancement Number

Cause

Resolution

PASOE configuration

On PASOE, enable the AJP protocol from the PASOE instance directory:

{CATALINA_BASE}/bin/tcman.sh feature AJP13=on
{CATALINA_BASE}/bin/tcman.sh config psc.as.ajp13.port=50000
tcman stop
tcman start

Note that due to updates in 11.7.6, 12.2.3 , 12.3, a PASOE instance fails to start properly because the AJP13 protocol is configured by default with: secretRequired="true". The secret option is supported since Apache Module mod_proxy_ajp 2.4.42, 2.5.

PAS does not start after enabling AJP13

Apache HTTPD configuration

Install Apache 2.2x or later
Configure your Apache to include the optional mod_proxy that configures the web server to act as a proxy server and mod_proxy_ajp modules, to use the AJP protocol to to forward requests to PASOE Tomcat.

In conf/httpd.conf, enable the following modules, removing the hash (#) sign to load then at Apache startup time

Include conf/extra/httpd-vhosts.conf

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so

Note that the limitation of the AJP protocol, is it's maximum packet size, therefore mod_proxy_ajp does not support large body sizes (8186 (8 Kbytes - 6)), and the number of bytes actually left to send from the request body in the packet. Whereas mod_jk and current Tomcat versions, the packet size can be enlarged to 64K. On the other hand mod_proxy this can be used to forward requests for a particular web application to a Tomcat instance, without having to configure a web connector such as mod_jk

The following modules don't specifically need to enabled:

#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so

Setup virtual hosts

Modify the httpd-vhosts.conf to setup virtual host settings. Enclose all the apache configuration parameters for each and every virtual host between these VirtualHost tags.

The following settings illustrate a configuration for the PASOE SOAP transport instead of WSA. Adjust the configuration accordingly for the other transports:

Edit /conf/extra/httpd-vhosts.conf

# Virtual Hosts

<VirtualHost *:80>
DocumentRoot <path to http root folder>/www
ServerName localhost

<Directory "<path to http root folder>/www/">
Options +Indexes +Includes +FollowSymLinks +MultiViews
AllowOverride All
Require local
</Directory>

ProxyPass /soap ajp://[host]:8009/soap
ProxyPassReverse /soap ajp://[host]:8009/soap
</VirtualHost>

VirtualHost *:80 – Indicates that all the name-based virtual hosts will be listening on the default port 80
Replace [host] with the PAS server hostname or IP address.
Any apache directives can be used within the virtualhost container such as ServerAlias, ErrorLog, CustomLog (access_log, error_log )
For the name-based virtual host to work properly, the DNS entry for each virtual host must point to the same external ip-address of the physical server where the Apache webserver is running.

Restart the Apache and test

apache2/bin/apachectl restart

Check VirtualHost Configuration Syntax:
apache/bin/httpd -S

VirtualHost configuration:
Syntax OK

When something is not configured properly, it will display a Warning message, example:

Warning: DocumentRoot [/apache/docs/<name>] does not exist

Please note that Third-Party product support, here Apache httpd as a proxy server is not covered in the scope of our technical support:
https://community.progress.com/s/products/openedge/scope-of-support

Workaround

Notes

References to Other Documentation:

Apache Module mod_proxy_ajp
https://httpd.apache.org/docs/trunk/mod/mod_proxy_ajp.html
Apache Tomcat 9: Proxy Support How-To
https://tomcat.apache.org/tomcat-9.0-doc/proxy-howto.html
Apache Tomcat 8: Proxy Support How-To
https://tomcat.apache.org/tomcat-8.0-doc/proxy-howto.html

Progress Articles:
PAS does not start after enabling AJP13
Is it possible to configure a third-party load balancer with PASOE?

Keyword Phrase

Last Modified Date

10/2/2025 10:08 AM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

How to configure an Apache httpd server as a reverse proxy for the PASOE? - Progress Community