Recommendations for Using Integration Server with Docker

If you opt to run Integration Server in a Docker container, Software AG recommends the following:

Create a Docker image for an installed, fully configured on-premise Integration Server. Make sure the server configuration is complete before creating the image.

Consider a Docker image of Integration Server to be immutable. Software AG does not recommend making configuration or content changes on an Integration Server running in Docker container. Instead, make any changes on the on-premise Integration Server, recreate the Docker image, load or push the Docker image to the Docker repository, and then start a Docker container for the image.

Note: You can change some server configuration for an Integration Server that runs in a Docker container through the use of configuration variables properties template which is available with Microservices Container or an Integration Server with additional licensing. You can also make more packages available for use with an Integration Server that runs in a Docker container by using the EXTERNALIZE_PACKAGES ENV variable when starting the Docker container. The configuration variables properties templates and/or the EXTERNALIZE_PACKAGES ENV variable provide ways to change e configuration and content of the server without rebuilding the Docker image.

If you intend to run a Docker image created for Integration Server in Integration Cloud, Software AG strongly recommends that you enable and configure CSRF guard in the Integration Server instance for which you are creating a Docker image. Enabling the CSRF guard feature prevents Cross-Site Forgery Request (CSRF) attacks through the Integration Server Administrator URLs. Enable and configure CSRF guard on the Integration Server instance before creating a Docker image for the instance. For information about enabling and configuring CSRF guard, see Securing Integration Server with CSRF Guard.