close

Filter

loading table of contents...

Release Notes / Version 10.2104

Table Of Contents

Standardize Spring-Boot applications

To simplify future deployments and cluster deployment automation, the CoreMedia Spring-Boot applications have been standardized in regards to ports, servlet contexts and management interfaces. The changes include:

  • 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:

    • HTTP: 8080

    • JDWP: 5005

    • Management: 8081

    • CORBA: 8083

    • gRPC: 6565

    • Prometheus Metrics: 8199

  • 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.

(CMS-14968)

Search Results

Table Of Contents