Intrexx on Microsoft Windows 2016 Server


1. IIS configuration

In order to run Intrexx on a Windows Server 2016, it is first necessary to install the Internet Information Server (IIS). The Tomcat Standalone Server, which is included with Intrexx can be used instead. This does not need to be configured but must simply be selected during the installation of Intrexx.

Open the server manager and click on the "Manage" menu item. From there, select "Add Roles and Features".

In the following dialog, select "Role-based or feature-based installation".

Select your server.

Select the role "Web Server (IIS)".

As an option, you can now install the IIS Administration Console (recommended).

Confirm the following dialog by clicking on Next, without selecting any features.

Confirm this dialog with Next.

Select the Role services as shown in the image.

Complete the installation.

2. Settings for file uploads and downloads

The default settings in IIS only allow for smaller files to be uploaded and downloaded in the Web browser. Therefore, the limit properties must be adjusted according to your requirements (size shown in bytes). To do that, open "Computer Management", followed by "Services and Applications" and select "Internet Information Services (IIS) Manager". There, open "ASP" and edit the "Limits Properties" Upload (Maximum Requesting Entity Body Limit) and Download (Response Buffering Limit).

These limit properties are inherited by all existing websites. But it is also possible to set individual limits for each website. The changes will take effect without the need to restart the "WWW Publishing" service. In addition to these settings, which will make file transfers of up to about 60 Mb possible, transfers of even larger files can be permitted with a further adjustment by specifying the corresponding byte value in the "web.config" file of the Intrexx portal. To do this, open the "web.config" file, which can be found in the portal directory /external/htmlroot/ in a text editor. Before editing the field, you should create a backup copy. Add the highlighted area (see below), and edit the byte value as required. The changes will take effect immediately after the file has been saved.
<?xml version="1.0" encoding="UTF-8"?>
   <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="3650.00:00:00" />
  <httpErrors errorMode="Detailed" />
    <requestLimits maxAllowedContentLength="2147483646" />

3. Opening the portal in the browser

To be able to access the portal at "http://servername" without specifying the virtual directory, the directory of the default web site must point to portal directory external/htmlroot.

This can be carried out in the settings of the settings of the Default Web Site.

Please note that these modifications should only be performed after discussing them with your system administrator to avoid system failures in the IT environment.

Additionally, the "Enable Parent Paths" option must be set to "True" in the ASP properties of the Default Web Site. If the portal is to be accessible with integrated Windows authentication, "Windows authentication" must be enabled and "Anonymous authentication" must be disabled in the settings for the Default Web Site. Depending on the IT environment, these options may be the default settings.

4. Authorization structure

Should an HTTP 500.19 error occur when accessing the portal, please ensure that the necessary permissions have been granted for the following folders: In this case, the following groups and users must be given permissions here:

5. Configuring IIS for using HTTPS

Create and bind a new certificate

In the IIS, select the server and then select "Server Certificates".

Here, click on "Create Self-Signed Certificate".

Enter the friendly name and then click on "OK".

Create binding

Under "Default Web Site", create a new binding.

Assign the certificate by clicking on "Add". Select "https" as the type. Enter the other details accordingly and select the certificate by clicking on "Select". The binding is created when you click on "OK". If you want to completely remove the option of connecting via normal HTTP, you need to remove it here.

Base-URL for the Intrexx portal

The Base-URL for the portal needs to be adjusted in the Portal properties in the portal manager. If you are using an official certificate, this must also be stored in the Manager's Certificate Store, as this is required for providing web services, for example.