lector) All other ports should not be accessible to the world. For your Apache Unomi client applications (such as the Jahia CMS), you will need to make the following ports accessible : The Apache Unomi Context Server administration REST API, so it is highly recommended that you design your client applications to use the HTTPS port for accessing the REST API. The user accounts to access the REST API are Updating applications consuming Unomi - Migrating your existing data 7.3. UPDATING APPLICATIONS CONSUMING UNOMI Since Apache Unomi is an engine, you’ve probably built multiple applications consuming

. . . . . . . . . 252 This part of the documentation covers support for Servlet-stack web applications built on the Servlet API and deployed to Servlet containers. Individual chapters include Spring Spring MVC, View Technologies, CORS Support, and WebSocket Support. For reactive-stack web applications, see Web on Reactive Stack. 1 Chapter 1. Spring Web MVC Spring Web MVC is the original web framework the ServletContext such that applications can use static methods on RequestContextUtils to look up the WebApplicationContext if they need access to it. For many applications, having a single WebApplicationContext

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve should feel confident with the topics exposed in this document before starting to code your real applications! For those who need further documentation on Wicket, there are many good books available for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve should feel confident with the topics exposed in this document before starting to code your real applications! For those who need further documentation on Wicket, there are many good books available for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve should feel confident with the topics exposed in this document before starting to code your real applications! For those who need further documentation on Wicket, there are many good books available for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Configuration of Wicket applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework and they continue to improve should feel confident with the topics exposed in this document before starting to code your real applications! For those who need further documentation on Wicket, there are many good books available for

. . . . . . . . . 176 This part of the documentation covers support for reactive-stack web applications built on a Reactive Streams API to run on non-blocking servers, such as Netty, Undertow, and framework, the reactive WebClient, support for testing, and reactive libraries. For Servlet-stack web applications, see Web on Servlet Stack. 1 Chapter 1. Spring WebFlux The original web framework included spring- webflux) and co-exist side by side in the Spring Framework. Each module is optional. Applications can use one or the other module or, in some cases, both — for example, Spring MVC controllers

llector All other ports should not be accessible to the world. For your Apache Unomi client applications (such as the Jahia CMS), you will need to make the following ports accessible : 8181 (Context Context Server administration REST API, so it is highly recommended that you design your client applications to use the HTTPS port for accessing the REST API. The user accounts to access the REST API are represented in Unomi by a simple string identifier and usually represents an application or set of applications from which Unomi gathers data, depending on the desired analysis granularity. In the context

network bandwidth not the latency. This typically allows you to create much higher performance applications. Messaging systems decouple the senders of messages from the consumers of messages. The senders which is transitory and doesn’t need to survive a restart. 3.6. Messaging APIs How do client applications interact with messaging systems in order to send and consume messages? Several messaging systems example shows how to configure an Apache ActiveMQ Artemis broker to have web browsers and Java applications exchanges messages. 7.11. Flow Control STOMP clients can use the consumer-window-size header

network bandwidth not the latency. This typically allows you to create much higher performance applications. Messaging systems decouple the senders of messages from the consumers of messages. The senders which is transitory and doesn’t need to survive a restart. 3.6. Messaging APIs How do client applications interact with messaging systems in order to send and consume messages? Several messaging systems example shows how to configure an Apache ActiveMQ Artemis broker to have web browsers and Java applications exchanges messages. 7.12. Flow Control STOMP clients can use the consumer-window-size header