Article No.3334IIS / TomcatIIS as the reverse proxy server with Intrexx 19.03
Description :
1) IIS preparations
1.1) IIS installation
1.2) Additional modules for the IIS web server
1.3) ARR module configuration
2) IIS configuration
3) Intrexx configuration
3.1) Web connector
3.2) Frontend web server
3.3) HTTPS
Solution :
Prepare and install IIS as the reverse proxy with Intrexx 19.03.

1) IIS preparations

To be able to use IIS with Intrexx 19.03, it needs to be prepared in advance.

1.1) Installation IIS
The shown role services need to be added when installing the IIS web server (s. iis-roles.png).

1.2) Additional modules for the IIS web server
In addition, IIS requires the ARR module (Application Request Routing) as the URL Rewrite Module to be used as a reverse proxy. To be able to install the modules, you need to install the IIS Web Platform Installer (WebPI 5.0 or higher) first. You can download this here ( Once the installation is completed, the IIS Manager needs to be restarted for the Web Platform Installer to appear (s. iis.web.png). The two modules required can be installed in the Web Platform Installer. Search for "routing" and install the module "Application Request Routing 3.0". This installs both the ARR module and the URL Rewrite Module (s. iis-arr-1.png).

1.3) ARR module configuration
To configure the ARR module, select the module at the server level and then select “Server Proxy Settings”. Activate the setting "Enable proxy". In addition, the option "Reverse rewrite host in response headers" needs to be deactivated (s. iis-arr-2.png).

2) IIS configuration

To be able to use IIS with Intrexx 19.03, an own site needs to be created in IIS for each portal. A configuration via virtual directories is no longer fully supported as of Intrexx 19.03 and therefore, cannot be recommended.

To create an own site in IIS, select the “Add website” option in the IIS Manager. Apply the following settings in the dialog that opens (s. iis-site.png):

Site name: Provide the site with a name – this is only for identification purposes.
Physical path: We recommend entering the “IIS wwwroot” (C:\inetpub\wwwroot) directory to begin with to test the connection to the host name. This can be changed to the correct directory later with the help of the Portal Manager. Alternatively, you can enter the portal directory at this point (<portal>\external\htmlroot\).
Binding: Select the preferred type (http/https) as well as the IP address and port.
Host name: Specify the host name used to access the portal in the browser (e.g. Please note that your DNS server needs to forward the request to the Intrexx server (web server). A corresponding DNS entry is required for this (CNAME Record, A- or AAAA Record).

3) Intrexx configuration

Open the Portal Manager and select “Portal properties” from the Portal menu. The connection between IIS and Intrexx can be configured on the “Web configuration” tab.

3.1) Web connector:

Host: Specify the server and port that the portal’s Tomcat Web Connector is running under (by default, localhost and port 1337 – additional portals are given the port one higher than the previous portal). Normally, you should not need to make any changes here (s. portal1.png).

3.2) Frontend web server:

Select the required web server / reverse proxy (IIS) and the site created earlier. Make sure the “Virtual directory” field is blank (s. portal2.png).

3.3) HTTPS:

This setting refers to the Tomcat Web Connector. If you are using a reverse proxy on the same server (localhost), a certificate is not necessary. We strongly advise against using encryption in this configuration.
If you are using Intrexx without a reverse proxy (IIS or NGINX), you should define a certificate here to be able to use HTTOS with the Embedded Tomcat.
The SSL/TLS (HTTPS) configuration of the upstream reverse proxy is always made in the respective system itself (IIS or NGINX) (s. portal3.png).
CategoryIIS / Tomcat
Found in version:
  • unspecific