Recommended Configurations

This chapter contains detailed descriptions of recommended system configurations for the Content Engine, CUE and an SSE Proxy, which is required to forward Server-Sent Events from the Content Engine to CUE clients. These components can be configured to work together in a variety of ways to meet different requirements, and typical system configurations will often also involve the configuration and use of other components such as web servers, load balancers and so on. This chapter only describes two possible configurations:

• A minimal HTTP-based development/test configuration, where all components are installed on the same host

• A more robust HTTPS-based production configuration where the CUE editor is installed on a different host from the Content Engine and the SSE Proxy.

These descriptions should provide a basis for understanding how the components communicate, so that you can make any adjustments needed to meet your specific requirements.

All configurations involve at least the following tasks:

• Installing an SSE Proxy (see the SSE Proxy documentation for details).

• Configuring your Content Engine installation's Tomcat server to direct SSE messages to the SSE Proxy.

• Configuring the SSE Proxy to accept messages from the Content Engine, and forward them to CUE.

• Configuring CUE to connect to the Content Engine.

If your installation includes more than one Content Engine web service host, with a load balancer distributing requests between them, then you must ensure that both CUE and its SSE proxy use sticky sessions and connect to the same back end.