All Spring-Boot applications except for the cae-preview-app , the cae-live-app and the studio-server-app are being deployed without a servlet context. The cae-preview-app and the cae-live-app are being deployed with /blueprint and the studio-server-app with /api .

All Spring-Boot applications except for the cae-preview-app , the cae-live-app serve their Spring-Boot management interface without a servlet context. The cae-preview-app and the cae-live-app have their management interface at /blueprint/servlet/actuator . Please make sure, that if you activate the actuators in the CAEs, that you restrict the access to them in your reverse proxy.

All Spring-Boot applications use the following ports if present:

For development in the workspace using the spring-boot-maven-plugin , the ports are being set to unique ports by activation of the *local Spring-Boot profiles.

For development against a remote system, the docker-compose setup forwards the internal ports to the same unique development ports.

In the deployment archive all ports are being set to the unique port schema as well.

To prevent misconfiguration all Spring-Boot applications do not set any development endpoint properties using localhost values.