Frontend Webserver (Reverse Proxy/Load Balancer) einrichten

After upgrading to Intrexx Silent TrackIntrexx - Set up front-end web server (reverse proxy/load balancer)

This section provides information about how you need to configure the portal properties in Intrexx so that your portal can be opened in a browser. In particular, this involves the connection between the "Embedded Tomcat" and the front-end web server you are using (reverse proxy). The configuration settings described in this chapter need to be made after both a new installation and an upgrade.

Internet Information Service (Windows)

Upgrade from Intrexx 19.03 to Intrexx Silent Track

Since the launch of Intrexx 21.03, the dialog for setting up the front-end web server has been different. The information stored in Intrexx 19.03 is automatically transferred during an upgrade.

19.03

Silent Track

Step-by-step guide

To configure the front-end web server in Intrexx Silent Track , proceed as follows:

  1. Start the Portal Manager as the Windows administrator.

  2. Log in to your portal.

  3. Open the portal properties ("Portal > Portal properties").

    This takes you to the "Edit portal" page.

  4. Click on the menu item "Frontend web server (reverse proxy / load balancer)".

    Name

    Description
    Type Select "Internet Information Service (IIS)" here.
    IIS website

    Select the website that you added to IIS for your portal earlier. Do not use the ""Default Web Site"" from IIS. Do not use the ""Default Web Site"" from IIS.
    Embedded Tomcat Port

    The port that you used in the previous version of Intrexx will be shown here. You can leave this port as it is.

    Please note Port 1337 is preset here for a new installation.
    Base URL of the portal The base URL needs to be entered here.
    The first part consists of the protocol. You have configured an encrypted connection between the Intrexx portal server and the browser. The second part is made up of the hostname that you defined in IIS. Please make sure that this ends with a slash (/). It is essential that this is correct so that your portal can be accessed in the browser.

  5. Click on "OK".
    You have configured the front-end web server (IIS) in Intrexx Silent Track .

    You may need to restart the Intrexx portal services after making your changes. (Start the Windows Services app to restart the Intrexx Portal service there.) Open the connected portal in the browser to check that the portal properties have been configured correctly and that the upgrade has been carried out successfully.

    Note You should generally check some functions after upgrading to Intrexx Silent Track . These include the correct appearance of portlets, for example.

NGINX (Linux)

Upgrade from Intrexx 19.03 to Intrexx Silent Track

Since the launch of Intrexx 21.03, the dialog for setting up the front-end web server has been different. The information stored in Intrexx 19.03 is automatically transferred during an upgrade.

19.03

Silent Track

Step-by-step guide

To configure the front-end web server in Intrexx Silent Track , proceed as follows:

  1. Start the Portal Manager as the Windows administrator.

  2. Log in to your portal.

  3. Open the portal properties ("Portal > Portal properties").

    This takes you to the "Edit portal" page.

  4. Click on the menu item "Frontend web server (reverse proxy / load balancer)".

    Name

    Description
    Type Select "NGINX" here.
    NGINX virtual host "NGINX Virtual Host" refers to the Embedded Tomcat. NGINX connects to the Intrexx portal service via the virtual host. Usually "localhost" is to be entered here. (One exception to this is when NGINX is installed on a different server to Intrexx. In this case, the Intrexx server should be specified here.)
    NGINX configuration file

    You can generate the NGINX configuration file with Intrexx.

    Enter the path to the directory in which you want to create the NGINX configuration file.
    Example: "/myfolder/portal.example.com.conf"
    Then copy or link the NGINX configuration file to the desired location below "/etc/nginx".
    Example: "/etc/nginx/sites-available/ portal.example.com.conf"
    Embedded Tomcat Port

    The port that you used in the previous version of Intrexx will be shown here. You can leave this port as it is.

    Note For a new installation, port 1337 is preset here.
    Base URL of the portal The base URL must be stored here.
    The first part refers to the protocol. You have configured an encrypted connection between the Intrexx portal server and the browser. The second part is made up of the hostname that you defined in the NGINX configuration file. Please make sure that this ends with a slash (/). It is essential that this is correct so that your portal can be accessed in the browser.

  5. Click on "OK".

    You have configured the front-end web server (NGINX) in Intrexx Silent Track .

    You may need to restart the Intrexx portal services after making your changes.

    Open the respective portal in the browser to test whether the portal properties have been configured correctly and the upgrade was successful.

    Note You should generally check some functions after upgrading to Intrexx Silent Track . These include the correct appearance of portlets, for example.

No front-end web server

Normally, a reverse proxy is used together with Intrexx. In most cases, these are IIS from Microsoft or NGINX.
Using a reverse proxy is recommended for numerous reasons. In particular, an existing Windows authentication can be used for portal access via a reverse proxy.
In principle, a portal can be accessed without a reverse proxy, however, this is only recommended for test and development portals.

Step-by-step guide

To not use a front-end web server for your portal, please proceed as follows:

  1. Start the Portal Manager as the Windows administrator.

  2. Log in to your portal.

  3. Open the portal properties ("Portal > Portal properties").

    This takes you to the "Edit portal" page.

  4. Click on the menu item "Frontend web server (reverse proxy / load balancer)".

    Name

    Description
    Type Select "No front-end web server" here.
    Embedded Tomcat Port Enter the port used to reach the embedded Tomcat. This is usually port 1337.
    Encryption (HTTPS) Activate this checkbox if you want to establish an encrypted connection between Intrexx or Embedded Tomcat and the browser.
    Selfsigned certificate for "localhost" Select this option if the communication between the Embedded Tomcat and the browser is to be encrypted with a self-signed certificate (for test or development portals).
    In this case, Intrexx automatically generates a self-signed certificate and uses it for the encrypted connection.
    Certificate file You can search for the certificate file using the icon.

    Certificate type

    Select the type of certificate store (keystore) that the certificate is saved in.

    Keystore password

    Enter the password for the keystore that the certificate is saved in.

    Certificate key password

    Enter the password for the certificate (certificate file).

    Note The keystore password and certificate key password are often identical.

    Base URL of the portal

    The base URL must be stored here.
    The first part refers to the protocol. You have configured an encrypted connection between the Intrexx portal server and the browser. The second part is made up of the hostname that you defined in the NGINX configuration file. Please make sure that this ends with a slash (/). It is essential that this is correct so that your portal can be accessed in the browser.

  5. Click on "OK".

    You have now configured your portal without a front-end web server (reverse proxy).

Manual setup

Use the "Manual setup" type if you want to set up the communication between the Embedded Tomcat and the browser manually.
This means that you do not need the dialog-supported setup that is available for the "Internet Information Service (IIS)", "NGINX" and "No front-end web server" types.

Further technical specifications for the manual setup can be found in the following files. This are included with Intrexx.

  • <portal directory>\tomcat\conf\server-https-default.xml

  • <portal directory>\tomcat\conf\server-http-default.xml

  • <portal directory>\external\htmlroot\WEB-INF\web.xml

  • <intrexx installation directory>\samples\web-tls-configuration\nginx\portal-internet.conf

  • <intrexx installation directory>\samples\web-tls-configuration\nginx\portal-remote.conf

  • <intrexx installation directory>\samples\web-tls-configuration\nginx\portal-intranet.conf

Please contact Intrexx Support Center if you require further information.

Name

Description
Base URL of the portal The base URL must be stored here.
The first part refers to the protocol. You have configured an encrypted connection between the Intrexx portal server and the browser. The second part is made up of the hostname that you defined in the NGINX configuration file. Please make sure that this ends with a slash (/). It is essential that this is correct so that your portal can be accessed in the browser.