Answers to: Using Websockets in axonIvy 7.4

Comment by Reguel Wermelinger on Reguel Wermelinger's answer

Reguel Wermelinger — Tue, 12 May 2020 04:21:45 -0400

Both mentioned alternatives should work (apache httpd + mod proxy) or nginx. While nginx seems to be more modern and is definitvely the best tested approach from our side.

However, we have a demo for both integrations: https://github.com/ivy-samples/docker-samples

Even so, the demos to not explicitly focus on websocket/HTTP upgrade scenarios.

Comment by timorupp on Reguel Wermelinger's answer

timorupp — Tue, 12 May 2020 04:06:28 -0400

Hi Reguel You say that AJP will not work. What's the recommended way of integration with a front-end web server like Apache httpd or nginx? Would reverse proxy work?

Answer by Reguel Wermelinger

Reguel Wermelinger — Thu, 10 Oct 2019 08:19:49 -0400

The easiest way to provide async communication in Axon.ivy is currently a REST service. See the ConnectivityDemos for some examples:

REST has been a good choice in the past for many customers as it does not require 'upgrade' request capabilities. Which is often a problem in real world installations where request reaches the client over front-end websevers that could apply request restrictions. Not to mention that the standard IIS integration approach, documented in the Axon.ivyEngine docs, can not use websockets. This restriction comes from the AJP protocol used between IIS and ivy.

However, if you know your target installation environment well you can activate any tomcat compatible websocket servlet. To do so the servlet must be deployed registered in a web-fragemnt.jar. For an example download the 6.3 engine and examine the portal-chat-endpoint.jar within ivy/webapps/WEB-INF/lib. Actually, we had websocket endpoints registered in there (based on PrimePush + Atmosphere). But, experience in many customer environments taught us that, for a generic platform, it is better to have an approach that works in any environment. So push servlets turned out to be a bad option.