April 21, 2026

Proactively Squeezing More Performance Out of TeamSite

At Klish Group, we are constantly looking for ways to make our clients’ OpenText TeamSite environments faster, more responsive, and more efficient. One of the highest-leverage optimizations we have rolled out recently is upgrading the Apache HTTP Server that handles all of the OpenText Web (TeamSite) requests from HTTP/1.1 to HTTP/2.

The result: a 30-50% improvement in page load performance for the TeamSite authoring experience, with no application-level changes required.

Why HTTP/2 Is So Much Faster

The TeamSite UI loads dozens — often hundreds — of individual assets per page: JavaScript bundles, CSS, icons, fonts, XHR calls to the WildFly back end, and DCR/template previews. Under HTTP/1.1, the browser opens a small number of TCP connections and sends requests one after another on each one. If a single asset is slow, everything queued behind it waits. Browsers work around this by opening more parallel connections, but each new connection carries its own TCP and TLS handshake cost.

HTTP/2 solves this with multiplexing. A single connection carries many requests and responses at the same time, interleaved as independent streams. Combined with header compression (HPACK) and smarter prioritization, that means:

  • No head-of-line blocking at the HTTP layer
  • One TLS handshake instead of many
  • Dramatically less overhead on every request
  • Better use of high-latency links (VPN, remote authors, branch offices)

For a request-heavy application like TeamSite, the cumulative savings are exactly where that 30-50% improvement comes from.

How the Request Flow Changes

HTTP/1.1 vs HTTP/2 request timeline comparison Side-by-side comparison showing HTTP/1.1 sending requests sequentially one at a time, while HTTP/2 multiplexes all requests simultaneously over a single connection. HTTP/1.1 Sequential requests Browser Server GET app.js Response GET style.css Response GET /api/data Response GET logo.png Response Slow HTTP/2 Multiplexed requests Browser Server app.js style.css /api/data logo.png All responses multiplexed Fast Head-of-line blocking Single connection, all streams
HTTP/1.1 vs HTTP/2 request timeline comparison Stacked vertical comparison: HTTP/1.1 sends each request one at a time, while HTTP/2 multiplexes all requests over a single connection. HTTP/1.1 Sequential requests Browser Server GET app.js Response GET style.css Response GET /api/data Response GET logo.png Head-of-line blocking HTTP/2 Multiplexed requests Browser Server app.js style.css /api/data logo.png All responses interleaved Single connection, all streams

Upgrading Apache in Front of WildFly

TeamSite installs an Apache HTTP Server to proxy user requests to the application server. Enabling HTTP/2 happens entirely at the Apache layer — WildFly Application Server and TeamSite itself are unchanged. The browser speaks HTTP/2 to Apache, and Apache continues to speak HTTP/1.1 to WildFly on the back end.

A few prerequisites apply to every platform:

  • Apache version 2.4.17+ (HTTP/2 Support was introduced in 2.4.17)
  • The mod_http2 module, compiled against the Apache build
  • TLS enabled (browsers only negotiate HTTP/2 over HTTPS)

Because the Apache build shipped with all currently shipping TeamSite installations do not include mod_http2, the upgrade generally requires a pre-compiled HTTP/2-enabled Apache package that matches your OS, architecture, and OpenText-supported version. More on that below.

Configuring HTTP/2 on Linux

Add additional shared libraries to the TeamSite/iw-webd/lib directory, with two of them being symbolic links:

lrwxrwxrwx. 1 root root      21 Mar 10 16:40 libnghttp2.so -> libnghttp2.so.14.25.0
lrwxrwxrwx. 1 root root      21 Mar 10 16:40 libnghttp2.so.14 -> libnghttp2.so.14.25.0
-rwxr-xr-x. 1 root root  463043 Mar 10 16:40 libnghttp2.so.14.25.0
-rwxr-xr-x. 1 root root  737261 Mar 10 17:31 libssl_iw.so.3
-rwxr-xr-x. 1 root root 4772373 Mar 10 17:31 libcrypto_iw.so.3

To create the symbolic links, do the following after copying libnghttp2.so.14.25.0:

ln -s libnghttp2.so.14.25.0 libnghttp2.so
ln -s libnghttp2.so.14.25.0 libnghttp2.so.14

Add the HTTP2 Apache module mod_http2.so to the TeamSite/iw-webd/modules directory.

TeamSite iwwebd.conf.template update

Update the TeamSite/iw-webd/conf/iwwebd.conf.template with the following additions:

  1. Add the HTTP2 module to the module listing for UNIX: 
     <IfDefine UNIX>
     ...
        
     LoadModule http2_module modules/mod_http2.so
 </IfDefine>
  2. Add the Protocols configuration parameter inside the HTTPS VirtualHost entry: 
     ##
 ## SSL Virtual Host Context
 ##

 <VirtualHost *:__IWWEBD_HTTPS_PORT__>

 Protocols h2 http/1.1

Configuring HTTP/2 on Windows

Add the nghttp2.dll file to the TeamSite\iw-webd\bin directory.

Add the HTTP2 Apache module mod_http2.so to the TeamSite\iw-webd\modules directory.

TeamSite iwwebd.conf.template update

Update the TeamSite/iw-webd/conf/iwwebd.conf.template with the following additions:

  1. Add the HTTP2 module to the module listing for non UNIX: 
     <IfDefine !UNIX>
     ...
        
     LoadModule http2_module modules/mod_http2.so
 </IfDefine>
  2. Add the Protocols configuration parameter inside the HTTPS VirtualHost entry: 
     ##
 ## SSL Virtual Host Context
 ##

 <VirtualHost *:__IWWEBD_HTTPS_PORT__>

 Protocols h2 http/1.1

Verifying HTTP/2 Is Active

Restart the TeamSite user interface components by running TeamSite/bin/iwreset -ui, then confirm the upgrade is working:

  1. In Chrome or Edge DevTools, open the Network tab, right-click a column header, and enable the Protocol column. Requests to the TeamSite host should show h2.

  2. From the command line:

     curl -I --http2 -k https://your-teamsite-host/

    The response should include HTTP/2 200.

  3. Check the Apache error log for any mod_http2 warnings on startup.

Get the Right Apache Build for Your Environment

The trickiest part of this upgrade is not the configuration — it is getting an Apache build that is HTTP/2-enabled, OpenText-supported, and compiled for your specific OS and architecture. OpenText provides pre-compiled HTTP/2-capable Apache modules for TeamSite customers, and Klish Group can deliver the correct build directly to you along with the configuration guidance above.

If you are running TeamSite and want to unlock a 30-50% performance boost without touching a single line of application code, reach out and we will match you with the right build for your environment.

Request the HTTP/2 Apache Build